Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Blue screens & stop codes · scoped error record
WHEA_UNCORRECTABLE_ERROR

WHEA_UNCORRECTABLE_ERROR: treat it as a hardware-oriented stop code

Microsoft identifies WHEA_UNCORRECTABLE_ERROR as a hardware error path; start with updates/drivers and recovery around recent changes.

Applies to: Windows 11 stop-code contextReviewed: 2026-09-17

What it means in this context

Microsoft’s current support page describes WHEA_UNCORRECTABLE_ERROR as a stop error that occurs when a hardware error is detected. Software steps can still matter—especially drivers and recent changes—but the error should not be framed as ordinary app corruption.

Start here
  1. Record the exact stop code and when it began.
  2. Install current Windows updates and recommended drivers.
  3. If a new driver or app preceded the error, preserve that timeline.
  4. Do not overclock or continue unstable firmware/hardware settings while diagnosing.
1

Update Windows and hardware drivers

Low risk

Why: Microsoft lists Windows Update and driver update among the first actions for this stop code.

  1. Open Settings > Windows Update and install current updates.
  2. Review relevant driver updates.
  3. Use the manufacturer’s current driver when a device-specific driver is required.
2

Use restore or startup recovery when a recent change is the trigger

Medium risk

Why: Microsoft points to System Restore or Startup Repair when a recent update, driver or app change may be responsible.

  1. Use Windows Recovery options that match the recent change.
  2. Prefer the least destructive recovery route first.
  3. Retest before making additional changes.
Scope boundary

When not to use this record

If hardware diagnostics fail, the PC is overheating, or the error persists across clean driver/software states, move to hardware service rather than endless Windows repair.

If it persists

Use manufacturer diagnostics for memory, CPU, motherboard, storage and power-related hardware as appropriate to the machine.

Evidence

Reviewed source

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

Error0x00000050 — PAGE_FAULT_IN_NONPAGED_AREA: invalid system memory was referenced

Microsoft defines bug check 0x50 as an invalid system-memory reference; driver and memory evidence matter.

Error0x0000007E — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: an unhandled kernel thread exception

Bug check 0x7E means a system thread generated an exception that the error handler did not catch.

Error0x0000009F — DRIVER_POWER_STATE_FAILURE: driver stuck in a power transition

Microsoft defines bug check 0x9F as a driver in an inconsistent or invalid power state.

Error0x000000D1 — DRIVER_IRQL_NOT_LESS_OR_EQUAL: a kernel driver made an invalid high-IRQL memory access

Microsoft describes bug check 0xD1 as a kernel-mode driver accessing pageable or invalid memory at an IRQL that was too high.

Error0x00000116 — VIDEO_TDR_FAILURE: Windows could not recover the display driver after a GPU timeout

Bug check 0x116 occurs when Windows attempts to reset the display driver after a timeout and recovery fails.

ErrorEvent ID 1001 — WER-SystemErrorReporting bugcheck: preserve the stop code and dump path

When Event ID 1001 says the computer rebooted from a bugcheck, the useful evidence is the exact bugcheck code, parameters and saved dump.