Critical Process Died on Lenovo Laptop: Complete Fix Guide (BSOD Stop Code)
Fix the 'Critical Process Died' BSOD on Lenovo laptops with step-by-step solutions including driver updates, SFC scans, and registry fixes.
- Root Cause 1: Corrupted or incompatible device drivers — especially after Windows Updates or Lenovo Vantage driver pushes — are the most common trigger for the CRITICAL_PROCESS_DIED stop code (0x000000EF) on Lenovo machines.
- Root Cause 2: Corrupted Windows system files, a damaged page file, bad RAM, or failing NVMe/SSD storage can cause a critical kernel process to terminate unexpectedly, forcing an immediate BSOD.
- Root Cause 3: Conflicting third-party software or malware that hooks into kernel-level processes (e.g., antivirus drivers, VPN kernel modules) can destabilize the session and trigger the stop code.
- Quick Fix Summary: Run 'sfc /scannow' and 'DISM /Online /Cleanup-Image /RestoreHealth' from an elevated command prompt, roll back recently updated drivers in Device Manager, disable Fast Startup, and check memory with Windows Memory Diagnostic — these steps resolve the issue in the majority of Lenovo CRITICAL_PROCESS_DIED cases.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| SFC + DISM System File Repair | First step for any CRITICAL_PROCESS_DIED; corrupted OS files suspected | 15–30 min | Low |
| Driver Rollback / Uninstall | BSOD started after a Windows Update or Lenovo Vantage driver update | 10–20 min | Low |
| Windows Memory Diagnostic / MemTest86 | Crashes are random and not tied to any specific action or app | 30 min – 8 hrs | None |
| Disable Fast Startup | BSOD on wake-from-hibernate or cold boot on Lenovo machines | 2 min | Very Low |
| Clean Boot (Selective Startup) | Suspect third-party software or kernel-mode driver conflict | 20–40 min | Low |
| Startup Repair / Automatic Repair | Cannot boot into Windows at all; stuck in BSOD loop | 15–25 min | Low |
| CHKDSK Scan | Crashes during file operations; SSD/HDD errors suspected | 20–60 min | Low |
| Reset / Reinstall Windows | All other methods failed; system is severely corrupted | 1–3 hrs | Medium-High (data loss risk) |
Understanding the 'Critical Process Died' Error on Lenovo
The stop code CRITICAL_PROCESS_DIED (Bug Check Code: 0x000000EF) appears when Windows detects that a process essential to system operation has terminated abnormally or illegally. On Lenovo laptops — including ThinkPad, IdeaPad, Legion, and Yoga series — this error is particularly common due to the combination of Lenovo-specific power management drivers, the Lenovo Vantage software stack, and aggressive Windows Update policies.
The full error screen typically reads:
Your PC ran into a problem and needs to restart.
We're just collecting some error info, and then we'll restart for you.
Stop code: CRITICAL_PROCESS_DIED
The crash dump file (usually located at C:\Windows\Minidump\) contains a WerFault or kernel reference that identifies the offending process. Common culprits seen in Lenovo minidumps include ntoskrnl.exe, lenovowmidriverpackage.sys, energy_driver.sys, or third-party antivirus kernel modules.
Step 1: Boot into Safe Mode (If You Cannot Reach the Desktop)
If your Lenovo is stuck in a BSOD loop:
- Force-shutdown your Lenovo 3 times in a row by holding the power button during boot. Windows will enter Automatic Repair mode.
- Navigate to Advanced Options → Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press F4 or 4 to boot into Safe Mode, or F5 / 5 for Safe Mode with Networking.
Once in Safe Mode, you can safely perform the steps below without triggering the crash.
Step 2: Run System File Checker and DISM
Corrupted Windows system files are the single most common cause of CRITICAL_PROCESS_DIED on Lenovo laptops. Run these commands in order from an elevated Command Prompt (Run as Administrator):
sfc /scannow
Wait for the scan to complete (this takes 10–20 minutes). If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them," proceed with DISM:
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
After DISM completes, run sfc /scannow one more time and then restart your Lenovo.
Step 3: Identify and Roll Back Problematic Drivers
Lenovo laptops push driver updates through both Windows Update and the Lenovo Vantage application. A newly installed driver that is unsigned or incompatible can immediately trigger this BSOD.
To check recently updated drivers:
- Open Device Manager (right-click Start → Device Manager).
- Look for devices with a yellow warning icon.
- Right-click the problematic device → Properties → Driver tab → Roll Back Driver.
High-priority drivers to check on Lenovo:
- Display adapter (Intel/AMD/NVIDIA GPU drivers)
- Network adapters (Intel Wi-Fi drivers are frequent offenders)
- Lenovo Power Management driver
- Thunderbolt / USB-C controller drivers
- Storage controller (Intel RST / NVMe drivers)
To list all recently installed drivers via PowerShell:
Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object TimeCreated, Message | Format-List
You can also use the WinDbg Preview app from the Microsoft Store to open the minidump file and identify the exact faulting driver.
Step 4: Disable Fast Startup
Lenovo's power management stack has a known conflict with Windows Fast Startup (Hybrid Shutdown), causing CRITICAL_PROCESS_DIED on boot or wake events.
- Open Control Panel → Power Options → Choose what the power buttons do.
- Click "Change settings that are currently unavailable".
- Uncheck "Turn on fast startup (recommended)".
- Click Save changes and restart.
Step 5: Run Windows Memory Diagnostic
Faulty RAM can cause seemingly random CRITICAL_PROCESS_DIED crashes. Run the built-in test:
- Press Win + R, type
mdsched.exe, press Enter. - Choose "Restart now and check for problems".
- The diagnostic runs before Windows loads and displays results on next boot.
For a more thorough test, boot from a MemTest86 USB drive and let it run at least 2 full passes.
Step 6: Check the Drive for Errors
A failing SSD or HDD can cause critical system processes to crash when they cannot read essential data.
chkdsk C: /f /r /x
You will be prompted to schedule the scan for the next restart. Type Y and restart. The scan runs before Windows loads and fixes bad sectors.
Step 7: Perform a Clean Boot
A clean boot starts Windows with a minimal set of drivers and startup programs, helping isolate a third-party software conflict.
- Press Win + R, type
msconfig, press Enter. - On the General tab, select Selective startup and uncheck Load startup items.
- Go to the Services tab, check Hide all Microsoft services, then click Disable all.
- Go to the Startup tab and open Task Manager; disable all startup items.
- Click OK and restart.
If the BSOD stops, re-enable services in batches to find the culprit. Lenovo Vantage background services and third-party antivirus kernel drivers are the most frequent offenders.
Step 8: Update or Reinstall Lenovo-Specific Drivers
Visit the Lenovo Support Driver & Software page for your exact model. Ensure you are downloading drivers matched to your specific machine type (found on the sticker on the bottom of your Lenovo or via msinfo32).
Key packages to update:
- Lenovo System Interface Foundation
- Lenovo Power Management Driver
- Lenovo Vantage (or uninstall it entirely if crashes persist)
- BIOS/UEFI firmware update (often fixes deep hardware-driver handshake issues)
Step 9: Use Startup Repair (If Still in BSOD Loop)
- Boot from a Windows 10/11 installation USB.
- Select Repair your computer → Troubleshoot → Advanced Options → Startup Repair.
- Let Windows attempt to automatically repair boot configuration data and system files.
Step 10: Reset or Reinstall Windows (Last Resort)
If all above steps fail, perform a Windows Reset:
- Go to Settings → System → Recovery → Reset this PC.
- Choose "Keep my files" first — this rebuilds Windows while preserving personal data.
- If that fails, choose "Remove everything" and perform a clean reinstall.
For a completely clean slate, create a bootable USB with the Media Creation Tool from Microsoft and perform a fresh install, then reinstall Lenovo drivers from the support site.
Frequently Asked Questions
:: ============================================================
:: Lenovo Critical Process Died - Diagnostic & Fix Commands
:: Run Command Prompt as Administrator
:: ============================================================
:: STEP 1: Check and repair system files
sfc /scannow
:: STEP 2: DISM health check and repair (use after SFC)
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
:: STEP 3: Run SFC again after DISM completes
sfc /scannow
:: STEP 4: Schedule disk error check on next boot
chkdsk C: /f /r /x
:: STEP 5: View recent stop codes from Event Log
wevtutil qe System /q:"*[System[Provider[@Name='Microsoft-Windows-WER-SystemErrorReporting']]]" /f:text /c:10
:: STEP 6: List recently installed/updated drivers (PowerShell)
powershell -Command "Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object TimeCreated, Message | Format-List"
:: STEP 7: Check driver versions and identify unsigned drivers
powershell -Command "Get-WindowsDriver -Online | Sort-Object Driver | Format-Table Driver, Version, Date, ProviderName"
:: STEP 8: Find and list all minidump files
dir C:\Windows\Minidump\ /s /b
:: STEP 9: Export system info for support analysis
msinfo32 /report %USERPROFILE%\Desktop\sysinfo.txt
:: STEP 10: Disable Fast Startup via registry (alternative to GUI)
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /v HiberbootEnabled /t REG_DWORD /d 0 /f
:: STEP 11: Reset TCP/IP stack (if network driver-related BSOD)
netsh int ip reset
netsh winsock reset
:: STEP 12: Run Memory Diagnostic
mdsched.exe
:: STEP 13: Open Windows Reliability Monitor for crash timeline
perfmon /rel
:: STEP 14: Verify BIOS version (note output for Lenovo Support)
wmic bios get smbiosbiosversion
:: STEP 15: Check for Windows Update pending restarts
powershell -Command "Get-WindowsUpdate" 2>nul || echo Install PSWindowsUpdate module to use this commandError Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, Windows SREs, and systems administrators with a combined 30+ years of experience diagnosing kernel-level failures, BSOD stop codes, and hardware-software conflicts across enterprise and consumer environments. Our guides are based on hands-on lab testing, real-world incident post-mortems, and ongoing analysis of Microsoft and Lenovo support documentation. We specialize in making complex system-level troubleshooting accessible and actionable for users of all skill levels.
Sources
- https://support.microsoft.com/en-us/windows/windows-stop-codes-whea-errors-and-bug-check-codes-a4fa0ca2-7e89-4df5-b3e9-7bba5cc50b6d
- https://support.lenovo.com/us/en/solutions/ht505097-blue-screen-errors-windows-10
- https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died
- https://answers.microsoft.com/en-us/windows/forum/all/critical-process-died-bsod-on-lenovo-laptop/
- https://superuser.com/questions/1715342/lenovo-laptop-getting-critical-process-died-bsod-after-windows-update