BSOD "Unmountable Volume" "Process Initialisation Failed" "WHEA UNCORRECTABLE ERROR"

[FLACS]

Hello,

 

I have the following config

CPU: i9 13900K

RAM: 4 x 32GB DDR 5 Fury Beast

GPU: 4080 Super Zotac

MOBO: MSI Z690-A PRO

BOOT: 990Pro 4TB M.2

Storage: 1 x 980 Pro 2TB M.2 and 1 x 4TB 860EVO SSD

PSU: Corsair HX1200i NOTE:2015 MODEL

 

Issue: System was working fine suddenly first crash occurred BSOD "Unmountable BOOT VOLUME"....it tried all options such as sfc scannow, chkdsk, rectboot fix commands etc...but none worked.

 

Had to reinstall the OS fresh and for safer side removed other storage drives and kept only 990PRO 4TB...After installing when started installing again randomly crashes BSOD "Unmountable BOOT VOLUME"...again restarted then BSOD "Process Initialisation Failed" and then stuck to "WHEA UNCORRECTABLE ERROR".

 

Did several attempts of fresh installation of windows and got the same result as mentioned above including tried updating BIOS firmware.

 

I tried now with 980 PRO as boot same issue again repeating...Finally used my old 960 EVO 256GB M.2 with windows freshly installed all works perfect no carsh observed.

 

I checked all my SSD using diskpart no issues, cpu diagnostics no issue, RAM MEM test no issues and GPU stress test no issues. 

 

Now i tried checking with a basic quadro GPU removing my RTX 4080 super and then installing again my 990PRO 4Tb with once again fresh installation of windows and no issues or no crashes like BSOD observed.

 

This looks weird, can anyone guide me what could be the issue here is my MOBO is dying or PSU is having any issue?

 

Thanks for your support and advice.

[Tetras]

Did you buy your 990 Pro recently? If you did not, have you updated the firmware?

[FLACS]

1 hour ago, Tetras said:

Did you buy your 990 Pro recently? If you did not, have you updated the firmware?

Yes bought recently, all drives updated with latest firmware...

[Bjoolz]

WHEA is from a Machine Check Exception when the CPU discovers an error. It monitors itself and PCIe devices. Then Microsoft decided to duct tape storage onto WHEA which doesn't use MCE. Storage errors in WHEA are driver reported, not CPU reported. It's rarely caused by drivers though. On a fresh install, it's almost certainly the drive itself or the slot/motherboard. A faulty drive is a lot more common than a faulty motherboard/slot. 

[FLACS]

51 minutes ago, Bjoolz said:

WHEA is from a Machine Check Exception when the CPU discovers an error. It monitors itself and PCIe devices. Then Microsoft decided to duct tape storage onto WHEA which doesn't use MCE. Storage errors in WHEA are driver reported, not CPU reported. It's rarely caused by drivers though. On a fresh install, it's almost certainly the drive itself or the slot/motherboard. A faulty drive is a lot more common than a faulty motherboard/slot. 

Thanks Bjoolz for your valuable suggestion.....but with the same 990 PRO 4TB paired with QUADRO 2000.... when processing storage intensive apps no crash or such till now.... But with same 990 PRO 4TB paired with RTX 4080 super  fresh install opens and will starting to install or working on processing storage intensive apps the shortly the BOSD with those errors popped up....was really frustrating to double I bought new NVME and same issue.

 

But when i use 960 EVO 256 GB with with RTX 4080 super no crash observed.....

[Bjoolz]

1 hour ago, FLACS said:

Thanks Bjoolz for your valuable suggestion.....but with the same 990 PRO 4TB paired with QUADRO 2000.... when processing storage intensive apps no crash or such till now.... But with same 990 PRO 4TB paired with RTX 4080 super  fresh install opens and will starting to install or working on processing storage intensive apps the shortly the BOSD with those errors popped up....was really frustrating to double I bought new NVME and same issue.

 

But when i use 960 EVO 256 GB with with RTX 4080 super no crash observed.....

Do you have any dump files so we can check why it's getting a WHEA crash? 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 you aren't getting dump files you can set it up to display more information in the BSOD screen. To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner.

 

If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard.

[FLACS]

10 hours ago, Bjoolz said:

Do you have any dump files so we can check why it's getting a WHEA crash? 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 you aren't getting dump files you can set it up to display more information in the BSOD screen. To make the BSOD screen display the additional info on the BSOD screen we need to add a field to the registry. If you are not comfortable editing the registry then do not do this step. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl, right click on the empty area on the right section and select New → DWORD value with the name "DisplayParameters". Right click on it, modify and set the value data to 1 (Does not matter if you use Hexadecimal or Decimal). It should look like this once done. Reboot to apply the registry change.

 

The next time you BSOD, you should have these extra numbers in the top left corner.

 

If Arg1 is 0x0000000000000010 then Windows is blaming the NVMe SSD. Note that it can't tell the difference between the SSD and M.2 slot/motherboard.

Once again Thanks Bjoolz for your valuable suggestion....I checked the crashed drive by using the NVME to USB adapter in another computer and checked the path you mentioned no dump files are generated...

 

I will try to do registry edit as you have mentioned and get the error code from BSOD.....can this registry edit works in WINDOWS SAFE MODE?....because i'm not getting time to edit the regedit after boot as it goes to immediate crash and loops to BSOD...but the drive works in SAFE MODE.....

 

Thanks

[Bjoolz]

13 hours ago, FLACS said:

Once again Thanks Bjoolz for your valuable suggestion....I checked the crashed drive by using the NVME to USB adapter in another computer and checked the path you mentioned no dump files are generated...

 

I will try to do registry edit as you have mentioned and get the error code from BSOD.....can this registry edit works in WINDOWS SAFE MODE?....because i'm not getting time to edit the regedit after boot as it goes to immediate crash and loops to BSOD...but the drive works in SAFE MODE.....

 

Thanks

Yes.