Error Medic

HP Critical Process Died (BSOD): Complete Troubleshooting Guide for HP Pavilion and Other HP Laptops

Fix the 'Critical Process Died' BSOD on HP laptops with step-by-step solutions: driver rollback, SFC scans, BIOS updates, and memory diagnostics.

Last updated:
Last verified:
2,215 words
Key Takeaways
  • Root Cause 1: Corrupted or incompatible drivers (especially after Windows Update or HP driver updates) trigger the CRITICAL_PROCESS_DIED stop code 0x000000EF, killing an essential Windows kernel process.
  • Root Cause 2: Failing or faulty RAM, corrupted system files (ntfs.sys, win32k.sys), or a damaged Windows installation can force the kernel watchdog to halt the OS with this BSOD.
  • Root Cause 3: BIOS/UEFI firmware that is out of date on HP Pavilion models can conflict with Windows 10/11 power management and cause random critical process crashes during sleep/wake cycles.
  • Quick Fix Summary: Run 'sfc /scannow' and DISM to repair system files, boot into Safe Mode to uninstall recently added drivers, update or roll back HP-specific drivers (chipset, ACPI, display), run Windows Memory Diagnostic, and flash the latest HP BIOS update from hp.com/support.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC + DISM System File RepairCorrupted Windows system files suspected; intermittent BSOD after updates10-30 minLow
Driver Rollback / UninstallBSOD started after a driver or Windows Update installation5-15 minLow
Windows Memory DiagnosticRandom BSODs, especially under load or after waking from sleep15-60 minNone
HP BIOS / Firmware UpdateHP Pavilion BSOD during sleep/hibernate, power state transitions15-20 minMedium
Startup Repair via WinRESystem cannot boot to desktop; BSOD on startup loop10-20 minLow
System RestoreBSOD appeared after a specific update or software install15-45 minLow-Medium
Clean Windows ReinstallAll other fixes failed; persistent BSOD; heavily corrupted OS60-180 minHigh (data loss)

Understanding the 'Critical Process Died' Error on HP Laptops

The Blue Screen of Death (BSOD) displaying CRITICAL_PROCESS_DIED (Stop Code: 0x000000EF) means the Windows kernel detected that a critical process it depends on terminated unexpectedly. On HP Pavilion, HP Envy, HP EliteBook, and other HP models, this is one of the most frequently reported stop errors and is particularly common after Windows 10 or Windows 11 feature updates.

The exact error screen looks like this:

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

Windows logs the crash in Event Viewer under Windows Logs > System with Event ID 41 (Kernel-Power) or Event ID 1001 (BugCheck), and minidump files are saved to C:\Windows\Minidump\.


Step 1: Collect Crash Information

Before applying any fix, identify what process or driver caused the crash.

Check Event Viewer:

  1. Press Win + X and select Event Viewer.
  2. Navigate to Windows Logs > System.
  3. Filter by Critical and Error levels.
  4. Look for Event ID 41 (unexpected shutdown) or Event ID 1001 (Windows Error Reporting).
  5. Note the timestamp matching the BSOD and record the faulting module name.

Analyze the Minidump file: Install WinDbg from the Microsoft Store or use the free tool WhoCrashed to analyze C:\Windows\Minidump\*.dmp files. These will identify the specific driver or process (e.g., nvlddmkm.sys for NVIDIA, iaStorA.sys for Intel RST, or hpdskflt.sys for HP disk filter drivers).


Step 2: Boot Into Safe Mode

If the BSOD appears during startup, you must access Windows Recovery Environment (WinRE):

  1. Force shutdown your HP laptop 3 times in a row during boot (hold power button for 5 seconds).
  2. On the third restart, Windows will enter Automatic Repair mode.
  3. Click Advanced Options > Troubleshoot > Advanced Options > Startup Settings > Restart.
  4. Press F4 to boot into Safe Mode or F5 for Safe Mode with Networking.

In Safe Mode, only essential Microsoft drivers load. If the BSOD disappears in Safe Mode, a third-party driver or HP-specific driver is the culprit.


Step 3: Run System File Checker and DISM

Corrupted Windows system files are a leading cause of CRITICAL_PROCESS_DIED on HP laptops, especially after interrupted Windows Updates.

Open Command Prompt as Administrator and run:

sfc /scannow

Wait for the scan to complete (100%). If it reports "Windows Resource Protection found corrupt files but was unable to fix some of them", run DISM first:

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

After DISM completes, run sfc /scannow again. Reboot when done.


Step 4: Update or Roll Back Drivers

HP Pavilion models frequently encounter this BSOD due to:

  • HP ACPI driver conflicts
  • Intel Management Engine Interface (MEI) driver issues
  • Display adapter drivers (Intel HD / UHD or AMD Radeon on HP dual-GPU models)
  • Intel Rapid Storage Technology (RST) driver corruption

To roll back a driver:

  1. Press Win + X > Device Manager.
  2. Right-click the suspected device > Properties.
  3. Go to the Driver tab > click Roll Back Driver (if available).

To uninstall a problematic driver:

  1. In Device Manager, right-click the device > Uninstall device.
  2. Check Delete the driver software for this device.
  3. Reboot and let Windows reinstall the driver automatically, or download the correct version from hp.com/support.

To get the exact HP driver package: Visit https://support.hp.com/us-en/drivers, enter your HP model number (found on the sticker on the bottom of your laptop or via msinfo32), and download the HP Support Assistant or individual driver packages.


Step 5: Update HP BIOS / UEFI Firmware

Outdated BIOS firmware is a known trigger for Critical Process Died BSODs on HP Pavilion models during sleep, hibernate, or power state transitions. HP regularly releases BIOS updates to fix compatibility issues with Windows.

To check your current BIOS version: Press Win + R, type msinfo32, and look at BIOS Version/Date.

To update:

  1. Go to https://support.hp.com/us-en/drivers
  2. Enter your product name or number.
  3. Filter by BIOS under the driver category.
  4. Download and run the HP BIOS update utility.
  5. Do NOT interrupt the BIOS update process — keep the laptop plugged into AC power.

Step 6: Run Windows Memory Diagnostic

Faulty RAM causes unpredictable critical process crashes.

  1. Press Win + R, type mdsched.exe, press Enter.
  2. Choose Restart now and check for problems.
  3. The tool runs on reboot and logs results to Event Viewer under Windows Logs > System, source: MemoryDiagnostics-Results.

For a more thorough test, use MemTest86 (bootable USB tool) to run extended RAM tests over several hours.

If RAM errors are found, reseat the RAM modules (if accessible on your HP model) or replace the faulty stick.


Step 7: Check Disk Health

A failing SSD or HDD can corrupt system files and cause this BSOD.

chkdsk C: /f /r /x

Schedule the disk check on reboot when prompted. For SSDs, also check S.M.A.R.T. data using CrystalDiskInfo (free tool).


Step 8: Perform a System Restore

If the BSOD started after a specific update or software install:

  1. Boot into Safe Mode (Step 2).
  2. Press Win + R, type rstrui.exe.
  3. Choose a restore point dated before the BSOD started.
  4. Follow the wizard and reboot.

Step 9: Disable Fast Startup (HP-specific fix)

HP Pavilion models with hybrid sleep enabled commonly crash with CRITICAL_PROCESS_DIED on wake. Disabling Fast Startup fixes this for many users:

  1. Go to Control Panel > Power Options > Choose what the power buttons do.
  2. Click Change settings that are currently unavailable.
  3. Uncheck Turn on fast startup (recommended).
  4. Click Save changes and reboot.

Step 10: Nuclear Option — Reset or Reinstall Windows

If all steps above fail, a clean Windows installation resolves persistent CRITICAL_PROCESS_DIED errors caused by deep OS corruption.

Option A — Keep your files: Go to Settings > Windows Update > Recovery > Reset this PC > Keep my files.

Option B — Full clean install: Create a Windows 11/10 bootable USB via the Microsoft Media Creation Tool, boot from USB, and perform a clean install.

After reinstalling, install only the HP drivers from hp.com/support — avoid installing all drivers at once. Add them one by one to identify any problematic driver.

Frequently Asked Questions

bash
# ============================================================
# HP Critical Process Died - Diagnostic & Fix Commands
# Run all commands in an elevated Command Prompt (Run as Admin)
# ============================================================

# --- 1. Check Windows version and BIOS info ---
msinfo32
# Look for: BIOS Version/Date and OS Build Number

# --- 2. System File Checker (SFC) ---
sfc /scannow
# Wait for 100% completion. Check output for errors.

# --- 3. DISM Repair (run before SFC if SFC fails) ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# After DISM completes, run SFC again:
sfc /scannow

# --- 4. Check Disk for errors (schedule on next reboot) ---
chkdsk C: /f /r /x
# Type Y when asked to schedule on next restart, then reboot

# --- 5. View recent BSODs in Event Viewer (PowerShell) ---
Get-EventLog -LogName System -EntryType Error -Newest 20 | Where-Object {$_.Source -eq 'Microsoft-Windows-WER-SystemErrorReporting' -or $_.EventID -eq 41 -or $_.EventID -eq 1001} | Format-List TimeGenerated, Message

# --- 6. List minidump files for analysis ---
dir C:\Windows\Minidump\

# --- 7. View installed driver list with dates (PowerShell) ---
Get-WmiObject Win32_PnPSignedDriver | Select-Object DeviceName, DriverVersion, DriverDate | Sort-Object DriverDate -Descending | Format-Table -AutoSize

# --- 8. Check recently installed Windows Updates ---
wmic qfe list brief /format:table

# --- 9. Run Windows Memory Diagnostic ---
mdsched.exe
# Choose 'Restart now and check for problems'

# --- 10. Disable Fast Startup (HP sleep/wake BSOD fix) via PowerShell ---
powercfg /h off
# This disables hibernation and fast startup, fixing HP power-state BSODs

# --- 11. Export System Info to file for HP Support ---
msinfo32 /nfo C:\SystemInfo.nfo
# Share this file with HP support if escalating the issue

# --- 12. Roll back a specific driver via Device Manager (PowerShell) ---
# Example: Roll back display driver
pnputil /enum-drivers
# Find the driver and use:
# pnputil /delete-driver oemXX.inf /uninstall
# (Replace XX with the actual number from enum-drivers output)

# --- 13. Scan for malware (may cause rogue process termination) ---
MpCmdRun -Scan -ScanType 2
# This runs Windows Defender full scan from CLI

# --- 14. Verify HP device drivers are up to date ---
# Open HP Support Assistant from Start Menu, or visit:
# https://support.hp.com/us-en/drivers
# Enter your product name to find the latest drivers and BIOS
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SRE professionals, and Windows systems administrators with 10+ years of experience diagnosing and resolving operating system errors, hardware failures, and enterprise software issues. Our guides are based on real-world troubleshooting scenarios, official vendor documentation, and community-validated solutions. We specialize in Windows BSOD analysis, Linux kernel panics, and cross-platform reliability engineering.

Sources

Related Articles in Hp Critical Process Died

Explore More windows Guides