WHEA_UNCORRECTABLE_ERROR is Windows stop code 0x00000124 (0x124). Unlike most blue screens, which Microsoft traces mainly to drivers, this one is defined as hardware from the first line: it "indicates that a fatal hardware error has occurred," using error data from the Windows Hardware Error Architecture (WHEA). Microsoft says it is "typically related to physical hardware failures," possibly heat-related, and it names three things to try: turn off over-clocking if it is on, make sure cooling such as fans works, and run diagnostics to confirm memory is not defective. A driver is possible but, in Microsoft's words, "less likely."
This page follows the Microsoft Learn article "Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR," read on 12 October 2026 and checked against the Microsoft Docs source file. Microsoft labels it as written for programmers and sends customers to https://www.windows.com/stopcode. We stay inside what the page says; where it is silent, we tell you.
What is WHEA?
The Windows Hardware Error Architecture is the Windows framework this bug check takes its error data from. The 0x124 page does not describe it in full; it links Microsoft's separate WHEA documentation. What it does explain is the record: when a hardware error occurs, Microsoft says, WHEA creates an error record describing it. The Windows kernel attaches that record to the hardware error event it raises, "so that the error record is saved in the system event log." The record format follows the Common Platform Error Record in the UEFI specification.
That last point is the practical one. Even if you cannot read a crash dump, the error that caused 0x124 should leave a trace in the System log.
What does Microsoft say causes 0x124?
The "Cause" section is short enough to summarise almost line by line:
- typically physical hardware failures
- it can be heat related
- or the result of defective hardware, memory, or even a processor that is beginning to fail or has failed
- it is "less likely, but possible," that a driver is causing the hardware to fail with this bug check
Microsoft also notes a version detail: this bug check is not used before Windows Vista. Older systems reported machine check exceptions as bug check 0x9C instead.
The three things Microsoft says to try
The same section gives three actions. They are listed here in the page's order, with nothing added.
- Disable over-clocking. "If over-clocking has been enabled, try disabling it." Microsoft does not say how; that depends on your PC or motherboard maker's firmware settings.
- Check cooling. "Confirm that any cooling systems such as fans are functional."
- Test memory. "Run system diagnostics to confirm that the system memory isn't defective."
For step 3, Microsoft's page for another stop code, Bug Check 0x50 (https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area), describes Windows Memory Diagnostics: open Control Panel, type Memory in the search box, select Diagnose your computer's memory problems, and after the test read the MemoryDiagnostics-Results entry in the Event Viewer System log. That procedure comes from the 0x50 page, not the 0x124 page.
What does parameter 1 tell you?
Parameter 1 identifies the type of error source that reported the problem. Parameter 2 is always the address of the WHEA error record. Parameters 3 and 4 are reserved for most values; the exceptions are noted below.
| Parameter 1 | Error source (Microsoft Learn) |
|---|---|
| 0x0 | A machine check exception occurred (parameters 3 and 4 hold the high and low 32 bits of the MCi_STATUS register for the failing bank) |
| 0x1 | A corrected machine check exception occurred |
| 0x2 | A corrected platform error occurred |
| 0x3 | A nonmaskable interrupt (NMI) error occurred |
| 0x4 | An uncorrectable PCI Express error occurred |
| 0x5 | A generic hardware error occurred |
| 0x6 | An initialization error occurred |
| 0x7 | A BOOT error occurred |
| 0x10 | Device driver error source |
| 0x11, 0x12 | Arm Synchronous External Abort; Arm SError Interrupt |
Microsoft's table has more rows: 0x8 for scalable coherent interface errors, 0x9 to 0xB for Itanium-based systems, and 0xC to 0xF for other error source types (including baseboard management controller and persistent memory sources). We left those out of the table because they rarely apply to a home PC, but the Microsoft page lists them all.
Two rows carry extra detail on Microsoft's page. For 0x0, the machine check exception, parameters 3 and 4 are not reserved: they hold the two halves of the MCi_STATUS register for the MCA bank that had the error, and Microsoft says these descriptions apply to x64 processors and to x86 processors with the MCA feature. For 0x9, an Itanium-only value, parameters 3 and 4 give the length and address of the SAL log. Beyond that, Microsoft names the source and stops; it does not tell you which part to replace for each value.
Where to find parameter 1
Microsoft's general page on blue screen data says the bug check event in the Windows system log lists all four stop code parameters. Open Event Viewer, then Windows Logs, System, and find the entry at the time of the crash. Because WHEA also writes its error record to the system event log, look at the entries just before the bug check as well.
Checklist
- Stop code and all four parameters, especially parameter 1
- Is any over-clocking enabled, by you or by a "game" or "performance" profile?
- Are all fans spinning, and are vents clear of dust?
- Did the crash happen under heavy load: gaming, rendering, long compiles?
- Memory diagnostics run, and the MemoryDiagnostics-Results entry read
- Any hardware added or moved recently: memory, graphics card, drive
Microsoft does not list "under heavy load" as a check. We include it because the page names heat as a possible cause, and the timing of a crash is free information to record.
For developers
Microsoft says identifying a specific cause normally requires understanding the WHEA_ERROR_RECORD structure. The page lists the tools:
!analyzefor the summary- `!errrec ` with parameter 2 to display the WHEA error record
!wheaand!errpktfor more WHEA information
The page also points to Microsoft's WHEA documentation and to the WHEA_ERROR_RECORD reference for the record layout.
Which part to replace. Microsoft names the error source but does not map values to specific parts, and we will not guess.
How current is the page this follows?
Microsoft's source file for Bug Check 0x124 carries a documentation date of 12 December 2022. That date is published in the file itself, not an estimate by us, and it sets the shape of this article: where the page says nothing about newer processor families or firmware behaviour, neither do we. Read together with the pre-Vista boundary above, it tells you the window the official text actually covers.
"Corrected" sources under an uncorrectable stop code
Four entries in the parameter 1 table are labelled corrected: 0x1, 0x2, 0xA and 0xB. Microsoft lists them without saying why a corrected condition can still end in a fatal bug check, and we are not going to fill that gap by guessing. If your parameter 1 is one of those four, the honest reading is narrow - the type of error source is known; the reason this particular event was fatal is not stated on the page.
Sources and how to check
- Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x124---whea-uncorrectable-error
- Bug Check 0x50 (Memory Diagnostics steps), Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x50--page-fault-in-nonpaged-area
- Analyze bug check (stop code error) data, Microsoft Learn: https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/blue-screen-data
- Troubleshoot blue screen errors (for regular users): https://www.windows.com/stopcode
- Source: Microsoft Learn, as of 12 October 2026. Checked against the Microsoft Docs source files (MicrosoftDocs/windows-driver-docs). Microsoft documentation is licensed under Creative Commons Attribution 4.0 (CC BY 4.0); this article adapts and summarises it with credit to Microsoft and links to the originals. Microsoft does not endorse this site.
Questions readers ask about WHEA_UNCORRECTABLE_ERROR Blue Screen 0x124
What is stop code 0x124?
It is WHEA_UNCORRECTABLE_ERROR (0x00000124). Microsoft says a fatal hardware error occurred, reported through the Windows Hardware Error Architecture.
Is WHEA_UNCORRECTABLE_ERROR always hardware?
Microsoft says it is typically related to physical hardware failures, and that a driver causing it is less likely but possible.
What does Microsoft tell you to try?
Disable over-clocking if it is enabled, confirm cooling such as fans works, and run diagnostics to confirm system memory is not defective.
What does parameter 1 mean?
The type of error source, for example 0x0 machine check exception or 0x4 uncorrectable PCI Express error. Parameter 2 is the address of the WHEA error record.
Is the error saved anywhere?
Yes. Microsoft says the WHEA error record is included with the hardware error event, so it is saved in the system event log.