CLOCK_WATCHDOG_TIMEOUT bsod (now with :( in win8) - thoughts on how to investigate

[irh1]

Hi,

m/b: Rampage III Extreme
cpu: i7 990X
gpu: asus 590gtx
2 SSDs in Raid 0 (using 3Gb/s Intel controller)
watercooled, but not yet overclocked (except memory running at XMP)

Looking for suggestions as how to get to the bottom of this error. PC seems fine, but after a bit (hour+) you will get bsod. Things I have tried
- all drivers are upto date (the usual advice when you google this issue)
- ran memtest86, and passed
I don't believe it's an over heating issue, haven't seen a record cpu temp above the 30's, I was also able to complete 3dMark.

Keen to get the system stable before I up the gpu clocks

Are there other programs I should be trying?
Is there more information that would be useful to give?
I also suspect Win8 as pretty much all the hardware is Win7 era (but then everyone blames Microsoft) so was wondering if I should give up and use Win7?

 

[Columbo]

Is the motherbaord overclocking the CPU automatically via either a BIOS setting or onboard header?

I had a friend with this earlier in the year and it seemed to related to the CPU being clocked from 3.6ghz to 4.4ghz automatically via one of these 'auto tune' features.

I think the crux of it was that when the board tried to change to speed Windows saw the CPU is being inactive and spat the timeout bsod at him.

I disabled it via a change to a header, reset the CMOS and it went away, I seem the think his board was an Asus but I could be wrong and he was on W8.

 

[irh1]

Meaning run through the BIOS options, and change anything that could govern cpu speed from Auto to a fixed value? Sounds like a plan. Thanks

 

[irh1]

I think I have it stable now. The solution did appear to be force the m/board into a gentle overclock (well, with XMP enabled). Just wanted to say thanks