Common BSOD codes

Devrij

Devrij

Devrij

Soldato
Joined
23 Jul 2009
Posts
14,108
Location
Bath
In your experience, do these codes (or the SB ones at least) still apply to Ivy chips? I never know if I'm putting needless volts into my vcore when I could just tweak another voltage slightly to fix the problem.

Taken from another forum:
Common BSOD Error 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 Sandy Bridge

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
Click to expand...
 
This is already proving handy for me. I'm now at 4.7GHz 102.2x46 @ 1.32V. But when I got a BSOD it was 0x50, which turns is my RAM. Touch of voltage and I'm back in business :D

E: I take it back, I'm not completely stable. I think I'd need to stop using offset because I get BSODs at idle.
 
Last edited:
offset can b a pain in the hole lol

Id like to use it properly as its a better power saver and i dont like keeping the cpu voltage at one setting.
im using at moment and cant get it sitting right where i want it.
With static voltage, i can have 4.5ghz at 1.215v under load.
If I used offset voltage, I get around 1.26v under load using auto LLC.
Ive tried using minus and positive offset to get it near 1.215v and cant get it.

Melt
 
Devrij said:
This is already proving handy for me. I'm now at 4.7GHz 102.2x46 @ 1.32V. But when I got a BSOD it was 0x50, which turns is my RAM. Touch of voltage and I'm back in business :D

E: I take it back, I'm not completely stable. I think I'd need to stop using offset because I get BSODs at idle.
Click to expand...

Offset is dictated by the CPU. I prefer control so rarely use it.
 
8 Pack said:
Offset is dictated by the CPU. I prefer control so rarely use it.
Click to expand...

My CPU clearly doesn't know what's good for it. 1.32V is fine for 100% load playing games etc, but anything inbetween or idle and the CPU drops volts/downclocks etc and poos the bed. I don't really want to sacrifice the power saving though so I'm not sure what the solution is. If I were just benching I'd lock the volts and push it a bit harder, but I'm trying to get the highest stable 24/7 so power consumption has to come into it.

I also noticed that I was getting 0x50 codes at stock RAM speed and timing, so would that indicate the IMC needing more volts?
 
Devrij said:
My CPU clearly doesn't know what's good for it. 1.32V is fine for 100% load playing games etc, but anything inbetween or idle and the CPU drops volts/downclocks etc and poos the bed. I don't really want to sacrifice the power saving though so I'm not sure what the solution is. If I were just benching I'd lock the volts and push it a bit harder, but I'm trying to get the highest stable 24/7 so power consumption has to come into it.

I also noticed that I was getting 0x50 codes at stock RAM speed and timing, so would that indicate the IMC needing more volts?
Click to expand...

050 error is memory related,what vccio or vccsa and dram volts you using? might need one/two clicks more
 
Get rid of the power saving crap man and have a solid system.

With offset the CPU its self governs the voltage so these crashes are often seen at idle when the CPU takes it too low. To get rid of the problem you can have a higher offset value but then you get higher temps and burn more power when your actually using your PC and drawing more current from the wall.

0x50 is DRAM timings or voltage usually, it can be IMC at the top end of a clock if the IMC becomes very unstable. I would try adding a touch of DRAM voltage first for this one.
 
I had the DRAM at 1.53V when it happened, as I had just reverted from my BCLK tinkering and forgot to change it back. I was just using the cpu multi for 4.7GHz at that point, so I thought maybe the IMC was losing it at that speed (at 1333MHz RAM?), but it could just be related to the cpu undervolting itself too much?

It looks like 4.6GHz is the highest I can go stable with offset voltage without increasing my vcore to 1.34V, which is more than it needs and pushes temps up to 80C in prime. I should really start a new 3570K thread :rolleyes:
 
You must log in or register to reply here.
Back
Top Bottom