Help diagnosing BSOD 0x00000124..?

im not sure on that board,you could try raising power limits a little see if that helps,you can still use a touch more dram v upto 1.575,

disabling cpu spread spectrum might help also

The general consensus over the net is that my power limits should be fine. I'll try disabling spread spectrum and run prime.

*edit* I have now re-set the DRAM voltage and the VTT voltage to the standard 1.50v and 1.051v while I prime with spread spectrum disabled just to check it like this first.

I am honestly expecting it to BSOD at this point. I may install an OS on a secondary drive while this continues so that when i'm playing around in the BIOS, the inevitable BSOD's won't damage my main OS.

Is it at all possible that priming with the temperatures 78, 80, 85, 83 could be the cause? I do still need to clean out the radiator. I went to grab a can of compressed air in town but I couldn't find any, so I ordered some. It isn't here yet.

*edit* I just opened my window. It's freezing in here now but the temperatures have dropped to something a bit more 'prime-friendly'.

Temps should drop 8°C - 12°C once the radiator is all cleared out.
 
Last edited:
BSOD after about an hour. Put spread spectrum back to 'auto' since that didnt seem to make a difference, DRAM now on 1.575v, VTT now on 1.09v.

Running blend.

If it's OK after 12 hours i'll try again with DRAM on 1.575v and VTT on 1.05v.

I'll also try 1.37v VCORE with the DRAM and VTT at stock,

and finally DRAM 1.575v, VTT 1.09v, VCORE 1.37v.

If none of those work i'll go back to stock settings until ive cleared the radiator out.

*edit* BSOD after 20 minutes with 1.575 DRAM and 1.09 VTT. (guess that rules out RAM voltage?)

Trying with VCORE at 1.376v, DRAM 1.50v and VTT 1.05v. (BIOS says VCORE is 1.376v, CPU-Z says VCORE is 1.360v, coretemp says VCORE is 1.381v. Why?!)

Running blend.

I am really hoping that it turns out to be faulty/partially incompatible RAM. Because that would be so easy to sort out. I have read that this RAM and this board are not compatible, a good few people have mentioned that they had to change RAM with this combination. It also completely refused to overclock.

I can try this with my 2x 2GB Patriot kit at some point, and if it turns out to be a RAM incompatibility I have a friend with some HyperX Genesis Grey who is willing to swap (since my RAM is listed as compatible with his sabertooth, and his is listed compatible with my board)

What is the liklihood of that do you suppose?
 
Last edited:
BSOD after 4 hours of blend with 1.375v VCORE.

Back on 1.360v VCORE, 1.50v DRAM and 1.05v VTT now. Everything back where it was. I'm going to clean my radiator out in a minute, see how much my temperatures drop, and then just prime95 it as it was before to see if the temps were causing the BSOD's.

They sat in the mid to high 80's peaking at 91°C during the blend with 1.375v. Back when the radiator was clean it sat in the high 60's to low 70's peaking at 74° or so IIRC.
 
Well I am now running 4.6GHz, spread spectrum disabled, 1.36v VCORE, 1.5v DRAM. About to run prime blend.

As it turns out temperatures were not the cause of the BSOD's. After cleaning the radiator, the load temperatures dropped a full 20°C! (see my latest thread for piccies :p )

But when I stressed with Prime, I still got a BSOD.
 
Last edited:
have you tried with just one ram stick 4gb installed? see how you get on

or try slightly looser timings 9-9-9-28-2t
 
have you tried with just one ram stick 4gb installed? see how you get on

or try slightly looser timings 9-9-9-28-2t

I have a slightly bigger issue now :(

Take a look at my latest threads. The ones about the motherboard. 'im finding it hard to keep my cool' and 'my motherboard is broken isnt it?'.

I can't get the PC to even boot with any kind of respectable overclock on it at the moment. It has just stopped working... The BIOS is at stock now apart from fan speed, storage configuration and the RAM being set to 1600MHz.
 
did you do a long cmos/battery removal for 30mins? regular bsd's/crashes can cause corrupted cmos so clear it and load optimised defaults/re enter bios/oc settings
 
did you do a long cmos/battery removal for 30mins? regular bsd's/crashes can cause corrupted cmos so clear it and load optimised defaults/re enter bios/oc settings

I clear it by pressing the clr-cmos button on the I.O. Does the long battery pull method work differently?

If it does, and this sorts it, you may have just saved me £140... Though that Z77 MPower is looking more and more tempting :p

*edit* I particularly love how the CMOS battery is under the GPU... Reeeeal convenient Asrock...
 
yes the battery removal is better,and leave it out a good 30mins as the board still stores power

just pinch together the metal tabs and the battery should lift out
 
1.65v is safe 24/7 on this set up.

How is this problem going now??? I got your PM on OC.net

Hi 8 pack, the problem seems to have been mostly resolved now. I flashed the latest BIOS to the board and now the chip is at 4.6GHz with the same volts as I had on 4.7. I am a bit miffed as to why 4.7 suddenly became unstable entirely (even with 1.38v) when it had been stable at 1.36v for over a year.

Surely 1.36v on a 47 x 100 overclock couldn't have degraded the chip that quickly..?

The only problems with the system are related to the motherboard hanging for a few seconds on an A5 error and the lack of Post 'beep' which could be down to just the new bios revision.
 
Back
Top Bottom