CLOCK_WATCHDOG_TIMEOUT error

[Pantinate]

Hey guys,

I overclocked my cpu a while ago to 4.4 ghz. I did a myriad of tests, including about 18 hours of OCCT and Prime 95 separately, so I know the clock is stable. I got it to 4.4, and I stopped there because I didn't want my cpu going above about 60 degrees, which it was at 63 max on the synthetic tests.

However, back to the problem. I like to play TF2 a lot, which is not a cpu intensive game at all. My game started crashing very often recently though, and finally today I got a blue screen while playing it with the error "CLOCK_WATCHDOG_TIMEOUT". I looked this up and it said on the internet that this is typically a cpu oriented issue, and it has to due with overheating, which I am not getting at all on that game (50-55 max).

Just because I was concerned, I just down clocked it to my stable 4.2. Should I add more voltage to my 4.4 clock, to try and get it stable again?
Is there any other stuff I should do to make sure it doesn't happen again?

Thanks, and gratz if you made it through this whole essay haha

 

[alienware]

Prime 95 and others may be a way of thrashing the crap out of your CPU and VRM circuitry but they seldom indicate that everything you do with your PC will work properly with an overclock.

It's similar with GPUs and Furmark/Kombustor. I could run both on my broken 6970 yet I couldn't even browse the net with it.

 

[Pr3d4t0r]

prime or occt are good synthetic benches but for a game like bf3 even 48hr stable prime oc might not work, bf always pushed the cpu and gpu to its very limit.

give it an hour or so on bf3 and if it crashes, your oc isnt stable

 

[Pantinate]

I have played crisis 3, which I believe is more intensive then bf3, and it works fine. Think it is a software issue and not just the cpu? Also, can you explain exactly what the crash code means? If you know that stuff.

 

[Mark3Max]

I don't know if this will help you , but I found this on Microsoft's webpage.
http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx
I hope this link works ok for you.

 

[airdeano]

OP, just like you said, up the voltage to next segment and retest with gaming.
seems one of the cores stops (x101 BSOD) responding. I used to get secondary
core response and upped voltage and seemed to have cured the issue. but this
can also be other situations and just not hardware related.
one thing to check if it continues is to make some stock (no overclock) runs to
duplicate the issue.

 

[Pantinate]

K thanks. One other thing though. I have both my ocs (4.2 & 4.4) set to offset voltage, not a 24/7 clock. I am not at my compter at the moment, but i believe i have my 4.2 set to -.60 and my 4.4 set to -.50. I played some more tf2 on my 4.2 and it still crashed, didnt feel as often though (think it mght be a.software issue?) I Havent played crysis 3 in a while but i will try some campaign on it whwn i get home with the 4.4 set to +-0 offset (stock), and see how that does. I do remember crysis crashing a few times, but every early game still has bugs so i dont think that would be a hardware issue. Ill also try the stock runs and see how that fares.

EDIT: 4.4 is at -.05, not -.50

 

[hood6558]

I got the same error the other day overclocking my 3570k to 4.5 GHz after a BIOS update, had to bump vcore a bit (to 1.240). For some reason I can't get a stable OC above 4.3 using offset, so I'm setting it manually, and it's stable now. Only runs hot benching with IBT ~80c, Prime95 ~65c, normal high load like video transcoding it runs 45-50c. H100 is doing it's job okay, but 4 fans, 2 fans, low speed, high speed - makes very little difference, if any. 4.5 is high enough for me anyway, the machine rips through everything so fast I'm bored half the time!