CRITICAL_PROCESS_DIED how to fix

CRITICAL_PROCESS_DIED – How to Fix

The CRITICAL_PROCESS_DIED error is a Windows Blue Screen of Death (BSOD) that occurs when a core Windows process essential to the system’s operation unexpectedly terminates. Since these processes handle vital functions such as input/output and kernel operations, their failure forces Windows to stop running entirely. While serious, this error is often tied to corrupted files, failing hardware, or driver problems, and can usually be repaired with methodical troubleshooting.

Have a different error code? Figure out how to fix it with our free Windows error code decoder.

Causes

Common causes of the CRITICAL_PROCESS_DIED stop code include:

Corrupted or missing system files
Failing or corrupted storage devices (HDDs or SSDs)
Outdated or faulty drivers (storage, chipset, or GPU)
Memory errors from faulty or unstable RAM
Malware infections altering or terminating core processes
Incomplete Windows Updates or interrupted installations

Fixes

Run SFC and DISM

Corrupted system files are one of the most frequent causes. Use these commands in an elevated terminal:

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

SFC checks and repairs critical files, while DISM restores the system image to a healthy state.

Check drive health with SMART and chkdsk

Storage failures can cause critical processes to crash. To test:

Run: chkdsk C: /f /r This checks for and repairs file system errors.
Use a tool like CrystalDiskInfo to view the drive’s SMART status. If warnings or failures appear, back up data immediately and replace the drive.

Reseat or replace storage devices

Loose or failing SATA/NVMe connections can cause intermittent errors. Power down, reseat the drive cables, or try a different port. For laptops, reseat the SSD module if possible.

Update or roll back drivers

Faulty drivers can terminate core processes. Update chipset, storage, and GPU drivers from your system or motherboard manufacturer’s support page. If the issue started after a driver update, roll back to the previous stable version through Device Manager.

Scan for malware

Malicious software can tamper with or terminate core processes. Run a full Windows Defender or third-party antivirus scan. For deeper cleaning, use bootable antivirus rescue media to scan outside of Windows.

Perform an in-place upgrade repair

If corruption persists after SFC/DISM, performing an in-place upgrade with the latest Windows ISO can repair the operating system while preserving files and applications.

Download the Media Creation Tool from Microsoft.
Choose Upgrade this PC now.
Select Keep personal files and apps to restore system components without wiping data.

Additional troubleshooting

Check RAM with Windows Memory Diagnostic or MemTest86 to rule out failing memory.
Uninstall recent updates or software that may have introduced instability.
Boot into Safe Mode to see if the system stabilizes—if so, third-party drivers or software are likely the cause.

Conclusion

The CRITICAL_PROCESS_DIED BSOD signals that Windows lost one of its core processes. While it can feel like a catastrophic failure, most cases stem from file corruption, bad drivers, or failing hardware. Running SFC and DISM, testing drive and memory health, updating drivers, and scanning for malware usually resolve the issue. For persistent cases, an in-place upgrade repair restores stability without requiring a full reinstall of Windows.

Have a different error code? Figure out how to fix it with our free Windows error code decoder.