[SOLVED] CLOCK_WATCHDOG_TIMEOUT Blue when playing certain games

Mrod09

Commendable
Jun 26, 2016
2
0
1,520
I've had this problem from quite some time here (about a couple of months). As the title says I get this only when I play certain games (So far it's only been Batman Arkham Origins and more recently The Witcher 3). It happens a few short minute after I load in and can start walking around. I know there are a lot of threads on this issue though I have not found one that has solved my problem, so any help would be much appreciated. I have update my BIOS to the most recent version from Asus's website with no changes. I also ran Driver verify with all test except for I think it was low resource usage, and got a different BSOD which was PAGE_FAULT_IN_NONPAGED_AREA which was (according to Blue Screen Viewer and Who Crashed) probably caused by npfs.sys. While the CLOCK_WATCHDOG_TIMEOUT was caused by ntkrnlmp.exe or ntoskrnl.exe. I'll post my most recent crash report here and I'll also include the crash I got after running driver verifier here

My specs are:

Motherboard: Asus Z 170a
CPU: Intel i7 6700K @ 4.00Ghz (not overclocked to my knowledge though my motherboard may have done some auto-overclocking)
GPU: Evga Nvidia Geforce GTX 970
RAM: G Skill Trident Z DDR4 2133 (16GB)
PowerSupply: Thermaltake 850W Tougherpower (Modular, not fully though)
OS: Windows 10 64bit
If I missed any specs or any additional details you may need please let me know, I'll do the best I can to answer any questions and provide any information you need

Thanks in advance for your help, I hope we can all figure out this problem together.


 
Solution
SOLUTION: What was happening, despite setting my BIOS to default settings, it was still overclocking, only by a little but enough to crash me. So what I had to do was go into the BIOS and manually alter some settings such as CPU turbo. While my baseclock (BLCK) was 100 (which is default and the target frequency should have been 4000Mhz or 4.00GHz) but with Turbo on it kicked it up to 4200Mhz (4.2Ghz) and caused instability and crashes. So good luck everybody I hope this can fix your problem because I'm 99% sure it fixed mine.

Mrod09

Commendable
Jun 26, 2016
2
0
1,520
SOLUTION: What was happening, despite setting my BIOS to default settings, it was still overclocking, only by a little but enough to crash me. So what I had to do was go into the BIOS and manually alter some settings such as CPU turbo. While my baseclock (BLCK) was 100 (which is default and the target frequency should have been 4000Mhz or 4.00GHz) but with Turbo on it kicked it up to 4200Mhz (4.2Ghz) and caused instability and crashes. So good luck everybody I hope this can fix your problem because I'm 99% sure it fixed mine.
 
Solution