BSOD While playing LoL,Browsing etc., error 0x00000124

Awke · 06 Apr 2013

I've been getting regular BSOD with the same error (0x00000124). Not only while playing games, even when browsing with only one tab open with nothing but Spotify running in the background. Even while I'm sleeping and my computer is idle.

A little history behind this..

After my Zalman ZD1225BTR Cpu fan went to sh*t I was the stuck with the Stock Cooling from Intel which at the time worked fine. I was running BF3 on ultra with no problem.
I started getting problems some time after this with overheating, I realized that and moved past it and set my GPU to default setting (Was OC'ed via Catalyst) and turned of OC Genie (which is the integrated OC in my motherboard) . Now it was just as stable as before.

Then I started getting these 0x124 BSOD's.. Have no idea why or exactly when it started but I'm getting frustrated.

A friend of mine who works at an IT Support office said it was most likely my RAM. Even with my cooling problems..

Speaking of cooling problems..:
1. My CPU is at 66 Celsius degrees while typing this. (Rarely goes below 63 degrees)
2. My GPU is at 50 Celsius degrees, also while typing this.

I'm no expert but I think that the BSOD I have might get more regular if I do not replace the stock cooling on my CPU, which is being resolved within the next 7 days (Corsair H60 Watercooling is on its way)

So really, I just wanted to check with you guys before using alot of money on a computer that might die anyway.

And please, if I have messed up including some of the files then tell me and I'll try to fix it as soon as I can. (I'm thinking of the dump file which is .zip'ed. If I've done it wrong I'd like to know and resolve it.)

Awke · 06 Apr 2013

So I've read on some similar threads and figured that getting it might resolve the issue with new/better cooling on cpu etc and reseating components and cables, cleaning the case for dust, and swap out RAM (which I am going to).

Would still appreciate feedback

Arc · 06 Apr 2013

Hello Awke.

You are highly overclocked. Here is the CPU overclock.

Code:

CPUID:        "Intel(R) Core(TM) i7 CPU         860  @ 2.80GHz"
MaxSpeed:     2800
CurrentSpeed: 3411

As you are getting Stop0x124, you should stop overclocking your CPU, GPU and RAM. Overclocking often cause this particular BSOD.

Also, your BIOS is kinda backdated; and an old BIOS also causes a stop 0x124.

Code:

BiosVersion = V1.7
BiosReleaseDate = 01/26/2010

Update your BIOS from MSI Global ? Motherboard - P55-GD65 ; take the version 1.B, dated 2011-08-18.

The CPU is really hot. How old the build is? Can you dismantle the system, clean the inside carefully.... specially the air vents and fan grills? So that it can blow the hot air out easily. While re-seating, dont forget to apply adequate thermal paste (arctic silver) below the CPU. Sometimes the old pastes get dried and causes overheating.

Also, as you know the the CPU fan is damaged.... take care of the CPU. Stress test the CPU.
Hardware - Stress Test With Prime95
It is to see that how the CPU is performing itself. BTW, better to replace the CPU with a damaged fan.

If the overheating continues after doing all these, afford additional cooling. In the mean time, leave one side of the case open.

Make it sure that the PSU is supplying adequate power.
eXtreme Power Supply Calculator

As the crashes are taking place during gaming, stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Finally, Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Do these, step by step. Let us know the results.
_______________________________________________________
BSOD ANALYSIS:

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa8006728028, ba000000, 400405}

Probably caused by : GenuineIntel

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, Machine Check Exception
Arg2: fffffa8006728028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000ba000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000400405, Low order 32-bits of the MCi_STATUS value.

Debugging Details:
------------------


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  Ruse.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f6cb58 fffff800`03822a3b : 00000000`00000124 00000000`00000000 fffffa80`06728028 00000000`ba000000 : nt!KeBugCheckEx
fffff880`02f6cb60 fffff800`039e5633 : 00000000`00000001 fffffa80`0671d870 00000000`00000000 fffffa80`0671d8c0 : hal!HalBugCheckSystem+0x1e3
fffff880`02f6cba0 fffff800`03822700 : 00000000`00000728 fffffa80`0671d870 fffff880`02f6cf30 fffff880`02f6cf00 : nt!WheaReportHwError+0x263
fffff880`02f6cc00 fffff800`03822052 : fffffa80`0671d870 fffff880`02f6cf30 fffffa80`0671d870 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f6cd50 fffff800`03821f0d : 00000000`00000008 00000000`00000001 fffff880`02f6cfb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f6cd90 fffff800`03815e88 : 00000000`285d8900 00000000`285d8900 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f6cdc0 fffff800`038cd52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f6cdf0 fffff800`038cd393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f6cf30 00000000`002f1012 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`090fcdf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x2f1012


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_MAE

Followup: MachineOwner
---------

Awke · 06 Apr 2013

Thank you Arc.
I will indeed try this and post results.

But first;
If you, Arc, got some spare time to answer this; As I have very little experience with this, I'm just a little bit scared to update the BIOS because I'm reading the How to that was in the zip file for it, and I'm terrified because I read it and still have no idea what Im doing.

Btw; Build is getting 3 years old now (end of May).

Arc · 06 Apr 2013

OK, as you are afraid, let it on pending :)
Do the other things .... and if all the others fail to solve it, then we will try it :)

Awke · 06 Apr 2013

According to the PSU calculator I'm doing fine with a spare 140W at 90% load.

According to FurMark my GPU was stable at 99% load @ 80 Celsius degrees with the fans at 58% (highest speed during test with automated fan speed.)

Tried the benchmark again with manual fan control and fixed the fans to 100% speed. it was stable at 63 Celsius degrees after 2 minutes of rising temperature at the start.
Although my CPU bounced around 80-85 degrees during the tests.

I did both benchmarks after setting the GPU clocks to default with AMD Catalyst, since you told me to not overclock.

Tonight I will also turn off OC Genie and I will perform the Memtest when I come back home, and will re-seat cables and components when I get a hold on my new CPU cooler (incl. brand new thermal paste) which will be this coming week as I have very little spare time because of school and work.

Arc · 06 Apr 2013

It's ok :)

Till now, things are going good .... inform us when the tests are done, and the changes are implemented :)
Best of luck.

Awke · 06 Apr 2013

Arc said:

It is to see that how the CPU is performing itself. BTW, better to replace the CPU with a damaged fan.

If the overheating continues after doing all these, afford additional cooling. In the mean time, leave one side of the case open.

When you say "better to replace the cpu with a damaged fan." do you mean that I should put the Zalman fan back on? I think that might be a bad idea now because I don't have any thermal paste at the moment, as it is being sent to me on Monday (hopefully..

).

Also the Memtest says it will start when i restart my system and nothing is happening. And I have gone through the steps accordingly to the step by step on this very forum. I have no idea what I'm doing wrong with it

EDIT: I have turned of OC Genie and Core Temp says the CPU frequency is at 2807.07MHz. Still not 100% sure if Core Temp reads default clock speed rather than the frequency it's running on now..
Got any program that can help me determine that? Just so I can be sure that the OC Genie is off (the motherboard says so.)

Awke · 07 Apr 2013

New update:
After a 24 hours of my cpu being at Its coldest point (40 degrees) in a years time it actually died on me.

I had it on in login screen for the last 3 hrs since i was out eating dinner with my family. I come home noticing the led lights in my nzxt sleeve being a little dark (just as dark as normal But for some reason i thought it was different). So i decided to check ig it was at low brightness or not and it was. I then switched to full brightness and setting it back down to the lowest ( all of this is done manually by hand with a switch).
Then i Get back up and before i can Even sit down in my chair it went black and wouldnt Get back on.

So now ill re-Seat cables and dust og the thing before checking for any life signs.

All overclocks have been gone the last 40 hrs.

Arc · 07 Apr 2013

Was there any more BSODs lately?