[Solution] Error 0xc000021a Windows 11/10 — BSOD STOP Error Fix

Error 0xc000021a is a critical BSOD (Blue Screen of Death) STOP error that occurs when Windows subsystem processes — specifically winlogon.exe or csrss.exe — fail or become corrupted. The system halts immediately to prevent data loss.

This error affects both Windows 10 and 11 and typically results in a system that cannot boot normally, entering a repair loop or requiring advanced recovery.

Description

The full error message typically reads:

“Your PC ran into a problem and needs to restart. We’re just collecting some error info, and then we’ll restart for you. STOP: 0xc000021a”

Or on the blue recovery screen:

“0xc000021a — {Fatal Error} The process encountered an unexpected error.”

This STOP code indicates that either winlogon.exe (responsible for handling user logons) or csrss.exe (the Client/Server Runtime Subsystem) terminated unexpectedly. These are critical Windows processes, and when they crash, Windows has no choice but to stop.

Common scenarios include:

  • After a Windows Update — A corrupted update replaces critical system files
  • After installing new software — Third-party software modifies protected system files
  • Driver conflicts — A recently installed driver corrupts the subsystem
  • Disk corruption — Bad sectors prevent system files from being read correctly
  • Registry corruption — The system registry hive is damaged

Common Causes

  1. Corrupted system files — winlogon.exe, csrss.exe, or dependent DLLs are damaged.
  2. Failed Windows Update — An incomplete or corrupted update modified protected files.
  3. Incompatible drivers — A recently installed driver conflicts with the Windows subsystem.
  4. Registry hive corruption — The SYSTEM or SOFTWARE registry hives are unreadable.
  5. Disk errors — Bad sectors on the system drive prevent critical files from loading.
  6. Third-party software conflicts — Security software or system utilities modifying boot processes.

Solutions

Solution 1: Run SFC from Recovery Environment

Since this error often prevents normal booting, you need to run System File Checker from the Windows Recovery Environment.

If you can boot into Safe Mode:

  1. Restart your PC and press F8 or hold Shift while clicking Restart.
  2. Navigate to Troubleshoot > Advanced options > Startup Settings > Restart.
  3. Press 4 or F4 to boot into Safe Mode.
  4. Open Command Prompt as administrator and run:
sfc /scannow

If you cannot boot at all:

  1. Boot from a Windows installation USB or recovery drive.
  2. Select Repair your computer.
  3. Go to Troubleshoot > Advanced options > Command Prompt.
  4. Run SFC targeting the offline installation:
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Replace C: with the correct drive letter if your Windows installation is on a different partition.

Solution 2: Run DISM to Repair the System Image

DISM can repair the Windows system image that SFC depends on:

From the recovery Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth

If running from recovery media against an offline installation:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

Wait for the process to complete (it can take 10–20 minutes). If it reports corruption that it cannot repair, you may need a Windows installation ISO as the repair source.

Solution 3: Disable Driver Signature Enforcement

If a recently installed driver with an invalid signature is causing the crash:

  1. Boot into Advanced Startup Options (hold Shift + Restart, or use recovery media).
  2. Go to Troubleshoot > Advanced options > Startup Settings > Restart.
  3. Press 7 or F7 to select Disable driver signature enforcement.
  4. Windows will boot normally — uninstall the problematic driver:
pnputil /enum-devices /driver oem*.inf

Find the recently installed driver and remove it:

pnputil /delete-driver oemXX.inf /uninstall

Solution 4: Check and Repair Disk Errors

Disk corruption can cause system files to become unreadable. Run Check Disk from the recovery environment:

chkdsk C: /f /r /x

The /r flag locates bad sectors and recovers readable data. This can take 30–60 minutes depending on disk size.

To schedule the check for the next boot if the drive is in use:

chkdsk C: /f /r /x

Type Y when prompted, then restart your PC.

Solution 5: Perform a System Restore

If the error started after a recent change, System Restore can revert the system to a working state:

  1. Boot into Advanced Startup Options.
  2. Go to Troubleshoot > Advanced options > System Restore.
  3. Select a restore point dated before the error started.
  4. Follow the prompts and let the restoration complete.

From the command line in recovery:

rstrui.exe

Solution 6: Rebuild BCD and Repair Boot Records

Corrupted boot configuration can cause subsystem failures:

bootrec /fixmbr
bootrec /fixboot
bootrec /rebuildbcd

If bootrec /fixboot fails with access denied:

bootsect /nt60 sys
bootrec /fixboot

Solution 7: Reset Windows as Last Resort

If none of the above solutions work, resetting Windows preserves your files while replacing system files:

From the recovery environment:

  1. Go to Troubleshoot > Reset this PC.
  2. Choose Keep my files to preserve personal data.
  3. Choose Cloud download for a fresh copy of Windows.
  4. Follow the prompts to complete the reset.
  • Error 0x000000ef — CRITICAL_PROCESS_DIED, another critical process failure BSOD
  • Error 0xc0000005 — Access Violation, related to memory and process crashes
  • Error 0x0000007e — SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
  • Error 0x0000003b — SYSTEM_SERVICE_EXCEPTION
  • Error 0xc0000234 — STATUS_LOGON_FAILURE, related to winlogon process issues

Comments