Help diagnosing BSOD 0x00000124..?

Akagi

Akagi

Akagi

Caporegime
Joined
29 Jul 2011
Posts
37,079
Location
In acme's chair.
Hey guys, my machine has been suffering from BSOD 0x00000124 for quite a while, but it has only become frequent very recently.

The windows event viewer shows many 'Critical - Kernel Power - 41' errors, each one corresponding to a BSOD, three of which occurred in the past 24 hours after multiple gaming sessions.

I read that 0x0 is a machine check exception error, and that the 124 can signify hardware incompatibility (I may be mistaken however) and I am aware that the compatibility of my RAM and motherboard is not fantastic, and I have had one person tell me that they experienced similar problems that went away when they changed to HyperX Genesis Grey,

This seems to point to the RAM being the issue, but I want to be completely sure before I replace it in-case something altogether different is the issue.

The full BSOD error code is: 0x00000123 (0x0000000000000000, 0xFFFFFA80129D028, 0x00000000BE000000, 0x0000000000800400)

The hardware specifications are as in my signature, the i5 is at 4.7GHz - 1.34v Prime95 stable, memory is at stock clocks, timings and voltages, the GPU is running at the factory overclock (however this problem existed with my previous GPU too), the SSD and F3 are in RST enhanced caching mode, all other hardware is completely sound apart from the motherboard which has an extremely small chip next to the front panel fire-wire header which is burned out due to me plugging the USB front panel into it on day-1, but I was informed that if I do not use firewire that it would not be an issue.

Thankyou all for your time, I would very much like to fix this ASAP so I can have peace of mind while using my PC.

Happy New Year :)
 
for me it's memory, replace with any if you have any for a test or best you have 2x4 yes?

take out one and retry, same error with each one, then faulty, no errors with either but same error when both installed its memory or m/b onboard memory controller.

single chip or different memory would test theory fine.

bet you have done all above anyway :(

hope it works, will look for more solutions if needed
 
wazza300 said:
124 error can be not enough cpu voltage on 1155 socket

on p55/x58 its memory controller voltage
Click to expand...

My overclock is 100% prime95 stable after 24+ hours of stressing, it has been at this clock for a while. Could it still be the voltage somehow?
 
zakblood said:
for me it's memory, replace with any if you have any for a test or best you have 2x4 yes?

take out one and retry, same error with each one, then faulty, no errors with either but same error when both installed its memory or m/b onboard memory controller.

single chip or different memory would test theory fine.

bet you have done all above anyway :(

hope it works, will look for more solutions if needed
Click to expand...

Hi zakblood, I will swap out the RAM with some ripjawz (i will swap RAM with a friend temporarily), the time between BSOD varies from a few hours to a few days, so if I were to test it that way, even though it would be a good idea, it would take weeks.

Might try some memtests, that might replicate the issue.

Thanks for the help

Can anyone recommend a within-OS memory stress test? And how many extended passes should I do on the standard microsoft memtest?
 
0x101 = increase vcore
0x124 = increase/decrease vcore
0x0A = unstable RAM/IMC
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0x50 = RAM timings/Frequency unstable
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue
0x7E = Corrupted OS file
 
memtest86,try 5-10 runs on intel burn test,try with standard then high if your temps are ok,be warned it gets the cpu very very hot
 
Thanks for the tips, i'll clean out my rad and then do the burn tests and mem tests.
 
acme15 said:
My overclock is 100% prime95 stable after 24+ hours of stressing, it has been at this clock for a while. Could it still be the voltage somehow?
Click to expand...

Yes. Mine was 24 hours prime stable but after a year or so started throwing up the same bsod as yours. It was completely random and only did it once a week or so. As wazza300 point's out, on mine it was the memory controller voltage that needed increasing a notch. Since doing that i have'nt had a bsod for over 6 months now.
 
pastymuncher said:
Yes. Mine was 24 hours prime stable but after a year or so started throwing up the same bsod as yours. It was completely random and only did it once a week or so. As wazza300 point's out, on mine it was the memory controller voltage that needed increasing a notch. Since doing that i have'nt had a bsod for over 6 months now.
Click to expand...

I have had two BSOD's from watching youtube video's now.

Why is it getting more frequent? Is there a reason for that I wonder?

And what setting in my BIOS is it that you think I should tweak? And by how much do you recommend? I don't pretend to be particularly good at overclocking. Thanks
 
124 is usually CPU power related as mentioned by previous posters.

While it may pass Prime now, or did so in the past, there is obviously a problem with the voltage due to degraded components or a mis-management of low power states. You need to remove the overclock and go stock for a while to make sure it's just a simple voltage problem.
 
yashiro said:
124 is usually CPU power related as mentioned by previous posters.

While it may pass Prime now, or did so in the past, there is obviously a problem with the voltage due to degraded components or a mis-management of low power states. You need to remove the overclock and go stock for a while to make sure it's just a simple voltage problem.
Click to expand...

It took me an age to get the overclock working on this motherboard, it is *extremely* fussy and it was *extremely* difficult to get it to work with a decent clock. I had to seek advice on these hallowed forums and some members helped me get it working.

The CPU is still prime stable. The BSOD's occur when gaming or during video playback.

I am running prime95 in place large FFT right now. Temps are between 65°C and 75°C, system is completely usable while it is running.
Kombuster is going as well.
 
Last edited:
Nickolp1974 said:
0x101 = increase vcore
0x124 = increase/decrease vcore
0x0A = unstable RAM/IMC
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0x50 = RAM timings/Frequency unstable
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue
0x7E = Corrupted OS file
Click to expand...

What is your source for this list?

Thanks :)
 
It err.. *ahem* yeah it BSOD'd just after I made the post claiming that it is prime stable :rolleyes:

More VCORE? 1.344v for 4.7GHz is a tad on the low side. It wasnt a careful overclocking process when I did it to be honest, it was more of a "yeah that will probably work..." - "Ooh it does work!" *leaves it like it for months* and then these random BSOD's start. I am pretty sure I did do a 24hr prime95 stress on this overclock at some point. I know I have definitely done at least 4x 8 hour stresses, and a fair few one or two hour stresses here and there just to see what temps I get depending on the weather etc.

Im running kombuster now for a while to see if it causes a BSOD.

The BSOD occurred a couple of minutes after opening kombuster just now, prime had already been going for a while at that point. It would tie in with the BSOD's happening during gaming and HD video watching I suppose.
 
Last edited:
wazza300 said:
Try with one or two clicks more CPU v,or try with 1.55v dram v,and see how it performs in games
Click to expand...

How much do you recon? Should I put it at 1.36v to 'play it safe'? or do you think I should play around adding tiny increments?
 
Try in small increments,try with 1.55v dram first as it could be that,it won't hurt your ram,I had some vengeance and it needed more than 1.5v to be stable
 
You must log in or register to reply here.
Back
Top Bottom