CRITICAL_PROCESS_DIED black screen at random times

Question

CRITICAL_PROCESS_DIED black screen at random times

Bill Lindsay 0

During the course of normal use, while I am playing a game, watching my video player, or basically doing anything (writing, etc), my system would freeze, and then moments later, it would jump to a black screen with the words 'Your PC has run into an error and needs to restart.' Under that, '0% complete'. And at the bottom, it says, 'Stop Code:' some words in all caps, often it's 'CRITICAL_PROCESS_DIED (0xEF)', sometimes it's something different. Sometimes, the system would restart on its own, but most of the time, the screen stays like that, and I have to manually restart (by pressing the power button. This started on Monday (2/9), the morning after I had received a big update. I tried re-installing Windows 11 (I don't know if that was complete, it took about two hours, and the system crashed a couple of times during the process), I tried downloading any new update available, etc etc. My system froze and black screened about ten times that morning, and has done so several times earlier today. It would work just fine for a time and then would crash very unexpectedly. I could use it for hours and it would not crash, then it would crash. I am at my wits' end. Thanks for any advice you have.

4 answers

Your answer

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

DaveM121 850.2K Independent Advisor

Sorry, I was offline.

That is not good if you are unable to log into Windows.

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Please try each option one at a time, then see if Windows will successfully login.

Go to Troubleshoot - Advanced Option - Startup Repair

See if Windows startup can repair itself

Go to Troubleshoot - Advanced Option - System Restore

Check to see if you have a restore point you can go back to

Bill Lindsay 0 Reputation points

2026-02-16T17:54:08.7166667+00:00

Thank you for your response. I tried each option that you suggested in Recovery mode (the startup repair, and system restore--with the restore point that you suggested earlier)--both processes went without a problem, but the system still took me to the login screen where it rejects my pin (same problem--due to too many shutdowns) and tells me to either wait 2 hours or try another sign-in method (where I have to wait 30 days for my cell phone number to be accepted. Do you think that after I did the recovery, it may not crash during the 2 hour wait period? I used the latest restore point (which I made when you suggested it), should I try an earlier one(if I have one)? or will I need to wait the 30 days for my cell number to be accepted? I am waiting the 2 hour period to see if it does not crash, then I will try the pin number again.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-16T17:58:21.4+00:00

Okay, if after the two hours you are still not able to log into the device, you may need to consider resetting or re-installing Windows.
Bill Lindsay 0 Reputation points

2026-02-16T20:22:00.6766667+00:00

I returned to my computer an hour and a half later and found that it had crashed. So I tried the reset--i chose local reset and to keep my personal files. When this was done, it took me to the login screen again and rejected my pin again, for the same reasons. Are we out of answers? Am I going to have to wait the 30 days?

Answer 3

DaveM121 850.2K Independent Advisor

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

Bill Lindsay 0 Reputation points

2026-02-11T20:18:16.04+00:00

Thank you for your prompt reply. I found the Minidump folder, but there was nothing in it. It is now about 2:11pmCST on 2/11; the folder list said that the Minidump folder was last modified at 9:22am on 2/10 (yesterday). I can't recall what I was doing at that time. If this is any help, the track I followed to find the folder was This PC > Local Disc (C:) >Windows.old > WINDOWS > Minidump .
DaveM121 850.2K Reputation points Independent Advisor

2026-02-12T07:02:27.9533333+00:00

Sorry, I was offline.

If the path you followed is This PC > Local Disc (C:) >Windows.old > WINDOWS > Minidump

Open File Explorer again, then go to This PC > Local Disc (C:) > WINDOWS > Minidump, are there any minidump files available in that folder,
Bill Lindsay 0 Reputation points

2026-02-12T14:04:11.44+00:00

Thank you for your response. There is no folder right under Local Disc (C:) named WINDOWS in all caps, though there is one named 'Windows'; under that, there is no Minidump folder. The one I mentioned above was the only one I found, and it was empty. Could this be part of the problem? Could it be that my Minidump folder got misplaced as a result of the recent updates?
DaveM121 850.2K Reputation points Independent Advisor

2026-02-12T14:09:01.3166667+00:00

CLick your Start Button, then just type sysdm.cpl and press Enter.

On the resulting utility, select the Advanced tab.

Click the Settings button in the 'Startup and Recovery' section.

Please provide a screenshot of the next window.
Bill Lindsay 0 Reputation points

2026-02-12T14:44:03.35+00:00

I take it you meant 'sysdm.cpl'?

I attempted to take a screenshot with Ctrl+Shift+S, and it didn't appear that anything happened. I looked at my Screenshots folder and didn't see the screen I took a shot of in it. But under 'System Failure', both 'Write an event to the system log' and 'Automatically restart' are checked. And under 'Write debugging information', 'Small memory dump (256KB) is selected, and the Small Dump Directory is '%SystemRoot%\Minidump' . If that is at all helpful...?
DaveM121 850.2K Reputation points Independent Advisor

2026-02-12T14:47:29.1433333+00:00

Yep, sorry about that, it was a typo.

If those are your settings, your system should be producing minidump files when it crashes, please wait for your system to crash again and ensure the percentage on the BSOD gets to 100% before the PC restarts, then check if there is any minidump file created.
Bill Lindsay 0 Reputation points

2026-02-12T15:07:34.01+00:00

How long should it take before the BSOD gets to 100% (I take it you mean the '0% complete' line)?? It doesn't seem to change, but then I might not be waiting long enough...?? Okay, I will wait next time and let you know of any minidumps. Thanks.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-12T15:09:00.6766667+00:00

Okay, I will be here, it should not take long for that to reach 100%
Bill Lindsay 0 Reputation points

2026-02-12T21:08:49.5233333+00:00

I had to leave for an appointment, but just as I was about to shut the system down, it froze and crashed again, and blackscreened, with '0% complete'. I left it like that and went to my appointment, at 10:40amCST, to see if it would process through. I returned at 1:25pmCST, 2 hours and 45 minutes later. The screen was still black with '0% complete'. I switched it off, then restarted, and still did not find a 'WINDOWS' folder under 'This PC > Local Disc (C:)', there was a 'Windows' folder under it but no minidump folder, and the minidump folder under 'This PC > Local Disc (C:) >Windows.old > WINDOWS' was empty with no modifications since 2/10. I hope I have not driven you crazy...?? What do you recommend? Did I still not wait long enough?
DaveM121 850.2K Reputation points Independent Advisor

2026-02-13T06:31:46.25+00:00

If your system did not produce a minidump file after ten minutes, then it is not going to.

To try to force Windows to show any faulting drivers, the best option would be to turn on Driver Verifier, let your PC crash 3 times, then you must turn off Driver Verifier, and finally, upload any newly created minidump files

Before you run Driver Verifier, please create a new System Restore Point

https://learn.microsoft.com/en-us/answers/questions/4377096/(article)-driver-verifier-tracking-down-a-mis-beha?forum=windows-windows_10-update&referrer=answers

.

.

.

Note, if you have any difficulty getting into Windows with Driver Verifier enabled:

Start your PC, just as Windows attempts to load (spinning dots), press and hold Power Button for 5 - 10 seconds to perform a Hard Shut Down

Do this twice

On the third start Windows will boot into the Recovery Environment and from there you can access System Repair, Safe Mode, Command Prompt... etc.

Go to Troubleshoot - Advanced Option - Startup Settings and click Restart

Upon restart, press 4 to enter Safe Mode

Open Command Prompt as Administrator and run these two commands, then restart your PC.

verifier /reset

verifier /bootmode resetonbootfail
Bill Lindsay 0 Reputation points

2026-02-13T12:50:41.52+00:00

I posted another comment, yesterday, but apparently it didn't go through. I had to leave for an appointment yesterday at 10:40am, and just as I was about to shut down my computer, it froze and crashed again, blackscreening. It had the '0% complete' line. I decided to leave it that way, with the blackscreen on, while I was away for my appointment. I returned at about 1:25pm, 2 hours 45 minutes later, and the blackscreen was still up, with '0% complete'. The Stopcode, by the way, was (and often is) CRITICAL_PROCESS_DIED (0xEF) . I don't know if that is helpful. But I restarted the computer, and found the same situation-- no minidump file under WINDOWS, but there was a 'Windows' folder, with no Minidump folder under it, and the Minidump folder under 'Windows.old' is empty. Was almost 3 hours still not long enough to wait? I hope I am not driving you crazy! Thanks for anything that you can recommend.
Bill Lindsay 0 Reputation points

2026-02-13T12:52:35.22+00:00

Oh okay, I see that you did get that message. Let me try your recommendation.
Bill Lindsay 0 Reputation points

2026-02-13T14:49:45.53+00:00

I did as you suggested, and this time I finally have some minidump files. I let it crash three times, as you suggested, and I got some stopcodes (I could catch only a few words of them, the system restarted before I could write them down, but here they are--) BUGCODE_NDSDRIVER....; SYSTEM_THREAT_EXCEPTION_NOT_HANDLED....; IQRL_NOT_LESS_OR_EQUAL... I could not recall anything in the parentheses. Also, I remembered to turn off the Verifier (with verifier/reset ; I had to log on as the administrator to do that). Question-- after I execute 'verifier/reset', is the final line supposed to be 'drivers verified: none'?? I recall checking all of the drivers that were NOT from Microsoft. Now I have zipped up the dump files and I am trying to follow your instructions about uploading them to the Cloud...? Sorry I am not so computer literate.
Bill Lindsay 0 Reputation points

2026-02-13T15:24:02.8333333+00:00

Here are the links to the zipped-up Minidump files---

https://1drv.ms/u/c/60c651e72e925d56/IQBab1SYO9O7RYYIOx87ukUdAWlhLCxA04DaszVt6Re9jqc?e=7TbFar

https://1drv.ms/u/c/60c651e72e925d56/IQD8o_kBczGjTI7FrksAgpHAAR_mXieCPE7lQ6GLnnX5lZk?e=KI1RbA

https://1drv.ms/u/c/60c651e72e925d56/IQDRa05pS6KeSrhybWcJwrrjARHXCcJHOEglNLz02zZe7sQ?e=2aAHwU

Let me know if you have any trouble viewing them. Thank you so much for your time and recommendations.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-14T06:57:01.48+00:00

Sorry, I was offline.

All your minidump files indicate it is the Realtek WiFi drivers causing your PC to crash.

Go to the support page for your PC on the manufacturers website, then from there, download and re-install (not update) the version of Realtek WiFi (WLAN) drivers they provide.
Bill Lindsay 0 Reputation points

2026-02-14T20:20:12.9733333+00:00

Thank you so much. I will do that. But the problem now is that my system has locked me out, because I have had to shut it down so much, when it did not restart after black screening. I was using my five digit pin, now it has been disabled. It tells me to keep it on for two hours, then try again. But then it would blackscreen before the two hours were up. The only other sign in option is a phone number that I had when I first set up the account years ago, and it's a land line. I have successfully changed the number, but I have to wait for 30days. I am writing with my cell phone right now, which I have attached to my computer, so now I can still check my Outlook account. But I still cannot log on to my system. Any suggestions?? Thank you so much for your help and suggestions.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-17T06:44:02.52+00:00

Sorry, I was offline, do you have a backup of your files, or use a cloud service like OneDrive to sync your files online.

If so, you may need to reset Windows while choosing to delete everything, then create a new account after the reset so you can access your device.
Bill Lindsay 0 Reputation points

2026-02-17T14:59:08.5533333+00:00

Can I not just call Microsoft support using the landline number that is already in my security information??: would that not be enough proof of my identity for the company to remove the restriction from my pin number?? Ido have some backup of my work, and I do use OneDrive, but I'd hate to risk losing a lot of it, if all I need to do to log in is prove my identity...? Thank you for your patience.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-18T06:29:20.66+00:00

Sorry, I was offline.

If you are able to contact their support, they may be able to provide you with access to your account, it is worth trying that first.
Bill Lindsay 0 Reputation points

2026-02-18T14:16:26.69+00:00

Thank you, I will. If this does not work, then I will try a full system reset. I 'll let you know how it goes.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-18T14:23:07.6866667+00:00

Glad to help!
Bill Lindsay 0 Reputation points

2026-02-18T16:23:55.8933333+00:00

You have been very helpful, I just haven't been very security conscious. Once I get back on my system, I will remember to freshen up my Wi-fi driver, as you recommended. And I will mark this problem as solved.
DaveM121 850.2K Reputation points Independent Advisor

2026-02-18T16:25:22.6166667+00:00

No problem at all, glad to help!

Answer 4

The issue you are experiencing, indicated by the stop code CRITICAL_PROCESS_DIED (0xEF), typically occurs when a critical system process fails during boot or while the system is running. This can lead to system instability, including the black screen and need for a restart that you described.

Here are some troubleshooting steps you can take to address this issue:

Check for Recent Changes: Since you mentioned that this started after a big update, consider rolling back the update if possible, or check for any new updates that might address the issue.
Device Drivers: Ensure that all your device drivers are up to date. You can do this through the Device Manager. Look for any drivers that may have issues or are marked with an exclamation point.
Hardware Diagnostics: Run hardware diagnostics provided by your system manufacturer to check for any underlying hardware issues.
Memory Diagnostics: Use the Windows Memory Diagnostics tool to check for memory errors. You can find this tool in the Control Panel under Memory.
Event Viewer: Check the Event Viewer for any critical errors that occurred around the time of the crashes. This can help identify the faulty driver or hardware.
Virus Scan: Run a full virus scan to ensure that no malware is affecting system processes.

If the problem persists after trying these steps, you may need to consider more advanced troubleshooting methods, such as attaching the OS disk to a recovery VM or enabling dump logs for further analysis.

References:

Share via

CRITICAL_PROCESS_DIED black screen at random times

4 answers

Your answer