Hi,
All of the attached DMP files are of the
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. This fatal error displays data from the Windows Hardware Error Architecture (WHEA).
If we run an !errrec on the 2nd parameter of the bug check (address of the WER structure) we get the following:
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe000a149b138
Section @ ffffe000a149b2c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=#ff0000]Error : DCACHEL0_WR_ERR (Proc 4 Bank 1)[/COLOR]
Status : 0xbf80000000000124
Address : 0x000000013892e140
Misc. : 0x0000000000000086
DCACHEL0_WR_ERR = L0 Cache Write error.
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ ffffe001ccc83138
Section @ ffffe001ccc832c0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=#4b0082]Error : DTLBL0_ERR (Proc 4 Bank 2)[/COLOR]
Status : 0xb200000000010014
In your case, we're dealing with a Translation lookaside-buffer (TLB) error. It specifically occurred on Processor #4 and Cache Bank #2.
What is a TLB? In a very basic definition, a Translation lookaside-buffer (TLB) is a cache that memory management hardware uses to improve virtual address translation speed. All current desktop, laptop, and server processors include one or more TLBs in the memory management hardware, and it is nearly always present in any hardware that utilizes paged or segmented virtual memory.
By default, a TLB miss whether caused by hardware and/or software complications is
not fatal (if the virtual address is not stored in the TLB, it's simply computed and found manually from other source data), but we're crashing on a TLB failure, this implies that the CPU determined there was corruption or a hardware error in date, therefore notified Windows that an unrecoverable hardware error has occurred.
There is only so much you can do with a bugcheck like this until it comes down to a faulty processor that will need to be replaced. Start from 1 and work downward:
1. Ensure your temperatures are within standard and nothing's overheating. You can use a program such as Speccy if you'd like to monitor temps -
Speccy - System Information - Free Download
2. Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting -
How To Clear CMOS (Reset BIOS)
3. Ensure your BIOS is up to date.
4. Software conflicts that can usually cause *124 bugchecks are OS to BIOS utilities from manufacturer's like Asus' AI Suite. If you have something like this software-wise, remove it ASAP.
5. If all of the above fail, the only left to do is replace your processor as you unfortunately seemed to have gotten a dud CPU.
Regards,
Patrick
