Answered by:
Constantly getting WHEA_UNCORRECTABLE_ERROR

Question
-
Hey there. I just got a new computer, and are having issues with a lot of BSOD. It mainly happens when the PC is under stress, but it occationally occurs when browsing etc.
Here is the most recent dump file:
https://www.dropbox.com/s/sleqo1hozmtz6g7/082513-18781-01.dmp
My system:
Summary
Operating System
Windows 8 64-bit
CPU
Intel Core i7 4770K @ 3.50GHz 33 °C
Haswell 22nm Technology
RAM
16.0GB Dual-Channel DDR3 @ 800MHz (9-9-9-24)
Motherboard
ASUSTeK COMPUTER INC. Z87-DELUXE (SOCKET 1150) 28 °C
Graphics
BenQ EW2730 (1920x1080@60Hz)
3072MB NVIDIA GeForce GTX 780 (ZOTAC International) 39 °C
3072MB NVIDIA GeForce GTX 780 (ZOTAC International) 35 °C
ForceWare version: 320.11
SLI Enabled
Hard Drives
224GB KINGSTON SH103S3240G (SSD) 25 °C
Optical Drives
TSSTcorp CDDVDW SH-224DB
Audio
NVIDIA High Definition Audio
WhoCrashed report:
On Mon 8/26/2013 15:57:56 GMT your computer crashed
crash dump file: C:\windows\Minidump\082613-18687-01.dmp
This was probably caused by the following module: hal.dll (hal+0x2D965)
Bugcheck code: 0x124 (0x0, 0xFFFFFA800F8E3028, 0xBF800000, 0x124)
Error: WHEA_UNCORRECTABLE_ERROR
file path: C:\windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This bug check indicates that a fatal hardware error has occurred. This bug check uses the error data that is provided by the Windows Hardware Error Architecture (WHEA).
This is likely to be caused by a hardware problem problem. This problem might be caused by a thermal issue.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.I have tried running a stress test on the computer (Prime 95). After a maximum of 5 minutes, the computer will crash. CPU temperature never goes above 72 degrees C during stress test and motherboard temperature stays at 28 degrees. Any suggestions to what I can do to fix or find the cause to the crashes?
- Edited by winnt32 exe Monday, August 26, 2013 4:41 PM
Monday, August 26, 2013 4:39 PM
Answers
-
You get a L0 Cache issue:
******************************************************************************* * * * 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: fffffa80109f9028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre STACK_TEXT: nt!KeBugCheckEx hal!HalBugCheckSystem nt!WheaReportHwError hal!HalpMcaReportError hal!HalpMceHandlerCore hal!HalpMceHandler hal!HalpMceHandlerWithRendezvous hal!HalHandleMcheck nt!KxMcheckAbort nt!KiMcheckAbort dxgmms1!DXGAUTOPUSHLOCK::AcquireShared FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
===============================================================================
Common Platform Error Record
-------------------------------------------------------------------------------
Record Id : 01ce9f820d4e9fec
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 8/25/2013 0:42:49 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f90a8
Section @ fffffa80109f9180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000004
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f90f0
Section @ fffffa80109f9240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000004
CPU Id : c3 06 03 00 00 08 10 04 - bf fb da 7f 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 @ fffffa80109f9240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f9138
Section @ fffffa80109f92c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHEL0_WR_ERRBiosVersion = 1007 BiosReleaseDate = 05/17/2013 BaseBoardManufacturer = ASUSTeK COMPUTER INC. BaseBoardProduct = Z87-DELUXE
Update the BIOS/UEFI to version 1205 and look of this fixes it.
Z87-DELUXE BIOS 1205 1.Improve system stability. 2.Fix XMP button issue 3.Revise help string for the German Language.
If not, RMA the cpu.
"A programmer is just a tool which converts caffeine into code"
- Edited by Andre.ZieglerEditor Monday, August 26, 2013 6:57 PM
- Marked as answer by winnt32 exe Monday, August 26, 2013 8:44 PM
Monday, August 26, 2013 6:56 PMAnswerer -
It seems like the BIOS version was the problem. After updating, i didn't have a crash during the stress test for an hour. Since it normally took 1-2 minutes, I assume the problem is fixed. Thank you both for your assistance!
- Marked as answer by Niki Han Tuesday, September 10, 2013 3:36 AM
Monday, August 26, 2013 8:44 PM
All replies
-
We do need the actual DMP file as it contains the only record of the sequence of events leading up to the crash, what drivers were loaded, and what was responsible.
WE NEED AT LEAST TWO DMP FILES TO SPOT TRENDS AND CONFIRM THE DIAGNOSIS.You may be able to get the DMP files without crashing by booting into safe mode (F8) with networking.If you are overclocking stop. (chances are if you dont know if you are, you are not)To enable us to assist you with your computer's BSOD symptoms, upload the contents of your "\Windows\Minidump" folder.The procedure:* Copy the contents of \Windows\Minidump to another (temporary) location somewhere on your machine.* Zip up the copy (compress them)*Please upload them to a file sharing service like Skydrive or"Rapidshare" and put a link to them in your reply.Link for how to upload below.To ensure minidumps are enabled:* Go to Start, in the Search Box type: sysdm.cpl, press Enter.* Under the Advanced tab, click on the Startup and Recovery Settings... button.* Ensure that Automatically restart is unchecked.* Under the Write Debugging Information header select Small memory dump (256 kB) in the dropdown box (the 256kb varies).* Ensure that the Small Dump Directory is listed as %systemroot%\Minidump.* OK your way out.* Reboot if changes have been made.Please also run MSinfo32 and upload the output as well.To run MSinfo32 please go to start>run>MSinfo32Go to "file" "save" and upload the saved file with the DMPSSystem specs are extremely useful so please include whatever you know.
Blue Screen View & Who Crashed are often wrong and should only be used in an emergency...
You can read more about BSODS hereYou can learn how to test your memory here
Team Zigzag3143.comWanikiya & Dyami--Team Zigzag
- Marked as answer by ZigZag3143x Monday, August 26, 2013 8:54 PM
- Unmarked as answer by Andre.ZieglerEditor Tuesday, August 27, 2013 4:56 AM
Monday, August 26, 2013 5:56 PM -
You get a L0 Cache issue:
******************************************************************************* * * * 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: fffffa80109f9028, Address of the WHEA_ERROR_RECORD structure. Arg3: 00000000bf800000, High order 32-bits of the MCi_STATUS value. Arg4: 0000000000000124, Low order 32-bits of the MCi_STATUS value. Debugging Details: ------------------ BUGCHECK_STR: 0x124_GenuineIntel CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: f ANALYSIS_VERSION: 6.3.9431.0 (debuggers(dbg).130615-1214) amd64fre STACK_TEXT: nt!KeBugCheckEx hal!HalBugCheckSystem nt!WheaReportHwError hal!HalpMcaReportError hal!HalpMceHandlerCore hal!HalpMceHandler hal!HalpMceHandlerWithRendezvous hal!HalHandleMcheck nt!KxMcheckAbort nt!KiMcheckAbort dxgmms1!DXGAUTOPUSHLOCK::AcquireShared FAILURE_BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE BUCKET_ID: 0x124_GenuineIntel_PROCESSOR_CACHE
===============================================================================
Common Platform Error Record
-------------------------------------------------------------------------------
Record Id : 01ce9f820d4e9fec
Severity : Fatal (1)
Length : 928
Creator : Microsoft
Notify Type : Machine Check Exception
Timestamp : 8/25/2013 0:42:49 (UTC)
Flags : 0x00000000
===============================================================================
Section 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f90a8
Section @ fffffa80109f9180
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
Error Type : Cache error
Operation : Generic
Flags : 0x00
Level : 0
CPU Version : 0x00000000000306c3
Processor ID : 0x0000000000000004
===============================================================================
Section 1 : x86/x64 Processor Specific
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f90f0
Section @ fffffa80109f9240
Offset : 536
Length : 128
Flags : 0x00000000
Severity : Fatal
Local APIC Id : 0x0000000000000004
CPU Id : c3 06 03 00 00 08 10 04 - bf fb da 7f 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 @ fffffa80109f9240
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa80109f9138
Section @ fffffa80109f92c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : DCACHEL0_WR_ERRBiosVersion = 1007 BiosReleaseDate = 05/17/2013 BaseBoardManufacturer = ASUSTeK COMPUTER INC. BaseBoardProduct = Z87-DELUXE
Update the BIOS/UEFI to version 1205 and look of this fixes it.
Z87-DELUXE BIOS 1205 1.Improve system stability. 2.Fix XMP button issue 3.Revise help string for the German Language.
If not, RMA the cpu.
"A programmer is just a tool which converts caffeine into code"
- Edited by Andre.ZieglerEditor Monday, August 26, 2013 6:57 PM
- Marked as answer by winnt32 exe Monday, August 26, 2013 8:44 PM
Monday, August 26, 2013 6:56 PMAnswerer -
It seems like the BIOS version was the problem. After updating, i didn't have a crash during the stress test for an hour. Since it normally took 1-2 minutes, I assume the problem is fixed. Thank you both for your assistance!
- Marked as answer by Niki Han Tuesday, September 10, 2013 3:36 AM
Monday, August 26, 2013 8:44 PM -
It seems like the BIOS version was the problem. After updating, i didn't have a crash during the stress test for an hour.
Nice to hear this :)
@Zz
Please don't always mark your own replies as answer if they are not the real answer. It was helpful so I voted for it, but didn't answered it.
"A programmer is just a tool which converts caffeine into code"
Tuesday, August 27, 2013 4:57 AMAnswerer