The OverClockers BSOD code list

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=

Good tread

tagged

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

Also will post over at tweaktown forums.

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?

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.

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.

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

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

Mostly hit by

0x101 =
0x124 =

when ocing 2600K around 5.3-5.4Ghz

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.

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

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

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

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

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

Thanks, nice bit of info :)

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

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.

Cheers Raising voltage in the RAM sorted the problem.

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)

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!!?

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

Quote:

---

Originally Posted by Cy4n1d3

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.

Quote:

---

Originally Posted by dnottis

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.

Quote:

---

Originally Posted by Sam_oslo

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.

---

I just pulled a 2500k that I managed to get to 5Ghz @ 1.44v. So it's definitely not the memory. Just since I put the 2600k this started.

124 is generall vccio related "VTT".. try adjusting it and bump up system agent a tiny bit..Should do the trick!

great guide and bookmarked

Sorry if it's sound noob, but what about when it is just freezing? (no BSOD) temps too high?

Thanks for the guide... sticky?

Quote:

---

Originally Posted by Charloz24

Sorry if it's sound noob, but what about when it is just freezing? (no BSOD) temps too high?

Thanks for the guide... sticky?

---

depending on what platform you are working on it could be Vcore or could be VTT voltage to low.

0x 124 is definitely not VTT. Bumped Vtt and still got one. It passes IBT, LinX and will BSOD 0x124 idle or surfing. 2500k didn't do this, extremely frustrating.

Quote:

---

Originally Posted by dnottis

0x 124 is definitely not VTT. Bumped Vtt and still got one. It passes IBT, LinX and will BSOD 0x124 idle or surfing. 2500k didn't do this, extremely frustrating.

---

could be Vtt
when idle or surfing is your clock droping its multiplyer... which causes Vtt to drop?
check with CPUz if your Vtt is changing compared from load to idle

Quote:

---

Originally Posted by dnottis

0x 124 is definitely not VTT. Bumped Vtt and still got one. It passes IBT, LinX and will BSOD 0x124 idle or surfing. 2500k didn't do this, extremely frustrating.

---

It's not vCore, specially when you are using manual vCore. Because when it passes IBT, LinX, then shouldn't BSOD at idle.
It's not you RAM either. Because it's working fine with 2500k, assuming you are using the same RAM and settings.
The next candidate, and most probable source of problem is the IMC.

If that 2500K is doing fine wiht same MB and same RAM, with same settings, then probably the problem is the IMC of your 2600k.

Adding more VVT/VCCIO should help, but UnCore runs at the same speed as Core on SB, and some IMCs seams to be having problems at x50+, no matter how much juice they get.

Quote:

---

Originally Posted by MadHacker

could be Vtt
when idle or surfing is your clock droping its multiplyer... which causes Vtt to drop?
check with CPUz if your Vtt is changing compared from load to idle

---

Ive disabled this in Windows. It no longer drops idle and still happens. I ordered another CPU. I've read a bunch of people with the same issue, seems the only fix is replacing the CPU. This one is just a bum OC'r with the random BSODs.

Quote:

---

Originally Posted by Sam_oslo

It's not vCore, specially when you are using manual vCore. Because when it passes IBT, LinX, then shouldn't BSOD at idle.
It's not you RAM either. Because it's working fine with 2500k, assuming you are using the same RAM and settings.
The next candidate, and most probable source of problem is the IMC.

If that 2500K is doing fine wiht same MB and same RAM, with same settings, then probably the problem is the IMC of your 2600k.

Adding more VVT/VCCIO should help, but UnCore runs at the same speed as Core on SB, and some IMCs seams to be having problems at x50+, no matter how much juice they get.

---

I ordered another CPU. Found others with the same issue, it just seems to be that some of these are plagued with it.

I dont want to deal with this, a week stable then 4 BSODs in an hour. Its ridiculous. I believe it's something with the chip itself.

All the hardware is the same, I swapped CPUs. Even reinstalled the OS last night in case it was something with the software or a driver. Had 3 today in an hour. been fine the last few hours though, its really random.

Now this thread is going to come in very handy sooner or later. :)

Nice thread and good guide!!!

Nice thread, but does it hold true for the LGA775 platform as well? If so, what voltages in the LGA775 platform are equivalent (for these purposes) to the QPI/VTT voltages?

Quote:

---

Originally Posted by RavenousBBT

Nice thread, but does it hold true for the LGA775 platform as well? If so, what voltages in the LGA775 platform are equivalent (for these purposes) to the QPI/VTT voltages?

---

I believe 775, 1366, 1156 codes are the same just 1155 changed some around...

Guys two days now i have BSOD 0x00000124 error code with 2500K on P67A-UD4 when everything is deafult...
I didn't have this problem before... when i change the Vcore from Auto to normal or I set it manualy to 1.22 (which is the normal) everything is ok!
I changed bios,I cleared Cmos...same problem :(
The problem is the too low Vcore for sure!
My question is... this problem is problem with cpu or with M/B?

Quote:

---

Originally Posted by Timoleros

Guys two days now i have BSOD 0x00000124 error code with 2500K on P67A-UD4 when everything is deafult...
I didn't have this problem before... when i change the Vcore from Auto to normal or I set it manualy to 1.22 (which is the normal) everything is ok!
I changed bios,I cleared Cmos...same problem :(
The problem is the too low Vcore for sure!
My question is... this problem is problem with cpu or with M/B?

---

problem is never use auto for a required voltage setting.... Most motherboards tend to overvolt on auto some can undervolt.

Quote:

---

Originally Posted by Timoleros

Guys two days now i have BSOD 0x00000124 error code with 2500K on P67A-UD4 when everything is deafult...
I didn't have this problem before... when i change the Vcore from Auto to normal or I set it manualy to 1.22 (which is the normal) everything is ok!
I changed bios,I cleared Cmos...same problem :(
The problem is the too low Vcore for sure!
My question is... this problem is problem with cpu or with M/B?

---

CPU. I've had 3 CPUs in here and only one ever gave me 124s. Usually too little vcore crashed with 101.

Quote:

---

Originally Posted by acebmxer

problem is never use auto for a required voltage setting.... Most motherboards tend to overvolt on auto some can undervolt.

---

Yes! but this error is since yesterday,all the others days before i didn't had this error or any other error when i set everything on Auto
Suddendly my mobo undervolt/overvolt? Strange!

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

Got this often overclocking my 2 gpu-s, so what to increase with a SB setup?

any idea what 7F code means ? i7 Bloomfield .

Look for memory issues... timing,voltage etc

thanks for your help

I was getting idle bsods, surfing in youtube etc..watching movies, gave a sudden x124 and x101, usually x124, disabled c3 and c6 never had problem since.

@i5 2500k / 4,5ghz,Vcore 1.32 - Sabertooth P67 B3(1606 BIOS), 8GB Ripjaws X 1600mhz CL9, HD 6950 2GB(unlocked shaders)

got code 124 when i enabled the XMP profile for my ripjaws , during gameplay comp froze up and BSOD.. Thru my Mushkins back in and viola! works perfect .. Little upset about the ripjaws not doing their job ,prob a bad stick or something.

been clocking my 2500K a bit these last days and my experience is that 0x124 is definitely not VCCIO (QPI/VTT) related but just a matter of too little vCore.

I have to disagree.
0x124 can be vcore but also vtt. Adjusting vtt can account for one or two notches lower vcore.
I do agree however that this depends hardly on the chip, some of my 2500/2600k's didn't care what vtt was set to.

usefull thread, goes straigth to favourites.

Yo guys,
today I ve got a pretty uncommon BSOD probably caused by ntkrnlmp.exe.
What is ntkrnlmp.exe and how can I prevent those BSOD?

Quote:

---

Originally Posted by HaMMeR=GoM=

BSOD codes for overclocking
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r
/eVo/HaMMeR=GoM=

---

my contribution

0x7E = incorrect mode set on the SATA controller in the bios
EG: installed OS with SATA controller set to IDE mode. Change it to AHCI and you will get the 0x7E BOSD

Quote:

---

Originally Posted by Cy4n1d3

I have to disagree.
0x124 can be vcore but also vtt. Adjusting vtt can account for one or two notches lower vcore.
I do agree however that this depends hardly on the chip, some of my 2500/2600k's didn't care what vtt was set to.

---

Interesting, i will tweak my vccio... Usually its just too aggressively low vcore for me and stability comes after bumping vcore a notch.

Nope. Bumped my VCCIO to 1.125 and still getting x124.

Quote:

---

Originally Posted by silis

I was getting idle bsods, surfing in youtube etc..watching movies, gave a sudden x124 and x101, usually x124, disabled c3 and c6 never had problem since.

@i5 2500k / 4,5ghz,Vcore 1.32 - Sabertooth P67 B3(1606 BIOS), 8GB Ripjaws X 1600mhz CL9, HD 6950 2GB(unlocked shaders)

---

What does c3 and c6 do?

Quote:

---

Originally Posted by marcolecorse

Good tread

---

agree,i printed it out and tacked it on my wall,lol...never wonder again

i just had the 1E bsod on my pc so according to this list i should increase my Vcore
my Vcore is set at 1.2v in the bios with high vdrop.aint that alot of V for just 4.1ghz?

I'm in the process of RMA'ing my cpu right now. If it's like mine, you might have a bad core... try enabling only 1 or 2 cores and see if it BSOD.

my experience with 0x9C is Vdimm (bloomfield/X58).

Greetings!

First at all, excellent thread, a must have when talking about OCing.

Quote:

---

Originally Posted by vitaminc

What does c3 and c6 do?

---

C3 and C6 info


Regards,

Great thread, a lot of help, i was getting BSOD while idling in windows (124) on a 2500k @ 4,8 with 1.35v. seems like what i need to do is up vcore a bit to 1.365. i was also recommended to up the vrm frequency from 300 to 350 and change the llc to 75% and disable c3.c6 and epu

what is code 7f for.....................

Few post back OldChap said it's for memory issues.

I would like to thank the threadstarter for this excellent initiative, this is one of the best tools for overclocking you can get. can shave hours and days of headache away.

i'm having 00000x8E ? on 1366 what does this mean?

Quote:

---

Originally Posted by fr0wn3r

Few post back OldChap said it's for memory issues.

---

thanks,,,, yep its related to memory timings.

usefull thread
thanks a lot

Quote:

---

Originally Posted by p3gaz_001

i'm having 00000x8e ? On 1366 what does this mean?

---

bump!

Quote:

---

Originally Posted by p3gaz_001

bump!

---

its looks memory problem to me but not sure .....





some time i getting f4 code when i interrupt bios loading.

any idea on 0x19h? (x58/gulftown)
could be vcore i guess, but i'm not sure?!

great thread btw... ;)

cheers.

Making sure I am reading this correctly...

0x124 means... 0x00000124... is this correct?

If so then what does 0x0000007A mean in terms of errors?

Quote:

---

Originally Posted by shimmishim

Making sure I am reading this correctly...

0x124 means... 0x00000124... is this correct?

---

Correct!

Guys on Sandy Bridge- E 101 means Vcore,VCCSA or VTT. I have observed this several times recently and tested the theory to make sure it stands true.

Just posting info about a recent problem i had with code 116, where the problem ended up being resolved with a bump to VTT (1.43 to 1.47). Raising the NB voltage actually made the problem worse (is at 1.2v from stock 1.1v).

This had the problem of seeming like a GPU fault since it causes the gpu driver to crash, and has GPU related errors in the bugcheck with gpu driver flags in the fault module fields etc, so it can take people some time to narrow down the real problem if they don't know where to look.

From my experience it would appear that 116 can point to any component between the gpu and the cpu, including the cpu itself.

I've received error code xBE. I've raised vcore for small increment which gave me x101. Bumped a little more vcore and now running prime95 for 10 min...and counting. So it means xBE will be increasing vcore.

Happy speed hunting. Cheers

Alen

yep

I notice a lot of error code questions without the specific type of CPU. I think it'd help if we all stated clearly what platform we're talking about since they're not all equal in error codes.

For me, I got a 124 code on my SB-E that was only multiplier oc'd (4.8@1.37v in Asus AI, but 1.42 in AIDA?). It was running Large FFT's for about 50 minutes when it crashed. It did Small FFT's for over 4 hours just fine though.
Adding some vcore and letting it run overnight again.

thanks! very useful information

Great info.
Any idea what 0xF4 is?

received 0xF4 on my 3770k ; ; using patriot ram and patriot MLC 32gb ssd

Maybe this can help you any further

BSOD 124 relates to wider aspect in X58 setup , low vtt volts, low vcore. even when both are high. i was getting 124 code because of less vcore many times..

For x124 and x101..

Voltage fluctuation might be causing the problem. Load-Line Calibration (AKA Lowering Vdroop) makes the motherboard "less able" to reduce volts supplied to the CPU under load. What that means is the voltage levels supplied to the CPU are more or less constant - when going from a light load to a heavy load (or vice-verse) the voltage supplied will be the same. Without Load-Line Calibration (Higher Vdroop) the voltage difference between different workloads can be significant.

I'll just summarize.... basically if you are using LLC (to make your Vdroop 'low') the IDLE vCore voltage may be MUCH LOWER than it would be using High Vdroop. I was able to get rid of x101 and x124 by disabling LLC in BIOS. After reading up on Vdroop and voltage I went back and re-enabled LLC and increased my Vcore to offset the negative effects I was seeing with the LLC. The increase was about .07. Haven't had any problems since.

More info can be found here if you're interested in learning more about Vdroop. http://forum.overclock3d.net/showthread.php?t=46502

Are these codes universal? Currently overclocking on Vista 64 Ultimate with an old X38 chipset.

Edit: Ah, I see it's for the i7. Either way good info since building one.

about 2 weeks now having this "BSOD 50, PAGE_FAULT_IN_NONPAGED_AREA" at browsing or idle and reboots. stressing the system linx or prime doesn't bsod or reboots. can't figure out what is the cause as windows is freshly installed. uncore, vtt, ram timming, all have been checked as mention in code 50.

I started get 1E BSOD on my i7930 OC to 4.2Ghz for 2 years
I bumped up the voltage. I guess my CPU is getting tired.

would be great to get a updated bsod list for HASWELL added on the main first post....

cant believe this. page fault in non page area were windows problem. and has been sorted when updated windows. i7 920 still going strong :D

August Windows updates have brought a lot of BSODs without the hardware's fault. Basically my extremely stable overclock on 4930K now BSODs constantly with 0x124. I am at a loss on what to do.

The system is stable on default settings, so definitely I've managed to fix what MS fscked up with the updates (see here, here and here for details).

One of the reasons I've yet to adopt Win 8/8.1 (besides the dreadful interface) is that it seems that stable overclocking settings on Windows 7 do not translate to Windows 8 (i.e. settings that are rock stable on Win7 keep on BSODing on Win8), so the biggest problem I see here is that by pushing updates lately MS made Win7 just as overclocking unfriendly as Win8 is. I will try and come back with updates as I'm trying to fix my system.

Sys specs: 4930K@4.3GHz@1.3V, Noctua NH-D14, 4x8GB GSkill TridentX DDR2400, Asus Rampage IV Extreme (4802 bios), EVGA GTX680, Antec Signature 650W, some SSDs and HDDs, Windows 7 Ultimate x64.

so I decided to quick stress test my second pc that is in sig. just occt as "large data set" as soon as it started testing, system gave BSOD 101 but shut down with code bF ram led on. I rebooted and tested same settings for 30min without any bsod or error. not sue what caused this.


will continue test and update until find the culprit...

EDIT: vccsa volts was the caused, mem controller needed little kick for high density ram.