Windows 10: ASUS Z390-A Will only boot one time to Samsung SSD 970 EVO M.2 from other boot disk Error...

My computer has 5 disks 3 have the EFI boot partition.

The 850 EVO SATA SSD has a EFI boot partition and 3 bootable OS partitions.

The 970 EVO M.2 SSD has a EFI boot partition and 4 bootable OS partitions.

The 500GB WD SATA HDD has a EFI boot partition and 0 bootable OS partitions.



All 7 bootable partitions are Windows 10 Home.

6 are version latest update 1909

1 is minimal updated version 1809 for testing this problem.



When the 850 or WD are set as the boot disk in the BIOS.

You can only boot to either one of the four OS partitions on the 970 one time. After that you get the Boot Failed error, error “Windows Failed to start” could not find \Windows\system32\winload.efi Error Code 0xc000000e.

If you go in to the BIOS and reselect the 850 or WD the problem repeats.

There are NO problems booting to any of the 3 OS partitions on the 850.



When the 970 is set as the boot disk in the BIOS.

There are no problems booting to any of the 7 OS partitions



Motherboard is ASUS Prime Z390-A

CPU i9-9900

CPU cooler Corsair H100i

Ram Corsair Vengeance LPX 16GB 2 x 8GB DDR4

Samsung 850 EVO SATA SSD

Samsung 970 EVO M.2 2280 NVMe 1.3 SSD

WD 500GB SATA HDD

WD 2TB SATA HDD

WD 42TB SATA HDD

Video Card – MSI GeForce GTX 1050 Ti

Power Supply - Seasonic FOCUS PX-850

:)

 

2 RAID Arrays on Z390 chipset (M.2x4 and SATA)

This is possible. I have successfully built a Z390 based machine with both an M.2 RAID 1 array (boot) and SATA RAID 0 array (D disk), all running off of the Z390 chipset Intel controller. Creating the RAID arrays is standard, and not significantly different than with just SATA disks. The primary difference being that the M.2 disks must have "RST PCIe Storage Remapping" Enabled.

This system is configured as such:

• i9 9900k
  
• ASRock Z390 Taichi Ultimate
  
• 2x 1TB Samsung 970 EVO M.2 SSDs (RAID 1 + Boot)
  
• 2x 1TB WD Blue SSDs (RAID 0)
  

 

Samsung introduces the Samsung 970 PRO and EVO NVMe M.2 SSDs

Samsung 970 PRO and EVO NVMe M.2 SSDs now available.

Order *Arrow SSD 970 PRO NVMe M.2 512GB Memory & Storage - MZ-V7P512BW | Samsung US

Order *Arrow SSD 970 PRO NVMe M.2 1TB Memory & Storage - MZ-V7P1T0BW | Samsung US


Order *Arrow SSD 970 EVO NVMe M.2 250GB Memory & Storage - MZ-V7E250BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 500GB Memory & Storage - MZ-V7E500BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 1TB Memory & Storage - MZ-V7E1T0BW | Samsung US

Order *Arrow SSD 970 EVO NVMe M.2 2TB Memory & Storage - MZ-V7E2T0BW | Samsung US

 

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