BSOD while playing a game, error x124

Mottoman · 21 Jul 2013

I've updated/installed drivers for my Intel Chipset..seems stable and no BSODs have occured yet. If that changes, I will make sure to post any updates.

Arc · 21 Jul 2013

The last crash dump is still one more stop 0x124.

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800519d028, bb800000, 175}

Probably caused by : GenuineIntel

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

If it still happens after updating the chipset, we have to take the final way ....

9) If all else fails, start removing items of hardware one-by-one in the hope that the culprit is something non-essential which can be removed. Obviously, this type of testing is a lot easier if you've got access to equivalent components in order to perform swaps.

Stop 0x124 - what it means and what to try

Mottoman · 21 Jul 2013

Unfortunately, another blue screen has occured after quite a while. I had my hopes up but it seems unlikely. I've attached the dump files if it has any importance.

A note to add to this; I've performed a Hard Drive fitness test with an advanced test and no errors came up on it. I also have no spare parts to attempt the tests that you've suggested towards the end of your post. What should I do now?

Arc · 21 Jul 2013

It is a continuous process of stop 0x124s.

Stop 0x124 - what it means and what to try

Complete the steps. Then report back. For a stop 0x124, your action is more needed than bugchecking.

Mottoman · 21 Jul 2013

As a last resort, I've reformatted the hard drive and I'm carefully installing one driver at a time. I'll update with another post if another blue screen rolls along.

Mottoman · 22 Jul 2013

An update; a BSOD occured yesterday involving Hal.dll and Ntoskrnl.exe. If I recall properly, I was just opening up a disc setup while exploring files. It feels like whenever I open too many things at once, the BSOD is more likely to happen. I've attached the file below.

I've performed another test involving the motherboard by removing all the RAM sticks and listening if it beeps or not. Fortunately the beeps occurred three times before shutting itself off. I suppose its safe to rule out the Motherboard at this point, yeah?

I have a strong belief it's the CPU at this point..I'm planning to order one the upcoming few days. Before I do that, I did order a power supply tester a few days ago. So I'm going to test that first before ordering a new CPU.

As an ending note, I have been updating drivers here and there, but there might be a few that are outdated. Could you please let me know if anything comes up? Thanks!

Arc · 22 Jul 2013

As you have formatted the HDD, a stray crash dump will not be enough there. Post it following the Blue Screen of Death (BSOD) Posting Instructions.

Mottoman · 22 Jul 2013

As requested, here is the SF file bundle.

Arc · 23 Jul 2013

Follow this link

Stop 0x124 - what it means and what to try

Code:

.......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa800516f028, bb800000, 175}

Probably caused by : GenuineIntel

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

3: 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: fffffa800516f028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000bb800000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000175, 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:  mscorsvw.exe

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02fdfa58 fffff800`03025a3b : 00000000`00000124 00000000`00000000 fffffa80`0516f028 00000000`bb800000 : nt!KeBugCheckEx
fffff880`02fdfa60 fffff800`031e8443 : 00000000`00000001 fffffa80`05174ea0 00000000`00000000 fffffa80`05174ef0 : hal!HalBugCheckSystem+0x1e3
fffff880`02fdfaa0 fffff800`03025700 : 00000000`00000728 fffffa80`05174ea0 fffff880`02fdfe30 fffff880`02fdfe00 : nt!WheaReportHwError+0x263
fffff880`02fdfb00 fffff800`03025052 : fffffa80`05174ea0 fffff880`02fdfe30 fffffa80`05174ea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02fdfc50 fffff800`03024f0d : 00000000`00000004 00000000`00000001 fffff880`02fdfeb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02fdfc90 fffff800`03018e88 : 00000000`012983d0 00000000`01297ce8 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02fdfcc0 fffff800`030d04ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02fdfcf0 fffff800`030d0353 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02fdfe30 000007fe`f081645c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`002ecc80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000007fe`f081645c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: GenuineIntel

IMAGE_NAME:  GenuineIntel

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

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

Mottoman · 02 Aug 2013

Greetings. I apologize for the long delay in responding to the status of my issue.

It turns it out it was the CPU, numerous Prime95 testing on Large FFTs ended up with BSODs. I've checked with the Windows Debugger tool and it pointed at the Processor having Cache Errors. I haven't touched the computer ever since, and I've done numerous re-tests on previous components such as the PSU, RAM stick, Motherboard (Which I obtained a new one after discovering one of the RAM slots did not work at all.), and CPU.

If another BSOD occurs, I will take the liberty of notifying on this thread. For now, thank you very much for assisting me Arc! And I hope this issue does not ever occur again.