Clock_watchdog_timeout BSOD when XMP is active
Clock_watchdog_timeout BSOD when XMP is active
Hello everyone,
I recently assembled a new computer with these specifications:
Processor: i7 7700k
Motherboard: MSI z270 gaming pro carbon
Graphics Card: MSI GeForce gtx 1080 gaming Z
Memory: Corsair vengeance lpx 3600mhz 2x8GB DDR4
Power Supply: Be quiet! 750w
During gameplay of ARK survival evolved, I encountered a blue screen error labeled Clock_watchdog_timeout.
After restarting the PC, the issue recurred.
A friend recommended using BlueScreenView, which identified the problem as related to hal.dll and ntoskrnl.exe.
I’ve confirmed all my drivers and BIOS are up to date.
There are no issues with games like Battlefield 1, H1Z1, Playerunknown Bsttlegrounds, Wildlands, or GTA V when running at maximum settings. I also have a 4K display.
It seems the problem might appear during overclocking, so I disabled the XMP profile for 3600mhz. After that, it stopped happening for two days.
I’m now hesitant to restart it but want to use the 3600mhz RAM I purchased.
Earlier, when XMP was enabled, I didn’t face any problems.
My SSD and HDD are running smoothly on Windows 10 without needing reinstallation. They required some initial repairs.
Could this be connected to the XMP setting? I’m unsure how to adjust clock timings or voltages manually. Or is ARK just not optimized well?
Looking forward to your thoughts,
MSI_Noob
watchdog is a safeguard for the cpu to help recover from errors. A timeout error indicates something serious. The likely cause is your windows system acting poorly with the processor, and a system restore or reinstall might be the best solution. However, it could also point to hardware issues. Did you overwork your cpu with intense tasks? If yes, your cpu may be experiencing stress and some cores might fail. Disable hyperthreading for better performance and run aida64 and Prime95 if problems persist. Test disabling all cores except one, then reactivate them once the faulty core is identified. In the worst scenario, it could be that windows itself is malfunctioning. As an additional note, a new drive might also be responsible.
The BSOD indicates an unstable system. I recommend increasing the voltage or reducing the frequency, then run prime95 to verify stability. Keep repeating until it works consistently.