The OverClockers BSOD code list

[Alen43]

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

[xpower]

yep

[tijgert]

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.

[Den Leiw]

thanks! very useful information

[zoson]

Great info.
Any idea what 0xF4 is?

[masterg]

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

[Fritz_the_germ]

Maybe this can help you any further

[xpower]

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

[Vampire_X]

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

[Rob94hawk]

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.

[xpower]

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.

[MadHacker]

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.

[ViRuS2k]

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

[xpower]

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

[Heartfixer]

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.

[xpower]

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.