Error code BSOD indicates a failing volume mount, initialization failure, and an unrecoverable WHEA error.
Error code BSOD indicates a failing volume mount, initialization failure, and an unrecoverable WHEA error.
Hello, I've reviewed your system configuration. CPU model: i9 13900K. RAM: 4 x 32GB DDR5 Fury Beast. GPU: 4080 Super Zotac MOBO (MSI Z690-A PRO). Boot device: 990Pro 4TB M.2. Storage: 1 x 980 Pro 2TB M.2 and 1 x 4TB 860EVO SSD. Power supply: Corsair HX1200i. Note: The issue started with a BSOD saying "Unmountable BOOT VOLUME." Despite running diagnostics like sfc, chkdsk, and using repair commands, it didn't fix the problem. I had to reinstall the OS completely and removed other drives, keeping only the 990Pro 4TB. After reinstalling Windows, crashes still occurred with BSODs about "Unmountable BOOT VOLUME" and "Process Initialisation Failed." I also tried using a different SSD (960 EVO 256GB) and a basic GPU, but it worked perfectly once. I checked all components—CPU, RAM, storage, and GPU—without issues. The problem seems to be related to the boot volume or possibly the PSU. Could your motherboard's BIOS or firmware be outdated? Also, ensure the power supply is stable and functioning properly. Let me know if you need further help!
WHEA appears as a Machine Check Exception indicating a CPU error. It watches itself and PCIe devices. Microsoft later added storage support without using MCE, but errors here are usually driver-related rather than CPU issues. Most often, problems stem from the drive or its slot/motherboard, not the motherboard itself. A bad drive is far more frequent than a faulty board or slot.
Thanks Bjoolz for your helpful idea... Using the same 990 PRO 4TB with QUADRO 2000 still performs well, especially with storage-heavy applications—no crashes so far. However, when paired with the RTX 4080, I started encountering errors after a fresh install or while running intensive apps. It was quite annoying to replace NVMe drives and see the same problems appear. On the other hand, using the 960 EVO 256 GB with the RTX 4080 didn’t cause any issues at all.
Do you have any dump files available for inspection? Check the C:\Windows\Minidump directory for any minidump files. If present, return to your Windows folder and move the entire Minidump folder to the Downloads folder (use the desktop if needed). Compress the moved folder and send it via email. Follow the provided steps carefully—Windows doesn’t allow changes in certain locations. If you don’t receive any dump files, consider enabling more details in the BSOD screen. To show extra information on the crash screen, add a registry entry. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right-click the empty space, select New → DWORD value with the name "DisplayParameters", set its value to 1 (hex or decimal). This should appear in the BSOD output once applied. Reboot to save the change. On subsequent BSODs, you should see these additional details in the top-left corner. If Arg1 equals 0x0000000000000010, it indicates a NVMe SSD issue. Keep in mind the system can’t distinguish between an SSD and a M.2 slot or motherboard.
Thanks again for your helpful advice, Bjoolz. I verified the crashed drive using an NVME to USB adapter on another machine and confirmed that no dump files are created. I plan to try editing the registry as you suggested and retrieve the error code from the BSOD. I’m curious if this registry operation will function in Windows Safe Mode—since I can’t access regedit after the system crashes and keeps looping into BSOD. Also, the drive seems to work in Safe Mode, which is reassuring.