For the Lenovo ThinkPad W510 (type: 4391-BK1) notebook (Intel Quad Core Processor i7-720QM 1.6 Ghz, 6 MB Intel Smart Cache) with Windows 7 Professional SP1 Operating System (OS), Blue Screen Of Death (BSOD) 0x00000124 (0x00000000, 0x88B7301C, 0xF6002DC0, 0x00040150) was occasionally encountered.
If we use the Nirsoft BlueScreenView v1.47 or higher version to view BSOD 0x00000124 crash information stored in the dump files (eg: 040813-16910-01.dmp) at c:\windows\minidump, Nirsoft BlueScreenView will indicate that the BSOD 0x00000124 was caused by the
halmacpi.dll (address in Stack is halmacpi.dll+efcd) and
ntkrnlpa.exe (address in Stack is ntkrnlpa.exe+124d48).
Using Lenovo ThinkVantage Toolbox application to update all the related Lenovo applications to the latest version (including updating the BIOS to the latest v1.45) or using Windows Update to update all the Windows 7 patches to the latest version did not help to solve the BSOD 0x00000124 error.
If we download the Lenovo Diagnostics (Bootable CD) v1.6 or higher version to test the Lenovo ThinkPad W510 notebook memory and hardisk, the memory and hardisk test (Controller Diagnostics, Read verification & Speed Test) will pass without any error. Lenovo Service Support had changed the Lenovo ThinkPad W510 motherboard, but the BSOD 0x00000124 error still occasionally encountered.
Analysis the DMP (dump) files at c:\windows\minidump
- Please download the Windows Driver Kit v7.1.0 (GRMWDK_EN_7600_1.ISO, 649,877,504 bytes).
- You can use the freeware MagicDisc from Magic ISO Maker to mount the .iso file, GRMWDK_EN_7600_1.ISO to a virtual drive (assume it is v:\ drive).
Assume you have already installed MagicDisc and had started it. On the lower RHS of the monitor screen, kindly right-click on the "MagicISO Virtual CD/DVD Manager" icon, go to "Virtual CD/DVD-ROM" -> "V: No Media" -> "Mount". At the pop-up "Mount CD/DVD image", please point to the GRMWDK_EN_7600_1.ISO file to mount the GRMWDK_EN_7600_1.ISO file to the v:\ drive.
Kindly open a Windows Explorer and go to v:\ drive. Please double-click "v:\KitSetup.exe" to start the Windows Driver Kit installation process. I have only checked to install the "Debugging Tools for Windows (To install Microsoft Windows Debuggers)". I have installed the Microsoft Windows Debuggers to d:\Util\WinDBG directory. - Please open the Microsoft Windows Debuggers by double-click the d:\Util\WinDBG\Debuggers\windbg.exe file. Kindly click "File" -> "Symbol File Path ...". Please insert the below Symbol File Path:
SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols - In the Microsoft Windows Debuggers (WinDBG), kindly click "File" -> "Open Crash Dump...", and point to the minidump file (eg: 040813-16910-01.dmp) to load it. When ask on whether to "Save information for workspace?", kindly check the "Don't ask again in this WinDbg session" and click the "Yes" button. WinDBG will now process the 040813-16910-01.dmp.
At the bottom "0: kd>" prompt, please enter the below command to get detail debugging information:
!analyze -v
Below are 2 examples of the Lenovo W510 notebook BSOD 0x00000124 minidump files analysis content:
Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [E:\040813-16910-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x83254000 PsLoadedModuleList = 0x8339d4d0
Debug session time: Mon Apr 8 10:06:30.233 2013 (UTC + 8:00)
System Uptime: 0 days 0:39:17.466
Loading Kernel Symbols
...............................................................
................................................................
.....................................................
Loading User Symbols
Loading unloaded module list
..........
0: 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: 00000000, Machine Check Exception
Arg2: 88b1e01c, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6001740, High order 32-bits of the MCi_STATUS value.
Arg4: 00040150, 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: TmListen.exe
CURRENT_IRQL: 1f
STACK_TEXT:
83378d0c 8322bfcd 00000124 00000000 88b1e01c nt!KeBugCheckEx+0x1e
83378d48 833257ac 88af2c31 88b1e01c 832cb740 hal!HalBugCheckSystem+0xab
83378d78 8322c27f 88afa780 83239e40 00000000 nt!WheaReportHwError+0x230
83378e8c 8322c371 88afa780 88afa7d0 00000008 hal!HalpMcaReportError+0x3b
83378eb0 8322c48d 00000000 88afa7d0 00000000 hal!HalpMceHandler+0x8b
83378ed0 8322c5d6 00000000 88afa780 83378ff0 hal!HalpMceHandlerWithRendezvous+0x4b
83378ee0 832225f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
83378ff0 8321f261 00000000 801e2000 00000000 hal!HalpMcaExceptionHandler+0x87
83378ff0 00000000 00000000 801e2000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
---------
Loading Dump File [E:\040813-25864-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*D:\Util\winDBG\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18044.x86fre.win7sp1_gdr.130104-1431
Machine Name:
Kernel base = 0x83219000 PsLoadedModuleList = 0x833624d0
Debug session time: Mon Apr 8 09:24:41.047 2013 (UTC + 8:00)
System Uptime: 0 days 0:42:23.280
Loading Kernel Symbols
...............................................................
................................................................
....................................................
Loading User Symbols
Loading unloaded module list
.........
0: 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: 00000000, Machine Check Exception
Arg2: 88ae701c, Address of the WHEA_ERROR_RECORD structure.
Arg3: f6002240, High order 32-bits of the MCi_STATUS value.
Arg4: 00040150, 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: svchost.exe
CURRENT_IRQL: 1f
STACK_TEXT:
8333dd0c 83639fcd 00000124 00000000 88ae701c nt!KeBugCheckEx+0x1e
8333dd48 832ea7ac 88adea39 88ae701c 83290740 hal!HalBugCheckSystem+0xab
8333dd78 8363a27f 88ade7e8 83647e40 00000000 nt!WheaReportHwError+0x230
8333de8c 8363a371 88ade7e8 88ade838 00000008 hal!HalpMcaReportError+0x3b
8333deb0 8363a48d 00000000 88ade838 00000000 hal!HalpMceHandler+0x8b
8333ded0 8363a5d6 00000000 88ade7e8 8333dff0 hal!HalpMceHandlerWithRendezvous+0x4b
8333dee0 836305f5 00000000 00000000 00000000 hal!HalpHandleMachineCheck+0x34
8333dff0 8362d261 00000000 801e2000 00000000 hal!HalpMcaExceptionHandler+0x87
8333dff0 00000000 00000000 801e2000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x89
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: hardware
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
Followup: MachineOwner
---------
All the minidump files that I had analysis all point to the same Intel CPU Cache fault (despite different PROCESS_NAME) for the BSOD 0x00000124 (fatal hardware error):
FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
After Lenovo had replaced the faulty Intel Quad Core Processor i7-720QM, the BSOD 0x00000124 (fatal hardware error) is solved.
References
[1] BSOD 0x00000124 hardware seems fine
[2] Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR
[3] How to open DMP files in Windows 7 ?
4 comments:
Super helpful post. Thank you,
Thank you so much for this post, i got problem with bluscreens with same numbers and files, and seems like, after making a analyst, reason for me is the same: "0x124_GenuineIntel_PROCESSOR_CACHE".
Thank you again, very helpful post indeed!.
Good Day I Am So Happy I Found Your Website, I
Found You By Mistake, While I Was Searching On Aol For
Something Else, Anyhow I Am Here Now And Would Just Like To Say Many Thanks For
A Remarkable Post And An All Round Entertaining Blog
I Don’t Have Time To Read It, All At The Moment But I Have BookMarked It
And Also Added In Your RSS Feeds, So When I Have Time I Will Be Back To Read More,
Please Do Keep Up The Fantastic Job.
Perform the basic RUN windows troubleshooter when you encounter some windows error thats the first step. if its not doing some changes.
try to check this website for more information about that error code.
https://www.errorsolutions.tech/error/0x00000124/
Post a Comment