BSOD 0x00000124 uncorrectable hardware error

[Kim125]

Hello,

I have a PC about a year old that unfortunately has had a series of problems. It's had a faulty power supply and recently a faulty hard drive.

Had both of these faulty hardwares replaced and then recently it began blue screening again whilst playing Dragon Age. This started occurring after installing mods so I uninstalled them assuming it was the cause, however a couple of days later the computer would not boot at all.

I reinstalled Windows and for a few days it has been fine but today it blue screened again whilst playing a game.

It was an "uncorrectable hardware error" with error code 0x0124, I managed to figure out the previous problems but I have no clue what is causing it this time.

Any help is much appreciated as University starts soon and I'm studying 3D Animation so really need this computer to be running perfectly..

Many thanks!
Kim

 

[koolkat77]

Welcome

BSOD Analyze

This is likely related to your processor.

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.

[COLOR="Blue"]BugCheck 124,[/COLOR] {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 :[COLOR="blue"] hardware[/COLOR]

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

1: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

[COLOR="blue"]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.[/COLOR]
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:  [COLOR="blue"]0x124_GenuineIntel[/COLOR]

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:  [COLOR="blue"]X64_0x124_GenuineIntel_PROCESSOR_CACHE[/COLOR]

BUCKET_ID:  [COLOR="Blue"]X64_0x124_GenuineIntel_PROCESSOR_CACHE[/COLOR]

Followup: MachineOwner

Do all the steps mentioned in the quote below:

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. :warn:WARNING: The steps that follow can void your warranty!!!

For your hardware stop 0x124 crash, read through http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html 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 http://www.sevenforums.com/tutorials/100352-hardware-stress-test-prime95.html 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 http://www.sevenforums.com/crash-lockup-debug-how/35349-stop-0x124-what-means-what-try.html 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

 

[Kim125]

Thanks for the quick reply,

just a quick update, I updated BIOS to the latest version and decided to run a game to see if it had helped. After a while it blue screened with
A clock interrupt was not received on a secondary processor within the allocated time interval.
code: 0x000000101

This happened twice now, so I will carry on with other methods suggested. Daemon tools was installed after the BSOD troubles, whilst attempting to setup memtest, but I will remove it anyway. Also temperatures are very good in the PC so I dont think anything is overheating.

The computer should still be under warranty, University starts in a couple of weeks so I need the computer working properly. Is it worth doing these tests to attempt fix the processor or am I better off just sending off for a new one so its all working before University starts?

Many thanks for your help!
Kim

 

[koolkat77]

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.

http://www.sevenforums.com/crash-lo...0x101-clock_watchdog_timeout-troubleshtg.html

I think its better you get it replaced.

 

[Kim125]

Here is the latest dump info.

Many thanks,
Kim

 

[koolkat77]

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.

 

[Kim125]

Thank you very much! You've been great help in finding the problem quickly!

Unfortunately found out that the processor has gone out of warranty

I decided to google around about my computers setup (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?

Motherboard: P8P67-M PRO
RAM: Corsair Vengeance 8GB (2x4G)
Processor: Intel Core i7-2600 3.40GHz (Sandybridge) Socket LGA1155

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

Sorry if this question should be taken to a different thread

 

[koolkat77]

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]

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.

 

[koolkat77]

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?

 

[Kim125]

Yes I did, installed the latest version several days back

 

[koolkat77]

Lets enable driver verifier to rule out buggy drivers.

Driver Verifier

I'd suggest that you first backup your data and then make sure you've got access to another computer so you can contact us if problems arise. Then make a System Restore point (so you can restore the system using the Vista/Windows 7 Startup Repair feature).

In Windows 7 you can make a Startup Repair disk by going to Start....All Programs...Maintenance...Create a System Repair Disc - with Windows Vista you'll have to use your installation disk or the "Repair your computer" option at the top of the Safe Mode menu .

Then, here's the procedure:
- Go to Start and type in verifier and press Enter
- Select Create custom settings (for code developers) and click Next
- Select Select individual settings from a full list and click Next
- Select everything EXCEPT FOR Low Resource Simulation and click Next
- Select Select driver names from a list and click Next
Then select all drivers NOT provided by Microsoft and click Next
- Select Finish on the next page.

Reboot the system and wait for it to crash to the Blue Screen. Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation (an estimate on my part).

If you can't get into Windows because it crashes too soon, try it in Safe Mode.
If you can't get into Safe Mode, try using System Restore from your installation DVD to set the system back to the previous restore point that you created.
Driver Verifier - Enable and Disable

Verifier puts extreme stress on the drivers, bad ones will cause BSOD. If we change all those drivers we hope for no more BSODs, If you get no BSODs, then its not a driver and we look to hardware. With verifier on your computer may be a little laggy, but actually..its just doing its work.

Information
Driver Verifier runs in the background, "testing" drivers for bugs. If it finds one, a Blue Screen of Death (BSOD) will result; the corresponding dump file will hopefully show the faulty driver.

Driver Verifier monitors kernel-mode drivers and graphics drivers to detect illegal function calls or actions that might corrupt the system. It can subject the drivers to a variety of stresses and tests to find improper behavior.

Continue to use your system normally, and if you know what causes the crash, do that repeatedly. The objective here is to get the system to crash because Driver Verifier is stressing the drivers out. If it doesn't crash for you, then let it run for at least 36 hours of continuous operation.

 

[Kim125]

Okay I've set it up and instantly I've had two Blue screens on boot, and also caused another immediately when launching a game(to purposely make it crash)

 

[Vir Gnarus]

No drivers here. The initial suspicion we're dealing with hardware failure is definitely possible. Though before going that route, make sure all software installed with your motherboard are uninstalled, leaving only drivers behind, and make sure the motherboard drivers are up-to-date, including the BIOS. If that's all been done, then there really is no choice but to swap out the CPU or the motherboard, since either can cause this (though with your 0x101 bugchecks, I put more blame on the CPU).

Btw, as a little more added info, I did !errrec on the first 0x124 crash to notice a generic error occuring on the CPU L2 cache:

1: kd> !errrec fffffa800c5b1028
===============================================================================
Common Platform Error Record @ fffffa800c5b1028
-------------------------------------------------------------------------------
Record Id     : 01cd8d5e78c7a324
Severity      : Fatal (1)
Length        : 928
Creator       : Microsoft
Notify Type   : Machine Check Exception
Timestamp     : 9/8/2012 7:28:49 (UTC)
Flags         : 0x00000000

===============================================================================
Section 0     : Processor Generic
-------------------------------------------------------------------------------
Descriptor    @ fffffa800c5b10a8
Section       @ fffffa800c5b1180
Offset        : 344
Length        : 192
Flags         : 0x00000001 Primary
Severity      : Fatal

Proc. Type    : x86/x64
Instr. Set    : x64
Error Type    : [COLOR=Red]Cache error[/COLOR]
Operation     : [COLOR=Red]Generic[/COLOR]
Flags         : 0x00
Level         : 2
CPU Version   : 0x00000000000206a7
Processor ID  : 0x0000000000000001

===============================================================================
Section 1     : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor    @ fffffa800c5b10f0
Section       @ fffffa800c5b1240
Offset        : 536
Length        : 128
Flags         : 0x00000000
Severity      : Fatal

Local APIC Id : 0x0000000000000001
CPU Id        : a7 06 02 00 00 08 10 01 - bf e3 9a 1f ff fb eb bf
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00
                00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00

Proc. Info 0  @ fffffa800c5b1240

===============================================================================
Section 2     : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor    @ fffffa800c5b1138
Section       @ fffffa800c5b12c0
Offset        : 664
Length        : 264
Flags         : 0x00000000
Severity      : Fatal

Error         : [COLOR=Red]GCACHEL2_ERR_ERR[/COLOR] (Proc 1 Bank 5)
  Status      : 0xbe2000000005110a
  Address     : 0x000000011ea04dc0
  Misc.       : 0x000000d084020086

Mobo software or bad BIOS can still cause this, but this points more blame on the CPU than the motherboard if it is indeed a hardware problem.

 

[Kim125]

Thankyou for the quick responses, I will double check that everything is up to date. I've just put a brand new CPU in today so it shouldnt be the CPU, are there any tests to narrow it down to the motherboard?

 

[Vir Gnarus]

Unfortunately, outside of swapping the mobo, or utilizing a PC bench (which is really just an open PC with reliable parts to quickly swap mobos in and out) there's nothing you can do with it. Same goes for the PSU if that's the cause of the problem.

Remember that motherboard software should be uninstalled, not updated. This includes any monitoring software, any "enhancement" software, etc. etc. Anything that came with the mobo must go, drivers excluded.

 

[Kim125]

Okay I've removed any software relating to the motherboard and started the process to update the motherboard drivers (apologies I'm a bit of a newbie), is there a place to check the dates of the motherboards current drivers against the website? Should I just get all of them so they are all freshly installed?

ASUSTeK Computer Inc. -Support- Drivers and Download P8P67-M PRO

 

[Kim125]

just some extra info....blue screens now aren't just limited to when the comp has a game launched, it just blue screened whilst using internet and did again on boot, it also completely froze earlier too

 

[Vir Gnarus]

Yes, you should just do a full update of everything. Stay away from the SATA stuff except for the Marvell Controller Driver. Utilities should be avoided.

Did these new symptoms just happen after you uninstalled the mobo software? If so, this may be a case where one of them uninstalled incorrectly, which is typical since those things are bugged up the wazoo. Driver Sweeper is a free app that's designed to clean that stuff off entirely, so you may wanna give that a shot.

Otherwise, I sure do hope your new CPU isn't bad on arrival. That'd be pretty disappointing :< .

 

[Kim125]

I did driver sweeper...computer took several attempts to boot and blue screened a lot. It's been a lot worse today than usual

Should I just do a fresh wipe and reinstall of windows so everything is just reset and if the problems are still there it's definitely hardware?