BSOD 0x00000124 uncorrectable hardware error

Welcome

BSOD Analyze

This is likely related to your processor.

Code:

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


Loading Dump File [C:\Users\Yusra\Downloads\SF_08-09-2012\090812-14976-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17017.amd64fre.win7_gdr.120503-2030
Machine Name:
Kernel base = 0xfffff800`0305e000 PsLoadedModuleList = 0xfffff800`0329ae70
Debug session time: Sat Sep  8 13:28:49.958 2012 (UTC + 6:00)
System Uptime: 0 days 6:20:15.879
Loading Kernel Symbols
...............................................................
................................................................
................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

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

Unable to load image \SystemRoot\system32\DRIVERS\intelppm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for intelppm.sys
*** ERROR: Module load completed but symbols could not be loaded for intelppm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware

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: fffffa800c5b1028, 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.

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


BUGCHECK_STR:  0x124_GenuineIntel

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

PROCESS_NAME:  System

CURRENT_IRQL:  f

STACK_TEXT:  
fffff880`009f4b58 fffff800`03027903 : 00000000`00000124 00000000`00000000 fffffa80`0c5b1028 00000000`be200000 : nt!KeBugCheckEx
fffff880`009f4b60 fffff800`031e3923 : 00000000`00000001 fffffa80`0c5a9a60 00000000`00000000 fffffa80`0c5a9ab0 : hal!HalBugCheckSystem+0x1e3
fffff880`009f4ba0 fffff800`030275c8 : 00000000`00000728 fffffa80`0c5a9a60 fffff880`009f4f30 fffff880`009f4f00 : nt!WheaReportHwError+0x263
fffff880`009f4c00 fffff800`03026f1a : fffffa80`0c5a9a60 fffff880`009f4f30 fffffa80`0c5a9a60 00000000`00000000 : hal!HalpMcaReportError+0x4c
fffff880`009f4d50 fffff800`03026dd5 : 00000000`00000008 00000000`00000001 fffff880`009f4fb0 00000000`00000000 : hal!HalpMceHandler+0x9e
fffff880`009f4d90 fffff800`0301ae88 : 00000000`00000000 fffff880`009ec180 00000000`00000000 00000000`00000000 : hal!HalpMceHandlerWithRendezvous+0x55
fffff880`009f4dc0 fffff800`030cc8ec : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : hal!HalHandleMcheck+0x40
fffff880`009f4df0 fffff800`030cc753 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxMcheckAbort+0x6c
fffff880`009f4f30 fffff880`04a039c2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiMcheckAbort+0x153
fffff880`02f1bc58 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : intelppm+0x39c2


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

Do all the steps mentioned in the quote below:

writhziden said:

You have an older system. I would recommend that you run the Windows 7 compatibility checks for your hardware: Windows 7 Compatibility: Software Programs & Hardware Devices: Find Updates, Drivers, & Downloads


Please refrain from using CCleaner for the duration of your troubleshooting. It tends to delete the .dmp files we need for analysis during its cleanup procedure.


Make sure you get your Windows updates installed, as well. I see only two updates installed out of 100+ and have not yet gotten to Service Pack 1.


Your LAN drivers are also out of date. Realtek


You have a 0x124 hardware bugcheck. If the system is still under warranty, I would recommend sending it in to have diagnostic tests done and any bad hardware replaced.

   Warning

Before you proceed with the following, answer these two questions: Are you still under warranty? Does your warranty allow you to open up the machine to check hardware? If you are unsure of the answers to these questions, contact your system manufacturer. WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through Stop 0x124 - what it means and what to try and use the following hardware checks to supplement that link.

• If you are overclocking any hardware, please stop.
  
  
• Monitor temperatures during the following tests.
  
  Use the following programs to monitor the temperatures.
  • Real Temp is a good CPU temperature monitor.
  • Speccy - System Information - Free Download will monitor all hardware temperatures.
  • HWiNFO, HWiNFO32 & HWiNFO64 - Hardware Information and Analysis Tools can be inaccurate for CPU temperatures, but is a good program for GPU temperature monitoring.
  
  
  • Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Let it run until the GPU temperatures even out or until the GPU temperatures reach a dangerous level (you can find the max temperature for your card on either the nVidia or AMD sites; if you are not sure, ask us). The goal is to get a steady temperature, find out if the GPU is overheating, or to see if there are any artifacts present in the test itself: look for strange pixelated patterns on the screen or colors that do not look like they belong. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory. Let the memory test run for at least seven passes; the more the better.
    
    
  • Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.
    
    
  • Follow the steps for doing CPU stress test using IntelBurnTest
  
  
• Run the boot version of Memtest86+ paying close attention to Parts 2 and 3 of the tutorial. Also, in case Memtest86+ misses anything and comes up with no errors, run the extended version of the Windows Memory Diagnostics Tool for at least five passes. These you may want to run overnight since they take a long time to complete (run them an hour before bed each of the next two nights and check before going to sleep that they are still running).
  
  For Part 3: If You Have Errors: If you swap any memory components, follow these steps for ESD safety:
  
  1. Shut down and turn off your computer.
  2. Unplug all power supplies to the computer (AC Power then battery for laptops, AC power for desktops)
  3. Hold down the power button for 30 seconds to close the circuit and ensure all power drains from components.
  4. Make sure you are grounded by using proper grounding techniques, i.e. work on an anti-static workbench, anti-static desk, or an anti-static pad. Hold something metallic while touching it to the anti-static surface, or use an anti-static wristband to attach to the anti-static material while working. If you do not have an anti-static workbench, desk, or pad, you can use your computer tower/case by finding a metal hold in it, such as a drive bay.
  
  Once these steps have been followed, it is safe to remove and replace components within your computer.

Remember to read closely through Stop 0x124 - what it means and what to try for the crash.

You also have Daemon tools which is a known cause of BSODS & get an update for your BIOS version from the manufacturers website.

Take your time and let us know what you've done

Please upload the dump so that I can analyze better.

and FYI, the new error code STOP 0x00000101: CLOCK_WATCHDOG_TIMEOUT relates to the processor too.

STOP 0x101: CLOCK_WATCHDOG_TIMEOUT troubleshtg

I think its better you get it replaced.

I've seen the dump its the same one, Stop 101 Clock watchdog timeout. Better send it for replacement before your university starts.

Sorry I couldn't be of more help.

Hi Kim,

First to your question:

(I don't know much about computer hardware setups and compatibility, my boyfriend picked the build for this PC) and came across a thread about my motherboard and RAM, that it can overwork the processor, and wondering if this has happened?

I don't think this is the case, because you said you had a series of problems since you got your computer a year back. This may have been one of the reasons behind all those problems as well.

Also:

If so, since I have to buy a new one, do I need a more powerful processor?

It's not about powerful. Your current processor is powerful enough but is a defected/faulty one.

Nothing extra is required. If you need a replacement - get another Core i7. And if you want to upgrade look for a one that matches the socket pins..Most vendors know about those stuff. Just say that you want a replacement of i7, and tell them your motherboard's model.

Be sure that the replacement of the processor will not violate your OEM license. Contact your system admin in the university first. (Ignore this in case its not an oem license)

Kim125 said:

Thanks for the reply,

I ordered a new processor and unfortunately the problem is still the same, still blue screens 0x101. I'm not sure what next steps to take from here. I've run memtest which passed, and monitored temperatures and they are all fine too.

Did you update your BIOS?