Quick fix: Boot to Safe Mode (Settings → System → Recovery → Advanced startup → Restart → Troubleshoot → Startup Settings → F4). Once in Safe Mode, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. The BSOD is usually corrupted system files; running these from Safe Mode lets them complete without competing services.

Windows 11 blue-screens with CRITICAL_PROCESS_DIED. You reboot. Same BSOD. Sometimes Windows attempts Automatic Repair which also fails. The stop code means a critical Windows service (csrss.exe, lsass.exe, winlogon.exe, or similar) crashed — and Windows can’t continue without it. The root cause is usually corrupted system files or a bad driver.

Symptom: Windows 11 BSOD with CRITICAL_PROCESS_DIED stop code; may BSOD on every boot.
Affects: Windows 11 (and Windows 10) with corrupted system files or driver issues.
Fix time: ~30-60 minutes.

What causes this

CRITICAL_PROCESS_DIED indicates that an essential Windows process terminated unexpectedly. The kernel can’t recover and triggers BSOD. Causes vary: corrupted system files in WinSxS, a buggy driver that crashed a kernel-side service, malware that corrupted a critical binary, failing disk producing read errors on system files.

Method 1: Run sfc and DISM in Safe Mode

The standard recovery for corrupted system files.

Boot to Safe Mode. If Windows still boots normally between BSODs: Settings → System → Recovery → Advanced startup → Restart now.
If Windows won’t boot: force three failed boots to enter Recovery Environment automatically.
From the recovery menu: Troubleshoot → Advanced options → Startup Settings → Restart → press 4 for Safe Mode.
Sign in.
Open Terminal (Admin).

Run system file checks:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

Each step takes 5-20 minutes.
If sfc reports “found corrupt files and successfully repaired,” reboot. The BSOD should be gone.
If sfc reports “found corrupt files but was unable to fix some,” proceed to Method 2.

Safe Mode is critical — fewer services are running, so fewer file locks to compete with repair.

Method 2: Run chkdsk to check for disk errors

Use when sfc/DISM don’t fully resolve, or when you suspect drive issues.

In Terminal (Admin):
```
chkdsk C: /f /r
```
The /f fixes errors; /r locates bad sectors and recovers readable info.
chkdsk can’t lock the C: drive while Windows is running. It asks: “Would you like to schedule this volume to be checked the next time the system restarts?” Press Y.
Reboot. chkdsk runs at boot before Windows loads. Takes 30-120 minutes depending on drive size and condition.
After chkdsk finishes, Windows boots normally. Note any errors logged.
If chkdsk found and fixed disk errors, the BSOD root cause may be addressed. Test by using the PC normally for a day.

Filesystem corruption is a common cause of BSODs that sfc can’t fix because the underlying disk has read errors.

Method 3: Identify and update the offending driver

Use when system files are clean but BSODs continue — a driver is the cause.

After the next BSOD, Windows creates a minidump in C:\Windows\Minidump\.
Open Settings → System → Recovery → Reliability monitor, or search Reliability Monitor in Start.
Find the BSOD event. Click View technical details. The faulting module name appears.
If a driver name is shown (e.g., nvlddmkm.sys = NVIDIA, iaStor.sys = Intel storage): update or roll back that driver.
For deeper diagnosis, install WhoCrashed (free, resplendence.com) or BlueScreenView (free, nirsoft.net). Both parse minidumps and identify the driver.
Update the driver from the vendor (NVIDIA, AMD, Intel, OEM support page).
If updating doesn’t help, roll back: Device Manager → (device) → Properties → Driver tab → Roll Back Driver.

This is the right approach when system files are clean but a specific driver is killing Windows.

How to verify the fix worked

Reboot the PC multiple times. No BSOD on any boot.
Use the PC normally for a day. No mid-session BSODs.
Run sfc /scannow. Result: “no integrity violations found.”
Check Reliability Monitor. No recent critical events.

If none of these work

If CRITICAL_PROCESS_DIED persists despite sfc/DISM, chkdsk, and driver updates, three causes apply. Hardware fault: failing RAM is a common cause. Run Memtest86 (memtest86.com) for at least one full pass. Any errors mean RAM replacement. Failing SSD also causes BSODs from read errors that sfc can’t fix permanently — check SMART status with CrystalDiskInfo. Recent Windows feature update: a feature update can introduce BSOD-triggering changes. Uninstall the latest update via Settings → Windows Update → Update history → Uninstall updates. Reset This PC: when all other fixes fail and you have backups, Reset This PC with Cloud download installs a clean Windows 11 fresh. Use as the escalation when hardware seems fine.

Bottom line: CRITICAL_PROCESS_DIED is system file corruption or driver crash — sfc/DISM in Safe Mode fixes file corruption, chkdsk fixes disk errors, dump analysis identifies the failing driver.