Blue Screen Errors in Windows 11: The Most Common Stop Codes Explained

Softkeyworld Team · 07 November 2026

Quick answer: A Windows 11 blue (now black) screen is a "bug check": Windows stopped itself to prevent damage. The stop code tells you where to look. Most are caused by drivers, faulty RAM or storage, overheating, or a bad update. Note the code and any file named, undo recent changes, update drivers, then run sfc, DISM and a memory test.

Written by the Softkeyworld technical team · Updated October 2026

A stop error is Windows deliberately halting because something running at the kernel level, usually a driver, did something that could corrupt data if the system carried on. That makes the stop code genuinely useful: it's Windows telling you which category of fault occurred and often which driver file was involved. This guide explains the stop codes we see most often on Windows 11 PCs, what each one usually means in practice, and the fix order that resolves the majority of cases without a reinstall.

Key takeaways

  • One crash is rarely worth chasing. Repeated crashes with the same code or file are.
  • Drivers cause most stop errors; graphics, storage, network and security software are the usual suspects.
  • WHEA_UNCORRECTABLE_ERROR and repeated MEMORY_MANAGEMENT errors usually point to hardware, not Windows.
  • Have your BitLocker recovery key ready before running repairs from the recovery environment.

Blue screen or black screen? What changed in Windows 11

If your crash screen was black rather than blue, you're not imagining it. As part of its Windows Resiliency Initiative, Microsoft replaced the classic blue screen with a simplified black "unexpected restart" screen in Windows 11 version 24H2 and later, rolled out from mid-2025. As Tom's Hardware reported, the new design drops the sad face and shows the stop code and, where Windows can identify it, the faulting driver. The underlying stop codes are the same as before, so everything below applies to both screens.

The same initiative introduced Quick machine recovery, which lets a PC stuck in a boot loop fetch fixes from Windows Update while in the recovery environment. You can review it under Settings > System > Recovery > Quick machine recovery; Microsoft's Quick machine recovery page explains the options.

How to find the stop code after the PC restarts

The screen often disappears before you can read it. You can recover the details afterwards:

  1. Reliability Monitor: press Windows + R, run perfmon /rel, and click the red X for the day of the crash. "Windows stopped working" entries show the bug check code and parameters.
  2. Event Viewer: open Windows Logs > System and filter for Event ID 1001 (source BugCheck). Event ID 41 (Kernel-Power) on its own means the PC lost power or reset without a bug check, which points to power or hardware rather than a driver.
  3. Minidump files: look in C:\Windows\Minidump. Install WinDbg from the Microsoft Store, open the newest .dmp file and run !analyze -v. Look for the MODULE_NAME and IMAGE_NAME lines.
  4. Stop auto-restart: to read the screen next time, run sysdm.cpl, open Advanced > Startup and Recovery > Settings and untick Automatically restart.

The most common Windows 11 stop codes

Microsoft's bug check code reference lists hundreds of codes, but a small group accounts for most crashes on home and office PCs.

Stop code Hex Usual cause Try first
IRQL_NOT_LESS_OR_EQUAL 0x0000000A Driver accessing invalid memory; sometimes RAM Update or roll back recent drivers
DRIVER_IRQL_NOT_LESS_OR_EQUAL 0x000000D1 A specific driver, often network or Wi-Fi Reinstall the named .sys driver
PAGE_FAULT_IN_NONPAGED_AREA 0x00000050 Faulty driver, antivirus filter or RAM Remove recent software; test memory
SYSTEM_SERVICE_EXCEPTION 0x0000003B Graphics or third-party kernel drivers Clean-install the GPU driver
KMODE_EXCEPTION_NOT_HANDLED 0x0000001E Incompatible or outdated driver Update drivers from the manufacturer
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x0000007E Driver thread crash, often at boot Safe Mode, remove the named driver
MEMORY_MANAGEMENT 0x0000001A RAM faults, unstable XMP/EXPO, corrupted memory Memory test; disable XMP/EXPO
CRITICAL_PROCESS_DIED 0x000000EF Essential Windows process crashed; corrupted system files or disk SFC, DISM, chkdsk
DPC_WATCHDOG_VIOLATION 0x00000133 Storage controller driver or SSD firmware Update SSD firmware and storage driver
VIDEO_TDR_FAILURE 0x00000116 Graphics driver timed out; GPU overheating or overclock Clean GPU driver install; check temperatures
WHEA_UNCORRECTABLE_ERROR 0x00000124 Hardware error reported by the CPU Remove overclocks; update BIOS; check cooling
INACCESSIBLE_BOOT_DEVICE 0x0000007B Windows can't read the system drive Revert BIOS storage mode; Startup Repair
KERNEL_SECURITY_CHECK_FAILURE 0x00000139 Corrupted kernel data structure, often a driver Update drivers; SFC and memory test
DRIVER_POWER_STATE_FAILURE 0x0000009F Driver mishandling sleep or wake Update chipset, Wi-Fi and USB drivers

What the main stop codes mean in practice

IRQL_NOT_LESS_OR_EQUAL and DRIVER_IRQL_NOT_LESS_OR_EQUAL

Both mean kernel code touched memory it wasn't allowed to at that priority level. The "DRIVER_" variant usually names the culprit on the crash screen, for example a Wi-Fi driver beginning Netwtw or a VPN filter driver. Search the file name to identify the product, then install the latest version from the hardware maker, not a driver-updater utility. If the code appears with different file names every time, suspect RAM instead.

PAGE_FAULT_IN_NONPAGED_AREA

Windows looked for data that must always be in memory and didn't find it. Security software with kernel components is a frequent trigger; this was the stop code widely reported during the July 2024 CrowdStrike incident. If it started after installing antivirus, backup or anti-cheat software, uninstall it and see whether the crashes stop.

MEMORY_MANAGEMENT

Run mdsched.exe (Windows Memory Diagnostic) and choose Restart now and check for problems. A pass doesn't fully rule RAM out, so if crashes continue on a desktop, disable XMP or EXPO memory profiles in the BIOS and test with one stick at a time. This is one of the most common causes we see on newly built gaming PCs.

CRITICAL_PROCESS_DIED

A process Windows can't run without, such as csrss.exe or wininit.exe, terminated. Causes include corrupted system files, a failing drive and, occasionally, an interrupted update. Run the repair commands in the next section and check drive health with the manufacturer's SSD tool.

DPC_WATCHDOG_VIOLATION and VIDEO_TDR_FAILURE

Both are timeouts. DPC_WATCHDOG_VIOLATION often traces back to storage: update your SSD's firmware and chipset or storage drivers. VIDEO_TDR_FAILURE names the graphics driver (nvlddmkm.sys for NVIDIA, atikmpag.sys or amdkmdag.sys for AMD, igdkmd64.sys for Intel). Do a clean driver install, remove GPU overclocks and check temperatures under load.

WHEA_UNCORRECTABLE_ERROR

The processor's hardware error architecture reported a fault it couldn't correct. Software is rarely the cause. Reset BIOS settings to defaults (removing CPU and memory overclocks and undervolts), update the BIOS, check CPU cooling and, if it persists, test the power supply. Persistent WHEA errors on a stock system usually mean a hardware repair.

SYSTEM_SERVICE_EXCEPTION and KMODE_EXCEPTION_NOT_HANDLED

These are generic "a driver threw an error Windows couldn't handle" codes. The value of the crash screen here is the file name: if it shows a third-party .sys file, that product is your lead. If it names a core Windows file such as ntoskrnl.exe, that's usually the messenger rather than the cause, and you'll need WinDbg's !analyze -v output or a pattern across several crashes to find the real driver. Older utilities that install kernel drivers, such as RGB lighting controllers, fan tools and hardware monitors, are frequent offenders after a Windows feature update.

DRIVER_POWER_STATE_FAILURE

This appears when a device driver fails to complete a power transition, typically when going to sleep, waking, or shutting down. Laptops with docking stations, USB hubs and Wi-Fi cards are the classic cases. Update the chipset, Wi-Fi, Thunderbolt and USB drivers from the laptop maker, and as a test, unplug the dock before sleeping. Disabling Fast Startup (Control Panel > Power Options > Choose what the power buttons do) can also help while you investigate.

Crashes during a feature update

If the PC crashes while installing a feature update and then rolls back, Windows Setup usually reports an error such as 0xC1900101. Strictly, that's a setup error rather than a stop code, but it nearly always means a driver failed under the new version. Disconnect non-essential USB devices, update or uninstall storage and security drivers, and try again.

INACCESSIBLE_BOOT_DEVICE

Windows started but lost access to its own drive. Common triggers are changing the SATA mode between AHCI and RAID/RST in the BIOS, cloning to a new SSD, or a storage driver update. Revert any BIOS change first. Otherwise boot into the recovery environment and run Startup Repair. If BitLocker is on, you'll need the recovery key; see our guide to finding your BitLocker recovery key.

A fix routine that works for most stop codes

If the code doesn't point clearly at one component, work through this in order. Use Safe Mode if Windows won't stay up long enough (hold Shift, select Restart, then Troubleshoot > Advanced options > Startup Settings).

  1. Undo the last change. Uninstall recently added software or hardware drivers. For a problem that began after Patch Tuesday, use Settings > Windows Update > Update history > Uninstall updates. Our guide to fixing stuck Windows 11 updates helps if updates themselves are failing.
  2. Update key drivers from the PC or motherboard maker: chipset, storage, graphics, Wi-Fi, and BIOS.
  3. Repair system files in an admin terminal: DISM /Online /Cleanup-Image /RestoreHealth then sfc /scannow.
  4. Check the disk: chkdsk C: /scan, and review SMART health in your SSD vendor's tool.
  5. Test memory with mdsched.exe.
  6. Remove overclocks and check temperatures. Clean dust from fans and heatsinks, especially on laptops. Heat-related instability also shows up as general sluggishness, covered in our Windows 11 performance fixes.
  7. Use System Restore from Troubleshoot > Advanced options if a restore point predates the crashes.
  8. Reinstall as a last resort. If software causes are exhausted, a repair reinstall via Settings > System > Recovery > Fix problems using Windows Update keeps your apps. Beyond that, see how to factory reset Windows 11 without losing your licence.

If Windows won't boot at all, create recovery media on another PC; our guide on how to create a Windows 11 bootable USB shows how, and the USB gives you access to Startup Repair, Command Prompt and System Restore.

When it's time to suspect hardware

  • Crashes continue after a clean reinstall with only Windows Update drivers.
  • The stop code and the named driver change randomly from crash to crash.
  • Crashes only happen under load (gaming, rendering) or when the PC is warm.
  • Event Viewer shows WHEA-Logger warnings even when the PC doesn't crash.

In these cases, test RAM, storage, power supply and cooling individually, or take the machine to a repair shop. Reinstalling Windows repeatedly won't fix a failing component.

Frequently asked questions

Is a blue screen of death dangerous for my PC?

The crash itself is a protective shutdown and doesn't damage hardware. The risk is unsaved work and, with repeated crashes, file-system corruption, so investigate recurring crashes promptly.

Why is my Windows 11 crash screen black instead of blue?

Microsoft redesigned the stop screen for Windows 11 24H2 and later. It shows the same stop codes in a simpler black layout and can name the faulting driver.

Where are blue screen logs stored?

Small memory dumps are saved to C:\Windows\Minidump, and a summary is logged in Event Viewer under Windows Logs > System as Event ID 1001. Reliability Monitor shows them on a timeline.

Can a Windows update cause a blue screen?

Yes, occasionally, usually through a conflict with an existing driver. Uninstall the update from Update history, pause updates briefly and check the Windows release health page for known issues.

Will resetting Windows fix a blue screen?

It fixes software and driver causes, but not faulty hardware. Try the targeted fixes first; reset only when those fail and hardware tests pass.

Do driver updater tools help with stop errors?

We don't recommend them for this. They can install mismatched drivers that cause new crashes. Use Windows Update and your PC or component manufacturer's support site.

Our recommendation

Read the stop code, check for a named driver, and fix the most recent change first; that resolves most cases in under an hour. If you end up rebuilding the PC from scratch, start with a clean, genuine installation rather than a pre-modified ISO, which is a common source of unstable drivers. A Windows 11 Pro licence key activates official Microsoft media on the same hardware for every future reinstall.

Get Windows 11 Pro

Related reading

Resource Why read it
Create a Windows 11 bootable USB Recovery tools for a PC that won't boot
Factory reset Windows 11 and keep your licence The last-resort fix, done safely
Windows 11 update stuck fix Repair update problems that often accompany crashes
Need a genuine licence key? Shop licences