Official Seven Forums Overclock Leader boards [2]

Nice one crank, will update in a short while.

Updated Cranky, that moves you nicely up a few places. Nice work

crankypenguin said:

Sorry to do this to you paul, but it turns out my PSU DOES have the ESP12V cable, its modular, I just misplaced it, now I got it going and I am ready to start going higher. Let's start with this for tonight.

CPU-Z Validator 4.0

No worries :) Updated.

crankypenguin said:

Sorry to do this to you paul, but it turns out my PSU DOES have the ESP12V cable, its modular, I just misplaced it, now I got it going and I am ready to start going higher. Let's start with this for tonight.

CPU-Z Validator 4.0

Very nice overclock, Cranky. Well done.

Great work Cranky, I bet you're on an all-nighter.

I will update it again in the morning Cranky, in case you go for any early morning OC's lol.

Here's some BSOD codes that may help when overclocking. These were compiled on Overclockers.net and other forums, they aren't my findings.

Code:

OC BSOD codes
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
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
0x7F = Setting the CPU to run at speeds above the rated specification can cause this error, try increase vcore
 
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