(BSOD) CRITICAL_PROCESS_DIED -> BAD_SYSTEM_CONFIG_INFO

David_Gregor

New member
Joined
Feb 20, 2025
Posts
3
Hello, this is my first time posting on Sysnative. I found this forum through a desperate search for a solution to my problem.

A few months ago, I bought and built my first custom PC, and since then, it hasn’t stopped giving me trouble. I have a licensed version of Windows 11, and from the very beginning—though not regularly—I’ve been getting BSODs with CRITICAL_PROCESS_DIED. After running a memory diagnostic, no issues were reported, although I did notice several "Kernel Power" events in the Event Viewer. I checked all connections, but I didn’t see anything wrong.

Later on, my PC started failing at startup, notifying me of an issue with Sihost.exe. Additionally, I encountered I/O error 0xc000000e when launching a game and again when joining a video call. I tried multiple solutions found online using Command Prompt as an administrator, but none of them worked. After repeated failed login attempts, my profile was locked, so I restored my system from a backup.

Some time later, the CRITICAL_PROCESS_DIED error returned. I tried other methods again, but nothing worked until my PC got stuck in the boot sequence with a BAD_SYSTEM_CONFIG_INFO error. This time, I reinstalled Windows from the cloud while keeping my files. It seemed to work fine at first, but the CRITICAL_PROCESS_DIED errors continued. Additionally, I am unable to install KB5051987 (version 24H2, x64) through Windows Update due to error 0x800f0831. Then, BAD_SYSTEM_CONFIG_INFO appeared again, forcing me to restore from a backup once more.

Other errors have also shown up, such as 0x800703F1, indicating a corrupted record database, along with issues related to Sihost.exe and winlogon.exe, which cause the system to reboot. In the end, I was once again forced to restore my system.

I have tried to be as detailed and precise as possible in case it helps. If anyone knows how to solve this, I would be extremely grateful, as I have been unable to fix it myself.

Thank you very much!
 

Attachments

Hi!

At the moment, are there bsods?
Or the only problem is that you are not able to install KB5051987?
Hi! since I performed the last restoration from the backup (less than two days ago), I haven't had another BSOD. However, I honestly believe it's only a matter of time before they reappear. If they do, I will update this thread. The update KB5051987 problem remains.
 
Hi!

At the moment, are there bsods?
Or the only problem is that you are not able to install KB5051987?
Hello again,

As I mentioned, today my PC started generating CRITICAL_PROCESS_DIED BSODs again, followed by a BAD_SYSTEM_CONFIG_INFO error that prevented me from booting. I tried running the following commands in Command Prompt with admin privileges:

  • chkdsk C: /f /r
  • sfc /scannow
  • DISM /Online /Cleanup-Image /RestoreHealth
None of these had any effect. Since I was also unable to restore the system, I was forced to perform a clean installation of Windows 11. During the process, I encountered error 0xe0000100 related to the internet drivers (though they seem to be working fine).

Although I was finally able to install the previously failing update, there are still two updates that won't install due to error 0x80070103:

  • Advanced Micro Devices Inc. Security Devices 4.13.0.0
  • Realtek-Net-1168.1.714.2021
I'm worried that I might run into these issues again, as this computer is my main work tool, and I can't afford to have it stop functioning randomly. If the BSODs return, I will update this thread.

Thank you for your time!
 
Firstly, can you please follow the BSOD Posting Instructions. There is other troubleshooting data that may be useful here.

Secondly, the CRITICAL_PROCESS_DIED bugcheck is most usually caused by a hardware problem. The BAD_SYSTEM_CONFIG_INFO bugcheck indicates an error in the registry. The registry hives are read into memory at boot time (and at login time) from the system drive. A system drive problem could also potentially cause the CRITICAL_PROCESS_DIED bugcheck, so I suggest that's the first place to start looking.

If we had the data requested by the BSOD Posting Instructions I could be more specific, but look for the diagnostic tool from your system drive manufacturer and run their diagnostics over the drive. Also post the SMART data from the drive. In addition, look for a firmware update for the drive and possibly an updated driver. If the system drive is an M.2 SSD you might even try removing an re-seating the drive, I've seen some people have niggly issues due to a badly seated M.2 drive. BE CAREFUL NOT TO DAMAGE ANY DRIVE HEATSINK THAT THERE MAY BE.

The BSOD Posting Instructions data may tell us more.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top