0x00000124 WHEA_UNCORRECTABLE_ERROR – Causes, Diagnosis and Troubleshooting

Quick Answer

0x00000124 WHEA_UNCORRECTABLE_ERROR is a Windows Blue Screen of Death (BSOD) error indicating that the Windows Hardware Error Architecture (WHEA) has reported a fatal hardware error that the system cannot recover from.

This error is commonly associated with processor problems, defective RAM, motherboard faults, overheating, unstable power delivery, PCI Express devices or hardware instability caused by overclocking. In some cases, firmware, BIOS or device-driver issues may also contribute.

To troubleshoot this error, restore default BIOS settings, disable overclocking, check system temperatures, run manufacturer hardware diagnostics, test memory, inspect Windows hardware error logs and update relevant drivers and firmware where appropriate.

Important: This stop code does not identify a particular defective component by itself. The underlying hardware error record and system diagnostics are needed to determine the actual cause.

1. What Is WHEA_UNCORRECTABLE_ERROR?

WHEA_UNCORRECTABLE_ERROR is a Windows stop error associated with the Windows Hardware Error Architecture (WHEA). Windows uses WHEA to collect, process and report hardware error information provided by the processor, system firmware and other hardware components.

When a hardware component reports an error that cannot be corrected or safely recovered from, Windows may stop operating and display a Blue Screen of Death to prevent further system damage or data corruption.

The error is identified by the bug check code 0x00000124, also known as Bug Check 0x124.

WHEA supports different hardware error sources, including:

• Processor machine check exceptions.
• Memory-related hardware errors.
• Chipset and motherboard error signals.
• PCI Express bus and device errors.
• Hardware errors reported through system firmware.

The error can occur on Windows 10 and Windows 11 systems, as well as supported Windows Server environments.

2. What Causes Error 0x00000124?

This error is generally associated with hardware-level problems. However, the exact cause depends on the hardware error information reported to Windows.

2.1 Processor (CPU) Problems

A processor can report hardware errors when it encounters internal faults, unstable operating conditions or problems involving its cache, execution units or communication with other components.

Possible contributing factors include:

• A defective or deteriorating processor.
• Unstable CPU operating voltage.
• Excessive processor temperature.
• CPU overclocking or undervolting instability.
• Incorrect motherboard firmware settings.

2.2 Faulty or Unstable RAM

Defective memory modules or unstable memory configurations can contribute to hardware-related system failures.

Possible memory-related issues include:

• Defective RAM modules.
• Incorrect memory timings or voltage.
• Unstable XMP or EXPO memory profiles.
• Improperly installed memory modules.
• Motherboard memory-slot problems.

Memory problems do not always produce this specific stop code. Memory testing and hardware error records should be used to investigate them.

2.3 Motherboard or Chipset Problems

The motherboard connects the processor, memory, storage devices and expansion cards. A motherboard fault can affect communication between these components or cause unstable power delivery.

Potential problems include:

• Defective motherboard components.
• Faulty voltage regulation circuitry.
• Chipset-related hardware errors.
• Damaged CPU socket or motherboard connections.
• Incorrect or outdated BIOS firmware.

2.4 Overheating

Excessive heat can cause hardware instability, particularly when the processor or other critical components operate outside their supported thermal conditions.

Common contributing factors include:

• Dust accumulation inside the computer.
• Non-functional cooling fans.
• Improperly installed CPU coolers.
• Insufficient airflow inside the cabinet.
• Degraded thermal interface material.
• Cooling system failures.

2.5 Power Supply Problems

An unstable or failing power supply unit (PSU) can cause unexpected system instability, particularly when the processor and graphics card operate under heavy workloads.

Possible issues include insufficient power capacity, unstable power delivery, damaged cables or a failing PSU.

Power-related problems should be investigated through appropriate hardware testing rather than assumed solely from the stop code.

2.6 Graphics Card and PCI Express Problems

A graphics card or another PCI Express device can report hardware errors through the system's hardware error reporting mechanisms.

Possible contributing factors include:

• Defective graphics hardware.
• PCI Express communication errors.
• Improperly seated expansion cards.
• Damaged PCI Express slots.
• Unstable GPU overclocking.
• Power delivery problems affecting the graphics card.

2.7 BIOS, Firmware and Driver Issues

BIOS and firmware control important hardware initialization and communication functions. Incorrect firmware settings, compatibility problems or firmware defects can contribute to system instability.

Device drivers may also contribute to some hardware-related failures, although a 0x124 error should not automatically be treated as a conventional driver problem.

3. Common Symptoms of WHEA_UNCORRECTABLE_ERROR

Users experiencing this error may notice one or more of the following symptoms:

• Windows suddenly displays a Blue Screen of Death.
• The computer restarts automatically.
• The system crashes during gaming or other demanding applications.
• Unexpected restarts occur under heavy CPU or GPU workloads.
• The computer freezes before displaying the stop error.
• Repeated crashes occur after enabling overclocking or changing BIOS settings.
• Windows becomes unstable after a hardware upgrade.
• Hardware error events appear in Windows Event Viewer.

The error may occur occasionally or repeatedly. The timing and circumstances of each crash can provide useful clues during diagnosis.

4. Understanding Bug Check Parameters

The Windows bug check documentation defines several parameters for error 0x00000124. These parameters help technical professionals identify the type of hardware error reported to Windows.

The four parameters are:

• Parameter 1: Identifies the hardware error source or type.
• Parameter 2: Contains the address of the WHEA error record.
• Parameter 3: May contain the high 32 bits of the processor machine-check status register for applicable processor errors.
• Parameter 4: May contain the low 32 bits of the processor machine-check status register for applicable processor errors.

For applicable x86/x64 machine-check errors, Parameter 1 commonly has a value of 0x0. Other values identify different hardware error sources.

Some documented Parameter 1 values include:

Parameter 1	Error source
0x0	Machine Check Exception.
0x1	Corrected Machine Check Exception.
0x2	Corrected platform error.
0x3	Nonmaskable interrupt (NMI) error.
0x4	Uncorrectable PCI Express error.
0x5	Generic hardware error.
0x6	Hardware initialization error.
0x7	Hardware boot error.
0x8	Scalable Coherent Interface generic error.
0x12	Arm SError Interrupt.

Note: These values identify error categories, not necessarily the defective physical component. For example, a Machine Check Exception does not automatically mean that the CPU itself is defective. The associated error record must be examined for additional details.

5. How to Fix 0x00000124 WHEA_UNCORRECTABLE_ERROR

Follow the troubleshooting methods below in order. Start with non-invasive checks before making BIOS changes, removing hardware or replacing components.

Method 1: Restart the Computer and Check for Recurring Errors

If the error occurs only once, restart the computer and observe whether Windows operates normally.

1. Allow Windows to restart after the blue screen.
2. Check whether the computer boots successfully.
3. Use the computer normally and observe whether the error returns.
4. Note which application or activity was running before the crash.

If the system repeatedly crashes, avoid continuing normal workloads until the hardware has been investigated. Back up important files whenever Windows remains accessible.

Method 2: Disable CPU and GPU Overclocking

Overclocking increases component operating frequencies beyond their standard specifications. Unstable overclocking or undervolting configurations can cause hardware errors.

If CPU, GPU or memory overclocking is enabled, restore the components to their supported default operating settings.

1. Restart the computer.
2. Enter the BIOS or UEFI setup using the appropriate motherboard or computer manufacturer's instructions.
3. Locate CPU overclocking, voltage and frequency settings.
4. Disable manually configured CPU overclocking and undervolting.
5. Disable XMP or EXPO memory profiles temporarily if memory instability is suspected.
6. Save the changes and restart Windows.

If GPU overclocking software is installed, restore the graphics card to its default settings as well.

Important: BIOS menus differ between manufacturers. Do not randomly change CPU voltage, memory voltage or other advanced settings. If the computer is managed by an organization or uses customized firmware settings, consult the system administrator before changing them.

Method 3: Check CPU Temperature and Cooling

Overheating can contribute to processor instability and hardware-related system failures.

1. Check whether the CPU cooling fan or liquid-cooling system is operating correctly.
2. Inspect the cabinet for excessive dust accumulation.
3. Check that the computer has adequate ventilation.
4. Use a reputable hardware monitoring utility or the manufacturer's diagnostic software to observe CPU temperatures.
5. Compare the reported temperatures with the processor manufacturer's specifications.

If temperatures exceed the supported operating range, investigate the cooling system before continuing demanding workloads.

Do not open a power supply unit or touch internal components while the computer is connected to electrical power.

Method 4: Run Manufacturer Hardware Diagnostics

Hardware diagnostic utilities can help identify problems with the processor, memory, storage, motherboard and other components.

Many computer manufacturers provide built-in diagnostics through BIOS, UEFI or a pre-boot diagnostic environment.

1. Restart the computer.
2. Open the manufacturer's diagnostic environment using the appropriate startup key or boot menu.
3. Select the available hardware diagnostic tests.
4. Run the processor, memory and other relevant tests.
5. Record any diagnostic error codes or failure messages.

For branded computers, use the official support and diagnostic tools provided by the manufacturer.

For custom-built systems, consult the motherboard, processor and component manufacturers for suitable diagnostic utilities.

A diagnostic test that passes does not completely rule out intermittent hardware problems.

Method 5: Test System Memory (RAM)

Defective or unstable RAM can contribute to system crashes. Windows Memory Diagnostic provides a built-in method for checking memory.

1. Press Windows + R.
2. Type mdsched.exe.
3. Press Enter.
4. Select Restart now and check for problems after saving your work.
5. Allow the memory test to complete.
6. After Windows restarts, check the diagnostic result.

If memory errors are detected, further testing may be required to identify the defective memory module or motherboard slot.

For advanced testing, a suitable bootable memory-testing utility may be used according to its official instructions.

Important: Before physically removing or reseating RAM, shut down the computer, disconnect its power source and follow the manufacturer's service instructions. If the system is under warranty, use authorized service support where appropriate.

Method 6: Check Windows Event Viewer for Hardware Errors

Windows Event Viewer stores hardware-related events that may help identify the source of the crash.

1. Press Windows + X.
2. Select Event Viewer.
3. Expand Windows Logs.
4. Select System.
5. Look for events recorded around the time of the blue screen.
6. Check entries from sources such as WHEA-Logger.
7. Open relevant events and examine their General and Details information.

Pay attention to the following information where available:

• Event timestamp.
• Error source.
• Processor or hardware identification.
• Reported error type.
• Memory or PCI Express information.
• Other hardware error record details.

Some systems may report WHEA-Logger Event ID 18 for a fatal hardware error. Other event IDs and descriptions may also be relevant depending on the hardware and error source.

Do not assume that every WHEA-Logger event indicates a defective CPU. Interpret the event details in the context of the complete error record and system configuration.

Method 7: Update Windows and Relevant Device Drivers

Outdated or incompatible drivers can contribute to system instability. Microsoft recommends using Windows Update as an initial method for obtaining recommended driver updates.

1. Open Windows Settings.
2. Navigate to Windows Update.
3. Select Check for updates.
4. Install relevant available updates.
5. Check the manufacturer's support website for applicable chipset, graphics and other device drivers.
6. Restart the computer.

For optional driver updates, check whether the update is appropriate for the exact hardware model and Windows version.

Avoid installing drivers from unknown third-party websites or using automated driver packages from untrusted sources.

Method 8: Check for BIOS and UEFI Firmware Updates

BIOS or UEFI firmware controls hardware initialization and provides communication between the operating system and system components.

A firmware update may resolve documented compatibility, stability or hardware-management problems.

1. Identify the exact computer or motherboard model.
2. Visit the official manufacturer's support website.
3. Check the available BIOS or UEFI updates.
4. Read the release notes and installation instructions.
5. Confirm that the update applies to the exact hardware revision.
6. Follow the manufacturer's firmware update procedure.

Warning: An interrupted or incorrect BIOS update can make a computer unbootable. Ensure stable power during the update and do not install firmware intended for another motherboard or system model. If the computer is stable and no relevant firmware issue is documented, a BIOS update should not be performed without a clear reason.

Method 9: Check Windows System Files

Although this stop code is generally associated with hardware errors, checking Windows system files may be useful when crashes started after software changes or Windows corruption is also suspected.

Open Command Prompt or Windows Terminal as an administrator and execute the following command:

sfc /scannow

System File Checker scans protected Windows system files and attempts to repair corrupted files using available repair sources.

If Windows reports that component-store corruption needs repair, run the following DISM command from an elevated terminal:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, run System File Checker again:

sfc /scannow

Restart Windows and observe whether the problem continues.

Note: These commands repair Windows component and system-file problems. They cannot repair a physically defective CPU, RAM module, motherboard or other hardware component.

Method 10: Inspect Hardware Connections

Loose or improperly connected hardware can contribute to system instability.

If you have the required technical experience and the computer manufacturer's service instructions permit it, inspect the following components:

• RAM modules and memory slots.
• Graphics card seating and power connections.
• CPU cooling assembly.
• Motherboard power connectors.
• Storage device connections.
• Visible signs of physical damage or overheating.

Shut down the computer and disconnect it from electrical power before inspecting internal components. Follow appropriate electrostatic discharge precautions.

Do not remove the processor or dismantle complex cooling systems unless you have the necessary expertise. For laptops and warranty-covered systems, use authorized service support.

Method 11: Use System Restore or Windows Recovery

If the error started after a recent driver installation, Windows update or software configuration change, Windows recovery options may help restore the previous working state.

Where available:

1. Open Windows Settings.
2. Navigate to System > Recovery.
3. Check whether System Restore is available through the recovery options.
4. Select a restore point created before the problem started.
5. Review the changes before confirming the restoration.

If Windows cannot start normally, access Windows Recovery Environment and use the available Startup Repair or System Restore options.

System Restore does not repair defective hardware. It is appropriate only when a recent software or configuration change may be contributing to the problem.

6. Advanced Troubleshooting Using Crash Dump Analysis

If the error continues after basic troubleshooting, analyzing the Windows crash dump can provide more detailed information about the reported hardware error.

6.1 Locate the Crash Dump File

Windows may save crash information in the following locations:

• C:\Windows\Minidump\ – Contains small memory dump files when configured and generated.
• C:\Windows\MEMORY.DMP – May contain a larger kernel or complete memory dump, depending on system configuration.

These files are useful for advanced diagnosis. Their availability depends on the Windows dump configuration, available disk space and whether the crash dump was successfully written.

6.2 Analyze the Dump Using WinDbg

WinDbg is a Microsoft debugging tool that can analyze Windows crash dumps and display bug check information.

1. Install WinDbg from Microsoft's official distribution channel.
2. Start WinDbg.
3. Open the relevant crash dump file.
4. Allow the debugger to load the required symbols.
5. Enter the following command in the debugger command window:

!analyze -v

This command displays detailed bug check analysis and related diagnostic information.

For a 0x124 error, the WHEA error record may provide additional information about the reported hardware problem.

If the address of the WHEA error record is available as Parameter 2, the following debugger extension can be used:

!errrec <WHEA_ERROR_RECORD_ADDRESS>

Replace the example value with the actual address reported in the applicable debugging context.

Additional WHEA debugger extensions, including !whea and !errpkt, may provide further information depending on the dump and debugging environment.

Microsoft's debugging documentation should be consulted when interpreting processor-specific error records and machine-check information.

Important: Dump analysis requires technical knowledge. A reported processor, cache, memory or PCI Express error category is diagnostic evidence, not always conclusive proof that the named component must be replaced.

7. When Should You Suspect Hardware Failure?

Hardware failure becomes a stronger possibility when the error repeatedly occurs despite restoring default settings, checking drivers and installing relevant updates.

Consider professional hardware testing when:

• Manufacturer diagnostics report a hardware failure.
• Memory testing repeatedly detects errors.
• WHEA error records repeatedly report similar hardware errors.
• The computer crashes during different operating systems or independent workloads.
• System instability continues with overclocking disabled.
• There are signs of overheating, physical damage or unstable power delivery.
• The computer repeatedly crashes during startup or even when idle.

Depending on the diagnostic findings, a technician may need to test the processor, memory modules, motherboard, power supply or PCI Express devices individually.

Do not replace expensive components solely because the screen displays WHEA_UNCORRECTABLE_ERROR.

8. How to Prevent WHEA_UNCORRECTABLE_ERROR

Although not every hardware failure can be prevented, the following practices can reduce the likelihood of system instability.

• Keep Windows and supported device drivers updated.
• Use stable CPU, GPU and memory settings.
• Avoid unsupported overclocking and undervolting configurations.
• Maintain proper cooling and cabinet ventilation.
• Clean dust from the cooling system periodically using appropriate methods.
• Use a reliable and adequately rated power supply.
• Install BIOS and firmware updates only when applicable and justified.
• Use compatible memory and expansion components.
• Monitor recurring WHEA hardware error events.
• Back up important data regularly.

9. Frequently Asked Questions (FAQs)

Q1. Is WHEA_UNCORRECTABLE_ERROR a hardware or software problem?

It primarily indicates a fatal hardware error reported through Windows Hardware Error Architecture. Hardware components, firmware, unstable operating settings and, less commonly, driver-related issues may contribute. Further diagnosis is necessary to identify the underlying cause.

Q2. Does error 0x00000124 mean my processor is damaged?

No. Although processor-related machine check exceptions are a common category of this error, the stop code can also involve memory, motherboard, PCI Express devices and other hardware error sources. Examine the WHEA error record before identifying a defective component.

Q3. Can faulty RAM cause WHEA_UNCORRECTABLE_ERROR?

Yes. Defective or unstable memory can contribute to hardware-related crashes. Run Windows Memory Diagnostic or an appropriate memory-testing utility and investigate any reported errors.

Q4. Can overheating cause error 0x00000124?

Yes. Excessive heat can contribute to hardware instability, including processor-related errors. Check the cooling system, airflow and component temperatures against manufacturer specifications.

Q5. Can a Windows update fix WHEA_UNCORRECTABLE_ERROR?

It may help when the issue is associated with a driver, firmware compatibility problem or a software-related defect addressed by an update. However, Windows updates cannot repair physically defective hardware.

Q6. Is it safe to continue using a computer showing this error?

Occasional errors should still be investigated. If the computer repeatedly crashes, overheats or shows hardware diagnostic failures, stop demanding workloads and arrange appropriate hardware testing. Back up important data whenever possible.

Q7. Can resetting BIOS settings fix this error?

Restoring supported default BIOS settings may resolve instability caused by overclocking, undervolting or incorrect memory configurations. However, it will not repair a physically defective component. Be aware that customized settings, including boot and storage configuration, may change when BIOS defaults are restored.

Q8. What is the difference between WHEA_UNCORRECTABLE_ERROR and MACHINE_CHECK_EXCEPTION?

WHEA_UNCORRECTABLE_ERROR is the Windows bug check code 0x124, which represents a fatal hardware error reported through WHEA. MACHINE_CHECK_EXCEPTION is a separate Windows bug check, commonly identified by code 0x9C, associated with processor machine-check reporting. Both relate to hardware error reporting, but they are not interchangeable error codes.

Q9. Can a faulty power supply cause this blue screen?

An unstable or failing power supply can contribute to system instability. However, the stop code alone cannot confirm a PSU failure. Appropriate power and hardware testing is required.

Q10. Does reinstalling Windows fix WHEA_UNCORRECTABLE_ERROR?

Reinstalling Windows is generally not the first recommended solution because this error is primarily associated with hardware-level failures. A clean installation will not repair defective RAM, a failing processor or a damaged motherboard. Investigate hardware and firmware first.

10. Key Takeaways

The 0x00000124 WHEA_UNCORRECTABLE_ERROR blue screen indicates that Windows has received a fatal hardware error report that it cannot safely recover from.

The most useful troubleshooting approach is to:

1. Restore stable default hardware settings.
2. Disable overclocking and investigate overheating.
3. Run manufacturer hardware diagnostics and memory tests.
4. Review WHEA-Logger events in Event Viewer.
5. Update applicable Windows drivers and firmware.
6. Analyze crash dumps when advanced diagnosis is required.
7. Obtain professional hardware testing when errors continue.

The most important point is to identify the actual hardware error rather than repeatedly applying software fixes. Correct diagnosis helps avoid unnecessary component replacements, protects important data and reduces the risk of further system instability.

11. Official References and Further Reading

The following Microsoft resources provide additional information about this stop code, hardware error reporting and Windows troubleshooting:

• Microsoft Support: How to Fix WHEA_UNCORRECTABLE_ERROR – Recommended troubleshooting steps for Windows 10 and Windows 11.
• Microsoft Learn: Bug Check 0x124 – WHEA_UNCORRECTABLE_ERROR – Technical explanation of bug check parameters, causes and debugger analysis.
• Microsoft Learn: Introduction to Windows Hardware Error Architecture – Explains the Windows hardware error reporting and recovery architecture.
• Microsoft Learn: Hardware Errors and Error Sources – Explains corrected and uncorrected hardware errors and their sources.
• Microsoft Learn: WHEA Error Records – Describes the structure and contents of hardware error records.
• Microsoft Learn: Windows Debugging Documentation – Provides guidance for analyzing Windows crash dumps using debugging tools.