Random BSOD's 0x00000124

pclinkcomputers · 20 Feb 2014

Hey all,

I've been experiencing random BSOD's this past week. Seems to only happen either when I'm watching video or gaming. The computer will be useable for quite some time, anywhere from 1-4 hours, but then without warning, will crash.

I have a Core i5-2500k that I have overclocked to 4.5 GHz. Naturally, my first assumption was that something was wrong there. I tweaked the voltage a little and played with some other BIOS settings, and then let Prime run for 11-ish hours. It was still going when I woke up. For those who are wondering, I have an H60 installed, max temp was 73. Idle temps are in the low 30's.

Soooo...it would seem the CPU is fine. And yet, the crash...dump? Report? Whatever it's called, it seems to indicate the CPU, which is odd. "X64_0x124_GenuineIntel_PROCESSOR_CACHE"

Unless I'm misinterpreting it. Anyway...

My suspicion is the video card, even though I really have no proof. BUT...about a week ago, I came home from work, fired up the computer and was greeted with a blank green screen. Irritated, I rebooted, thinking that would fix it, which it didn't. So I removed the video card, cleaned and reseated it...everything worked fine.

That seems to be when the problems began, which is why I suspect it as the culprit.

I haven't checked my HDD or RAM yet. Hmmm, I probably should've ran Memtest before posting. But anyway, I thought I'd see if anyone here had any ideas/feelings/hunches/tremors in the Force.

Some misc. info: Airflow in my case is great, I would say. Antec Three Hundred, 2 front intake, top exhaust, and the H60 exhausts out the back. I opened a video clip and watched video card temps for a bit earlier, the auto fan setting seems to be working as advertised, temps are well within norm. I have a Corsair Professional Gold 850w PSU, so unless I'm extremely unlucky and my unit is dying, that should be good to go.

Anyway, thanks in advance for any thoughts/suggestions/comments.

Arc · 23 Feb 2014

Code:

BugCheck 124, {0, fffffa800a02e028, be200000, 5110a}

Probably caused by : GenuineIntel

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

1: 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: fffffa800a02e028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000be200000, High order 32-bits of the MCi_STATUS value.
Arg4: 000000000005110a, Low order 32-bits of the MCi_STATUS value.

It is not indicating to the CPU.

Machine Check Exception means the CPU detected a hardware error and ordered the memory to record a crash dump.

And overclocking and the heat output caused by overclocking is the primary reason behind the Machine check exceptions.

If the computer runs stable without overclocking, let it be there.

For more information, have a look here:

pclinkcomputers · 24 Feb 2014

Hey, thank you for the reply.

It's interesting to me that Prime was rock-solid for nearly 12 hours, while watching an episode of The Clone Wars would cause a crash. I understand that overclocking the CPU causes excess heat and stress, but when a program that is specifically used to detect instability/excess heat fails to cause a single problem...can you really blame the overclock?

I'm not trying to be argumentative, and I genuinely appreciate your reply. I had given up on receiving any responses at all, in fact. I guess I'm just trying to encourage any alternate theories/suggestions.

FWIW, it hasn't happened a single time since I started the thread, and I use the machine every day.

Arc · 25 Feb 2014

I am not blaming anything or anyone.

There is a discrete procedure to debug stop 0x124. And if your computer is overclocked, no further troubleshooting is feasible until and unless you disable the overclock.

Number of times of the occurrence of the issue does not matter at all. If you dont solve the issue by identifying the root, it will strike back rightly, anytime and anywhere.