BSOD 0x00000124

[webnoob]

I have a system that craches with 0x00000124.

The system:

Windows 7 Ultimate x64
850W psu
phenom II 1100T processor
M4A87TD/usb3
Kingston HyperX 2x4096 MB DDR3 1600 MHz CL9 Kingston KHX1600C9D3B1K2/8GX
Gainward gtx 560 GS

Windows is fully updated and the system uses all the newest drivers.

I have looked at the dump file and what I can see it is a hardware issue, but which one?

Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
 
Loading Dump File [C:\Users\Thomas\Downloads\dump.rar\112211-38360-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\XPsymbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02e12000 PsLoadedModuleList = 0xfffff800`03057670
Debug session time: Tue Nov 22 18:53:50.785 2011 (UTC + 1:00)
System Uptime: 1 days 3:55:33.940
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 124, {0, fffffa8007496028, b4142000, 145}
Probably caused by : hardware
Followup: MachineOwner
---------
5: 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: fffffa8007496028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b4142000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000000145, Low order 32-bits of the MCi_STATUS value.
Debugging Details:
------------------
 
BUGCHECK_STR:  0x124_AuthenticAMD
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  iexplore.exe
CURRENT_IRQL:  f
STACK_TEXT:  
fffff880`03090b08 fffff800`0340da3b : 00000000`00000124 00000000`00000000 fffffa80`07496028 00000000`b4142000 : nt!KeBugCheckEx
fffff880`03090b10 fffff800`02f9f513 : 00000000`00000001 fffffa80`0619bea0 00000000`00000000 fffffa80`0619bef0 : hal!HalBugCheckSystem+0x1e3
fffff880`03090b50 fffff800`0340d700 : 00000000`00000728 fffffa80`0619bea0 fffff880`03090eb0 00000000`00000000 : nt!WheaReportHwError+0x263
fffff880`03090bb0 fffff800`0340d052 : fffffa80`0619bea0 fffff880`03090eb0 fffffa80`0619bea0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`03090d00 fffff800`03400e8f : 00000000`205aab30 00000000`00000001 fffff880`03090f30 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`03090d40 fffff800`02e8d52c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x47
fffff880`03090d70 fffff800`02e8d393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`03090eb0 00000000`684de424 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`107cf410 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x684de424
 
STACK_COMMAND:  kb
FOLLOWUP_NAME:  MachineOwner
MODULE_NAME: hardware
IMAGE_NAME:  hardware
DEBUG_FLR_IMAGE_TIMESTAMP:  0
FAILURE_BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
BUCKET_ID:  X64_0x124_AuthenticAMD_PROCESSOR_CACHE
Followup: MachineOwner

 

[panais]

Hi.

Stop 0x124 error?


Is better though for us to have the minidumps.


http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

 

[JMH]

Hello webnoob,

A stop error of 0x124 is a general hardware error that requires checking ram, psu, mobo, etc

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here...
Please read through the 9 steps of good advice.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

 

[panais]

Hi.

Stop 0x124 error?


Is better though for us to have the minidumps.


http://www.sevenforums.com/crashes-debugging/96879-blue-screen-death-bsod-posting-instructions.html

Hello webnoob,

A stop error of 0x124 is a general hardware error that requires checking ram, psu, mobo, etc

A "stop 0x124" is fundamentally different to many other types of bluescreens because it stems from a hardware complaint.

Stop 0x124 minidumps contain very little practical information, and it is therefore necessary to approach the problem as a case of hardware in an unknown state of distress.

You can read more on this error and what to try here...
Please read through the 9 steps of good advice.

http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html

We agree!