Critical Process Died on Lenovo: How to Fix BSOD CRITICAL_PROCESS_DIED (Stop Code 0x000000EF)

Understanding the CRITICAL_PROCESS_DIED Error on Lenovo

The CRITICAL_PROCESS_DIED Blue Screen of Death (BSOD) carries stop code 0x000000EF and appears when the Windows kernel detects that a process essential to operating system integrity has terminated unexpectedly. On Lenovo ThinkPad, IdeaPad, Yoga, and Legion models, this error is disproportionately linked to driver-level conflicts, Lenovo-specific firmware bugs, and Windows Update side effects.

The full error message displayed on screen reads:

Your PC ran into a problem and needs to restart.
Stop code: CRITICAL_PROCESS_DIED

Windows may attempt to restart and loop back into the same BSOD, or it may boot into the Automatic Repair environment.

Step 1: Determine Whether You Can Boot Normally

Before any fix, assess your situation:

• Can you reach the Windows desktop? Even intermittently? If yes, start at Step 2.
• Are you stuck in a BSOD loop? You will need to access the Windows Recovery Environment (WinRE). Force the shutdown 3 times during the Windows boot animation to trigger Automatic Repair, or boot from a Windows 11/10 USB installation media.

From WinRE, navigate to: Troubleshoot > Advanced Options > Command Prompt to run repair commands.

Step 2: Boot into Safe Mode

Safe Mode loads Windows with only essential drivers, which helps isolate whether a third-party or Lenovo driver is causing the crash.

To enter Safe Mode:

1. Hold Shift and click Restart from the Start menu.
2. Go to Troubleshoot > Advanced Options > Startup Settings > Restart.
3. Press F4 for Safe Mode or F5 for Safe Mode with Networking.

If the BSOD does NOT appear in Safe Mode, a driver or startup service is almost certainly the culprit.

Step 3: Run System File Checker and DISM

Corrupted Windows system files are a leading cause of CRITICAL_PROCESS_DIED on Lenovo machines. Run these commands in an elevated Command Prompt:

sfc /scannow

Wait for completion. If SFC reports "Windows Resource Protection found corrupt files but was unable to fix some of them," follow up with DISM:

DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

After DISM completes, rerun sfc /scannow. Restart your Lenovo and check if the BSOD returns.

Step 4: Update or Roll Back Lenovo Drivers

Lenovo hardware relies on proprietary drivers for Thunderbolt, Power Management, ACPI, and the Lenovo Energy Management module. An incompatible or outdated version of any of these can terminate a critical Windows service.

Using Lenovo System Update (recommended):

1. Download Lenovo System Update from support.lenovo.com.
2. Run it and install all Critical and Recommended driver updates.
3. Prioritize: Chipset, ACPI, Thunderbolt, Intel ME Firmware, and Display drivers.

To roll back a specific driver:

1. Open Device Manager (Win + X > Device Manager).
2. Expand the relevant category (e.g., Display adapters, System devices).
3. Right-click the device > Properties > Driver tab > Roll Back Driver.

Common offenders on Lenovo devices include:

• intelppm.sys (Intel Processor Power Management)
• lenovo_pm_driver.sys (Lenovo Power Management)
• thunderbolt.sys (Thunderbolt controller)
• iaStorAVC.sys (Intel Rapid Storage Technology)

Step 5: Check Disk Health with CHKDSK

A failing SSD or HDD can corrupt process memory and trigger stop code 0x000000EF. Run:

chkdsk C: /f /r /x

You will be prompted to schedule the scan on next reboot. Type Y and restart. CHKDSK will run before Windows loads and repair bad sectors if possible.

For NVMe SSDs on Lenovo ThinkPads, also check the drive health using the manufacturer's tool (Samsung Magician, Crucial Storage Executive, or Intel SSD Toolbox).

Step 6: Analyze the Memory Dump File

Windows writes a minidump file each time a BSOD occurs, located at C:\Windows\Minidump\. Use WinDbg or the free WhoCrashed utility to identify the exact driver or process at fault.

Using WhoCrashed:

1. Download and install WhoCrashed (free) from resplendence.com.
2. Open it and click Analyze.
3. Look for the Caused by driver field — this will name the specific .sys file responsible.

Using WinDbg (advanced):

!analyze -v

Run this command inside WinDbg after opening the minidump file via File > Open Crash Dump.

Step 7: Test RAM with Windows Memory Diagnostic or MemTest86

Faulty RAM modules can cause process crashes. To run the built-in Windows test:

mdsched.exe

Choose Restart now and check for problems. For a deeper test, create a bootable MemTest86 USB from memtest86.com and let it run for at least 2 full passes (1-2 hours).

Step 8: Use System Restore

If the BSOD started after a Windows Update or software installation:

1. Search for Create a restore point in the Start menu.
2. Click System Restore > Next.
3. Select a restore point dated before the BSOD began.
4. Complete the wizard and restart.

This will not affect personal files but will remove recently installed apps and drivers.

Step 9: Reset or Reinstall Windows (Last Resort)

If the BSOD persists after all above steps:

1. Go to Settings > Update & Security > Recovery.
2. Under Reset this PC, click Get started.
3. Choose Keep my files to preserve personal data, or Remove everything for a clean slate.

Alternatively, perform a clean Windows installation from a USB drive, then reinstall Lenovo drivers manually from support.lenovo.com using your machine's serial number.

Lenovo-Specific Notes

• ThinkPad models (X1 Carbon, T14, T15, T490): Check for Lenovo BIOS/UEFI firmware updates, as several ThinkPad BIOS releases have contained fixes for ACPI-related BSODs.
• IdeaPad and Yoga models: Lenovo Energy Management and Lenovo Vantage have been known to conflict with Windows 11 updates. Try uninstalling and reinstalling Lenovo Vantage from the Microsoft Store.
• Legion gaming laptops: Nvidia driver conflicts are frequent. Use DDU (Display Driver Uninstaller) in Safe Mode to fully remove the GPU driver before reinstalling the latest version from nvidia.com.