Skip to content
WhySoGeek.
Tech Support

Fix 0xc000021a BSOD Boot Loop on Windows 11

Stop code 0xc000021a means a critical system process died and Windows cannot boot. Use Startup Repair, SFC, and update rollback from WinRE to fix it.

Sam Carter 8 min read
Cover image for Fix 0xc000021a BSOD Boot Loop on Windows 11
Photo: Dr Stephen Dann / flickr (BY-SA 2.0)

The 0xc000021a stop code is a boot-time blue screen that puts Windows 11 into a loop: it tries to start, hits the error, and restarts into the same crash. The code stands for STATUS_SYSTEM_PROCESS_TERMINATED, a critical user-mode process that Windows depends on to boot, such as winlogon.exe or csrss.exe, terminated unexpectedly, so the kernel halts because the system cannot function without it.

Because the PC cannot reach the desktop, every fix here runs from the Windows Recovery Environment (WinRE). The most common triggers are a bad Windows update, corrupted system files, or a recently connected device, and the guide tackles them in that order.

Quick answer

0xc000021a (STATUS_SYSTEM_PROCESS_TERMINATED) means a critical boot process like winlogon.exe or csrss.exe died, so Windows refuses to load. Fix it from WinRE in this order: unplug all non-essential USB devices, run Startup Repair, then Uninstall the latest update, then repair system files offline with SFC and DISM, and use System Restore as a fallback. None of these steps touch your personal files, and a recent bad update is by far the most common cause.

Note

You will need to get into WinRE. If Windows fails to boot three times in a row, it should open the recovery menu automatically. If not, force it: power on, and as soon as the Windows logo appears, hold the power button to shut off; repeat twice, and the third boot lands on Automatic Repair > Advanced options.

Key takeaways

  • 0xc000021a means a critical system process died during boot, Windows halts because it cannot run without it.
  • Almost every fix runs from WinRE; reach it with three interrupted boots if it does not appear on its own.
  • A recent bad update is the top cause, uninstalling the latest update or rolling back the build often fixes it instantly.
  • Startup Repair, then SFC/DISM offline, then System Restore resolve the file-corruption cases.

Work the fixes in order of likelihood and risk, stopping as soon as Windows boots:

FixLikely cause it addressesRisk to dataTime
Unplug external devicesA faulty USB device or dockNone2 min
Startup RepairGeneric boot-blocking damageNone5-15 min
Uninstall latest updateA bad quality or feature updateNone10-20 min
SFC and DISM offlineCorrupted system filesNone15-30 min
System RestoreBad update, driver, or config changeNone (personal files kept)15-30 min
Reset or reinstallDeep corruption, nothing else workedHigh (back up first)30-90 min

First, disconnect external devices

A faulty USB device or external drive can disrupt a critical process during boot and trigger this exact code. Before anything else, unplug every non-essential device, USB drives, external HDDs, docks, secondary monitors, printers, leaving only keyboard and mouse. Restart. If Windows boots, reconnect devices one at a time to find the offender.

Run Startup Repair

This is the safest first WinRE step; it scans and fixes common boot-blocking problems automatically.

    1. In WinRE, go to Troubleshoot > Advanced options > Startup Repair.

    2. Select your account and enter the password if prompted.

    3. Let it run, it can take several minutes. If it reports a fix, restart and check whether Windows boots.

Windows Recovery Environment Advanced options menu with Startup Repair selected
Photo: cubeydev / flickr (PDM 1.0)

Uninstall the latest update or roll back the build

If the boot loop started right after Windows Update, removing the update usually fixes it immediately.

    1. In WinRE, go to Troubleshoot > Advanced options > Uninstall Updates.

    2. Choose Uninstall latest quality update first, confirm, and restart.

    3. If that fails, return and choose Uninstall latest feature update.

    4. If neither option is offered, use System Restore (next section) to a point before the update.

Repair system files offline

Corrupt system files are a core cause of 0xc000021a. Run the repair tools from WinRE's Command Prompt, targeting your offline Windows drive.

    1. In WinRE, open Troubleshoot > Advanced options > Command Prompt.

    2. Find your Windows drive letter (it may not be C: in WinRE): run diskpart, then list volume, note the letter for the Windows volume, then exit.

    3. Run System File Checker against it (replace D: with your actual letter): sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

    4. Repair the image: DISM /Image:D:\ /Cleanup-Image /RestoreHealth

    5. Check the disk for errors: chkdsk D: /f /r

    6. Type exit and restart.

Note

If sfc or DISM report they repaired files, reboot and test before doing anything more drastic. These offline repairs fix the majority of corruption-driven 0xc000021a loops without touching your data.

Use System Restore as a fallback

If the file repairs do not resolve it, roll the whole system back. In WinRE, choose Troubleshoot > Advanced options > System Restore, pick a restore point dated before the crashes began, and let it complete. This reverts system files, drivers, and updates to a known-good state while leaving your personal files intact.

If none of these succeed and the machine still loops, the cause may be deeper disk corruption or a hardware fault rather than software. The diagnostic path then overlaps with our inaccessible boot device guide, which covers storage-driver and disk issues that also block boot. For random hardware-driven crashes that are not a boot loop, see PC random restarts with no BSOD.

Frequently asked questions

What does STATUS_SYSTEM_PROCESS_TERMINATED actually mean?

It means a critical system process, one Windows cannot run without, like winlogon.exe or csrss.exe, terminated unexpectedly. The kernel responds by halting to prevent further damage. The blue screen is Windows refusing to continue without that process, not the process itself being unfixable.

Will these fixes erase my files?

Startup Repair, update rollback, SFC/DISM, and System Restore all preserve your personal files. They repair or revert system components only. The only step that risks data is a full reset or reinstall, which you should treat as a last resort after the above options fail.

I cannot even reach the recovery menu. What now?

Force WinRE by interrupting boot three times: power on, and at the spinning dots, hold the power button to cut power; repeat twice. The third attempt opens Automatic Repair. If that still fails, boot from a Windows 11 installation USB and choose Repair your computer to reach the same recovery tools.

Could bad RAM or a failing drive cause 0xc000021a?

Yes. Faulty memory can corrupt the critical process in memory, and a failing drive can corrupt the system files it loads. If software repairs do not stick, run a memory test (Windows Memory Diagnostic or MemTest86) and check the drive's health with chkdsk and the manufacturer's diagnostic tool.

#bsod#boot

Sources & further reading

Keep reading