Windows 10: CLOCK_WATCHDOG_TIMEOUT BSOD While Playing Hardware Intensive Games

Hey everybody,

I've been struggling with this issue for a while, I thought I resolved it a few months ago but it has come back and I'm out of ideas.

Ever since upgrading to Win10 at the start of last year I've started getting Clock Watchdog Timeout BSODs. After searching everywhere for a solution I gave up and went back to Win7 which continues to work without any problems. After a few months I discovered my Ethernet card was faulty and I replaced it, I was experiencing a couple of minor stability issues with my computer at the time but this resolved everything. So I thought I'd give Win10 another go on a new SSD. It worked perfectly with all my games working fine except Star Citizen which would get Clock Watchdog Timeouts after about 30min. This was fine by me as I could run it without BSODing on my Win7 HDD. Things have been running like this up until a couple of months ago when I installed BF1 (and it's summer here now so the heat might have something to do with it too). BF1 will now BSOD after about 30min as well as COH 2. The computer will also become more unstable on the boot after one of these BSODs with a BSOD while the computer is idling likely to occur within about an hour. I moved BF1 to the Win7 HDD and it runs mostly fine there, but if I change HDDs after a Win10 BSOD BF1 will cause a BSOD on Win7 but will run fine after that.

I've tried removing my old card reader and my old old sound card but it made no difference to the problem. I've also tried playing with drivers and keeping them as updated as possible. My computer is overclocked and has been running unchanged and stable for the last 5 years. I feel this has probably got something to do with the problem but I'm reluctant to return to stock speeds as this overclock is keeping the computer running the latest titles and without it I'd just be buying a new computer anyway. So if the overclock is likely to be the problem, any suggestions that could stabilise this overclock would be most appreciated.

Thank you for your time and I look forward to any suggestions that could fix this long lasting problem of mine.

Cheers,
Jason

:)

 

Computer BSODs

I have had BSODs with clock_watchdog_timeout, or just computer freezing while playing games on browser that used Macromedia Flash on a totally fresh start after a full system format. I got clock_watchdog_timeout error before the format, built a new rig using
old Hard Drives, and GPU from previous PC.

I tried uninstalling Flash, uninstalling browser(Chrome), uninstalled audio drivers. Reinstalled Chrome, tried again. And same hard freeze/clock_watchdog_timeout every time.

Minidump always identifies a different program as the fault. One time it was Chrome, one time it was Steam, and so on. Ran driver verifier, ran multiple Flash games and after a while driver verifier produced a BSOD. Speccy64 was also running during this,
and the dump identifies it as the program. The first link has this dump, and another dump that was from the time before Speccy64 was installed.

So far, Macromedia Flash is the only reliable freeze/bsod causer besides Speccy. I've played World of Tanks on max settings, and other intensive video games, and not a single freeze or bsod during them. Nothing came up during memtest. Prime 95, less than
2 minutes of running and bsod. Noted nothing happening on worker8, and prime95 simply said error for it. Checked CPU and Motherboard, no bent pins. Cpu had plenty of thermal paste, even got it on my fingers taking it off.

[edit]Odd, the process of taking off the CPU to inspect it, then putting it back on seems to have fixed the issue for prime95. Worker8 is now working and prime95 did not bsod the computer when running it for 10 minutes. However turning on driver verifier
then rebooting produced WHEA_UNCORRECTABLE_ERROR (124). Starting up after that, no error. Second link is the minidump for this.

Tried running multiple macromedia flash games during driver verification, computer bsodded just when I started Speccy64. 3rd link is memory and minidump for this instance, would seem to link Speccy64 as a reliable BSOD causer. Uninstalled it and trying to
BSOD with just Macromedia Flash right now. So far, games that previously reliably produced a BSOD before cpu inspection are not doing so, but will have to test for this longer given previously they sometimes ran without issue.

CPU: AMD FX-8350 4.0 GHz 8-core

GPU: Sapphire Radeon R9 285 O.C. 2 Gt GDDR5

Memory: Four Corsair Vengeance 4 GB PC3-12800, 1600MHz, 240 DIMM 4 GB modules

Motherboard: Asus M5A99X EVO R2.0 990X

PSU: Corsair CX750W V2 CX-series 750 W

Windows Hard Drive: Samsung 850 EVO SSD 120 Gt 2,5" SATA3

https://1drv.ms/u/s!Ag_oGXM7aD7ngQfRFRSpxeDyNVnY

https://1drv.ms/u/s!Ag_oGXM7aD7ngQhOBKx_xYLli2Bf

https://1drv.ms/u/s!Ag_oGXM7aD7ngQkktIknys9xEcRO

 

Heating Up while Playing Game & using Application & Battery Draining very fast

If you are play a game like that online, it is using a lot of data connection and thus the radio will get warm (maybe even hot depending on intensity of use).

I'm assuming you do not get that issue when playing a game loaded on your device. However, if you do play a memory intensive game loaded on your device, it could get warm but it is not an issue with the device. Not to worry!

 

Please remove all overclocking for the CPU/GPU/RAM!

 

Never mind, a slight increase to the vcore solved all my problems.

Thanks anyway,
Jason