How to Fix CRITICAL_PROCESS_DIED on Windows 10/11

Overview

CRITICAL_PROCESS_DIED happens when a Windows process essential to system operation crashes — usually `csrss.exe`, `wininit.exe`, `smss.exe`, or `services.exe`. Without these, Windows can't continue running, hence the BSOD.

Causes range from corrupted system files (most common) to malware, failing SSDs, or registry damage. The fixes are the standard "system integrity" toolkit, plus a few specific tactics for this BSOD code.

If you can't boot to Windows at all and only see this BSOD on every restart, jump to step 4 (Safe Mode boot).

Before you start

✓Administrator access (or Windows recovery USB if you can't boot)
✓Recent backup

The fix

5-step guide

Read time: ~15-35 min

Run System File Checker

Most CRITICAL_PROCESS_DIED cases are corrupted system files. Run SFC first.

bashsfc /scannow

Run DISM

If SFC reported errors it couldn't fix, DISM repairs the underlying system image SFC pulls from.

bashDISM /Online /Cleanup-Image /RestoreHealth

Scan for Malware

Some malware kills critical processes intentionally. Run a thorough scan with Malwarebytes — it catches threats Windows Defender misses.

Recommended Tool

Malwarebytes Premium

freemium

Specialized malware remover that catches what your antivirus misses.

Boot Safe Mode If You Can't Reach Windows

If BSOD loops on every boot:

Steps:

Force-shutdown your PC 3 times in a row (hold power button) — this triggers Windows Recovery.
Choose Troubleshoot → Advanced options → Startup Settings → Restart.
Press 4 for Safe Mode.

In Safe Mode, run sfc, DISM, and Malwarebytes. If they fix the issue, normal boot will work afterward.

Check Disk Health

A failing SSD/HDD corrupts system files randomly, causing recurrent CRITICAL_PROCESS_DIED.

Steps:

Open Command Prompt as Admin.
Run:

bashchkdsk C: /f /r

Still seeing CRITICAL_PROCESS_DIED?

If the guide is not enough, describe the issue first. We will explain whether remote help is appropriate before any access is granted.

Talk to a tech

No automatic remote access.

DIY steps first
Permission before access
Hardware limits explained

FAQ

Common questions

What's a 'critical process'?

Windows processes marked as critical can't be killed without crashing the whole OS. Examples: csrss.exe (manages console windows), wininit.exe (system initialization), smss.exe (session manager). They have to be running for Windows to function.

I see this BSOD on every boot, can't reach desktop. What now?

Force-shutdown 3 times to enter Recovery, then boot Safe Mode (step 4). All standard tools work in Safe Mode. If that fails, use a Windows installation USB to run Startup Repair.

Will I lose data fixing this?

Standard fixes (SFC, DISM, Malwarebytes scan) don't delete files. CHKDSK with /r flag can rarely flag and isolate bad sectors which may contain file data — but it's unusual.

How is this different from KMODE or DRIVER_IRQL BSODs?

KMODE/DRIVER_IRQL = a third-party driver crashed. CRITICAL_PROCESS_DIED = a core Windows process crashed. The fixes are different: CRITICAL_PROCESS_DIED needs system integrity repairs (SFC/DISM); KMODE needs driver fixes.

When do I just reinstall Windows?

If SFC, DISM, malware scan, and CHKDSK all complete clean but the BSOD persists, your Windows installation is too damaged for in-place repair. A clean install fixes it permanently. Back up first.

Written by PCDoc Team

Tested on a real Windows machine on 2026-05-20. Found a mistake? Tell us.