Skip to content

CRITICALPROCESS/critical-process-died

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 

Repository files navigation

💀 Fixing CRITICAL_PROCESS_DIED (Windows BSOD)

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


⚠️ Why This Error Happens

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

🛠️ Step-by-Step Solutions

Here are 8 step-by-step solutions. Start from the top and work your way down.


✅ 1. Run System File Checker (SFC)

Goal: Detect and repair corrupted Windows system files.

Steps:

  1. 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)
  2. Go to: TroubleshootAdvanced OptionsCommand Prompt

  3. In Command Prompt, type:

    sfc /scannow
  4. Wait for the scan to complete (can take 10–15 mins). Follow any recommendations.


✅ 2. Run DISM to Restore System Health

Goal: Use Windows Update to restore broken system components.

Steps:

  1. In the same Command Prompt (from recovery), enter:

    DISM /Online /Cleanup-Image /RestoreHealth
  2. Let it finish (can take 10–20 mins). If it fails, try running it again.


✅ 3. Check Disk for Errors (CHKDSK)

Goal: Detect and fix disk issues like bad sectors or file system errors.

Steps:

  1. In Command Prompt, type:

    chkdsk C: /f /r
  2. If it asks to schedule on next restart, type Y and reboot.
    This may take up to 1 hour, depending on your drive.


✅ 4. Boot into Safe Mode and Update Drivers

Goal: Replace faulty or outdated drivers that may be causing BSOD.

Steps:

  1. In WinRE:
    TroubleshootAdvanced OptionsStartup Settings → Click Restart

  2. After restart, choose option 4 or F4 for Safe Mode.

  3. Once inside Safe Mode:

    • Open Device Manager (Win + X → Device Manager)
    • Expand Disk Drives, Display adapters, and Network adapters
    • Right-click each one → Update driverSearch automatically
  4. If a recent driver is causing problems, roll it back:

    • Right-click device → PropertiesDriver tab → Roll Back Driver

✅ 5. Uninstall Problematic Windows Updates

Goal: Remove buggy updates that broke critical processes.

Steps:

  1. In WinRE: TroubleshootAdvanced OptionsUninstall Updates

  2. Choose either:

    • Uninstall latest quality update
    • Uninstall latest feature update
  3. Follow the instructions to complete rollback.


✅ 6. Perform a Clean Boot

Goal: Rule out third-party services causing conflicts.

Steps:

  1. Boot into Safe Mode.
  2. Press Win + R, type msconfig, hit Enter.
  3. Go to the Services tab → check Hide all Microsoft services → click Disable all.
  4. Go to Startup tab → click Open Task Manager.
  5. Disable all startup apps.
  6. Reboot and see if the error persists.

✅ 7. Use System Restore

Goal: Revert the system to a previous working state.

Steps:

  1. In WinRE: TroubleshootAdvanced OptionsSystem Restore

  2. Choose a restore point dated before the issue started.

  3. Let the system restore complete.


✅ 8. Reset or Reinstall Windows

Goal: Completely reset the system, keeping or removing files.

Steps:

  1. In WinRE: TroubleshootReset this PC

  2. Choose:

    • Keep my files (apps & settings will be removed)
    • Or Remove everything (clean install)
  3. Follow the on-screen instructions.


💬 Feedback & Support

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.


📎 Tags

#Windows #BSOD #CRITICAL_PROCESS_DIED #blue-screen #boot-error #recovery #fix #windows-crash

About

Fix for CRITICAL_PROCESS_DIED — Windows BSOD error caused by system process failure during boot or runtime. Includes PowerShell recovery script, system repair steps, and diagnostics.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Contributors