Grrr... BSODs

Narj

Narj

Narj

Soldato
Joined
19 Feb 2010
Posts
13,254
Location
London
Hi all,

Since upgrading (fresh install) to Win10 I keep getting these occasional BSOD errors:

CLOCK_WATCHDOG_TIMEOUT

This only ever seems to happen on the desktop if I'm browsing or if the PC is left idle for a while - I can quite happily play games for hours on end and any sort of lockup is extremely rare (have never had this BSOD while gaming).

Initial googling suggests the CPU needing more volts for the overclock but surely this would mean I'd get more crashes in games? Also, when I built the PC and installed Win7, I hammered it with Prime, SuperPi, Furmark, Memtest and everything else I could throw at it for hours on end to verify a stable OC.

Specs in sig - any suggestions welcome. I'm wondering if it's something to do with voltage dropping too much at idle but I never used to get this in Win7. I've had USB devices causing odd problems like this before but it's happened a couple of times with them removed. I'll do the usual stuff when I have time with stress/mem tests. :(

Cheers!
 
Last edited:
Remove the overclock and see if the problems remain.

Might need more voltage, bluescreenview will be useful to get a better idea of what happens when th3 BSOD happens.
 
ThaReaperGuy said:
Remove the overclock and see if the problems remain.

Might need more voltage, bluescreenview will be useful to get a better idea of what happens when th3 BSOD happens.
Click to expand...

I was trying to figure out how I could analyse the memory dumps in a meaningful way to see if it pointed to a specific driver - I've saved them. Is that tool adware/malware free? Thanks!

I just saw in another thread someone else mentioned their 2500K needed more voltage after 5 years... :)
 
Never used it myself but a fair few have on here when figuring out issues, so you'll be OK to download.

And indeed, more volts may help as CPU's degrade. :)
 
Upped my offset one notch to +0.05v I think it was, ran PRIME all night and no problems. Fingers crossed! I've left it idle so will see if it's crashed or not when I get home.
 
Narj said:
Upped my offset one notch to +0.05v I think it was, ran PRIME all night and no problems. Fingers crossed! I've left it idle so will see if it's crashed or not when I get home.
Click to expand...

Good news so far, if it does BSOD again, try another bump up, it won't affect your temps if at all but does help ensure it's stable.
 
Just thought I'd post here to say that I've had no issues since upping the voltage a notch. Fingers crossed I haven't just jinxed it!

Seems the idea that CPUs degrade and need a little extra as they age is right! :)
 
I've been getting the same problem on Windows 10 since upgrading to a 1070. I have now gone back to Windows 7 as I never really liked Windows 10
 
Narj said:
Seems the idea that CPUs degrade and need a little extra as they age is right! :)
Click to expand...
Unless you're running at voltages exceeding the CPU manufacturer's recommended limits, no, it isn't. It is fairly common for a change of OS to highlight instabilities in an overclock though.

A CPU running at stock speed and voltage will always have plenty of headroom to ensure stability under all circumstances. Most overclockers fail to factor in the same degree of headroom.
 
You must log in or register to reply here.
Back
Top Bottom