clock watchdog timeout crash? any ideas?

[DarrenTheBstard]

just wondering if anyone could help me out with this problem ive had for over a year now, i tend to mostly get it on battlefield ie. the new battlefield 4 and on the 3rd one but sometimes get it in global offensive aswell

my specs:Gigabyte G1.Sniper 3 Motherboard
Intel Core i7 3770K 4-Core Ivy Bridge CPU @ 4.5GHz
Nvidia GeForce GTX 690 4GB Graphics Card
16GB Corsair Vengeance 1600MHz Gaming RAM
2TB (2000GB) Sata III Hard Drive
Corsair 1200W professional series
Zalman CNPS11X Extreme CPU Cooler
currently using nvidia driver:331.65

the computer will seem to hardcrash, buzz from the audio and reset itself after a while, ive checked the temperatures and they seem fine

whocrashed shows this:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Sun 03/11/2013 18:39:44 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110313-18937-01.dmp
This was probably caused by the following module: Unknown (0xFFFFF800CC564CA0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD000201C2180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT



On Sun 03/11/2013 18:39:44 GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: Unknown (0xFFFFF800CC564CA0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD000201C2180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
A third party driver was identified as the probable root cause of this system error.
Google query: CLOCK_WATCHDOG_TIMEOUT



On Sun 03/11/2013 15:03:18 GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\110313-24625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x101 (0x30, 0x0, 0xFFFFD000201C2180, 0x2)
Error: CLOCK_WATCHDOG_TIMEOUT
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a thermal issue.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.

i bought the pc from a shop and they did the overclocking, do you guys think maybe the voltage needs tweaking on the OC or are some dodgy drivers sometimes to blame

[MasterMarci]

the same problem i have now did you find a solution ?

[Ecksehl]

I can confirm that

3) you have to disable the "Enhanced Intel SpeedStep Technology" thru BIOS
EXAMPLE : https://i.ytimg.com/vi/50qziHraZBs/maxresdefault.jpg

Was what fixed this for me, I also turned down the GFX settings in CS GO so I'm not sure exactly what helped more.

My specs are as follows:
i3790k
16GB RAM
asrock z97 killer fatal1ty mobo, ssd, main drive, media drive

[MasterMarci]

oh yeah thanks i fixed it with restetting my bios

[EL GORDO VALOR]

Any ideas on amd?