BSOD CRITICAL_PROCESS_DIED crashes while starting up a game or during gameplay

Question

BSOD CRITICAL_PROCESS_DIED crashes while starting up a game or during gameplay

AzraelVP 20

Hello, I have a problem with my Windows 11 desktop PC, where during game startup (any game) or after like 5-15 minutes of gameplay, my PC restarts and BSOD screen flashes for less than a second, without the usual blue background, just plain white text about how my device ran into a problem and needs to restart.

Problem started while I had Windows 11 24H2 update installed, uninstalling update did not help, now I have 25H2 and it still crashes. PC was in multiple repair shops for diagnostics (total 7 times on diagnostics/windows reinstalls/..) and no issue with RAM, CPU, GPU or even drives was found, even under heavy load. I sent my main system drive (NVMe drive) on warrancy replacement, same as my motherboard, just to be sure. BIOS was updated during the last repairshop visit as I forgot to update it when the replacement motherboard came back.

99% of BSOD crashes are CRITICAL_PROCESS_DIED, only twice or thrice a SET_OF_INVALID_CONTEXT appeared since the problems started.

This is the report from Event Viewer after the crash:

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 28. 11. 2025 13:47:00

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: DESKTOP-DN3OAUJ

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:

<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />

<EventID>41</EventID>

<Version>10</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2025-11-28T12:47:00.3309786Z" />

<EventRecordID>7407</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>DESKTOP-DN3OAUJ</Computer>

<Security UserID="S-1-5-18" />

</System>

<Data Name="BugcheckCode">239</Data>

<Data Name="BugcheckParameter1">0xffff9e8a34b9d080</Data>

<Data Name="BugcheckParameter2">0x0</Data>

<Data Name="BugcheckParameter3">0x0</Data>

<Data Name="BugcheckParameter4">0x0</Data>

<Data Name="SleepInProgress">0</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">0</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">0</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">true</Data>

<Data Name="CheckpointStatus">0</Data>

<Data Name="CsEntryScenarioInstanceIdV2">0</Data>

<Data Name="LongPowerButtonPressDetected">false</Data>

<Data Name="LidReliability">false</Data>

<Data Name="InputSuppressionState">0</Data>

<Data Name="PowerButtonSuppressionState">0</Data>

<Data Name="LidState">3</Data>

<Data Name="WHEABootErrorCount">0</Data>

</EventData>

</Event>

My PC specs are:

AMD Ryzen 5 5600X 6-Core 3701 MHz
Nvidia GeForce RTX 3060 12GB
32GB RAM DDR4
700W PSU
ASUS TUF Gaming A520M-PLUS II motherboard
System drive: Kingston KC3000 M.2 NVMe
Other drives: ADATA SU650 (like month old; for games), GIGABYTE GP-GSTFS31240GNTD (a bit older but no system files on it, only games)

0 comments

Answer accepted by question author

David-M 128.2K Independent Advisor

Sorry for the delay in reply. I've been offline.

That's unfortunate. Your best option now is to consult a trusted technician for a thorough hardware inspection. And by "thorough", I don't mean running stress tests; I mean physically examining the components themselves to identify the issue.

If no problems are identified, I believe it would be a good idea to check the electrical system in the house.

What I can tell you for sure is that I don't see any evidence that it's a software problem.

Feel free to ask back any questions.

0 comments

3 additional answers

Your answer

Answer 1

David-M 128.2K Independent Advisor

Thanks for the screenshot.

I suggest doing the following:

Go to the Asus website using the link below, download the latest Chipset driver, and install it.

https://www.asus.com/supportonly/tuf%20gaming%20a520m-plus%20ii/helpdesk_download/

Driver name: AMD Chipset driver v6.05.16.221 for Windows 10, Windows 11 64-bit

(Extract the ZIP file, and double-click the file "AsusSetup" to run it. Then, follow the on-screen instructions to install the driver.)

Then, restart your PC and see if the system will work stably.

If the BSOD occurs again after doing this, please share the minidump it created.

Feel free to ask back any questions.

Standard Disclaimer: There is a link to a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.

AzraelVP 20 Reputation points

2025-11-28T17:50:54.15+00:00

Done, same BSOD crash - CRITICAL_PROCESS_DIED. Literally within first 3 minutes of me starting a game. And yet, no minidump folder in Windows folder on C:, so I cannot provide you with any log unfortunately :(
David-M 128.2K Reputation points Independent Advisor

2025-11-28T17:59:26.62+00:00

This type of crash is usually the result of severe system corruption or hardware issues. The only driver that comes to mind that could potentially cause it is the chipset. Since your BIOS is already up to date, we can rule that out as the source of the problem.

You said the system was reinstalled.

Do you know which method was used to reinstall it?

Was it a clean installation using an installation media (USB flash drive), completely erasing the system drive before reinstalling? Or reset the PC?

I await your reply.
AzraelVP 20 Reputation points

2025-11-28T18:13:04+00:00

As much as I remember, it was reinstalled through a USB flash drive in the repairshop last time I was there (approximately 2 weeks ago).
David-M 128.2K Reputation points Independent Advisor

2025-11-28T18:17:58.7166667+00:00

Thanks for the clarification.

This procedure is called a Clean Install. BSOD problems do not survive a Clean Install unless the problem is caused by the hardware.

Do you have any objections to attempting a clean installation yourself? I'll give you all the steps you need to do it.

Clean Installing Windows will remove all data stored on the system. Therefore, you will need to back up your personal files on an external drive or cloud storage service.

I await your reply.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T18:23:44.8+00:00

Is it really neccessary when it was done and the problems still persist? Last time I also had some problems activating my old Windows 11 Home license that I had, so I had to buy new one after reinstall and I do not wish to buy another one if same problem occurs.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T18:28:29.4566667+00:00

Thanks for the clarification.

If you're certain that a clean install was performed, there's no need to repeat the process. In that case, the issue is confirmed to be hardware-related.

Regarding the license, you can use the same license you used previously, and the system will be activated.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T18:32:59.0066667+00:00

What kind of hardware issue could this be? Repairshop had no problems running the games I normally do, when the PC was there for the past week. Just as I get it back and plug it in at home, same problems occur instantly.

In repairshop they also did heavy-load tests on CPU, GPU, even PSU. They did memory diagnostics through the tool, no problems found. I myself did the SFC command within CMD, no problems found. I even tried DISM command, nothing has changed. The system drive (NVMe) and motherboard underwent warrancy replacement (so I have those brand new).

To be honest, I seem to be out of options and don't know what to do. I hoped you might have had some answers to this problem :-/
David-M 128.2K Reputation points Independent Advisor

2025-11-28T18:39:50.62+00:00

Unfortunately, your PC isn't providing any clear signs that would allow me to identify which component might be causing the issue remotely. A precise diagnosis would only be possible through a physical inspection with spare parts.

Based on what you mentioned, since the problem started after returning, have you tried plugging the computer into a different outlet? Power-related issues can make the system unstable.

Another possibility is that a component wasn't seated properly and may have shifted slightly during transport.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T18:42:49.4466667+00:00

Yes, I tried two different outlets, worked fine yesterday, today it started doing the problems again, so I switched outlets, still crashes.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T18:49:19.1566667+00:00

Thanks for the clarification.

Do you have other desktop computers in your home that work without problems?

I await your reply.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T18:58:22.46+00:00

Hi again. My earlier question may have seemed vague, so let me clarify why I asked it.

If the other desktops in your home are working normally, then the issue is unlikely to be power-related. However, if those desktops are also showing unusual behavior, that would strengthen the possibility of a power problem in your home. This would explain why the issue only reappeared once you started using your PC at home again.

Based on all the reports you've given and the procedures performed, I'm certain that the problem is not software-related.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T19:01:02.8533333+00:00

I don't have any other desktops at home, this is the only one. I am trying something to re-check the minidumps, as to why are they not being created. If I succeed on getting one from the crash, I will share it with you through onedrive. In the meanwhile, what else should I try?
David-M 128.2K Reputation points Independent Advisor

2025-11-28T19:09:19.6466667+00:00

Unfortunately, there's really nothing you can do to force your PC to generate minidumps. The inability to create them is almost certainly related to the type of crash that's occurring. I've seen this behavior many times before, and in those cases, the root cause was hardware, most often the motherboard or processor. Pinpointing the exact faulty component can be quite challenging. Therefore, it wouldn't be surprising if the issue went unnoticed by the technician during the inspection. Another important point: stress tests aren't reliable for diagnosing this type of problem.

At this point, I don't see any software-related procedure that could help, since all the evidence strongly suggests the problem lies in the hardware.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T19:38:11.0066667+00:00

Understood, thank you for trying to help me. Now I do not know what I did, but the game that previously crashed the system now works fine and I do not dare to touch anything else as long as it works :D
David-M 128.2K Reputation points Independent Advisor

2025-11-28T19:43:35.66+00:00

Did you move the PC or tamper with any components?

If yes, that strengthens my suspicion that a component might not be properly fitted. This isn't that uncommon.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T19:49:25.63+00:00

No, I did not tamper with anything other than turning off and back on my power breaker for the PC room outlets, thought it might do something with their electrical current, which sounds ridiculous as it is, but apparently it helped.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T19:56:34.2033333+00:00

It's not ridiculous at all. This problem could very well be electrical. When a game starts up, that's when the computer draws the most power. I've seen computers exhibit similar behavior, and in those cases, the issue was traced back to faulty wiring in the outlet or even the electrical system of the entire house, although this is rare.

Faults in the wiring of the outlet or even in the electrical installation of the house can generate voltage drops, spikes, or electrical noise that affect the computer's operation. This can result in crashes, unexpected restarts, or strange behavior.

This would explain why the problem doesn't occur when taking it to a technician.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T23:35:39.1+00:00

Okay so it has worked until now, but even now crashes occur like hour into gameplay or more and not in usual form of freezing the pc, then flashing of the BSOD and restart. It occurs as frozen game quickly changing into blank grey screen, with no text, speakers buzzing and I need to manually restart it (manual restart most likely because I turned off automatic restart so I could properly see the stop codes, even though this does not provide one).

Event Viewer still leaves a log of Kernel-power critical error, with 239 bugcheckcode though, even after that manual restart.

Answer 2

David-M 128.2K Independent Advisor

Hi. I'm David, and I'm happy to help you.

BSOD issues can have several reasons. It is necessary to investigate.

Please see if your computer created minidump files.

These files are in C:\Windows\Minidump.

(If you don't have a Minidump folder, check if it is in the plural Minidumps.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

I await your reply.

AzraelVP 20 Reputation points

2025-11-28T14:05:31.06+00:00

Hi David, I searched through the Windows folder within my C: drive, there is no Minidump/s folder in it. I even checked the startup and recovery settings and it is set correctly, to save them into Minidump folder in %SystemRoot%.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T14:10:33.5733333+00:00
Thanks for the clarification.

In this case, please export and share the log for analysis:

Press Windows + X and select Event Viewer;

Expand Windows Logs and select System;

In the Actions panel on the right, select Filter Current Log;

In Event level, check the boxes Critical, Warning, and Error and click on Ok;

Again, in the Actions panel, select Save Filtered Log File As and save in an easily accessible place.

Then, upload the file to the cloud (OneDrive), choose to share it, and get the link.

Post the link to the file here so I can have a look.

I await your reply.
AzraelVP 20 Reputation points

2025-11-28T14:21:00.14+00:00

https://1drv.ms/u/c/0f7e01fd1708b1bc/IQCmoNLP2G-jQLAZPH61hZmYAe-9CmVpqhS8HoTOt6ZqMzw?e=qI2qHX
David-M 128.2K Reputation points Independent Advisor

2025-11-28T15:51:44.46+00:00
Thanks.

I found that errors are occurring when creating the dump files. This is probably due to the type of crash that is happening.

I suggest you use the Driver Verifier utility. This utility is used to force the system to show the driver causing the problem.

Before turning on Driver Verifier, I like to create a restore point just in case. I suggest doing the same.

https://support.microsoft.com/windows/system-protection-e9126e6e-fa64-4f5f-874d-9db90e57645a

Turn on Driver Verifier, let the system crash 3 times, then turn off Driver Verifier. Share the minidumps that the crashes created.

Press Win + R, type verifier, and press Enter;

Select Create custom settings (for code developers) and click Next;

Check these options:

Pool Tracking

I/O Verification

Deadlock Detection

DMA Checking

Security Checks

Force pending I/O requests

IRP Logging

Miscellaneous Checks

DDI compliance checking

Select Select driver names from a list;

Sort by Provider and choose all non-Microsoft drivers;

Click Finish and restart your computer. Driver Verifier will now monitor the selected drivers.

(Pay attention to the blue screen that is displayed. Sometimes, it may contain useful information.)

After the system crashes at least 3 times, follow the procedure below to disable the Driver Verifier.

Open Start and type cmd, right-click on Command Prompt and select Run as administrator.

Run the following commands at the Command Prompt one at a time:

verifier /reset verifier /bootmode resetonbootfail

Then, restart the PC.

If the system no longer starts due to BSOD caused by the Driver Verifier, start it in Safe Mode and perform the above procedure to disable Driver Verifier.

https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f

I await your reply.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T16:50:42.3666667+00:00

It crashed 3 times with error SYSTEM_THREAD .. something (it happened so fast I wasn't even able to read the stop code completely). But then instead of safe mode, I restored to the restore point I created, which was wrong I suppose? Suddenly I have a folder on desktop named LocaleMetaData with two .MTA files in it.

How should I proceed? Should I remake the restore point and follow your instructions again with the driver verifier?
David-M 128.2K Reputation points Independent Advisor

2025-11-28T16:55:05.4733333+00:00

If a minidump was created by the crashes, the restore point may have removed it. But if restoring the system was your only option because you couldn't boot into safe mode, that's fine.

Were you unable to boot into safe mode to disable Driver Verifier?

I await your reply.
AzraelVP 20 Reputation points

2025-11-28T16:59:38.6+00:00

To be honest, I forgot about the instruction to boot into safe mode, so I chose restore point instead, when the pc could not boot itself normally (due to the verifier being active). That is why I am asking you, if I should re-enable the verifier and run it again.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T17:06:12.1966667+00:00

Thanks for the clarification.

In this case, create a new restore point and use Driver Verifier again. The same behavior will likely occur, but this time, try booting into Safe Mode first. If Safe Mode doesn't work, then use System Restore.

If minidumps are created, please share them with me.

I await your reply.

Feel free to ask back any questions.
AzraelVP 20 Reputation points

2025-11-28T17:22:04.6733333+00:00

Alright, I did everything according to your instructions, system crashed three times with SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x7E) stop code, then I booted the pc into safe mode and disabled driver verifier with commands you gave me. If minidumps were created, should they be in C:/Windows/Minidump ? Because there is still no such folder there.
David-M 128.2K Reputation points Independent Advisor

2025-11-28T17:26:10.7566667+00:00
Yes, the minidumps would be in that folder.

I will suggest a procedure for updating essential drivers. But for that, I need more information about your device.

Please share a screenshot of your system information.

Press "Windows + R", type msinfo32 and press Enter.

Maximize the window and use the shortcut "Windows + Shift + S" to use the screenshot tool.

I await your reply.
AzraelVP 20 Reputation points

2025-11-28T17:33:34.6933333+00:00

Here it is. I hope it is not an issue, that the list is in Slovak as my whole OS.

Answer 3

The BSOD error CRITICAL_PROCESS_DIED indicates that a critical process in Windows has unexpectedly terminated. This can occur due to various reasons, including issues with drivers, corrupted system files, or hardware incompatibilities. Since you've already gone through multiple diagnostics and hardware replacements, here are some steps you can take to troubleshoot this issue further:

Check for Outdated Drivers: Ensure that all your drivers, especially for your graphics card and chipset, are up to date. You can do this through Device Manager or by visiting the manufacturer's website.
Run System File Checker: Use the System File Checker tool to repair any corrupted system files. Open Command Prompt as an administrator and run the command SFC /scannow.
Check for Windows Updates: Make sure your system is fully updated. Sometimes, Microsoft releases patches that can resolve compatibility issues.
Event Viewer Analysis: You mentioned an Event Viewer report with Event ID 41. This indicates that the system rebooted without a clean shutdown. Look for additional critical errors in the Event Viewer that occurred around the same time as the crashes, which may provide more insight.
Memory Diagnostics: Since RAM issues can sometimes be elusive, run the Windows Memory Diagnostics tool to check for memory problems. You can access it by searching for "Memory" in the Control Panel.
Safe Mode: Boot your system in Safe Mode to see if the crashes persist. This can help determine if the issue is related to third-party software or drivers.
Check for Hardware Compatibility: Ensure that all installed hardware components are compatible with Windows 11. Sometimes, newer versions of Windows may have compatibility issues with older hardware.
Clean Boot: Perform a clean boot to eliminate software conflicts. This starts Windows with a minimal set of drivers and startup programs.
Reinstall Windows: If all else fails, consider performing a clean installation of Windows 11. This can resolve deep-rooted issues that other troubleshooting steps might not fix.

If the problem persists after trying these steps, it might be beneficial to consult with a professional technician who can perform more advanced diagnostics.

References: