Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: BSOD error 0x124

19 Nov 2011   #1
famik

Windows 7 Ultimate x64
 
 
BSOD error 0x124

Hello, I have II Xeon E5462 processors on an TYAN PW5400 motherboard and I'm facing the "famous 0x124" BSOD message. I'm writing this thread because I'l like to check if someone could help me by seeing the Dump Analysis:

Note: I 've check MemTest - Disks - Graphics Card all working fine, motherboard also new.

System Log:
Code:
The computer has rebooted from a bugcheck.  The bugcheck was: 0x00000124 (0x0000000000000000, 0xfffffa801a813028, 0x00000000b2000008, 0x0000000006000e0f). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: 111811-44078-01.
System Log:
Code:
Error,11/19/2011 12:50:15 PM,Microsoft-Windows-WHEA-Logger,18,None,"A fatal hardware error has occurred.

Reported by component: Processor Core
Error Source: Machine Check Exception
Error Type: Bus/Interconnect Error
Processor ID: 1

The details view of this entry contains further information."


followed is the crash dump analysis:
Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\windows\MEMORY.DMP]
Kernel Summary Dump File: Only kernel address space is available

Symbol search path is: SRV*e:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a19000 PsLoadedModuleList = 0xfffff800`02c5e670
Debug session time: Fri Nov 18 13:06:13.672 2011 (UTC + 2:00)
System Uptime: 0 days 11:57:08.500
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols

Loading unloaded module list
........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa801a813028, b2000008, 6000e0f}

*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
Probably caused by : hardware

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: fffffa801a813028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000008, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000006000e0f, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02f80b58 fffff800`03014a3b : 00000000`00000124 00000000`00000000 fffffa80`1a813028 00000000`b2000008 : nt!KeBugCheckEx
fffff880`02f80b60 fffff800`02ba6513 : 00000000`00000001 fffffa80`1a7e84e0 00000000`00000000 fffffa80`1a7e8530 : hal!HalBugCheckSystem+0x1e3
fffff880`02f80ba0 fffff800`03014700 : 00000000`00000728 fffffa80`1a7e84e0 fffff880`02f80f30 fffff880`02f80f00 : nt!WheaReportHwError+0x263
fffff880`02f80c00 fffff800`03014052 : fffffa80`1a7e84e0 fffff880`02f80f30 fffffa80`1a7e84e0 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02f80d50 fffff800`03013f0d : 00000000`00000008 00000000`00000001 fffff880`02f80fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02f80d90 fffff800`03007e88 : 00000000`00000000 fffff880`02f78180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02f80dc0 fffff800`02a9452c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02f80df0 fffff800`02a94393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02f80f30 fffff880`045119c2 : fffff800`02a9f4a9 00000000`00299e90 fffffa80`1abde578 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02fa0c98 fffff800`02a9f4a9 : 00000000`00299e90 fffffa80`1abde578 00000000`00000000 00000000`002a051f : intelppm+0x39c2
fffff880`02fa0ca0 fffff800`02a8d93c : fffff880`02f78180 fffff880`00000000 00000000`00000000 fffff880`01119500 : nt!PoIdle+0x52a
fffff880`02fa0d80 00000000`00000000 : fffff880`02fa1000 fffff880`02f9b000 fffff880`02fa0d40 00000000`00000000 : nt!KiIdleLoop+0x2c


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_BUS

Followup: MachineOwner
---------
And a second MiniDump Analysis after seeing the same BSOD event:


Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\111911-27015-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*e:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`02a65000 PsLoadedModuleList = 0xfffff800`02caa670
Debug session time: Sat Nov 19 13:53:22.001 2011 (UTC + 2:00)
System Uptime: 0 days 0:13:55.658
Loading Kernel Symbols
...............................................................
................................................................
...................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 124, {0, fffffa801a6ab028, b2000000, 60151}

Probably caused by : hardware

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: fffffa801a6ab028, Address of the WHEA_ERROR_RECORD structure.
Arg3: 00000000b2000000, High order 32-bits of the MCi_STATUS value.
Arg4: 0000000000060151, Low order 32-bits of the MCi_STATUS value.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  SearchProtocol

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`02ff1b58 fffff800`02a2ea3b : 00000000`00000124 00000000`00000000 fffffa80`1a6ab028 00000000`b2000000 : nt!KeBugCheckEx
fffff880`02ff1b60 fffff800`02bf2513 : 00000000`00000001 fffffa80`1a6aea60 00000000`00000000 fffffa80`1a6aeab0 : hal!HalBugCheckSystem+0x1e3
fffff880`02ff1ba0 fffff800`02a2e700 : 00000000`00000728 fffffa80`1a6aea60 fffff880`02ff1f30 fffff880`02ff1f00 : nt!WheaReportHwError+0x263
fffff880`02ff1c00 fffff800`02a2e052 : fffffa80`1a6aea60 fffff880`02ff1f30 fffffa80`1a6aea60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`02ff1d50 fffff800`02a2df0d : 00000000`00000008 00000000`00000001 fffff880`02ff1fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`02ff1d90 fffff800`02a21e88 : 00000000`00000000 00000000`0089ca10 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`02ff1dc0 fffff800`02ae052c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`02ff1df0 fffff800`02ae0393 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`02ff1f30 00000000`ffff5b38 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
00000000`00be95c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff5b38


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: hardware

IMAGE_NAME:  hardware

DEBUG_FLR_IMAGE_TIMESTAMP:  0

FAILURE_BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

BUCKET_ID:  X64_0x124_GenuineIntel_PROCESSOR_CACHE

Followup: MachineOwner
---------
As last resort I now check every CPU one by one. Any kind of help would be very much appreciated

Thank you,
Gus


My System SpecsSystem Spec
.
19 Nov 2011   #2
zigzag3143

Win 8 Release candidate 8400
 
 

Your .dmp file shows a stop error of 0x124 which is a general hardware error .

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.

Some generic advice.

If you are overclocking STOP. return to the default settings at least for now.
If you are running a RAID update its driver.


You can read more on this error and what to try here... Stop 0x124 - what it means and what to try
My System SpecsSystem Spec
Reply

 BSOD error 0x124




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
BSOD while on Firefox, error 0x124
Hello, I've lurked a bit on this forum in my search for some solutions of why my laptop has been BSODing and I haven't really come across any reasons why. I know that this error is a hardware error but I'd like more details. I've uploaded my dump files with SF tool and hopefully you guys can...
BSOD Help and Support
Bsod playing Gta 4, Error 0x124
Hi, I got Bsod while Im playing Gta 4. After 10minutes to 1 hour. I Googled and read that it could be overheating. I haved run Prime95 and i got Bsod. Thx Best Regards
BSOD Help and Support
BSOD Playing BF3, error 0x124
OS Windows 7 Home Premium x64 Retail Version Processor AMD Phenom II X6 1100T x64 Motherboard MSI NF750-G55 Ram 8GB DDR3 Graphics Card EVGA GeForce GTX 670
BSOD Help and Support
BSoD on after Login, error 0x124
So I built a new computer a couple of days ago. . . and all was well. I got my new drivers, my favorite applications, and games, and was all good. . . but then I logged in one time, started up some applications, and BAM, STOP error. I rebooted, did nothing for 2 minutes, and BAM, STOP error. I...
BSOD Help and Support
BSOD After Start up Error 0x124
Windows 7 Pro x64 -This is the original OS and I bought it retail. It has been reinstalled -I bought the hardware in Dec 2011 and about 5 months after started having the problems. CPU: Intel Core i7 2006k 3.4g LGA 1155 MB: Asus P8P67 pro Rev 3.1 Mem: Kingston HyperX grey...
BSOD Help and Support
BSOD 0x124 halmacpi.dll error
Hi i wondered if any one could help me with a issue i am having. this is the first time i have had to start a tread as i am completely stuck. i normally am able to find the solution using the forums. basically i built a new system for a friend of mine, but unfortunately after completing...
BSOD Help and Support


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 19:43.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App