Asus raid controller driver windows 10 drivers#

Asus raid controller driver windows 10 drivers#

The Reflect recovery USB stick and reimage the NMVe stick. Automatically update your drivers Identify your products and get driver and software updates for your Intel hardware. Instead of spending an hour trying to get the system to see the F8 key being spammed so I could select Now, if it boot loops again, my first troubleshooting step will be to turn on RAID mode for the NVMe stick and see if that fixes the boot issue. Listed in device manager), disable NVMe RAID, enable SATA RAID and resolve the issue. Standard NVM Express Controller Driver (because now there is only one AMD-RAID Bottom DeviceР’В and AMD-RAID-Controller This let me boot, change the driver back to the I don't know of an easy way to figure out which AMD-RAID Bottom DeviceР”Р„nd AMD-RAID-Controller are assigned to which device so I temporarily put the NMVe stick into RAID mode so it would boot and disabled RAID for the remainder of the SATA devices. I only realized what actually happened after I restored a Macrium Reflect (HIGHLY RECOMMENDED) image of the C: drive (NVMe) from the night before the reboot, opened device manager and saw what it had done. I rebooted to cure a different issue and Windows 10 ended up in a boot loop.

I went and used the Windows 8 driver available on Asus website called: Marvell SATA Driver V1. Standard NVM Express Controller driver wasn't sufficient for the NVMe stick not running RAID mode (disabled in BIOS) and installed theР”Р„MD-RAID Bottom Device and AMD-RAID Controller drivers for it. The issue I have is that I have 2 7200rpm drives installed, each with 2 TB storage, in the Marvell Raid Controller, and installing Windows 10 doesnt detect the driver for it. Last night at some point the system - Newly upgraded to Windows 1903 with all available post upgrade patches - that the I have an AMD Ryzen system with an Asus X370 motherboard and two SATA drives in a RAID 1 array booting from a Western Digital NVMe stick

Mostly posting this in case others run into this issue.