Windows relies on several critical system processes to function properly. These processes handle tasks like managing memory, running drivers, and ensure smooth communication between hardware and software. If one of these essential processes fails or becomes corrupted, Windows cannot continue running and immediately triggers a Blue Screen of Death (BSOD) with the stop code CRITICAL_PROCESS_DIED. It usually happens due to corrupted system files, outdated or faulty drivers, disk errors, memory problems, or conflicts introduced by Windows updates or external devices. Here are the most effective solutions to fix the Critical Process Died Error on Windows 10.
Contents
- 1 What Causes the CRITICAL_PROCESS_DIED Error
- 1.1 Disconnect External Devices and Restart
- 1.2 Update or Reinstall Device Drivers
- 1.3 Run System File Checker (SFC) and DISM Tools
- 1.4 Test RAM with Windows Memory Diagnostic
- 1.5 Run Check Disk Utility (CHKDSK)
- 1.6 Use System Restore
- 1.7 Disable Fast Startup Feature
- 1.8 Uninstall Recent Updates or Applications
- 1.9 FAQs: CRITICAL_PROCESS_DIED Error in Windows 10
What Causes the CRITICAL_PROCESS_DIED Error
This error usually occurs when an essential system process fails, often due to corrupted system files, faulty drivers, hardware issues, or malware.
- Corrupted or Outdated Drivers: Drivers are essential for hardware to communicate with the OS, and corrupted or outdated ones can cause instability.
- Corrupted System Files: Damaged or missing critical Windows files, potentially caused by failed updates or other issues, can trigger the error.
- Hardware Malfunctions: Issues with components like RAM, hard drives, or other peripherals can lead to data errors and trigger the BSOD.
- Software Conflicts: Newly installed or incompatible software can conflict with system operations and disrupt critical processes.
- Recent Hardware Additions: Connecting new hardware can sometimes cause conflicts or driver issues that result in the error.
Disconnect External Devices and Restart
External devices such as USB drives, printers, external hard disks, and even faulty peripherals can load unstable drivers during startup. If one of these devices interferes with a critical Windows process, it can trigger the CRITICAL_PROCESS_DIED BSOD.
- Shut down your PC completely.
- Unplug all unnecessary external devices (USB drives, printers, external HDD/SSD, etc.).
- Restart your computer and check if the error appears.
Note: If your PC keeps restarting and doesn’t stay on long enough to apply fixes, try starting Windows in Safe Mode. Safe Mode loads only the essential drivers and services, making it easier to troubleshoot.

Update or Reinstall Device Drivers
Drivers serve as a communication bridge between hardware and the operating system. If they are outdated, incompatible, or corrupted, they can cause the system to crash. Updating drivers ensures compatibility with the operating system and addresses known bugs or issues.
Keeping drivers updated prevents system instability and ensures compatibility with Windows updates.
- Press Windows + X and select Device Manager.
- Expand the relevant category (e.g., Display Adapters, Network Adapters).
- Right-click on the suspect device and select Update driver.
- Choose Search automatically for updated driver software to let Windows find and install the latest version.
- If no updates are found, visit the manufacturer’s website, download the latest driver, and install it manually.
Steps to Reinstall Drivers
- In Device Manager, right-click the problematic device and select Uninstall device.
- Check the box for Delete the driver software for this device and confirm.
- Restart your computer. Windows will attempt to reinstall the default driver automatically.
Run System File Checker (SFC) and DISM Tools
Corrupted or missing system files can cause the “Critical Process Died” error. Run System File Checker (SFC) and DISM (Deployment Image Servicing and Management) tools can detect and repair such issues.
- SFC (System File Checker) scans and automatically repairs corrupted Windows files.
- DISM (Deployment Imaging Service and Management Tool) fixes deeper issues in the Windows image that SFC cannot repair.
These tools ensure the integrity of system files and repair corrupted files, stabilizing the operating system.
- Press Windows key + S and type cmd, right click on command prompt and select run as administrator,
- Type command sfc /scannow and press enter key to scan and repair system files.
- This will take 15-20 minutes to complete, depending on the system file corruption level.
- Next, run DISM restore health command, dism /online /cleanup-image /restorehealth to scan and repair the system image.
- Once the scanning is complete 100% reboot your computer and check if the BSOD error is gone.
Test RAM with Windows Memory Diagnostic
Again, Faulty hardware, particularly RAM or the hard drive, can lead to system instability. You can use the Windows memory diagnostic tool to check your computer memory for Problems. Also, run the chkdsk command to scan and fix disk drive errors and bad sectors. Diagnosing and replacing failing hardware ensures stable system performance.
To Test RAM:
- Press Windows + R, type
mdsched.exe, and hit Enter. - Choose Restart now and check for problems.
- Windows will reboot and scan your memory.
- Once finished, results will appear after login.
If errors are found, you may need to replace the faulty RAM to restore system stability.
Run Check Disk Utility (CHKDSK)
A failing hard drive or SSD with bad sectors can corrupt critical processes. Windows may attempt to read system files from a damaged area, triggering the BSOD. The CHKDSK (Check Disk) utility scans your drive for errors and fixes them, helping prevent crashes caused by faulty storage.
- Open Command Prompt as an administrator.
- Type command chkdsk C: /f /r and press enterkey
- Press Y and press enter to schedule the scan on next boot, then restart your PC.
- This will scan the hard drive for errors and fix them if possible
This repair tool ensures your storage device is healthy, which directly impacts system stability.
Use System Restore
If the issue started recently, a System Restore can revert your system to a previous state where it functioned correctly. Restoring your system eliminates recent changes that might have triggered the error.
- Press Windows + R, type
rstrui.exe, and hit Enter. - Follow the prompts to choose a restore point and complete the process.
Disable Fast Startup Feature
Several Windows users report that disabling the Fast Startup Feature fixes most of the blue Screen errors for them. Fast Startup (hybrid Shutdown Feature) introduced on Windows 10 reduces startup time and makes Windows start faster. But sometimes the fast Startup feature causes different Problems. So we recommend just disable the Fast Startup feature to prevent a BSOD error on Windows 10.
To Disable Fast Startup Feature:
- Open the Control Panel, search for and select Power Options.
- Click on Choose What the Power Buttons Do
- Next, click on Change Settings that are Currently Unavailable.
- Here, uncheck the Turn on Fast Startup option (recommended) to disable the Fast Startup Feature.
Uninstall Recent Updates or Applications
Sometimes, newly installed software or updates can conflict with the system. Removing recent changes helps identify and resolve compatibility issues.
- Press Windows + I and go to Apps.
- Locate and uninstall any recently installed applications.
- Navigate to Update & Security > View update history.
- Select Uninstall updates and remove any recent updates.
In addition, Malware can interfere with critical system processes, causing unexpected crashes. Scanning for and removing malware ensures that your system operates without interference from malicious software.
FAQs: CRITICAL_PROCESS_DIED Error in Windows 10
Q1. What triggers CRITICAL_PROCESS_DIED in Windows 10?
It usually happens due to corrupted system files, faulty drivers, disk errors, or memory problems.
Q2. Can I fix CRITICAL_PROCESS_DIED without reinstalling Windows?
Yes. In most cases, running SFC/DISM, updating drivers, or restoring Windows fixes the issue.
Q3. Does Safe Mode stop CRITICAL_PROCESS_DIED errors?
If the error doesn’t appear in Safe Mode, it likely means third-party drivers or software are responsible.
Q4. Is CRITICAL_PROCESS_DIED a hardware problem?
Not always. While RAM or disk issues can cause it, most cases are software-related and fixable.
Q5. Should I reset Windows 10 if nothing works?
Yes. Resetting provides a clean system and usually eliminates persistent BSOD errors.
- Solved: Windows 10 black screen with cursor after update
- kernel security check failure during Windows 10 install
- How To Fix Windows 10 Memory Management Error Stop code 0x0000001A
- Windows 10 Stuck on Welcome Screen? Here 5 working solutions to get rid of this
- Solved: Thread stuck in device driver BSOD Error in Windows 10