Windows 10: My m.2 nvme SSD no longer getting detected in bios after uninstalling KB5029351

The issue started with BSODs from KB5029351 https://www.tomshardware.com/news/msi-details-official-workaround-for-windows-11-kb5029351-bsods I have MSI H310M Pro-M2 Plus so I thought maybe uninstalling the update might help. I went in the settings, uninstalled the update and went away for a coffee break. I returned, Fedora was booted I have one nvme with windows, one SATA SSD with fedora and a hard disk to keep data, I thought maybe uninstalling update had restarted PC. So I restarted again, selected Windows in grub grub has boot priority and it loads windows but this time it c

:)

 

M.2 NVME SSD No longer detected by motherboard

I bought a Crucial P1 1TB nvme ssd and installed it on to my motherboard, booted into windows, created new simple volume and copied all my stuff into it, everything's great. I turn off my pc and turn it on the next day and the drive is missing, I thought huh, maybe the connection is lose or something, so I take it out and plug it back in, turned on the computer and the drive is back with all my stuff. Then I turn the pc off and on again and the drive is missing again! I go into bios and there it says no nvme drive detected. What is happening, why is my drive no longer being detected?

I'm on the latest bios version.

My drive order:

1. 250gb ssd (OS)

2. WD 1TB

3. Seagate 2TB

4. nvme ssd

My motherboard: http://download.gigabyte.eu/FileList/Manual/mb_manual_ga-z170-gaming-k3_e.pdf

Also to mention I configured the nvme to gpt if it matters, I think my other drives are mbr.

 

NVME M.2 SSD detected in BIOS - not detected in Windows 10 x64

Hi,

I purchased an PNY CS3030 2TB M.2 NVME SSD disk which I installed in my system. My BIOS can see it just fine under my NVME Configuration menu options, and also the BIOS function to do a controller test for this disk passes without a problem.

However, in Windows 10 x64 (up to date) I am unable to see the disk in Device Manager, or Computer Management / Disk Management section - meaning I can't initialize and format the drive.

This is a second NVME disk in this system. My first one which is also the boot/system disk is a Samsung Evo 970 Plus (also seen in the BIOS, right next to the PNY) and functions properly in Windows.

System specs:

AMD Ryzen 3900X

Asus X570 Pro - BIOS version 1405 (latest available as of this time)

32 GB DDR4 3600MHz Patriot Viper 4 (4x8GB)

Disks:

- Samsung Evo 970 Plus 500 GB M.2 NVME

- PNY CS3030 2TB M.2 NVME

- 2x WD Blue 10EZEX SATA 7200RPM 1TB drives configured in RAID0

- 1x WD Blue 320GB SATA 7200RPM

GPU: Sapphire RadeOn RX560

Power: Corsair RM1000x

OS: Windows 10 x64 Home

As said, all other disks work fine. Initially I was thinking this to be a driver issue of some sort, since the BIOS can see the PNY just fine but Windows can not. I also made sure I installed the latest available chipset and SATA drivers (I know its NVME,
but still.. ) from my motherboard manufacturer: ASUS, at PRIME X570-PRO｜Motherboards｜ASUS Global

I do not think the PNY is deffective, otherwise my BIOS would not detect it, and it would also not pass the BIOS' NVME controller tests.

Ideas?

 

My Samsung 970 EVO 2TB NVMe m.2 ssd not being detected in BIOS

I am having problems with the Samsung 970 EVO 2TB NVMe m.2 ssd and it not being detected in BIOS. I recently had to submit my motherboard in RMA for repairs and the drive was working perfectly before, but now it's not being detected. I receive this code
in "Secure Erase" in ASUS BIOS: SMNVMeROM

I have an ASUS ROG RAMPAGE VI OMEGA x299 motherboard and I have 2 other NVMe m.2 drives that do work on the motherboards m.2 slots, and in the dimm.2 adapter slot. It's just that the 970 EVO had my operating system on it, and I'm confused by what SMNVMeROM
means. Did it turn into a ROM file? Should I try putting an operating system on one of the working m.2 drives, to see if I can access the m.2 drive in question(windows disk management)? ASUS wasn't able to help me out in terms of tech. support.

Thanks,

Steve