Critical Process Died ntoskrnl.exe: How to Fix the BSOD Error in Windows 10/11

You are here:

Home
Support
Tips System Rescue
Critical Process Died ntoskrnl.exe: How to Fix the BSOD Error in Windows 10/11

17 March 2026 Jennifer Thatcher Technology Manager of Test Dept.

Last update by Emma Johnson at 17 March 2026

Summary
This article analyzes the critical_process_died ntoskrnl exe Blue Screen of Death error in Windows environments. It outlines common crash scenarios, underlying causes, and structured solution categories ranging from basic checks to system recovery and reinstallation options.

Table of contents

Quick Checks Before Advanced Fixes

Using Renee PassNow for Data Recovery or Data Backup

Repair Methods

1. Repairing System Files with Built‑in Windows Tools
2. Driver and Update Rollbacks to Address Root Causes
3. Hardware Diagnostics for Persistent BSOD Issues

Final Method: Resetting or Reinstalling Windows as a Last Resort

Frequently Asked Questions

The CRITICAL_PROCESS_DIED Blue Screen of Death (BSOD) stop code (technically 0x000000EF) appears when a critical Windows system process terminates unexpectedly, forcing an immediate shutdown to prevent further damage.

Critical Process Died ntoskrnl.exe Windows 10

The error often lists ntoskrnl.exe (the Windows kernel executive) as the faulty module because the kernel is involved in almost every operation; however, it is rarely the root cause itself and usually points to a faulty driver, corrupted system file, hardware issue, or recent software change that destabilizes the kernel. This critical_process_died ntoskrnl exe issue can manifest in various disruptive ways.

Common scenarios include:

Boot loop or repeated restarts right after login.
Post-Windows Update crash (especially after feature or security patches).
Gaming or high-load crashes (when graphics/storage drivers are stressed).
New hardware installation (RAM, SSD, GPU, or motherboard changes).

Important note on support status: Windows 10 reached end of support on October 14, 2025. Microsoft no longer provides security updates, technical assistance, or fixes for this operating system. You cannot expect official Microsoft help, and many repair paths must be performed manually by the user. Before executing any method in this article, perform a full data recovery and backup/transfer operation first to prevent permanent data loss.

Comparison of Symptoms, Causes, and Solution Paths

Symptom	Likely Cause	General Solution Path
BSOD on every boot	Corrupted system files or drivers	Safe Mode → SFC/DISM → Driver rollback
Crashes during games	Graphics/storage driver conflict	Driver update/rollback or hardware test
Post-update instability	Faulty Windows Update or component	Update rollback or system reset
After new RAM/SSD	Hardware incompatibility or failure	Memory/disk diagnostics + reseat parts
Random crashes under load	Overheating, failing HDD/SSD, malware	Hardware diagnostics + clean install

refer:

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef–critical-process-died

https://support.microsoft.com/en-us/windows/use-the-system-file-checker-tool-to-repair-missing-or-corrupted-system-files-79aa86cb-ca52-166a-92a3-966e85d4094e

Quick Checks Before Advanced Fixes

Before using any repair tools or running system commands, start with these safe, non‑destructive checks. They don’t change system files or personal data and can sometimes resolve—or at least narrow down—the cause of a critical_process_died ntoskrnl exe BSOD with minimal effort.

1. Perform a full power cycle

Shut the computer down completely. Unplug the power cable, and if you’re using a laptop, remove the battery if it’s removable. Wait about 2–3 minutes, then reconnect everything and power the system back on. This clears residual power and can resolve temporary hardware or firmware glitches.

2. Disconnect all external devices

Remove all non‑essential peripherals, including USB drives, printers, external hard drives, webcams, and secondary monitors. Leave only the keyboard and mouse connected. Faulty or incompatible devices can sometimes trigger kernel‑level crashes during startup.

3. Try booting into Safe Mode

Restart the system and hold Shift while selecting Restart, or use the recovery menu to enter Safe Mode. If Windows starts successfully in Safe Mode, the problem is likely caused by a third‑party driver, startup program, or recent software change rather than core system files.

These checks usually take just a few minutes and carry virtually no risk. However, they won’t fix severe system corruption or failing hardware. If the blue screen continues to appear, the next priority should be backing up important data before moving on to more advanced repair methods.

Using Renee PassNow for Data Recovery or Data Backup

Before performing ANY subsequent repair steps (including Safe Mode commands, driver rollbacks, or Windows Reset), back up or transfer all important data using Renee PassNow.

This is the safest first action because the tool runs outside Windows in a bootable environment, allowing you to access and copy files even when the system is stuck in BSOD loops or completely unbootable. Prioritizing this step is crucial when facing the critical_process_died ntoskrnl exe error to avoid data loss during troubleshooting.

Renee PassNow is most effective in these situations:

Repeated BSOD prevents normal or Safe Mode boot.
Built-in Windows tools (SFC, DISM, Recovery) are inaccessible.
You need to clone/transfer data to an external drive before risky repairs.

Main features of Renee PassNow for recovery/backup:

Data Transfer & Backup: Copy files, folders, or entire partitions from a non-booting drive to another internal/external disk without starting Windows.
Disk Cloning: Create a full backup image of your hard drive (including OS, programs, and personal files) to an external device.
Undeleter / Data Recovery: Recover deleted or lost files from corrupted disks (photos, documents, etc.) with preview support.
Windows Recovery: Fixes common boot failures and general BSOD issues (MBR, DBR, black screen, etc.) in minutes.

It works via a simple bootable USB/CD created on any working computer; supports Windows 10/11 and runs in a PE/Linux environment.

Renee Passnow – Professional Windows Password Remover

Remove Windows Login Password 3 steps for whole password remove process.

Recover the files Recover the deleted files without Windows system.

Transfer the data Transfer the important files of the computer with system.

Multifuctional Data transfer, data recovery, bootable problem recovery can be run without system.

Highly compatible Windows 11/10/8.1/8/7/XP/Vista. UEFI boot.

Remove Login Password Support Windows 11/10/8.1/8/7/XP/Vista. UEFI boot.

Recover the files Recover the deleted files without Windows system.

Transfer the data Transfer the important files of the computer with system.

Free Trial Free TrialNow 2000 people have downloaded!

In addition, Renee PassNow supports Bitlocker:

Repair Methods

If you have already backed up your data and the PC still won’t boot normally, you can access the Windows Recovery Environment (WinRE) to fix the issue.

To create WinRE media:

Required if your built-in Windows Recovery Environment is broken

1. On another working Windows PC, download the Media Creation Tool from the official Microsoft page:

https://www.microsoft.com/software-download/windows10

https://www.microsoft.com/software-download/windows11

2. Run the tool, choose “Create installation media for another PC”, select Windows 10, and make a bootable USB flash drive (minimum 8 GB, completely empty).

3. Insert the USB into the affected PC, enter BIOS/UEFI (usually F2, Del, or F10), set USB as first boot device, and boot to access repair options.

1. Repairing System Files with Built‑in Windows Tools

SFC (System File Checker) and DISM (Deployment Image Servicing and Management) are built‑in Windows utilities designed to detect and repair corrupted system components. File‑level corruption is a common trigger behind ntoskrnl.exe‑related crashes in the critical_process_died ntoskrnl exe BSOD, especially after interrupted updates, improper shutdowns, or malware activity. When used correctly, these tools are safe and do not affect personal files.

Prerequisites

You must be able to access Safe Mode with Command Prompt or the Windows Recovery Environment (WinRE). If Windows cannot boot normally, installation media may be required.

Advantages:

Free and built-in
No third-party software required
Can repair system corruption without data loss
Effective for update-related issues

Disadvantages:

May fail if system image is severely damaged
Requires WinRE or bootable media if Windows won’t start
Cannot fix hardware or driver-level problems
Limited to Windows system files

Step 1: Boot into WinRE or Safe Mode with Command Prompt

If Windows still boots (even briefly):

1. Restart the PC.

2. Hold Shift, then select Restart from the power menu.

3. Navigate to Troubleshoot → Advanced options → Startup Settings → Restart.

select startup settings in advanced options

4. Press 6 or F6 to select Safe Mode with Command Prompt.

If Windows does NOT boot at all:

1. Power on the PC and interrupt the startup process three times in a row by holding the power button to force shutdown while Windows is loading.

2. On the next startup, Windows should automatically enter the Windows Recovery Environment (WinRE).

3. Select Troubleshoot → Advanced options → Command Prompt.

4. Choose your Windows user account and enter the account password if prompted.

If you do not have the administrator account password, please use the Windows Password reset function or Windows Account creation function.

Renee Passnow – Professional Windows Password Remover