Error Medic

HP Critical Process Died (BSOD): Complete Troubleshooting Guide for HP Pavilion & Laptop Users

Fix the HP 'Critical Process Died' BSOD error with step-by-step commands, driver fixes, SFC scans, and registry repairs. Works for HP Pavilion and all HP laptop

Last updated:
Last verified:
2,436 words
Key Takeaways
  • Root cause 1: Corrupt or incompatible HP device drivers (especially graphics, chipset, or touchpad drivers) trigger the CRITICAL_PROCESS_DIED stop code 0x000000EF when Windows cannot safely terminate a protected process.
  • Root cause 2: Damaged Windows system files, bad disk sectors, or faulty RAM cause protected kernel processes to crash, resulting in the blue screen error on HP Pavilion and other HP models.
  • Root cause 3: Recent Windows Updates, HP Support Assistant auto-updates, or third-party software installations can corrupt critical system processes and trigger the stop code.
  • Quick fix summary: Run SFC /scannow and DISM commands in an elevated Command Prompt, update or roll back HP drivers via Device Manager, disable Fast Startup, run CHKDSK on your system drive, and if all else fails, perform a Startup Repair or system reset from Windows Recovery Environment (WinRE).
Fix Approaches Compared
MethodWhen to UseTimeRisk
SFC & DISM ScanSystem files are corrupt; BSOD occurs randomly or after Windows Update10-30 minLow — read-only scan then in-place repair
Driver Rollback / UpdateBSOD started after a driver or HP Support Assistant update5-20 minLow — reversible via Device Manager
CHKDSK Disk ScanBSOD accompanied by slow performance or disk errors in Event Viewer20-120 minLow — read-only by default; /f flag writes fixes
Disable Fast StartupBSOD occurs only on cold boot or after hibernate/sleep2 minVery Low — settings change only
Windows Startup RepairCannot boot into Windows at all; stuck in reboot loop15-45 minLow-Medium — modifies boot configuration
Uninstall Recent Updates (KB)BSOD began immediately after a specific Windows Update10-20 minLow — uninstall single update package
Memory Diagnostic (MemTest)Random BSODs with different stop codes; suspect faulty RAM1-8 hoursVery Low — non-destructive read test
System RestoreBSOD appeared after software or configuration change; restore point exists20-40 minLow-Medium — reverts system state
Windows Reset / ReinstallAll other methods failed; data backed up1-3 hoursHigh — may erase personal files if not careful

Understanding the HP Critical Process Died Error

The Blue Screen of Death (BSOD) error CRITICAL_PROCESS_DIED (Stop Code: 0x000000EF) appears when Windows detects that a critical system process — one that must remain running for the OS to function — has either crashed or been terminated unexpectedly. On HP laptops and desktops (including the HP Pavilion series), this error is more common due to the proprietary HP driver ecosystem and HP Support Assistant updates interacting with Windows kernel processes.

The exact on-screen message you will see 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

In some variants, the screen may also show a QR code and reference critical_process_died in lowercase. The system will attempt to reboot automatically, and in loop-crash scenarios, it will eventually boot into Windows Recovery Environment (WinRE).


Step 1: Identify the Triggering Driver via Event Viewer

If you can boot into Windows (even in Safe Mode), the first diagnostic step is to check Windows Event Viewer for the exact failing process.

  1. Press Win + X and select Event Viewer.
  2. Navigate to Windows Logs > System.
  3. Filter for Error and Critical events around the time of the BSOD.
  4. Look for entries from sources like BugCheck, nvlddmkm (NVIDIA), atikmdag (AMD), igdkmd64 (Intel), or HpqKbFiltr (HP keyboard filter driver).
  5. Note the Event ID and the faulting module name — this is your primary lead.

Alternatively, navigate to C:\Windows\Minidump and locate the most recent .dmp file. Open it in WinDbg or upload it to an online minidump analyzer to identify the crashing module.


Step 2: Boot into Safe Mode (If You Cannot Load Windows)

If the system is stuck in a reboot loop:

  1. Force power off the HP laptop three times in a row during the Windows logo screen. On the third reboot, Windows will automatically enter WinRE.
  2. In WinRE, go to Troubleshoot > Advanced Options > Startup Settings > Restart.
  3. Press F4 to enable Safe Mode or F5 for Safe Mode with Networking.
  4. Once in Safe Mode, proceed with the diagnostic and repair steps below.

Step 3: Run SFC and DISM to Repair System Files

Corrupted Windows system files are a leading cause of CRITICAL_PROCESS_DIED on HP machines. Run these commands in an Administrator Command Prompt in this exact order:

# Step 1: Run DISM to repair the Windows component store first
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

# Step 2: Run System File Checker after DISM completes
sfc /scannow

If SFC finds and fixes files, it will report: "Windows Resource Protection found corrupt files and successfully repaired them." Restart after this step.


Step 4: Update or Roll Back HP Drivers

HP-specific drivers are a frequent culprit. Follow these sub-steps:

Option A — Roll Back a Recently Updated Driver:

  1. Press Win + X > Device Manager.
  2. Expand Display adapters, right-click your GPU (e.g., AMD Radeon, NVIDIA GeForce, or Intel UHD Graphics).
  3. Select Properties > Driver tab > Roll Back Driver.
  4. Repeat for Human Interface Devices (HP HID driver), Keyboards (HpqKbFiltr), and System devices (HP chipset drivers).

Option B — Download Fresh Drivers from HP Support:

  1. Visit https://support.hp.com/us-en/drivers and enter your exact model number (found on the sticker under your HP Pavilion).
  2. Download and install: Chipset, Graphics, Audio, and HP System Event Utility drivers.
  3. Restart after each critical driver installation.

Option C — Uninstall HP Support Assistant: HP Support Assistant occasionally pushes incompatible driver versions. Temporarily uninstall it via Control Panel > Programs > Uninstall a program to rule it out.


Step 5: Disable Fast Startup

Fast Startup keeps the Windows kernel session in a hibernation state, which can cause driver state corruption on HP systems and trigger CRITICAL_PROCESS_DIED on next boot.

  1. Open 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 perform a full shutdown (not restart).

Step 6: Check Disk Health with CHKDSK

Bad sectors on the SSD or HDD can corrupt system files mid-read, causing protected process failures.

# Schedule CHKDSK on the system drive for next reboot
chkdsk C: /f /r /x
# You will be prompted: "Would you like to schedule this volume to be checked the next time the system restarts? (Y/N)"
# Type Y and press Enter, then restart

For NVMe SSDs on newer HP Pavilion models, also run the HP PC Hardware Diagnostics tool (available from BIOS/UEFI on boot — press Esc at startup, then F2 for Diagnostics).


Step 7: Run Windows Memory Diagnostic

Faulty RAM can cause random CRITICAL_PROCESS_DIED stops.

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

For deeper testing, create a bootable USB with MemTest86 (free) and run it overnight through multiple passes.


Step 8: Uninstall Problematic Windows Updates

If the BSOD started immediately after a Windows Update:

  1. Go to Settings > Windows Update > View update history > Uninstall updates.
  2. Sort by Installed On date and uninstall the most recent cumulative update (e.g., KB5034122, KB5031445).
  3. Restart and monitor for recurrence.
  4. To prevent the update from reinstalling, use Microsoft's Show or Hide Updates troubleshooter tool.

Step 9: Perform Startup Repair from WinRE

If none of the above resolves the issue:

  1. Boot into WinRE (force three crashes or use Windows installation media).
  2. Go to Troubleshoot > Advanced Options > Startup Repair.
  3. Let Windows attempt automatic repair.
  4. If startup repair fails, try System Restore from the same menu using a restore point dated before the BSOD started.

Step 10: Reset or Reinstall Windows (Last Resort)

  1. In WinRE, go to Troubleshoot > Reset this PC.
  2. Choose Keep my files for a non-destructive reset, or Remove everything for a clean install.
  3. After reset, install HP drivers manually from the HP support site before running Windows Update.

HP-Specific Registry Fix for Critical Process Died

In some HP Pavilion models, a known registry key conflict with HP's diagnostic tools causes the error. To check:

# Open Registry Editor (run as Administrator)
regedit

# Navigate to:
# HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager
# Look for the "BootExecute" key
# Default value should be: autocheck autochk *
# If it contains unfamiliar HP or third-party entries, those may be culprits

Do not modify registry keys unless you have exported a backup first (File > Export in Registry Editor).

Frequently Asked Questions

bash
# ============================================================
# HP Critical Process Died - Diagnostic & Repair Script
# Run all commands in an ELEVATED Command Prompt (Run as Admin)
# ============================================================

# --- STEP 1: Check Windows System File Integrity ---
DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

# --- STEP 2: Schedule CHKDSK on System Drive ---
chkdsk C: /f /r /x
# Enter Y when prompted, then restart manually

# --- STEP 3: Export Recent BSOD Info from Event Log ---
wevtutil qe System /q:"*[System[Provider[@Name='BugCheck']]]" /f:text /c:5

# --- STEP 4: List Last 10 Installed Driver Files (PowerShell) ---
# Run this in PowerShell as Admin:
# Get-WinEvent -LogName System | Where-Object {$_.Id -eq 7045} | Select-Object -First 10 | Format-List TimeCreated, Message

# --- STEP 5: Check for Pending Corrupt System Files ---
findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log | findstr /c:"cannot repair"

# --- STEP 6: View Current Driver List and Find HP-Specific Drivers ---
driverquery /v /fo list | findstr /i "hp"

# --- STEP 7: Disable Fast Startup via Registry ---
reg add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Power" /v HiberbootEnabled /t REG_DWORD /d 0 /f

# --- STEP 8: Check Minidump Location for BSOD Files ---
dir C:\Windows\Minidump

# --- STEP 9: Run Windows Memory Diagnostic (schedules for next reboot) ---
mdsched.exe

# --- STEP 10: List Recently Installed Windows Updates ---
wmic qfe list brief /format:table | sort /r

# --- STEP 11: Uninstall a Specific KB Update (replace KBXXXXXXX with actual KB number) ---
# wusa /uninstall /kb:XXXXXXX /quiet /norestart

# --- STEP 12: Run HP BIOS Diagnostics Tool (from Command Prompt) ---
# This requires HP PC Hardware Diagnostics for Windows to be installed:
# HPSFViewer.exe (locate in C:\Program Files (x86)\HP\HP PC Hardware Diagnostics Windows)

# --- STEP 13: Collect System Info for HP Support Ticket ---
msinfo32 /report %USERPROFILE%\Desktop\SystemInfo.txt

# --- STEP 14: Verify Boot Configuration Data (BCD) Integrity ---
bcdedit /enum all

# --- STEP 15: Rebuild BCD if Corrupt (run from WinRE Command Prompt) ---
# bootrec /fixmbr
# bootrec /fixboot
# bootrec /scanos
# bootrec /rebuildbcd

# ============================================================
# After running scans, restart the system.
# Check C:\Windows\Logs\CBS\CBS.log for detailed SFC results.
# ============================================================
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and Windows system administrators with 10+ years of experience diagnosing BSOD errors, kernel panics, and system failures across enterprise and consumer hardware. Our HP troubleshooting guides are tested on HP Pavilion, HP ProBook, HP EliteBook, and HP Spectre hardware running Windows 10 and Windows 11. We consult Microsoft's official documentation, HP's driver support database, and real-world community reports from Stack Overflow and Microsoft Answers to ensure every fix is actionable and accurate.

Sources

Related Articles in Hp Critical Process Died

Explore More windows Guides