bsod PC BSOD after login but before launch programs startup.

[JunkerPug]

I just upgraded my PC r9 5900x to r9 9950x also having to change motherboard and ram.

 

It worked fine for a month and then randomly started blue screening but specifically after I logged into the computer but before the start up programs launched. The blue screen error is CRITICAL_PROCESS_FAILED. I tryed sfc/scannow in recovery mode, repairing windows with a usb and also tried rolling back the windows update none of it worked so I ended up formating my boot drive and re installing windows which worked for a week but the same issue just started happening again and I dont want to be re intalling windows every week. If anyone has ideas for a diffrent fix id love to know about it.

 

Current PC Specs:

Aorus x870e Pro

Ryzen 9 9950x

Aorus 4080 Master

T-Force Delta Ram 64GB 6400MHz

Corsair RM1000x shift psu

Boot drive: WD_Black 2tb NVMe

Windows 11 pro

 

[Quackers101]

hopefully its not the bad windows update (dont fully remember what it was about).

If its windows or bad SSD (corrupted files or the path)

as this is mostly with the new CPU in "older" motherboard? did you do any BIOS changes?

Also try with a single RAM stick of either one you have, unless you only have one, rip.

 

but if its "process_died" that you got, a lot says about checking for malware and check all drivers to not be corrupt or broken.

https://learn.microsoft.com/en-gb/answers/questions/1530603/bsod-(critical-process-failed)

 

And some of this before saying RAM failure, or believe it was a part of it due to corsairs software. so if you have any software related to RAM or other stuff, can impact it too. So if its related to RAM, turn OFF XMP/DOCP?

Edited November 11 by Quackers101

[SpookyCitrus]

The Critical Process Failed BSOD, can be caused by a few different things. Since you have completely formatted and reinstalled Windows it's likely not a software issue. It could be caused by overheating, bad Ram, or a bad CPU/Mobo. CPU/Mobo failure is pretty rare so I'd test for overheating or if the Ram is bad first. It could also be an issue caused by an out of date bios as stability issues could be fixed via a bios update if it was something to do with that. If there is a newer bios version than what you have available I'd update it first and for most.

 

Troubleshooting steps for if you are already on the most up to date bios or if it still has the crashing problem:

 

First, I would check to see if there are any thermal issues. Use HWMonitor and a program such as Prime95 or Cinebench R24 to test your temps both while idle and while at full load. If your temps are fine, move to the next troubleshooting step.

 

Next would be Ram testing, use Windows Memory Diagnostics or Memtest86 to scan for errors. If the crashing is fairly repeatable another option is to test with and without EXPO enabled. If the computer doesn't crash with EXPO disabled it could be an incompatibility with the kit and your board/CPU.

It very well could be this as the best kits to pair with 7000 and 9000 series Ryzen CPUs would be 6000MT/s CL30. Anything higher would be a minimal gain in performance and more chance for instability. I'd also check to make sure the kit you have is on the QVL list for your motherboard, if it isn't this would further point to the Ram possibly causing instability.

 

In rare cases it can also be caused by a problem with the storage drive Windows is installed on. You can check the health of your OS drive by using CrystalDiskInfo. 

 

I'd do the above testing before moving on to drastic testing like replacing the CPU or motherboard. 

[Bjoolz]

First and foremost, which WD SSD? They have a firmware bug that causes BSODs on newer Windows versions. I haven't had a chance to look at dump files from a confirmed case of this so I don't know what they look like, but I know it's something a good amount of people have had issues with. Article with download links here.

 

There is some misinformation here so just stating some things. Critical_Process_Died means that a core Windows process crashed. This is almost always from corruption to OS files, though memory issues also cause this because OS files are loaded into memory. You wouldn't see the same crash every time, at least not this one, if it was memory. The OS can corrupt by random chance, but you have to consider faulty storage as a possibility. This crash isn't a very strong indicator of faulty storage by itself as it can show up under other circumstances and if it's one of several other crashes (And none of the other crashes look like storage) it's usually not considered to be storage related at all. So context is important with this crash.

 

We can look at dump files (Logs from the BSODs), but if this is the only crash error you get there usually isn't much point to it. It will just show that something in Windows crashed. If you want us to look at the dump files, go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

 

If it's the only crash error you get, reinstall Windows. Wipe the drive and do a clean install from USB. If you still crash with the same error (Or other errors that indicate storage like Unexpected_Store_Exception and Kernel_Data_Inpage_Error) I would replace the storage. 

[JunkerPug]

Update, again I already tried re-installing windows and it only worked for about a week before i ran into the same problems. XMP/EXPO has always been off I couldn't get it to be stable I just Assumed it was a new motherboard so wait for updates. I tried both crystal disk info and windows memory test and they both yielded nothing saying everything is fine and there is no problems, this is why its such a weird problem. like right now I'm typing this on the pc but if I turn it off then back on it might crash again after login and before start up programs. 

 

Also I looked for the C:windows/minidump and I couldn't find it. Tomorrow I'm going to switch the thermal pad with thermal paste because i have had the pc go to 74c on idle, and if It crashes again i will swap the WD drive with a Samsung one. i have this picture of Task manager, core temp, Device manager and crystal disk info if you can spot something weird. Its random on what launch it crashes on but it does decide to BSOD it always does it in between login in and when the launch programs open. This is so weird, thanks for the suggestions, any other suggestions are defiantly welcome.

[Bjoolz]

8 hours ago, JunkerPug said:

Also I looked for the C:windows/minidump and I couldn't find it.

There are some settings or scenarios that can cause dump files not being created, but faulty storage is the main suspect.

 

Other reasons:

 

• Not enough room on the storage with the page file. You need as much free storage as your amount of RAM + 3-4GB.
• Not enough room in the page file if you have manually set a size for the page file. Same amount needed as above.
• Encrypted storage, e.g. via Bitlocker. The BSOD process happens outside of Windows so it can't access encrypted drives.

[JunkerPug]

Its been working for a bit now with only two bsod. I did a software backtrack and it said it failed but when I restarted the pc and then it worked its to inconsistant for me to pin it down. None of the things listed should prevent dump files from being created i dont use bit locker, i havent manually set anything, and i have lots of ram. I wouldnt say the issue is solved but it could just be software issue that need to be fixed on the new platform