Question Random BSOD on a new PC - - - Critical_Process_Died ?

Oct 29, 2024
9
0
10
I’ve had this computer for almost a month now, and the issue started about two weeks ago.

My PC experiences a “Critical_Process_Died” BSOD at random moments. Sometimes, I can use it for hours without any issues, but once the first BSOD appears, it’s crash after crash…

After such a crash, I can reach the Windows start screen and open apps, but after about 30 seconds, the first app freezes, then my cursor a few seconds later, and eventually the entire system hangs. (This also happens with the first crash.)

I’ve tried running both SFC and DISM, which report that there are corrupted files, but regardless of how many times I attempt these repairs, the errors persist.

I also can’t find my dump folder (weird).

My PC Specs
MBD: Asrock B650M HDV/M.2
CPU: Ryzen 7800X3D
GPU: Gigabyte 4070 TI Super
RAM: G.Skill 32 GB DDR5-6000
PSU: Corsair RM850x ATX 3.1
SSD: WD Black SN770 NVMe
 

Aeacus

Titan
Ambassador
I’ve tried running both SFC and DISM, which report that there are corrupted files, but regardless of how many times I attempt these repairs, the errors persist.
Format the OS drive and make a new, clean installation.

SFC and DISM can get rid of low/medium severity issues. But high severity issues are only fixed with format and clean installation. That includes getting rid of malware as well, which may cause the corruption (except firmware rootkits that is).
 
Oct 29, 2024
9
0
10
Format the OS drive and make a new, clean installation.

SFC and DISM can get rid of low/medium severity issues. But high severity issues are only fixed with format and clean installation. That includes getting rid of malware as well, which may cause the corruption (except firmware rootkits that is).
Tried it, but it still say it found corrupt files. Sadly.
 

KingLoki

Upstanding
Jul 10, 2024
401
65
270
Have you looked in folders... Windows\Logs ?
Also, when it crashes, try rebooting into safe mode to see if it still crashes/freezes
 
Last edited:

KingLoki

Upstanding
Jul 10, 2024
401
65
270
That's good 👍 ...did you click the microsoft link next to the secureboot error at the bottom of the window?
Can you post the link in here?

You can copy and paste the images into the posting box if necessary.
 
  • Like
Reactions: DonRoger
Oct 29, 2024
9
0
10
That's good 👍 ...did you click the microsoft link next to the secureboot error at the bottom of the window?
Can you post the link in here?

You can copy and paste the images into the posting box if necessary.
It send me to this page: https://support.microsoft.com/nl-nl...riabelen-37e47cf8-608b-4a87-8175-bdead630eb69 . Again, it's in Dutch, so no problem if I need to translate it for you!

Type sysinfo into the windows search box and look for "Secure Boot State" to see if it says "On" If it's Off, try enabling it in the Bios

https://www.thewindowsclub.com/fix-event-id-1796-the-secure-boot-update-failed

https://answers.microsoft.com/en-us...a-secure/ad838ae2-96c5-475f-9a76-a3119f97bb9d
Its Off indeed, I'm going to try to find it on my BIOS! Thanks for the links.
 
Oct 29, 2024
9
0
10
I have followed the steps and enabled Secure Boot, as it constantly reported ID1796 in the Event Logs with the description: "The Secure Boot update failed to update a Secure Boot variable with error Secure Boot is not enabled on this computer. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931."

Now the crashes have decreased, but I occasionally receive ID1785 with the description: "The Secure Boot update failed to update a Secure Boot variable with error The parameter is incorrect. For more information, please see https://go.microsoft.com/fwlink/?linkid=2169931."

ID10010 with the description: "The server {C53A4F16-787E-42A4-B304-29EFFB4BF597} did not register with DCOM within the required timeout."

ID11 with the description: "The driver has detected a controller error in \Device\RaidPort1."

ID161 with the description: "Cannot create dump file due to an error while creating the dump. BugCheckProgress is: 0x00040049."
 

KingLoki

Upstanding
Jul 10, 2024
401
65
270
Did you try the registry hack in the provided link?

1. Press windows+r and type regedit
2. Navigate to the following path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\State
3. Locate and double click on
DWORD UEFISecureBootEnabled
4. Change the value to 1 and click OK.
5. Reboot your computer.
 
  • Like
Reactions: DonRoger
Oct 29, 2024
9
0
10
Did you try the registry hack in the provided link?

1. Press windows+r and type regedit
2. Navigate to the following path:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecureBoot\State
3. Locate and double click on
DWORD UEFISecureBootEnabled
4. Change the value to 1 and click OK.
5. Reboot your computer.
Yep, the value is already on 1.
 

KingLoki

Upstanding
Jul 10, 2024
401
65
270
Thats a slight positive. Have you updated your motherboard to the latest bios version?

This can work for some in bios settings...

- change CSM Support from ON to OFF
- change secure boot mode from Standard to Custom
- Factory Default Keys
- changed Secure Boot to Enabled
- change secure boot mode back from Custom to Standard
- Save and Exit
 
  • Like
Reactions: DonRoger
Oct 29, 2024
9
0
10
Thats a slight positive. Have you updated your motherboard to the latest bios version?

This can work for some in bios settings...

- change CSM Support from ON to OFF
- change secure boot mode from Standard to Custom
- Factory Default Keys
- changed Secure Boot to Enabled
- change secure boot mode back from Custom to Standard
- Save and Exit
That’s something, at least indeed. I updated the BIOS this morning, then still had one crash after starting up Windows like 15 minutes later.

I’ll take a look at your steps when I’m home again . I’ll let you know in a few hours!