Best I can Answer Questions...
X64 bit operating system
original os was windows 7
around 4 to 5 years old
we have had to reinstall windows 7 1 time (I think it was this computer...)
AMD A6-3670 APU with Radeon(tm) HD Graphics 2.70ghz
Motherboard (no clue)
the cable came with the pc so I have no clue
System manufacturer is CyberPowerGaming pc
model # (hopefully this is it...) SC3000-217703-4
So I hope this means that you can help in some way and I would be very thankful if you would help.
It looks like you've been having the same problem intermittently since at least July of 2016 according to the dump files. Unfortunately, there's not enough information in a minidump to be able to determine the likely culprit for the bugcheck code you're getting. We would need at least a kernel dump to have any real chance. Does the file C:\Windows\MEMORY.DMP exist on your system drive with a recent timestamp? If so, please copy it to your Desktop, create a zip of the copy, and then make the zip available via a cloud drive or files sharing service if you'd like someone here to do a manual analysis.
There are some things in the MEMORY.DMP file that have me confused so I'll need to do some research to see if I can figure out what I'm seeing. In the meantime, if this is your motherboard's product support page and your computer is stable in the BIOS menus I'd recommend updating to the latest BIOS for your motherboard. I've seen CLOCK_WATCHDOG_TIMEOUT problems solved after a BIOS update on some system. I'd use the Instant Flash download which should have an image you'd load while in the BIOS menus.
Can you give us a bit of background on the system? Do you know if this has always been a problem? Was Windows 7 reinstalled previously to try and fix this problem?
I thinkthe first step is to update your graphics driver.
1: kd> !thread fffffa800a161060
THREAD fffffa800a161060 Cid 0304.0f34 Teb: 000007fffffde000 Win32Thread: fffff900c018bc10 RUNNING on processor 1
Owning Process fffffa800a283b00 Image: eso64.exe
Attached Process N/A Image: N/A
Wait Start TickCount 34028 Ticks: 461 (0:00:00:07.191)
Context Switch Count 159055 IdealProcessor: 3 LargeStack
Win32 Start Address 0x000000014066c26c
Stack Init fffff8800c197db0 Current fffff8800c197a20
Base fffff8800c198000 Limit fffff8800c18f000 Call 0000000000000000
Priority 10 BasePriority 10 PriorityDecrement 0 IoPriority 2 PagePriority 5
Child-SP RetAddr : Args to Child : Call Site
00000000`00000000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x0
//Empty registers and call stack, let's see if I can recreate the stack
1: kd> k= fffff880`0c1948f8 fffff880`11085ca9 ffff
# Child-SP RetAddr Call Site
00 fffff880`0c1948f8 fffff8a0`187c6ef0 atikmdag+0x33ca9
01 fffff880`0c1949e8 fffff800`0343723d 0xfffff8a0`187c6ef0
02 fffff880`0c1949f0 fffff880`11089c1a nt!ExFreePoolWithTag+0x22d
03 fffff880`0c194aa0 fffff880`117ecce4 atikmdag+0x37c1a
04 fffff880`0c194ad0 fffff880`118b8508 atikmdag+0x79ace4
05 fffff880`0c194b50 fffff880`11820f34 atikmdag+0x866508
06 fffff880`0c194b80 fffff880`117e8c3f atikmdag+0x7cef34
07 fffff880`0c194bb0 fffff880`1184034f atikmdag+0x796c3f
08 fffff880`0c194c40 fffff880`0c194d70 atikmdag+0x7ee34f
09 fffff880`0c194cc0 fffff880`0c194de0 0xfffff880`0c194d70
0a fffff880`0c194cc8 fffff880`11085ca9 0xfffff880`0c194de0
0b fffff880`0c194cd0 00000000`00000004 atikmdag+0x33ca9
0c fffff880`0c194dc0 fffff8a0`00023608 0x4
0d fffff880`0c194dc8 fffff8a0`00000004 0xfffff8a0`00023608
0e fffff880`0c194dd0 00000000`00000004 0xfffff8a0`00000004
0f fffff880`0c194dd8 00000000`00000000 0x4
//As good as it will get from my knowledge
//Lets see if we can see what the other cores were doing
00 fffff880`0b376ac0 fffff880`0b376ae0 0xfffff880`0b376ae0
01 fffff880`0b376ac8 00000000`08000000 0xfffff880`0b376ae0
02 fffff880`0b376ad0 fffff880`0b376ae0 0x8000000
03 fffff880`0b376ad8 fffff880`00e01593 0xfffff880`0b376ae0
04 fffff880`0b376ae0 fffff880`00e02ff4 amd_sata+0x1593
05 fffff880`0b376b10 fffff880`00e0c83e amd_sata+0x2ff4
06 fffff880`0b376b70 fffff880`010a11a7 amd_sata+0xc83e
07 fffff880`0b376bd0 fffff800`032195f3 storport!RaidpAdapterContinueScatterGather+0x157
08 fffff880`0b376c40 fffff880`010a0eab hal!HalBuildScatterGatherList+0x203
09 fffff880`0b376cb0 fffff880`010a0af7 storport!RaUnitStartIo+0x2bb
0a fffff880`0b376d30 fffff880`010a071d storport!RaUnitScsiIrp+0x397
0b fffff880`0b376df0 fffff880`01104a23 storport!RaDriverScsiIrp+0x5d
0c fffff880`0b376e30 fffff880`0196e445 amd_xata+0x1a23
0d fffff880`0b376e60 fffff880`0196e975 CLASSPNP!ServiceTransferRequest+0x355
0e fffff880`0b376f00 fffff880`00f0b0af CLASSPNP!ClassReadWrite+0xd5
0f fffff880`0b376f50 fffff880`00f202b3 partmgr!PmGlobalDispatch+0x9f
10 fffff880`0b376f80 fffff880`0191f2bf volmgr!VmReadWrite+0x243
11 fffff880`0b376fc0 fffff880`0191f53c fvevol!FveReadWrite+0x47
12 fffff880`0b377000 fffff880`018d30dd fvevol!FveFilterRundownReadWrite+0x1dc
13 fffff880`0b377060 00000000`00000000 rdyboost!SmdProcessReadWrite+0xca1
00 fffff880`0a57ef30 fffff880`0a57f520 0xfffff880`0a57f520
01 fffff880`0a57ef38 fffff880`0a57f148 0xfffff880`0a57f520
02 fffff880`0a57ef40 fffffa80`0e6cb060 0xfffff880`0a57f148
03 fffff880`0a57ef48 fffff800`03442180 0xfffffa80`0e6cb060
04 fffff880`0a57ef50 fffffa80`0e6cb120 nt!KiInitialPCR+0x180
05 fffff880`0a57ef58 00000000`00000000 0xfffffa80`0e6cb120
1: kd> lmvm atikmdag
Browse full module list
start end module name
fffff880`11052000 fffff880`11c9b000 atikmdag (no symbols)
Loaded symbol image file: atikmdag.sys
Image path: \SystemRoot\system32\DRIVERS\atikmdag.sys
Image name: atikmdag.sys
Browse all global symbols functions data
Timestamp: Tue Oct 8 06:51:03 2013 (52540DC7)
File version: 184.108.40.2061
Product version: 220.127.116.111
File flags: 8 (Mask 3F) Private
File OS: 40004 NT Win32
File type: 3.4 Driver
File date: 00000000.00000000
Information from resource tables:
CompanyName: Advanced Micro Devices, Inc.
ProductName: ATI Radeon Family
FileDescription: ATI Radeon Kernel Mode Driver
LegalCopyright: Copyright (C) 1998-2012 Advanced Micro Devices, Inc.
Well the callstacks aren't too helpful, lots of missing symbols.
From an educated guess...
Processor 0 was scheduling video driver work, and sent out an IPI.
Processor 1 was executing a lot of AMD display driver functions.
Processor 2 was doing some IO
Processor 3 doesn't have much, apart from intialising the processor control region.
At this point, given how old the AMD driver is, I'd recommend updating that first and seeing if it happens again.
So Cwsink that does look like my motherboard, however I can not update it through the link you gave (it would seem to be a problem with me being on windows 7 and not 8). I could try and download a new Windows 8 or 10, but I'll ask you all before that.
IDK much more about my pc past I have 2 of them, this one is 1 year older model than the other (gotten at the same time), I think it was this one about 3 years ago I had to reinstall Windows 7 (however it could be the other too... I'm not 100% sure). The only thing we have done with both Pcs was upgrade their Ram from 8gs to 12gs.
However Unless it did it by itself I have not updated this pc, But if you think I should try to download windows 8 or 10 then update I will otherwise idk what else I can tell you about this pc...
I can tell you about the other, however, but I don't think it'll be much help.
The confusing part about the dump file is the context for 3 of the 4 cores wasn't included in the bugcheck for some reason so I can't tell what exactly the corresponding threads were doing. As Jared wrote, we can look at the raw callstacks but I can't really tell where in the callstack processor 1 actually was at the time of the bugcheck. It does look like it had done GPU related work at some point but it also looks like it had performed some network related work at some point as well. Updating the GPU, network, and audio drivers could help. Together, the raw callstacks of the 3 cores show work having been done for those components at some point.
Do you know if your computer has a product support site? I can't seem to find anything based on the model number.
Have you tried updating the GPU drivers as suggested in the replies above? If so and you're still getting bugchecks please make the most recent MEMORY.DMP available for download so we can compare (MEMORY.DMP gets overwritten for each bugcheck.)
I'd also suggest uninstalling AMD Overdrive; at least while we're troubleshooting.