Windows 8 Pro BSOD help!

124 bsod is cpu v too low on sb/ib,can also be memory but mainly cpu

if your getting whea errors that also points to cpu v too low,either add one/two clicks more dvid or one level higher llc

also set cpu voltage response to fast in the bios,whether overclocked or not it will help with stability
 
chrisgt said:
400246572633906364672341.jpg
Click to expand...

What I thought the ntoskrnl.exe is the Windows kernel witch controls memory management. This can be RAM and hard drive in your case SSD.

So you need to check SSD with some software? not sure what software is out there you could run though.

Did you also set the RAM to 1.575v? Since this is your second Windows install they is no doubt its an hardware issue you have going on.
 
wazza300 said:
124 bsod is cpu v too low on sb/ib,can also be memory but mainly cpu

if your getting whea errors that also points to cpu v too low,either add one/two clicks more dvid or one level higher llc

also set cpu voltage response to fast in the bios,whether overclocked or not it will help with stability
Click to expand...

Or this...
 
wazza300 said:
124 bsod is cpu v too low on sb/ib,can also be memory but mainly cpu

if your getting whea errors that also points to cpu v too low,either add one/two clicks more dvid or one level higher llc

also set cpu voltage response to fast in the bios,whether overclocked or not it will help with stability
Click to expand...

Cpu Vcore is default; ranges from 0.9 to 1.1v. I'll have a look at the 'Fast' option in BIOS shortly. Are you referring to this? http://www.gigabyte.com/microsite/306/images/3d-power.html

shankly1985 said:
What I thought the ntoskrnl.exe is the Windows kernel witch controls memory management. This can be RAM and hard drive in your case SSD.

So you need to check SSD with some software? not sure what software is out there you could run though.

Did you also set the RAM to 1.575v? Since this is your second Windows install they is no doubt its an hardware issue you have going on.
Click to expand...

I went into BIOS and DRAM settings, I can see the DRAM Voltage is set at 1.65v but its greyed out, as-in, I can't seem to edit it...

I'll look for some software to check SSD health. From my point of view, I'm going to try and eliminate possibilities.

1) Graphics card - I ran the 3D Mark 11 bench and Unigine Heaven, plus a fair bit of Blops 2/PoE without a crash.

2) Memory - I ran the Windows Memory Diagnostic without issue. Will try memtest86+ for a few hours this afternoon.

3) CPU - Downloading Prime95 right now, to see if I get any errors/BSODs whilst running it.

4) SSD - will try and check health.

5) Motherboard - what can I do to check this???
 
Ran into a BSOD 3 minutes into Prime95 running Blend tests. What should I run to just target CPU?

I have loaded BIOS defaults and will try running again...all I had changed was the memory profile, the i5 is completely out of the box...
 
im referring to cpu offset(dvid) you set the cpu voltage to normal in the list and then add extra vcore needed to be stable in dvid

so say setting cpu to normal uses 1.2v yet you need 1.25v to be stable,you would enter +0.025v into dvid and so on

each llc level adds a tiny amount of voltage aswell so you have to be patient in finding the right setting that will give you 1.248v at full load

i would try high llc and +0.015v dvid to start

cpu will throttle down at idle in speed/volts and switch to full speed/volts if stressed

it wont throttle if you used a fixed cpu voltage
 
Right, ran Prime95 with stock DRAM settings (667Mhz) and it got through without BSOD!

So, it would appear the issue is RAM related when I try running it at its correct (1600MHZ not 1333MHZ) speed.

Any suggestions? This is it currently:

838605361573967537675191.jpg


This is what CPU-Z is showing for the i5, with BIOS defaults:

31513246472094426073572.png


Isn't the Vcore high? Note: this was during a Blend test run...



EDIT: So, when BIOS Optimized Defaults are loaded, Prime95 runs fine. When XMP Memory Profile is selected, I get WHEA_UNCORRECTABLE_ERROR. I went into BIOS and used your settings Shankly, so timings: 9-9-9-27 and DRAM Voltage 1.575. Got into Windows, fired up Blend test and instantly WHEA_UNCORRECTABLE_ERROR Blue Screened. I then tried the manufacturers settings for 1600MHZ (the XMP-1600 column on the SPD tab), which meant upping the voltage to 1.65v, and that also Blue Screened.

So it looks like running the RAM at its correct speed is causing this...which is odd, because on my old PC I had all 16GB running at 1600MHZ using an XMP Profile and that was fine.

I then reverted the RAM to BIOS default; and thought I'd try OC'ing the CPU by its self, so set the multiplier to 38 (3.8Ghz). So this was with the CPU @ 3.8Ghz and RAM @ 667Mhz, I ran Prime95 Blend and Blue Screened almost instantly! So that was without touching the RAM settings - is this an issue with the CPU, or is the CPU overclock linked to the RAM in some way?

Full system specs:
i5 3570k (running at completely stock)
16GB PC3-12800 Kington HyperX Genesis Grey (having to run at PC3-10700 to prevent BSOD'ing :( )
Gigabyte Z77X-D3H
Gigabyte 7970 GHZ
Agility3 120GB SSD
XFX 850w PSU
 
Last edited:
what bios are you using? flashed to the latest one off gigabyte website? put it onto a usb memory stick and flash with qflash from within the bios
 
The Ram Voltage grayed out you must be able to change this setting. I never known a board to not let you change the voltage.

1.65v is to high for sandy bridge and ivy bridge you want to be running ram @1.5 for 1300mhz and 1.575 for 1600mhz

If you have XMP selected try switching this off and see if you can change then? if so double check the timings also.
 
wazza300 said:
what bios are you using? flashed to the latest one off gigabyte website? put it onto a usb memory stick and flash with qflash from within the bios
Click to expand...

F16 - the latest stable release.

shankly1985 said:
The Ram Voltage grayed out you must be able to change this setting. I never known a board to not let you change the voltage.

1.65v is to high for sandy bridge and ivy bridge you want to be running ram @1.5 for 1300mhz and 1.575 for 1600mhz

If you have XMP selected try switching this off and see if you can change then? if so double check the timings also.
Click to expand...

I can change this, I was looking in the wrong place. I've tried 1.50v, 1.575v, 1.65v @ 1600MHZ with the recommended timings, all resulting in BSOD..
 
chrisgt said:
F16 - the latest stable release.



I can change this, I was looking in the wrong place. I've tried 1.50v, 1.575v, 1.65v @ 1600MHZ with the recommended timings, all resulting in BSOD..
Click to expand...

Run Memtest86 for couple hours then I say for about 3 full passes. Dont use Windows memory test its not as good has Memtest86.

Run the test on stock RAM settings to make sure reset the BIOS to default settings.
 
shankly1985 said:
Run Memtest86 for couple hours then I say for about 3 full passes. Dont use Windows memory test its not as good has Memtest86.

Run the test on stock RAM settings to make sure reset the BIOS to default settings.
Click to expand...

Will try MemTest86+, but, as I can see from Prime95 the memory seems stable @ 667Mhz but instantly crashses @ 800Mhz. So running at 667Mhz might result in no errors and give me no further information - so is it not best to try running at 800Mhz?

Re my other point - I tried just OC'ing the CPU and leaving the RAM @ 667Mhz but this still BSOD'ed - can this be attributed to the RAM, or is it likely an issue with the CPU too?
 
*sigh*

Thought everything was hunky dory @ stock settings but just had another 0x124 WHEA_UNCORRECTABLE_ERROR whilst playing PoE...so annoying, Prime95 blend ran for an hour fine, but PoE crashes it...
 
thats for older x58/p55

124 bsod can also be cpu voltage on z68/77


BSOD codes for overclocking

X58, P55 Codes

0x101 = increase vcore
0x124 = increase/decrease QPI/VTT
0x0A = unstable RAM/IMC, increase QPI/VTT 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
0xF7 = increase/decrease QPI/VTT


BSOD Codes for SandyBridge P67,Z68 and Ivy Bridge Z77

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
 
Last edited:
Thanks guys. Wazza, could you run me through what to set for CPU voltages? It ranges from 0.9 (1600mhz idle) to 1.21 (3800mhz load).

Is that not sufficient you think?

It's all stock by the way...nothing OC'ed/been modified.
 
are you setting the bclk to 100? and cpu voltage response to fast? do that for stock or oc'ed

then set cpu voltage to normal,youll see normal in the cpu v list
set llc to high and dvid to +0.010 or +0.015v to start with (this is for your original oc)

stress cpu whilst looking in cpu-z with prime95 and see how much cpu v is used,you wanna get it close to 1.248v as you can

do that by adding more dvid,one click at a time

enable extrm performance for phase control and x.m.p for your memory
 
You must log in or register to reply here.
Back
Top Bottom