Critical Process Died + Storage exception nightmare

[Tigerboss]

I've been having this problem on and off for as long as I've had this computer, although now I cant call it the same computer anymore because I've replaced everything part until nothing was original anymore. The first time I thought it was the cpu so I rma'd that. And at this point I dont know what to think anymore. These crashes usually happen when I try and run a heavy game like monster hunter wilds or spiderman 2. Sometimes even Path of exile 2. It leaves so dmp files so maybe ssd. If this sounds familiar to anyone the help would be greatly appreciated.

 

[ChatGPT]

Hi Tigerboss,
Given your description of recurring "Critical Process Died" and "Storage Exception" BSODs, especially during heavy gaming loads like Monster Hunter Wilds and Spider-Man 2, plus the fact that you've replaced nearly every component, this issue is quite complex but can be narrowed down with careful analysis.
Based on similar cases and known patterns from WindowsForum archives and community insights:

1. SSD/Storage Issues
   • Many users report "Unexpected Store Exception" and "Critical Process Died" linked to SSD faults or firmware problems. The symptom of multiple .dmp files after crashes strongly suggests storage-related faults.
   • SSD firmware may be outdated or buggy, causing corruption under load. A firmware update for your SSD could resolve these crashes.
   • Drive cable connection quality and power stability to the SSD are also crucial—ensure SATA cables are well connected or try swapping cables and ports.
   • Some cases show that SSDs failing or loosely connected can trigger such errors, and sometimes Windows loses the SSD momentarily after a crash.
   • Running manufacturer-specific SSD diagnostic tools and checking S.M.A.R.T. data can help rule out hardware failure.
2. Memory (RAM) and Drivers
   • Although you replaced hardware, unstable or faulty RAM can cause similar critical process and storage errors. Running MemTest86 overnight is recommended.
   • Driver conflicts or outdated storage drivers can cause these crashes. Update chipset, storage controller drivers (SATA/NVMe), and GPU drivers to the latest versions from the official manufacturer sites.
3. System BIOS/UEFI
   • Ensure your BIOS/UEFI is up to date since storage handling, especially for NVMe drives, can be significantly affected by firmware.
4. Power Supply and Heat
   • Power delivery to the drives and CPU/GPU must be stable. Even if temps are okay, unstable power can cause system crashes under load.
5. Crash Dump Analysis
   • The "Critical Process Died" bugcheck (0xEF) typically signals that a crucial system process terminated unexpectedly, often due to driver or hardware faults.
   • "Unexpected Store Exception" points toward storage subsystem failures.
   • Dump file analyses on similar cases frequently flagged "storport.sys" or SSD firmware bugs as root causes.

Next Steps for You:

• Update SSD firmware to the latest version directly from your SSD manufacturer's site.
• Re-seat and/or replace SATA/data cables.
• Update all motherboard chipset and storage controller drivers.
• Run comprehensive memory tests (MemTest86).
• If you have another SSD or HDD, try installing Windows there temporarily to identify if the current SSD is faulty.
• Update BIOS/UEFI to the latest stable release.
• Check Windows pagefile settings; corrupt pagefiles can trigger unexpected store exceptions, so try disabling and re-enabling the pagefile.
• Consider running Windows memory diagnostics and CHKDSK /f /r on your SSD to detect file system errors.

If you want, you can use debugging tools like WinDbg or BlueScreenView to open the dump files and look for the specific bugcheck code and driver names, then share those details here for more focused help.
These troubleshooting steps mirror those successfully applied in multiple similar WindowsForum threads where users had persistent Critical Process Died + Storage Exception crashes under gaming or load conditions that turned out to be SSD, driver, or RAM related issues.
Feel free to share the bugcheck codes from your dump files or any error messages you see. That will let us dig deeper if needed.
Good luck, and we're here to assist you further!

 

[datawizard0103]

Crashes while intense gaming might be caused by a faulty power supply, overheating, a failing SSD, bad RAM, or GPU difficulties. Check your power supply, keep an eye on temps, test your storage and memory, and consider updating or switching your GPU.

 

[ChatGPT]

Good summary — those are the usual suspects. Here’s a compact, practical troubleshooting checklist you can follow to isolate the cause and fix the crashes during intense gaming.

1. Gather evidence first
   • Check C:\Windows\Minidump (or enable memory dumps) and open with WhoCrashed / BlueScreenView to see cause.
   • Open Reliability Monitor (Control Panel → Security and Maintenance → Reliability Monitor) for timestamps and error types.
   • Check Event Viewer (Windows Logs → System/Application) for critical errors around crash time.
2. Temperature checks
   • Monitor temps while gaming with HWMonitor, HWiNFO, or MSI Afterburner. Watch CPU, GPU, VRM, and SSD temps.
   • If temps spike >85–90°C (GPU/CPU) or sustained high VRM temps, stop and address cooling (clean fans, reapply thermal paste, improve case airflow).
3. GPU/driver isolation
   • Do a clean driver reinstall with DDU (Display Driver Uninstaller) in safe mode, then install a known stable driver.
   • Try lowering graphics settings or run at a lower resolution; if stable, likely GPU/temps/power/driver.
   • If you have integrated graphics, test the game with it (or swap GPU into another system) to see if GPU is the culprit.
4. Power supply (PSU)
   • Make sure the PSU wattage and rails are sufficient for your GPU+CPU (check GPU requirements).
   • Try another known-good PSU if possible. If not, run OCCT/other PSU load tests or measure voltages with a multimeter while gaming — look for large deviation from 12V/5V/3.3V.
   • Check all GPU/CPU power cables and connectors for damage and tight seating.
5. RAM and system memory
   • Run MemTest86 (bootable) for several passes (overnight if possible).
   • Try running with one stick at a time (if multiple DIMMs) to find a bad module or slot.
   • Run Windows Memory Diagnostic as a quick check.
6. Storage/SSD
   • Check SMART with CrystalDiskInfo or the drive manufacturer’s tool (e.g., Samsung Magician, WD Dashboard).
   • Run chkdsk /f /r on the drive that holds the game.
   • If crashes correlate with loading new areas or stutters, consider testing the game on another drive.
7. CPU / stability
   • Run Prime95 or AIDA64 stress test (with temps monitored) to see if CPU/VRMs cause instability.
   • If unstable at stock speeds, check cooling, BIOS settings, or consider reverting any overclocks/auto-overclocking (disable XMP/DOCP as a test).
8. Software / OS checks
   • Verify game files (Steam/Epic/other) and try reinstalling the game.
   • Disable overlays (Discord, GeForce Experience, Steam overlay) and third-party apps (recorders, instant replays).
   • Run: sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system files.
   • Ensure chipset drivers and BIOS/UEFI firmware are up to date (but be cautious: if system was stable, only update when necessary).
9. Other tips
   • Try running the game with V-Sync or frame limiter to reduce instantaneous power draw/heat spikes.
   • If crashes are sudden BSODs, copy/paste the STOP code and driver name (if present) — that helps a lot.
   • If you suspect the SSD or OS install, test using a clean Windows install or bootable Linux to run a game/benchmark.
10. When in doubt
    • Swap suspect parts (PSU, GPU, RAM, drive) into a known-good system or borrow parts to confirm failures.
    • Collect logs and crash dumps and post the minidump/WhoCrashed output if you want help interpreting them.

If you tell me your system (CPU, GPU, PSU model/wattage, RAM, whether it’s a laptop or desktop) and paste the latest minidump/BSOD stop code or Reliability Monitor entry, I can help narrow it down further.