Error screen appears immediately after logging in but before the program starts.
Error screen appears immediately after logging in but before the program starts.
I recently upgraded my PC from R9 5900X to R9 9950X, along with a new motherboard and RAM. It functioned properly for a month until it began showing random blue screen errors. The issue appears after logging in but before startup programs begin. The error code is CRITICAL_PROCESS_FAILED. I ran the SFC/scannow utility in recovery mode, used a USB to repair Windows, and attempted to roll back updates, but neither resolved it. Eventually, I had to format the boot drive and reinstall Windows, which worked for a week. However, the problem started again shortly after. I’m looking for alternative solutions and would appreciate any suggestions.
Current PC Specs: Aorus X870e Pro, Ryzen 9 9950X, Aorus 4080 Master T-Force Delta RAM, 64GB, 6400MHz, Corsair RM1000x, PSU, WD Black 2TB NVMe, Windows 11 Pro.
Hopefully it's not the bad Windows update (I don't fully recall what it involved). Could it be a corrupted SSD—like broken files or a wrong path—especially since this is paired with the new CPU on an older motherboard? Have you made any changes to the BIOS? Try using just one RAM stick, either of the ones you own, unless you're certain. If you see "process_died," it suggests malware or driver issues are likely. Check for malware and verify all drivers are intact. https://learn.microsoft.com/en-gb/answer...ss-failed) Also, consider RAM-related software that might affect performance. If it's RAM, disable XMP/DOCP settings. Updated November 11, 2024 by Quackers101
The BSOD due to critical process failure might stem from various factors. With a fresh install and setup, software problems are unlikely. Possible causes include overheating, faulty RAM, or a failing CPU/Motherboard. CPU or motherboard issues are uncommon, so start by checking for heat buildup or damaged RAM. A bad CPU or motherboard is rare, so test for overheating or RAM quality first. An outdated BIOS could also trigger stability problems; updating it may resolve the issue if it relates to BIOS settings. If your system has a newer BIOS version, apply it before proceeding. For troubleshooting steps when you already have the latest BIOS:
Begin by examining thermal conditions using tools like HWMonitor and software such as Prime95 or Cinebench R24. Monitor temperatures during idle and under load. If temperatures are normal, continue with RAM testing via Windows Memory Diagnostics or Memtest86. Since the crash appears consistent, try running tests with EXPO disabled to determine if compatibility issues exist. If the system remains stable without EXPO, it may point to a hardware incompatibility between your motherboard and CPU. In exceptional cases, storage problems—such as an unhealthy OS drive—could be responsible. Use CrystalDiskInfo to assess drive health. Always perform these checks before considering major replacements like swapping the CPU or motherboard.
First, which WD SSD model is affected? They report a firmware issue leading to BSODs on newer Windows versions. I haven’t examined dump files from confirmed cases yet, so I can’t confirm the exact appearance. However, many users have experienced similar problems. For more details, there are download links provided in the article. Be aware that some information may be misleading, so I’m focusing on verified facts.
A critical crash like Critical_Process_Died usually results from OS file corruption, often due to memory issues since those files are loaded into RAM. While random memory errors can cause this, faulty storage is a likely factor here. This crash isn’t strongly tied to storage problems unless it occurs alongside other crashes—especially if none of the others suggest storage failure. Context matters.
You can review dump files located at C:\Windows\Minidump. If you have them, copy the Minidump folder to your Downloads folder (or use the desktop if syncing isn’t available). Compress the folder and send it in a post. Follow instructions carefully—Windows doesn’t allow file manipulation there.
If the same error persists, reinstall Windows. Clear the drive and perform a clean installation from a USB drive. If the issue continues with additional errors (like Unexpected_Store_Exception or Kernel_Data_Inpage_Error), replace the storage device.
Updates already attempted, only temporary fix lasted a week before recurring issues. XMP/EXPO consistently unstable; initially thought new hardware but updates didn’t help. No clear errors from disk info or memory tests—everything appears normal, which explains the unpredictable crashes. Currently experiencing instability when powering off and on, especially before programs launch. Found no C:windows/minidump file. Planned to replace thermal pad with paste tomorrow due to overheating warnings at idle (74°C). If it fails again, I’ll swap the WD drive for a Samsung one. Attached Task Manager, Core Temp, Device Manager, and Crystal Disk Info screenshots for reference. The crashes seem random but often occur during login or when launch programs start. Any further advice appreciated.
Some configurations or situations might prevent dump files from forming, but bad storage is the primary concern. Other factors include insufficient space on the storage drive paired with the page file. You should have at least as much free space as your RAM plus 3-4GB. If you've manually defined a page file size, there won't be enough room. Encrypted drives, such as those protected by Bitlocker, are also problematic because the BSOD runs outside Windows and can't reach encrypted media.
It has been functioning for a while now using just two BSD drives. After running a software backup, it reported failure, but restarting the PC made it work—though the behavior was too erratic to identify clearly. None of the listed settings should block file creation; I don’t use BitLocker, haven’t changed anything manually, and have ample RAM. The problem isn’t fully resolved yet—it might be a software-related issue that needs fixing on the new system.