Overview
The "Critical Process Died" blue screen (CRITICAL_PROCESS_DIED) appears when an essential Windows process stops unexpectedly — usually due to corrupted system files, faulty drivers, bad updates, or failing hardware. This guide works through the fixes in order, including options you can use from the recovery environment if Windows will not boot.
The Critical Process Died error is a blue screen caused by a failed system process.
Key Takeaways
- The error is usually corrupted system files, a bad driver, or a faulty update.
- Repair system files with SFC, DISM, and CHKDSK.
- Use Startup Repair and boot-sector repair if Windows will not start.
- Roll back recent drivers, updates, or apps that triggered the crash.
What Causes It?
- Corrupted or missing system files.
- Faulty, outdated, or incompatible drivers.
- A bad Windows update or recently installed app.
- Disk errors, bad sectors, or failing hardware; sometimes malware.
Fix 1 — Disconnect Unnecessary Devices
1. Unplug recently added peripherals (USB devices, external drives, docks).
2. Restart the PC to see if a faulty device was triggering the crash.
3. Reconnect devices one at a time to identify the culprit.
Fix 2 — Run Startup Repair
1. Boot to recovery (hold Shift and click Restart, or interrupt boot three times to reach Automatic Repair).
2. Go to Troubleshoot > Advanced options > Startup Repair.
3. Let it diagnose and repair startup problems, then restart.
Fix 3 — Repair System Files (SFC, DISM, CHKDSK)
1. Open Command Prompt as administrator (or via Advanced options > Command Prompt).
2. Run: sfc /scannow
3. Run: DISM /Online /Cleanup-Image /RestoreHealth
4. Run: chkdsk C: /f /r to check the disk, then restart.
Fix 4 — Repair Boot Sectors
1. Open Command Prompt from the recovery environment.
2. Run: bootrec /fixmbr
3. Run: bootrec /fixboot
4. Run: bootrec /rebuildbcd, then restart.
Repair boot sectors from Command Prompt if Windows will not start.
Fix 5 — Update or Roll Back Drivers
1. Open Device Manager and look for devices with a warning icon.
2. Update the driver, or use Properties > Driver > Roll Back Driver if the crash started after a driver update.
3. Reinstall the driver from the manufacturer if needed, then restart.
Fix 6 — Undo Recent Changes
- Uninstall apps installed just before the crashes began (Settings > Apps).
- Uninstall recent Windows updates (Settings > Windows Update > Update history > Uninstall updates).
- Run a full malware scan with Windows Security or a trusted tool.
Fix 7 — Reset Windows
1. If nothing else works, open Settings > System > Recovery > Reset this PC.
2. Choose Keep my files (or Remove everything for a clean slate).
3. Follow the prompts; this reinstalls Windows and usually clears persistent corruption.
Warning: Back up important data before resetting Windows or running CHKDSK repairs on a failing disk.
Troubleshooting
Problem: Windows will not boot at all.
Solution: Use the recovery environment (Automatic Repair) to run Startup Repair, SFC/DISM, and bootrec commands from Command Prompt.
Problem: The BSoD returns after a specific update.
Solution: Uninstall that update from Update history, and pause updates until a fix is available.
Problem: CHKDSK finds many bad sectors.
Solution: Your drive may be failing. Back up immediately and consider replacing the disk.
Problem: Crashes continue after all software fixes.
Solution: Test RAM (Windows Memory Diagnostic) and check hardware; faulty memory or storage can cause this error.
Conclusion
Critical Process Died is recoverable in most cases. Repair system files and boot data, roll back recent drivers or updates, and reset Windows as a last resort — backing up your data along the way.
</w:pBdr><w:spacing w:before="220" w:after="40"/></w:pPr><w:r><w:rPr><w:b/><w:bCs/><w:color w:val="0B5394"/><w:sz w:val="21"/><w:szCs w:val="21"/><w:rFonts w:ascii="Calibri" w:cs="Calibri" w:eastAsia="Calibri" w:hAnsi="Calibri"/></w:rPr><w:t xml:space="preserve">About TechHub
This guide is part of the TechHub Knowledge Base. For more step-by-step IT guides and support, visit techhub.com.lk.
