Error Medic

HP Critical Process Died (BSOD): Complete Fix Guide for Windows 10/11

Fix the 'Critical Process Died' BSOD on HP laptops & desktops. Step-by-step solutions: driver rollback, SFC, DISM, BIOS update, and memory diagnostics.

Last updated:
Last verified:
2,139 words
Key Takeaways
  • Root Cause 1: Corrupt or incompatible HP drivers (especially HP SimplePass, CyberLink, or audio/network drivers) triggering the CRITICAL_PROCESS_DIED stop code (0x000000EF).
  • Root Cause 2: Corrupted Windows system files, a failed Windows Update, or faulty RAM/SSD hardware causing a critical kernel process to terminate unexpectedly.
  • Root Cause 3: Outdated BIOS firmware on HP Pavilion, ENVY, Spectre, or EliteBook models creating hardware-software conflicts with Windows 10/11 kernel.
  • Quick Fix Summary: Boot into Safe Mode, run SFC /scannow and DISM to repair system files, roll back or uninstall suspect drivers, check hardware with Windows Memory Diagnostic and HP PC Hardware Diagnostics UEFI, then update BIOS via HP Support Assistant.
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC & DISM System File RepairSystem files corrupted after update or improper shutdown15-30 minLow
Driver Rollback / UninstallBSOD started after a driver or Windows Update10-20 minLow
Windows Memory DiagnosticRandom BSODs, possible RAM failure30-60 minLow
HP PC Hardware Diagnostics UEFISuspect hardware (SSD, RAM, battery)30-90 minLow
System RestoreBSOD started after a recent change20-40 minLow-Medium
BIOS/UEFI Firmware UpdateOutdated BIOS causing HP-specific conflicts15-30 minMedium
Startup Repair / Reset This PCNothing else works, OS deeply corrupted1-3 hoursHigh (data risk)
Clean Windows InstallPersistent BSOD, hardware confirmed healthy2-4 hoursHigh (data loss)

Understanding the 'HP Critical Process Died' BSOD

The full error message displayed on your HP laptop or desktop 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 Windows stop code 0x000000EF (CRITICAL_PROCESS_DIED) means the Windows kernel detected that a process essential to system operation terminated either unexpectedly or in an invalid state. On HP machines, this frequently occurs due to HP-bundled software, outdated firmware, or driver conflicts introduced via Windows Update.


Step 1: Boot Into Safe Mode (If You Cannot Log In)

If your HP is stuck in a BSOD reboot loop, you must access Safe Mode first.

Method A – Interrupt the boot 3 times:

  1. Power on your HP. As soon as you see the HP logo, hold the power button to force shutdown.
  2. Repeat 2-3 times. Windows will boot into Windows Recovery Environment (WinRE).
  3. Navigate to: Troubleshoot → Advanced Options → Startup Settings → Restart.
  4. After restart, press F4 for Safe Mode or F5 for Safe Mode with Networking.

Method B – Using installation media:

  1. Boot from a Windows 10/11 USB.
  2. Select Repair your computer → Troubleshoot → Advanced Options → Command Prompt.

Step 2: Check the Minidump / Event Log to Identify the Culprit Process

Before applying fixes blindly, identify which process triggered the crash.

Using Event Viewer:

  1. Press Win + R, type eventvwr.msc, press Enter.
  2. Navigate to Windows Logs → System.
  3. Filter by Error and Critical levels. Look for events just before the crash time.
  4. Note any referenced .sys files (driver) or .exe processes.

Using WinDbg or WhoCrashed (free tool):

  • Download WhoCrashed from resplendence.com, install, and run. It parses minidumps in C:\Windows\Minidump\ and tells you exactly which driver caused the crash.
  • Common culprits on HP machines: HpqKbFiltr.sys, hpaudiorts.sys, cyhid.sys, iaStorA.sys (Intel RST), HpSAMD.sys.

Step 3: Run SFC and DISM to Repair Corrupted System Files

Open Command Prompt as Administrator (or from WinRE):

:: Step 3a – System File Checker
sfc /scannow

:: Step 3b – If SFC reports errors it cannot fix, run DISM first
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

:: Step 3c – Run SFC again after DISM completes
sfc /scannow

Restart your HP after these complete. If the BSOD is gone, corrupted system files were the culprit.


Step 4: Roll Back or Uninstall Problem Drivers

HP machines ship with many proprietary drivers. A Windows Update or manual driver update can introduce a broken version.

Via Device Manager:

  1. Press Win + XDevice Manager.
  2. Expand Display Adapters, Network Adapters, Sound, Video and Game Controllers.
  3. Right-click a device → Properties → Driver tab → Roll Back Driver.

Uninstall HP SimplePass / CyberLink / HP Audio Switch:

  1. Press Win + Rappwiz.cpl.
  2. Uninstall: HP SimplePass, CyberLink Power2Go, HP Audio Switch, HP 3D DriveGuard (if present).
  3. Reboot and test.

Prevent a specific Windows Update driver from reinstalling:

:: Run in elevated PowerShell
wushowhide.diagcab
:: Use the 'Hide updates' wizard to block the problematic driver update

Step 5: Run Windows Memory Diagnostic

Faulty RAM is a major cause of CRITICAL_PROCESS_DIED on HP Pavilion and ENVY models.

  1. Press Win + R → type mdsched.exe → Enter.
  2. Choose Restart now and check for problems.
  3. Windows will run a full memory test on reboot (takes 20-40 min).
  4. Results appear in Event Viewer under Windows Logs → System, source: MemoryDiagnostics-Results.

If errors are found, try reseating your RAM sticks. If the error persists with a single stick, the RAM module is defective.


Step 6: Run HP PC Hardware Diagnostics UEFI

HP provides a built-in hardware test you can access without Windows:

  1. Shut down your HP completely.
  2. Power on, immediately press Esc repeatedly until the Startup Menu appears.
  3. Press F2 to enter HP PC Hardware Diagnostics UEFI.
  4. Run the Extensive Test for storage (SSD/HDD) and Memory Test.
  5. If a component fails, note the Failure ID (24-character code) for HP support.

Common failure IDs related to CRITICAL_PROCESS_DIED:

  • Storage failures → SSD/NVMe corruption or failure
  • Memory failures → RAM defect

Step 7: Update or Roll Back BIOS Firmware

An outdated BIOS is a frequent HP-specific cause of this BSOD, especially after upgrading from Windows 10 to Windows 11.

Update BIOS via HP Support Assistant:

  1. Open HP Support Assistant (search in Start).
  2. Go to Updates → Check for Updates and Messages.
  3. If a BIOS update is listed, install it. Your HP will restart into a BIOS flash utility.

Manual BIOS update:

  1. Visit https://support.hp.com/us-en/drivers.
  2. Enter your HP model number.
  3. Filter by BIOS under the driver category.
  4. Download the .exe installer and run it on Windows, or download the .bin file for a USB-based update.

WARNING: Never interrupt a BIOS update. Ensure your HP laptop is plugged in.


Step 8: Use System Restore

If the BSOD started after a recent change and you have restore points:

  1. Boot into WinRE (see Step 1).
  2. Navigate to Troubleshoot → Advanced Options → System Restore.
  3. Select a restore point dated before the BSOD started.
  4. Follow the wizard to restore.

Step 9: Reset This PC / Clean Install (Last Resort)

If all else fails and hardware is confirmed healthy:

Reset This PC (keeps files option):

  1. WinRE → Troubleshoot → Reset this PC → Keep my files.
  2. Follow the prompts. This reinstalls Windows while preserving your personal files.

Clean Install:

  1. Create a Windows 11 USB with the Media Creation Tool.
  2. Boot from USB, select Custom: Install Windows only.
  3. Format the Windows partition and install fresh.
  4. Download HP drivers from https://support.hp.com after install.

HP Pavilion-Specific Notes

HP Pavilion 15, 14, and 17 series users frequently encounter CRITICAL_PROCESS_DIED due to:

  • Intel Rapid Storage Technology (RST) driver conflicts with NVMe SSDs. Fix: Update or uninstall Intel RST via Device Manager.
  • HP Fast Charge software conflicts. Uninstall from Programs and Features.
  • Realtek audio driver versions shipped with Pavilion causing RTKVHD64.sys crashes. Download the latest Realtek audio driver directly from HP's support page for your exact model.

Frequently Asked Questions

bash
:: ============================================================
:: HP CRITICAL PROCESS DIED - Diagnostic & Fix Commands
:: Run Command Prompt as Administrator
:: ============================================================

:: --- 1. Check stop code in system log ---
wevtutil qe System /q:"*[System[(Level=1 or Level=2) and TimeCreated[timediff(@SystemTime) <= 86400000]]]" /f:text /rd:true /c:20

:: --- 2. List recent minidump files ---
dir C:\Windows\Minidump\ /od

:: --- 3. Run System File Checker ---
sfc /scannow

:: --- 4. DISM - Check and restore Windows image health ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

:: --- 5. Check disk for errors (will run on next reboot) ---
chkdsk C: /f /r /x

:: --- 6. Run Windows Memory Diagnostic ---
start mdsched.exe

:: --- 7. List installed drivers with details (export to file) ---
driverquery /v /fo csv > C:\Temp\drivers_list.csv

:: --- 8. Check for recently installed/updated drivers (last 7 days) ---
pnputil /enum-drivers

:: --- 9. Uninstall a known bad HP driver by INF name (example: HP SimplePass) ---
:: pnputil /delete-driver oem42.inf /uninstall /force

:: --- 10. View recent critical/error events in System log ---
powershell -Command "Get-EventLog -LogName System -EntryType Error,Warning -Newest 50 | Format-List TimeGenerated, Source, EventID, Message | Out-File C:\Temp\system_errors.txt"

:: --- 11. Export BugCheck (BSOD) events only ---
powershell -Command "Get-WinEvent -FilterHashtable @{LogName='System'; Id=41} | Select-Object TimeCreated, Message | Format-List | Out-File C:\Temp\bsod_events.txt"

:: --- 12. Check Intel RST driver version (common HP Pavilion culprit) ---
powershell -Command "Get-WmiObject Win32_PnPSignedDriver | Where-Object {$_.DeviceName -like '*Intel*Storage*' -or $_.DeviceName -like '*Rapid*'} | Select-Object DeviceName, DriverVersion, DriverDate"

:: --- 13. List HP-specific software installed ---
powershell -Command "Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like 'HP*'} | Select-Object Name, Version | Sort-Object Name | Format-Table -AutoSize"

:: --- 14. Startup Repair (run from WinRE Command Prompt if Windows won't boot) ---
:: bootrec /fixmbr
:: bootrec /fixboot
:: bootrec /scanos
:: bootrec /rebuildbcd

:: --- 15. Open HP PC Hardware Diagnostics (if available in Windows) ---
:: C:\Windows\System32\HPSFAClient.exe

:: ============================================================
:: After running diagnostics, reboot and test.
:: ============================================================
E

Error Medic Editorial

Error Medic's editorial team is composed of senior DevOps engineers, SRE specialists, and Windows system administrators with 10+ years of experience diagnosing and resolving BSODs, kernel panics, and OS-level failures across enterprise and consumer hardware. Our guides are validated against real hardware configurations and updated with each major Windows release.

Sources

Related Articles in Hp Critical Process Died

Explore More windows Guides