CPU Overclocking / Prime95 Issues

[Pookieraaj]

So i'm having a bizarre issue with my machine and receiving a CLOCK_WATCHDOG_TIMEOUT. Now at first I imagined that this was just not enough voltage or something else with my OC, so I did some adjusting and I'm still getting this issue. Here are my specs.

Core i7-3930K @ 4.5 GHz (1.425 Vcore)

Corsair H100

Asus Sabertooth X79 Motherboard

16 GBs Kingston HyperX Ram

EVGA GTX 680

2 x Intel 520 series 180 GBs SSD (Raid 0)

WD Black 1 TB Drive

So at first I was running my CPU at a 1.410 Vcore and thought that would suffice. After running Prime 95 on small fft's it would crash from BSOD after about 20 minutes, figured it was voltage so I boosted it up to 1.425 (which I thought is kinda high for my cpu's OC but whatever). I was able to run Prime95 on small ffts for about 2 hours and everything was fine. During the time I was testing it I decided to watch Linus' live stream from friday as it was stress testing. I didn't have any problems while doing this. Then I decided I would run it over night to make sure it was a complete stable oc, and after 10 minutes i got the CLOCK_WATCHDOG_TIMEOUT. Now i'm wondering If I need to boost my Vcore up any higher, which I think is a little much for only 4.5GHz. I'm not sure what else to try, any help would be great!

[MunsonedForLife]

This is what I found on your error code.

http://msdn.microsoft.com/en-us/library/windows/hardware/ff557211(v=vs.85).aspx

[star102]

Hmm I don't think Your cpu is of a good bin i only need 1.31Vcore for my 3970x @ 4.5 ghz.

[Pookieraaj]

Would you recommend boosting up the Vcore anymore than that? Or just running at a lower OC? I really don't think 4.5 is too much to ask for :(

[Wats]

When you got the BSOD did happen to notice the first 0x0...00??? code?

[Pookieraaj]

No just the CLOCK_WATCHDOG_TIMEOUT part. I can run it again and I'm sure it will crash so I can observe the code. Oh btw i'm on Windows 8 if that makes any diff.

[Wats]

Ill just give you my code list :P

Not too sure if it will work very accurately on the x79, but It works for z77 and all the amd's I have so.. :]

Copy and paste this somewhere safe. You might find more codes online but I haven't bothered since this works fine for me.

BSOD codes for overclocking

BSOD Codes for i7 x58 chipset

0x101 = increase vcore

0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is

0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage

0x1E = increase vcore

0x3B = increase vcore

0x3D = increase vcore

0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage

0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances

0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x

0x109 = Not enough or too Much memory voltage

0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)

0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r

BSOD Codes for SandyBridge

0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)

0x101 = add more vcore

0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT

0x1E = add more vcore

0x3B = add more vcore

0xD1 = add QPI/VTT voltage

“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instancesâ€

0X109 = add DDR3 voltage

0x0A = add QPI/VTT voltage

[Pookieraaj]

You're the bomb Wats, I'm going to test it first thing tomorrow morning and get to the root of the problem.

[Pookieraaj]

So i'm sitting here stresing my CPU and I couldn't help but notice that even though my Vcore is set to 1.425 in the BIOS, all my programs read out a much lower Vcore setting. Somewhere between 1.3461-1.382. Is this normal for the software to read inaccurately? Or do I have some setting enabled thats bring my Vcore back? I'm new to OC'ing so I'm not sure what I've got set wrong. Also It just crashed and great old windows 8 doesn't give you the error code in the BSOD, Is there somewhere else to find it?

[Pookieraaj]

Anyone got any ideas??

[star102]

increase loadline calibration.

[Pookieraaj]

Thanks for the advice, I brought up the loadline from medium to high and ran Prime briefly and everything seems to be working fine, I will definitely try a full overnight test to make sure its stable. That being said am I able to bring down the Vcore a bit now to see where it drops off? with having the loadline up I would like to bring down that Vcore if possible just because i think 1.425 is a tad high, and the temperatures definitely reflect that. Would I be able to slowly drop the Vcore down until the machine doesn't POST, bring it up a notch from that and run Prime till my hearts content? Let me know if my logic is sound.

[killerx525]

Yep, slowly lower it down till it is unstable but the current vcore is pretty high.

[Pookieraaj]

So I guess that loadline calibration makes a pretty big difference, been testing Prime95 in lower increments on my Vcore, and currently i'm down to 1.385 and haven't had any issue yet. Gives me hope :D