Yes, thanks!
Many of the attached DMP files are of the
WHEA_UNCORRECTABLE_ERROR (124) bugcheck.
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 bugcheck (address of the WER structure) we get the following:
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa800289a148
Section @ fffffa800289a2d0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : BUSL0_SRC_ERR_M_NOTIMEOUT_ERR (Proc 1 Bank 0)
Status : 0xb200004000000800
BUSL0_SRC_ERR_M_NOTIMEOUT_ERR = Implies that the processor sent out a read request to L0 Cache, and there was a delay in return (cache miss or corrupt / invalid data in the cache).
The majority are of this error, however I saw a different one as well:
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa8003495148
Section @ fffffa80034952d0
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
Error : GCACHEL2_ERR_ERR (Proc 1 Bank 3)
Status : 0xb22000460002010a
MODULE_NAME: hardware
IMAGE_NAME: hardware
FAILURE_BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
BUCKET_ID: X64_0x124_GenuineIntel_PROCESSOR_CACHE
GCACHEL2_ERR_ERR = L2 Cache issues.
-------------------------------
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. The
only software conflict 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 it is faulty.
Regards,
Patrick
