The OverClockers BSOD code list

HaMMeR=GoM= · Feb 8, 2011

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

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 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.

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

Voltage_Drop · Feb 8, 2011

This would be nice to have as a reference for quick OC diagnosis.

n3tr0m · Feb 8, 2011

Someone should make an iPhone or Android app for BSOD codes, just a quick search and you get information about the error on the go

jid · Feb 8, 2011

This is great, I only had a fraction of these written down from posts I came across and had to guess at the BSOD I got (1E) because I was missing it in my list.. this should get stickied

HaMMeR=GoM= · Feb 9, 2011

Bump...sorry, but I think this could be useful. I want the Pro's opinions and inputs to make this the end all resource for BSOD codes when overclocking. I've already confirmed that 0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r.
That's the kind of stuff that I'm looking for. I also want info for AMD, SandyBridge, and future chip sets.

kennyparker1337 · Feb 17, 2011

Quote:

Originally Posted by HaMMeR=GoM=;12310318
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

I'm running sandybridge, this thread is very great, I fav'ed it in Firefox.

I BSOD with a 124, and I dropped QPI/VTT from 1.08v to 1.05v (stock) and now I am 100% stable.

101 definitely is 100% vCore issue.

PsYLoR · Feb 17, 2011

Quote:

Originally Posted by n3tr0m;12310770
Someone should make an iPhone or Android app for BSOD codes, just a quick search and you get information about the error on the go

Why not just use a PEN & PAPER?

H969 · Mar 5, 2011

Here is another where SFC/Scannow and chkdsk /r, got a rig back on track!

PapaSmurf · Mar 5, 2011

Quote:

Originally Posted by HaMMeR=GoM=;12310318
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

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 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.

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

Is the section I highlighted in red supposed to be VTT by any chance?

HaMMeR=GoM= · Mar 6, 2011

Nice find PapaSmurf. I corrected it in the first post. Thank you. Now if an admin could get this post stickied, it would be great.

PapaSmurf · Mar 6, 2011

That probably isn't going to happen unless a lot of users recommend it to them. For now just bump it every couple of days.

{Artem} · Mar 6, 2011

I think, that's a little weird, but while overclocking q9450 a few years ago and testing it with prime95 if i got low vCore one of my workers just stpopped working.. and i had to manually adjust settings in the bios. But now, OC'ing SB no workers stops, just BSODs all the time if my voltages are incorrect, at least i finally got it stable. Very usefull thread.

evolart · Mar 6, 2011

Very useful.

anthony92 · Mar 6, 2011

you should add 775 Codes aswell seeing as many people still oc with these

q series

evolart · Mar 6, 2011

Anthony if you check the 2 sets they are pretty much the same results. I believe the wording is just different because what you change in the BIOS / UEFI for the different chip is worded slightly.

tucsondude · Mar 6, 2011

seriously someone should compile and sticky a thread of BSOD codes...

i finally went and printed a list out a week ago...

Eno75 · Mar 11, 2011

+1 for sticky.

About 10 guys a day come in floating questions that are answered by people who just copy and paste this code list anyway. It would be totally irresponsible to have a sticky that clarifies killswitch technology and not bsod codes inherent with overclocking. It is overclock.net, isn't it?!

ttoadd.nz · Mar 11, 2011

Sticky Icky. This is good info!

H969 · Mar 24, 2011

Very useful thread!

bloomstomb · Apr 15, 2011

Excellent thread. Is this stickied ? I just came across it on a link.

+1

Also I can confirm x00000124 was vcore issue.

bloomstomb · Apr 15, 2011

Quote:

Originally Posted by PsYLoR;12416604
Why not just use a PEN & PAPER?

The same reason why you didnt just write out this message on a piece of paper and mailed it out to everyone.

c00lkatz · May 6, 2011

Good to see my i7 BSOD list being put to good use (with some good additions)

Starbomba · May 6, 2011

Nice list, very useful
I'd like to see 1156 and 775 BSOD codes as well tho, lots of people still using those sockets, including me

Spooony · May 7, 2011

Quote:

Originally Posted by Starbomba;13402624
Nice list, very useful
I'd like to see 1156 and 775 BSOD codes as well tho, lots of people still using those sockets, including me

Make one yourself then. Take that list apply more than usual to each setting and write the code down for the bsod

El_Capitan · May 8, 2011

For SandyBridge 0x124 BSOD's, if you have 16GB's RAM populated and running at the spec timings and voltages, and you crash after the first couple of tests in Prime95, increasing the DRAM voltages will fix the problem, if your CPU voltages are fine.

AdmRose · May 8, 2011

What would the 124 relevant voltage be listed as in an MSI BIOS?

The OverClockers BSOD code list

Top Contributors this Month

Recommended Communities