Unusual crashes hitting the screen Mind going haywire, system struggling
Unusual crashes hitting the screen Mind going haywire, system struggling
Hello. Over the past year, I own this system: AMD Ryzen 7 7800X3D (4.2 GHz), Sapphire Radeon RX 7800 XT PURE, Gigabyte X870 AORUS ELITE WIFI5ICE, DDR5 Corsair Vengeance White, 32 GB (2 x 16 GB) at 6000 MHz, CAS 36. I need quiet power – Straight Power 12, 850W, quiet. Pure Base 500DX, white, quiet. Shadow Rock 3, white, Samsung 980 Pro, Crucial T700 1To (Windows installed). Issue: Frequent BSODs – often multiple per hour. Can't run high-end games with the current setup. Most errors are WHEA_UNCORRECTABLE_ERROR.
What I've tried:
- Hardware changes: Swapped motherboard (ASUS B650 Prime Plus had same issues), sent CPU to AMD for repair, but it worked fine.
- GPU: Ran PC without GPU, still crashes with the same error.
- Software: Ran MemTest86+ RAM check, SSDs checked via chkdsk and manufacturer tools, Windows updated from basic 11 to clean version, BIOS updated, voltage tests with OCCT (3.5V, 5V, 12V), LatencyMon test – no problem detected.
- Reddit help: Shared a post on r/pchelp with all attempts; still unclear what’s happening.
Problem remains. I bought a new PC just to play games and not to deal with random crashes. I’ve sent it to two repair shops, but they can’t find the cause or seem uninterested in fixing it. They charged over 100€ without solving anything. I’m not in a good place – living in the French countryside, there aren’t many nearby shops.
Help is appreciated!
Consider asking a friend whose PC is similar to yours for assistance in diagnosing issues. Exchange parts gradually—swap one component at a time between your machine and theirs. Begin inserting your CPU into his PC, then his CPU into yours. If you encounter BSODs on your own system, proceed to the next part. Continue this process until you identify the root cause. Utilize any warranty coverage if applicable for the faulty component.
Currently, there are no nearby people available to assist you.
WHEA stands for a hardware problem involving the CPU or a PCIe device. When combined with Critical_Process_Died, it suggests a Windows process stopped unexpectedly, pointing toward an NVMe SSD issue. Because of this, I’d favor the T700 over the 980. You may have tested the SSDs, but those results don’t apply well to NVMe drives—they’ve disabled self-diagnostics for these types of storage devices, leaving minimal useful data in logs.
Let’s see if you have any dump files from the BSOD. If you experience storage-related crashes, it’s often because the drive failed before the crash. Check the C:\Windows\Minidump folder for any minidump files. If present, move the folder to your Downloads directory (or use your desktop if OneDrive isn’t syncing). Compress the file and share it here.
Follow these steps carefully: Open Event Viewer, search for “WHEA” events. Right-click and save or upload the .evtx file. For filtering, go to Windows Logs → System, click “Filter Current Log,” choose “WHEA-logger,” and apply the filter. Highlight all events and save them together.
If no files exist and no events appear, we can try another approach. We can modify the registry to show crash details on the BSOD screen. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, create a DWORD value named “DisplayParameters” with value 1, then reboot. The next BSOD should display extra information.
If you see the error code 0x0000000000000010, it indicates an NVMe SSD issue. Be aware it can’t distinguish between SSD and M.2 slots or motherboards. Replace the SSD, update firmware, and verify temperatures—avoid overheating. If the problem persists, take a screenshot.
To prevent automatic restarts on BSOD, disable the check in Windows settings. For manual recovery, simply press the power button.
Another BSOD occurred, critical process died once more, identical details. However, upon reviewing the Minidump, a .dmp file was found—dated March 16th. It appears to be a WHEA, which is all I could grasp. The ZIP file is attached as requested. Minidump.zip
It's indicating an NVMe SSD. The dump file doesn't specify which one. Uncertain if a WHEA event was logged; storage with activity will help identify the problematic unit. A simple check removes the non-Windows drive and observes if crashes cease. If the EFI partition remains on the OS-free drive, Windows won't boot. The installer places the boot partition on the drive the motherboard designates as Disk 0, no matter where you install the operating system.
Oh, ok Yes, before sending my CPU to verification at AMD, I had 2 SSDs in my PC. Windows were on the Samsung one, so I took this one off and installed a new Windows on the Crucial. After that, there was/is still BSODs, but there is less different BSOD error codes, so for me the Samsung is faulty (not the only one, but it is). It's possible I did the SSD change after the 16/03, so if it's unusable because of it, sorry and I'll wait for a new WHEA. A CRITICAL_PROCESS_DIED cannot show anything useful?
From the dump file occasionally it works, yet it merely indicates which Windows process failed and why—this doesn’t provide useful insight. Also, have you verified WHEA events in Event Viewer?