The OverClockers BSOD code list

[HaMMeR=GoM=]

BSOD codes for overclocking
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

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

Please feel free to comment, advise, correct, and add to this list. I am not the original author and will not take credit for it. I simply thought that it should be posted by itself. I am only repeating the info that I got here and at OCN. This is currently for Intel i7 systems, but I would like for everyone to help me set it up for other systems as well. I will update the list as new information is received.

Thanks, just giving back,
/eVo/HaMMeR=GoM=

[marcolecorse]

Good tread

[thobel]

tagged

[acebmxer]

124 is mostly qpi/vtt but can some times be vcore try qpi/vtt first.

Also will post over at tweaktown forums.

[In-Fluence]

Good thread indeed, thanks for sharing.

My observation with stop code 124 was that I needed to increase vcore to get past large fft tests in prime95, but it definitely does relate to qpi too. Anyone else notice this?

[Sam_oslo]

The 0x124
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore.

On i7 32nm SB, usually means too little vCore. I've been getting it specifically when the vCore is too far from the target, but have been getting 0x101 when it was closer.

[HaMMeR=GoM=]

Thanks everyone for the input. I will edit as the experts suggest. We could have a real winner here. I like how the 0x124 was different for Sandy Bridge. That and AMD stuff would be good.

[Johnny87au]

I use this guys.. handy dandy tool
http://www.mydigitallife.info/2009/0...h-information/

[Cy4n1d3]

Great one, thanks
124 on SB seems to be Vcore, tried VTT but didn't help!

[PatRaceTin]

Mostly hit by

0x101 =
0x124 =

when ocing 2600K around 5.3-5.4Ghz

[sin0822]

These are from my SB OC guide:
BSOD Codes for SB
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

I have nbeen seeing 7E and it always ram tmings and voltage.

[the_real_7]

nice post this will help alot later when im in the mood to push a bit more

[The Duke]

great lists here ... will the OP be updated as more codes are added so we dont have to go digging when this thread gets huge

[HaMMeR=GoM=]

Yes, I will keep it updated and edited as the Guru's give me their input. Thanks to everyone so far.

[nijel]

Let's make this more confusing...
Just got D1 and it was definitely more Vcore.

[pazza316]

Great Thread this and geat tool Johnny. Cheers all!!

[ginfest]

Thanks, nice bit of info

[pazza316]

Guys what is 0x1a any ideas??

Is it the same as 0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore

Thanks

[HaMMeR=GoM=]

0x1A error code is for a memory management error. From what I just Googled it usually means a bad stick of Ram. You need to test with Memtest or whatever you prefer. You might try raising your Ram voltage.

[pazza316]

Cheers Raising voltage in the RAM sorted the problem.

[Dark-Energy]

BSOD 124 on LGA775 platforms means Vcore 90% of the time, but sometimes can be caused by VTT being too high or too low (I've tested this myself)

[dnottis]

bump - been looking for this. Just got a 2600k and getting 124s randomly. Can pass IBT and LinX, but sitting at the desktop idle will crash to 124. WTF!!?

[Cy4n1d3]

Often happens if Offset Voltage is set too low. You could also try lowering Offset a bit and using LLC4 instead of 5.

[dnottis]

Often happens if Offset Voltage is set too low. You could also try lowering Offset a bit and using LLC4 instead of 5.

I'm using fixed voltage and for some reason when I manually overclock I lose the LLC option on Asrock P67 Pro3. I'm guessing it's not enough vcore. But I pass 10 passes of IBT, 20 passes of LinX and it crashes while surfing or idle.

If it were vcore I'd think LinX or IBT would fail.

[Sam_oslo]

I'm using fixed voltage and for some reason when I manually overclock I lose the LLC option on Asrock P67 Pro3. I'm guessing it's not enough vcore. But I pass 10 passes of IBT, 20 passes of LinX and it crashes while surfing or idle.

If it were vcore I'd think LinX or IBT would fail.

With that description, probably it's related to your RAM/IMC, but some of these early BIOSes, a buggy one, can act that way too.
You could try to run a memtest, and if it passes, the try a little 1-hour Prime small FFT. In this way you can determine if it's the CPU/vCore or RAM. If both passes, look for BIOS update.