TroubleByteSearch
SOURCE VERIFIEDSource review Sep 7, 2026No hands-on test claimed2 sources

WHEA_UNCORRECTABLE_ERROR in Windows 11

Microsoft describes WHEA_UNCORRECTABLE_ERROR as a stop/blue-screen error that can occur when Windows encounters a hardware error. The safe first path is updates/drivers and recent-change recovery before hardware diagnosis.

AuthorshipWritten and source-reviewed by Mihailo Ivanjac
Record created Sep 7, 2026Last source review Sep 7, 2026Source review only
SymptomWindows restarts with the WHEA_UNCORRECTABLE_ERROR stop code, often described as a blue-screen or black-screen stop error.
Problem familyWindows · Windows
Highest step riskCaution
Editorial statePublic launch · indexed
Affected scope
Windows 11Windows hardwareDevice driversSystem recovery
Start here

Apply Windows and device-driver updates

Install current Windows updates and recommended drivers, note any hardware/device named by the stop error, and undo a recent driver/app/update change with supported recovery options if the crashes began immediately afterward.

  1. Run Windows Update and install current recommended updates/drivers.
  2. If the stop screen identifies a device, use its supported manufacturer driver path.
  3. Restart normally and observe whether the same stop code returns.
  4. Keep a note of any change that affects frequency.

Why this branch first: Microsoft recommends Windows Update and driver updates as early actions for WHEA_UNCORRECTABLE_ERROR.

TroubleByte Tool

Decode the WHEA stop code

Open the reviewed BSOD catalog with WHEA_UNCORRECTABLE_ERROR preselected, then return here for the full troubleshooting path.

Decode WHEA stop code →
Visual diagnosis

TroubleByte diagnostic path

01
Capture

Record stop code and module.

02
Update

Apply supported Windows/driver updates.

03
Recent change

Rollback or remove the triggering change.

04
Hardware

Escalate persistent evidence to diagnostics.

Original TroubleByte diagnostic map. It summarizes the cited troubleshooting order; it is not a vendor screenshot.

Diagnosis

What this usually means

WHEA stands for Windows Hardware Error Architecture, and Microsoft frames this stop code as a hardware-error condition. That does not prove which component is faulty; the useful evidence is repetition pattern, recent changes, named devices/drivers and Windows crash data.

What the evidence establishes

What we verified from the source material

Microsoft explicitly describes WHEA_UNCORRECTABLE_ERROR as a hardware-error stop condition and recommends Windows/driver updates, supported recovery after recent changes and general stop-code troubleshooting when the error persists.

Before you change anything

Prerequisites and checks

Prepare first

  • Record the stop code and any named module/device.
  • Preserve recovery options before making firmware or driver changes.
  • Disconnect newly added nonessential hardware only when it can be done safely.

Checks that prevent the wrong fix

  • Record the exact stop code and any “What failed” module name.
  • Note whether the issue began after new hardware, a driver, Windows update or application change.
  • Check Windows Update for current system and recommended driver updates before using third-party driver tools.
Scope

Applies to

✓ Windows 11✓ Windows hardware✓ Device drivers✓ System recovery
Troubleshooting path

Solutions, in order

01
SAFE · START HERE

Apply Windows and device-driver updates

  1. Run Windows Update and install current recommended updates/drivers.
  2. If the stop screen identifies a device, use its supported manufacturer driver path.
  3. Restart normally and observe whether the same stop code returns.
  4. Keep a note of any change that affects frequency.

Why this can work: Microsoft recommends Windows Update and driver updates as early actions for WHEA_UNCORRECTABLE_ERROR.

02
CAUTION

Undo recent changes and escalate hardware evidence

  1. If the crashes began after a recent driver/app/update, use supported System Restore or Startup Repair where appropriate.
  2. Remove newly added hardware for a controlled test when safe to do so.
  3. Preserve dump/event information if crashes persist.
  4. Escalate to hardware diagnostics when the same WHEA error continues after software recovery.

Why this can work: Microsoft recommends recovery options for recent changes and broader stop-code troubleshooting when the error persists.

Verification

How to know the fix actually worked

  1. Windows runs through normal workloads without repeating the same stop code.
  2. If hardware was isolated, the failure pattern changes consistently when the suspect component is removed or repaired.

Do not count a temporary disappearance of the symptom as a confirmed fix if the problem normally returns after a restart, reconnect or several minutes of use.

Stop conditions

When not to keep changing things

  • Repeated WHEA errors after updates and controlled rollback are a reason to stop random software changes and move to hardware/crash-dump diagnosis.

Escalation: If the stop code repeats after supported software recovery and updates, preserve crash dumps/logs and proceed to hardware diagnostics or professional service rather than repeatedly reinstalling drivers at random.

Evidence

Sources used for this record

Primary · checked Sep 7, 2026Microsoft — How to fix WHEA_UNCORRECTABLE_ERRORFirst-party documentation used to verify the troubleshooting scope and steps.Corroborating · checked Sep 7, 2026Microsoft — Troubleshooting Windows unexpected restarts and stop code errorsFirst-party documentation used to verify the troubleshooting scope and steps.
Who reviewed this

Mihailo Ivanjac

This record was written and source-reviewed by Mihailo Ivanjac. Source review means the cited documentation was checked against the troubleshooting order on this page; it does not imply a hands-on reproduction unless the page explicitly says so.

Author profile and editorial scope →
Community troubleshooting

Discuss this exact problem

Share what happened on your system, ask a focused follow-up question, or add evidence that may help someone with the same symptom. Community posts are separate from TroubleByte editorial verification.

Before posting Do not include passwords, API keys, recovery codes, private IP addresses or other secrets. TroubleByte automatically attaches only coarse OS, browser and device-class context. Your full Browser & System Info report is not uploaded automatically.
Start a discussion
Posts are public. Guest identity is pseudonymous and browser-specific.

Loading community discussions…
Keep diagnosing

Related Windows problems

WindowsEthernet not working in Windows 11A wired connection can fail because of the cable, router port, ISP path, disabled or unhealthy Ethernet adapter, bad IP configuration, VPN/proxy software, or a driver problem. The useful first split is whether another device can use the same router and whether Windows sees the Ethernet link at all.WindowsExternal monitor not detected in Windows 11An external display can disappear because of projection mode, a bad cable or adapter, dock conflicts, the monitor input, or display-driver state. The efficient path proves the physical connection first, then checks Windows display detection and only later changes drivers.WindowsFile Explorer won’t open in Windows 11When File Explorer refuses to open or start, Microsoft recommends beginning with Windows Update and a normal restart before escalating to broader system repair. The failure can be transient, update-related, or tied to damaged system components rather than one folder or drive.
Change log

Revision history

Show 1 recorded revision

2026-09-07 — Created for the v0.8 content-scale pass from current first-party documentation; held noindex for editorial review.