What should I check first if I see critical process died symptoms?

First, proceed with the ‘Record the stop code and what happened’ step. The stop code is a key clue to narrowing down the cause, including drivers, memory, storage, and GPU. We recommend that you avoid changing multiple settings at once and check to see if your symptoms change after each step.

How do I check for ‘system file corruption’ as a possible cause?

If there is no change in the first step, compare ‘Revert recently added hardware, drivers, and programs’ in order. If symptoms disappear immediately after certain actions or the conditions for their occurrence change, this can be an important clue in narrowing down the cause.

CRITICAL_PROCESS_DIED Blue Screen Problems: When Do I Need a Professional Check?

Even if you follow the above solution steps in order, if the critical process died symptom repeats or hardware abnormal signals such as a burning smell, abnormal noise, overheating, or component recognition failure appear together, we recommend backing up important data and performing a professional inspection.

PC FIX

Computer Troubleshooting Guide

Windows

CRITICAL_PROCESS_DIED Blue Screen Issue

Among Windows issues, the “critical process died” symptom may be related to system file corruption or storage errors. Record the stop code and when it occurred, then narrow down the cause by recent changes, RAM/storage, and system files.

Solving Order
We've organized the methods starting with the simplest and least expensive ones. Please check the solutions one by one, starting from the top.

Do you have these symptoms?

critical process died
Kill important processes
0xef

main causes

System file corruption
storage error
Driver or security software conflict

How to solve

Please check them in order from the top. If the issue is resolved, you do not need to proceed to the next step.

Record stop codes and what happens

The stop code is a key clue to narrowing down the cause, including drivers, memory, storage, and GPU.

Difficulty Easy time 5 minutes cost 0 won

1Take a picture of the stop code and the 'What failed' item displayed on the screen.
2It records when things like gaming, booting, sleep, etc. occur.
3Make sure it's always the same code.

confirmation point

After these steps, see if the “critical process died” symptom decreases or disappears. If there is no change, check for possible system file corruption in the next step.

Revert recently added hardware, drivers, and programs

This is often caused by elements that were changed just before the blue screen.

Difficulty Moderate time 15-30 minutes cost 0 won

1If you have recently installed hardware, remove it and compare.
2Roll back the most recently updated driver or reinstall the manufacturer's stable version.
3Also check the system utilities installed immediately before the problem.

Check the same symptom in safe mode

Safe mode loads only a minimal number of drivers and services, which is helpful in narrowing down the cause.

Difficulty Moderate time 10-20 minutes cost 0 won

1Go to Settings → System → Recovery → Advanced startup.
2After restarting, select Troubleshoot → Advanced options → Startup Settings → Restart.
3See if the issue reproduces in safe mode.

confirmation point

In safe mode, if normal, third-party drivers, services, and startup programs are suspected first.

Diagnosing RAM and storage

Memory and system drive errors can create a variety of stop codes.

Difficulty Moderate time 30~120 minutes cost 0 won

1Run Windows Memory Diagnostic or Trusted Memory Scan.
2Check system drive SMART status and manufacturer diagnostics.
3If an error occurs, back up important files first.

Check Windows system files

Corrupted system files can create boot, explorer, app, and update problems.

Difficulty Moderate time 15-40 minutes cost 0 won

1Open a terminal or command prompt with administrator privileges.
2Run DISM /Online /Cleanup-Image /RestoreHealth.
3After completion, run sfc /scannow.
4When the scan is finished, restart your PC.

Review BIOS defaults and firmware updates

WHEA/Memory/Power Status errors may be related to unstable overclocking or an outdated BIOS.

Difficulty Advanced time 20~40 minutes cost 0 won

1Temporarily set Overclock, Undervolt, and XMP/EXPO to default settings.
2Check with your motherboard/laptop manufacturer for stable BIOS and chipset drivers.
3Never turn off the power during the BIOS update.

Frequently Asked Questions

We've put together a list of things we frequently check regarding this issue.

Related issues

If the symptoms do not match exactly, please check the issue below.

Windows

Windows blue screen keeps happening

Among Windows problems, “blue screen” symptoms may be related to driver or hardware errors, or memory/storage problems. Record the stop code and when it occurred, then narrow down the cause by recent changes, RAM/storage, and system files.

View solutions →

Windows

MEMORY_MANAGEMENT Blue Screen Issue

If you are seeing “memory management bsod” symptoms, possible causes include RAM failure or instability, or driver memory corruption. Record the stop code and when it occurred, then narrow down the cause by recent changes, RAM/storage, and system files.

View solutions →

Windows

INACCESSIBLE_BOOT_DEVICE Blue Screen Issue

If the current symptom is closer to “inaccessible boot device”, first check for storage controller driver or mode changes or boot drive errors. Record the stop code and when it occurred, then narrow down the cause by recent changes, RAM/storage, and system files.

View solutions →

Windows

SYSTEM_SERVICE_EXCEPTION Blue Screen Issue

If you see a “system service exception” symptom, potential causes include graphics, security, or system driver errors, or corrupted system files. Record the stop code and when it occurred, then narrow down the cause by recent changes, RAM/storage, and system files.

View solutions →

Look for other symptoms too

If you enter the symptoms you are currently seeing in the PC FIX search box, we will find the related problem.

Search for other issues →