The OverClockers BSOD code list

Post
Gratuitous
FTW Member
2012/07/26 01:13:39
I found this information a wile ago and it has proved very helpfull when overclocking my systems. I want to make it clear this is not my reaserch but was reposted by user HaMMeR=GoM= from xtream systems forum. I'm not sure who he got the info from.
 
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


 
 
here is the source where I found it
http://www.xtremesystems.org/forums/showthread.php?266589-The-OverClockers-BSOD-code-list
direraptor22
CLASSIFIED ULTRA Member
Re:The OverClockers BSOD code list 2012/07/26 02:48:46
I wonder if there's a BSOD list for Ivy Bridge... any luck finding one?
Gratuitous
FTW Member
Re:The OverClockers BSOD code list 2012/07/26 02:55:21
the same as sandy should apply to ivy, at least it is a good place to start troubleshooring. but to answer your question, I havnt found anything specific to ivy
feniks
CLASSIFIED Member
Re:The OverClockers BSOD code list 2012/07/26 09:51:54
that list is maintained in OCN as well:
http://www.overclock.net/...-list-for-overclocking
flasher4q
FTW Member
Re:The OverClockers BSOD code list 2012/07/26 12:16:28
Thanx for the info....
TECH_DaveB
EVGA Alumni
Re:The OverClockers BSOD code list 2012/07/26 13:00:25
Already knew several of these, but this is a VERY handy tool to have consolidated in one place!
 
If anyone has any others not listed, PLEASE ADD THEM!
feniks
CLASSIFIED Member
Re:The OverClockers BSOD code list 2012/07/27 13:17:40
direraptor22

I wonder if there's a BSOD list for Ivy Bridge... any luck finding one?

 
list for IB is same as for SB ... but there is one more thing with Ivy Bridge and it's crucial to check that too. namely, open the Computer Management (e.g. right click on "Computer" and select Manage) and check the Event Viewer - Custom Views - Administrative Events and look for WHEA-logger warnings.
 
Those warnings are related to unstable CPU when overclocking, but they are correctable by CPU and go in background silently, you won't see failing stress testers because of them, because since CPU corrects those errors and always sends the correct output to application (so the application doesn't even know anything went wrong), yet the CPU will call the OS and log the yellow Warning (which is awesome!).
 
WHEA stands for Windows Hardware Error Architecture.
 
appearance of WHEA in event logs means basically that CPU OC is not stable (yet stable enough to recover silently) and CPU is loosing performance by correcting itself (so it won't BSOD) and servicing the same interrupts twice (by correcting itself).
So, when you see WHEA in Event Logs, you can be sure of 3 things:
1. First of all, your system is not fully stabilized.
2. CPU is loosing some performance on correcting itself
3. those silent WHEA when ignored long enough may turn into BSOD crashes at some point.

WHEA might be happening under full load, but when you run with C1E disabled they could also be happening at idle when only background processes are utilizing gently 1 core in the background.
post edited by feniks - 2012/07/27 13:46:27
  • Back to Mobile