CRITICAL_PROCESS_DIED is a fatal Windows stop error (BSOD) that occurs when a key system process—such as winlogon.exe, csrss.exe, or smss.exe—suddenly terminates. This is a fail-safe mechanism in Windows to prevent further system corruption.
✅ SEO Keywords: CRITICAL_PROCESS_DIED, Windows BSOD, stop code critical process died, fix blue screen, Windows 10 crash, system file corruption, boot error fix, PowerShell recovery script
The error can happen during boot, after login, or randomly while working. It often leads to restart loops or recovery mode. Common causes include:
- Corrupted system files (from power loss, failed updates, or malware)
- Incompatible or outdated drivers (especially for storage, antivirus, chipset)
- Failing SSD/HDD (bad sectors or controller issues)
- Interruptions during critical Windows updates
- Malware or rootkit infections
- Unstable overclocking or BIOS settings
Here are 8 step-by-step solutions. Start from the top and work your way down.
Goal: Detect and repair corrupted Windows system files.
-
Boot into Windows Recovery Environment (WinRE):
- If your PC won't boot, turn it on and off 2–3 times forcefully to trigger recovery.
- Or boot from a Windows installation USB (created via Media Creation Tool)
-
Go to:
Troubleshoot→Advanced Options→Command Prompt -
In Command Prompt, type:
sfc /scannow
-
Wait for the scan to complete (can take 10–15 mins). Follow any recommendations.
Goal: Use Windows Update to restore broken system components.
-
In the same Command Prompt (from recovery), enter:
DISM /Online /Cleanup-Image /RestoreHealth
-
Let it finish (can take 10–20 mins). If it fails, try running it again.
Goal: Detect and fix disk issues like bad sectors or file system errors.
-
In Command Prompt, type:
chkdsk C: /f /r
-
If it asks to schedule on next restart, type
Yand reboot.
This may take up to 1 hour, depending on your drive.
Goal: Replace faulty or outdated drivers that may be causing BSOD.
-
In WinRE:
Troubleshoot→Advanced Options→Startup Settings→ Click Restart -
After restart, choose option
4orF4for Safe Mode. -
Once inside Safe Mode:
- Open Device Manager (
Win + X→ Device Manager) - Expand
Disk Drives,Display adapters, andNetwork adapters - Right-click each one →
Update driver→Search automatically
- Open Device Manager (
-
If a recent driver is causing problems, roll it back:
- Right-click device →
Properties→Drivertab →Roll Back Driver
- Right-click device →
Goal: Remove buggy updates that broke critical processes.
-
In WinRE:
Troubleshoot→Advanced Options→Uninstall Updates -
Choose either:
Uninstall latest quality updateUninstall latest feature update
-
Follow the instructions to complete rollback.
Goal: Rule out third-party services causing conflicts.
- Boot into Safe Mode.
- Press
Win + R, typemsconfig, hit Enter. - Go to the Services tab → check Hide all Microsoft services → click Disable all.
- Go to Startup tab → click Open Task Manager.
- Disable all startup apps.
- Reboot and see if the error persists.
Goal: Revert the system to a previous working state.
-
In WinRE:
Troubleshoot→Advanced Options→System Restore -
Choose a restore point dated before the issue started.
-
Let the system restore complete.
Goal: Completely reset the system, keeping or removing files.
-
In WinRE:
Troubleshoot→Reset this PC -
Choose:
Keep my files(apps & settings will be removed)- Or
Remove everything(clean install)
-
Follow the on-screen instructions.
If this guide helped you resolve the CRITICAL_PROCESS_DIED blue screen, please consider starring ⭐ this repository to support the project and help others find it.
You can also open an Issue if you’re still stuck or suggest improvements.
#Windows #BSOD #CRITICAL_PROCESS_DIED #blue-screen #boot-error #recovery #fix #windows-crash