ERROR_UNWIND 0X0000021E: Exception unwind code in Windows 10/11 fixes

When does this error hit?

You're working fine, then suddenly—blue screen. The error code is 0X0000021E (STATUS_UNWIND). I've seen it most often right after a Windows Update reboot, or when plugging in a new device (like a USB-to-Ethernet adapter or external GPU). It can also show up if you're running an older driver on Windows 11 22H2 or 23H2. One user reported it after installing a third-party antivirus that tried to hook into the kernel.

What's actually going on?

The Windows kernel uses exception handling to manage crashes and errors. When a driver or system component triggers an exception, the kernel tries to “unwind” the stack—basically roll back function calls to a safe point. If that unwind process fails (bad stack state, corrupted handler, or a driver that doesn't follow the rules), you get ERROR_UNWIND. The root cause is almost always a driver that's buggy or incompatible with your current Windows build. Rarely, it's a corrupt system file.

Fix 1: Boot into Safe Mode and check drivers

Safe Mode loads minimal drivers. If the error stops, you've confirmed a driver culprit.

1. Restart your PC and press F8 (or hold Shift + Restart from the login screen) to enter recovery.
2. Choose Troubleshoot > Advanced Options > Startup Settings > Restart.
3. Press 4 or F4 for Safe Mode.
4. Once in Safe Mode, open Device Manager (devmgmt.msc).
5. Look for devices with a yellow exclamation mark. Right-click and update the driver, or uninstall it if you suspect it's the problem.
6. Pay special attention to network adapters, graphics cards, and USB controllers—common offenders.

If you can't even boot to Safe Mode, skip to Fix 4 below.

Fix 2: Run SFC and DISM to repair system files

Corrupted system files can break the unwind mechanism. I've fixed this exact error twice with SFC alone.

1. Open Command Prompt as admin (cmd from Start > right-click > Run as administrator).
2. Run sfc /scannow. Let it finish—this can take 15-30 minutes.
3. If SFC finds errors but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth.
4. Reboot after DISM completes, then run SFC again.

Pro tip: If DISM fails, make sure you're connected to the internet—it downloads replacement files from Windows Update.

Fix 3: Update or roll back drivers using Driver Verifier

Driver Verifier stresses drivers to find the bad one. It's a blunt tool but works.

1. Open Command Prompt as admin.
2. Type verifier and press Enter.
3. Select Create standard settings > Automatically select all drivers installed on this computer.
4. Restart. The system will run slower under the verifier. If it crashes, the blue screen will name the offending driver (e.g., xyz.sys).
5. Once identified, update that driver from the manufacturer's site, or roll back to a previous version in Device Manager.
6. After fixing, run verifier /reset in Command Prompt to turn off verifier.

Warning: Don't run Verifier on a production machine without a backup—it can force crashes every few minutes.

Fix 4: System Restore or Reset as last resort

If nothing else works, roll back to before the error started.

1. Boot into recovery (Shift + Restart from login).
2. Choose Troubleshoot > Advanced Options > System Restore.
3. Pick a restore point dated before the first BSOD.
4. If no restore points exist, select Reset this PC and choose Keep my files.

I've had users say this error vanished after a reset. It's nuclear but effective.

Still crashing? Check these

• Hardware conflict: Try unplugging all non-essential USB devices. I've seen a faulty webcam driver trigger this.
• BIOS/UEFI update: Outdated firmware can cause kernel-level faults. Check your motherboard or laptop manufacturer's site.
• Windows update history: If the error started after a specific update (like KB5034441), uninstall it via Settings > Windows Update > Update history > Uninstall updates.
• Third-party security software: Temporarily uninstall any antivirus or firewall (besides Windows Defender). Kernel hooks from these are a common cause.

This error isn't common, but when it hits, it's a stubborn one. Start with Safe Mode, then system file repair. Drivers are the real enemy here—hunt them down methodically.