Fix Stop Code 0xc000021a on Windows 10/11 (Exact Commands)

The fast answer. Stop code 0xc000021a (STATUS_SYSTEM_PROCESS_TERMINATED) means a critical user-mode process — Winlogon (winlogon.exe) or the Client Server Run-Time Subsystem (csrss.exe) — crashed, and Windows shut itself down because it can't run without them. The most common trigger is corrupted system files after a failed Windows Update or an incompatible third-party program. Boot into Windows Recovery (WinRE), open a Command Prompt, and repair the system files:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Then reboot. If that alone doesn't fix it, run DISM first (see Step 3) and repeat SFC, or roll back the last update from WinRE.

Why this happens

Failed or partial Windows Update — a cumulative update or service pack installation didn't finish cleanly, leaving mismatched or corrupted system files. This is the single most common cause.
Incompatible third-party software — a recently installed program or driver interferes with winlogon.exe or csrss.exe, causing them to crash at startup.
Corrupted system files — an unclean shutdown, disk errors, or a backup restore that skipped in-use files left critical OS binaries damaged or mismatched.
Bad or unsigned driver — a driver that fails signature verification can prevent csrss.exe from initialising, especially after a major feature update changes driver-signing enforcement.

Step-by-step fix

Step 1 — Get into Windows Recovery (WinRE)

Force three failed boots (power on, then hold the power button to kill it as the Windows logo appears, three times) and Windows opens Automatic Repair. Or boot from a Windows 10/11 install USB and choose Repair your computer. Then go to Troubleshoot → Advanced options.

Step 2 — If it started after an update, uninstall the update

In Advanced options, choose Uninstall Updates → Uninstall latest quality update (or Uninstall latest feature update if a feature update was the last thing installed). This reverses most update-triggered cases without touching your data. Reboot and test before doing anything else.

Step 3 — Repair system files with SFC and DISM (offline)

In Advanced options → Command Prompt, confirm which drive letter WinRE assigned to your Windows partition (it may not be C:). Then run DISM to repair the component store, followed by SFC to fix individual system files:

dism /image:C:\ /cleanup-image /restorehealth

Wait for DISM to finish (it can take 15–30 minutes), then run SFC:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Replace C: with the actual Windows drive letter if it differs in WinRE. Reboot and test.

Step 4 — Try System Restore

If SFC and DISM didn't help and you have restore points, go back to Advanced options → System Restore and pick a restore point from before the error started. This rolls back system files, drivers, and registry entries without deleting your personal files.

Step 5 — Boot into Safe Mode and remove suspect software

From Advanced options → Startup Settings → Restart, press 4 or F4 for Safe Mode (or 5/F5 for Safe Mode with Networking). In Safe Mode, uninstall any recently added programs or driver updates via Settings → Apps or Device Manager. If the BSOD appeared right after installing new software, removing it here often clears the error.

Step 6 — Check disk health

Corrupted system files sometimes point to underlying disk damage. From a WinRE Command Prompt:

chkdsk C: /f /r

Replace C: with the Windows drive letter. /f fixes file-system errors; /r locates bad sectors and recovers readable data. Reboot and test.

Data safety: If the files on this machine matter and you don't have a backup, image the drive before you run repairs. SFC, DISM, and chkdsk /r are normally safe, but a drive that's already failing can lose data when stressed by a full-surface scan. Take a sector image to a known-good external disk first, and never run repairs on the only copy of irreplaceable data.

GRAM tip: The repair steps above run in Windows Recovery, which is already on the broken PC. Once the machine boots again, plug in GRAM — a free portable repair toolkit that runs from a USB inside Windows — to read the crash dump, check disk health, review event logs, and let its AI agent confirm the root cause so the stop code doesn't return.

Download GRAM free See AI pricing →

FAQ

Can I fix this without a second working computer?

Yes. Windows Recovery (WinRE) lives on the broken PC itself — force three failed boots to trigger Automatic Repair, or boot from any Windows install USB. All the SFC, DISM, and System Restore steps run inside WinRE. No second computer is required. (GRAM runs inside Windows rather than from boot media — use it once the machine boots to read the crash dump and verify the root cause.)

Will SFC or DISM erase my files?

No. SFC replaces only corrupted or mismatched protected system files with known-good copies. DISM repairs the Windows component store. Neither command touches your personal files, documents, or installed applications.

The error appeared right after a Windows Update — what should I try first?

Uninstall the latest update from WinRE (Advanced options → Uninstall Updates). Choose the quality update first; if a feature update was most recent, uninstall that instead. This is the safest and fastest fix for update-triggered 0xc000021a cases.

What if Safe Mode also blue-screens with 0xc000021a?

If even Safe Mode crashes, the damage is deeper than a single bad driver. Run the offline SFC and DISM sequence from WinRE (Step 3), try System Restore (Step 4), and check the disk with chkdsk /f /r (Step 6). If none of those resolve it, the Windows installation may need a repair install (in-place upgrade) from a Windows install USB, which reinstalls the OS while keeping your files and most programs.