Hi,
The latest attached DMP file is 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 0 : Processor Generic
-------------------------------------------------------------------------------
Descriptor @ fffffa80079b4978
Section @ fffffa80079b4a50
Offset : 344
Length : 192
Flags : 0x00000001 Primary
Severity : Fatal
Proc. Type : x86/x64
Instr. Set : x64
[COLOR=#ff0000]Error Type : BUS error[/COLOR]
Operation : Generic
Flags : 0x00
Level : 3
CPU Version : 0x0000000000600f12
Processor ID : 0x0000000000000000
^^ BUS error.
Code:
===============================================================================
Section 2 : x86/x64 MCA
-------------------------------------------------------------------------------
Descriptor @ fffffa80079b4a08
Section @ fffffa80079b4b90
Offset : 664
Length : 264
Flags : 0x00000000
Severity : Fatal
[COLOR=#ff0000]Error : BUSLG_GENERIC_ERR_*_TIMEOUT_ERR (Proc 0 Bank 0)[/COLOR]
Status : 0xb880000000020f0f
^^ Specifically, a timeout occurred somewhere along the bus (Processor 0 - Cache Bank 0 - *primary CPU core*)
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. Run Memtest for NO LESS than ~8 passes (several hours):
Memtest86+:
Download Memtest86+ here:
Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works:
Memtest86 writes a series of test patterns to most memory addresses, reads back the data written, and compares it for errors.
The default pass does 9 different tests, varying in access patterns and test data. A tenth test, bit fade, is selectable from the menu. It writes all memory with zeroes, then sleeps for 90 minutes before checking to see if bits have changed (perhaps because of refresh problems). This is repeated with all ones for a total time of 3 hours per pass.
Many chipsets can report RAM speeds and timings via SPD (Serial Presence Detect) or EPP (Enhanced Performance Profiles), and some even support changing the expected memory speed. If the expected memory speed is overclocked, Memtest86 can test that memory performance is error-free with these faster settings.
Some hardware is able to report the "PAT status" (PAT: enabled or PAT: disabled). This is a reference to Intel Performance acceleration technology; there may be BIOS settings which affect this aspect of memory timing.
This information, if available to the program, can be displayed via a menu option.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
6. If all of the above fail, the only left to do is replace your processor as it is faulty.
Regards,
Patrick
