Clock_watchdog_timeout BSOD with XMP enabled

PyroMSI

Reputable
May 8, 2017
23
0
4,520
Hello everyone,

I have just built a new computer with the following components:
CPU: i7 7700k
MOBO: MSI z270 gaming pro carbon
GPU: MSI GeForce gtx 1080 gaming Z
MEMORY: Corsair vengeance lpx 3600mhz 2x8GB DDR4
Power supply: Be quiet! 750w

I was playing ARK survival evolved when I suddenly got the Clock_watchdog_timeout bluescreen.
When I restarted the pc and the game it happened again.

A friend suggested to download BlueScreenView, and it told me the bluescreens were caused by hal.dll and ntoskrnl.exe

I already have all my drivers and bios up to date.
There arent any problems when playing games like Battlefield 1, H1Z1, Playerunknown Bsttlegrounds, Wildlands, GTA V. All on the highest settings. I have a 4k screen.

I also read that it might occur when you are overclocking. So I disabled my XMP profile for 3600mhz. After this it didnt happen again for 2 days.

Now im scared to put it on again but I want to use the 3600mhz ram i payd for.
Earlier that day I played ARK without having problems with XMP turned on though.

I also use my SSD and HDD with win 10 straight outta my old pc without reinstalling. It needed some repairing at first. Could this also be the problem?


The temps of the CPU were max 65 and the GPU max 40 so nothing strange.

What do you guys think, is it he XMP profile? I have no idea how to set clock timings and stuff manually. Or voltages. Or is ARK just bad optimalized.

GREETINGS,

MSI_Noob
 
Solution
That BSOD is symptom of an unstable system. I suggest you raise voltage or lower frequency, and test with prime95. Repeat until stable.
watchdog is a protection for the cpu that make it recover of errors, a timeout error is something bad. The most probably thing is that your windows sistem is playing bad whit the procesor and a sistem restore/ reinstall is the best thing. But can be something bad. Did you oc your cpu heavely whit crazy vcore? If the answer is yes welll your cpu is dyng some cpu cores/theards can start to fail, desactivate hyperthearding to better results and do some aida64 and Prime95 if fails again test disabling all cores less one and do the test. activate cores and when you identifique what core is failing desactivate it forever...........ok well thats the worst case the most probably thing is that windows is playing bad___________________ As a extra a new drive can cause that....