![uninstall samsung nvme controller driver windows 10 uninstall samsung nvme controller driver windows 10](https://tips.thaiware.com/upload_misc/tips/2021_06/images/1606_210622153753sB_14.png)
- #Uninstall samsung nvme controller driver windows 10 install
- #Uninstall samsung nvme controller driver windows 10 drivers
- #Uninstall samsung nvme controller driver windows 10 windows 10
It looks like the chipset driver is irrelevant however, since the NVME controller driver I ended up with comes from Microsoft (system32\Drivers\stornvme.sys) I installed the Chipset driver and GPU driver, and after that this was the main thing that stood out. Then I compared what was in device manager between the 2 installations. I right-click -> uninstalled it including its driver software, let device manager scan for new hardware, and it replaced this device with "Standard NVM Express Controller" and my SSD instantly started working without a reboot.Īfter trying everything you guys suggested, (including testing with and without the chipset drivers) I installed Windows (build 2004) on the SSD which worked without a problem. In Device Manager, under Storage controllers, there was a device called "AMD RAID Bottom Device". I had the same problem with a brand new XPG Gammix S50 lite on an AsRock X570 board.įormating the SSD or anything like that didnt help in my case. I've dealt with drive letter conflict before, the drive should still be showing up in Drive Manager. So the NVMe drive was running in RAID mode, but not in a RAID with other drivers. However, I have to change the NVMe mode from normal to RAID mode when I changed the SATA controller from AHCI to RAID, if that makes sense. Windows was never installed to the NVMe drive, Windows was only on the 120GB SSDs in RAID and the 240GB SSD. It was always a stand alone data drive, only the two 120GB SSDs were every used in a RAID array. The NVMe drive was never in a RAID array. This is obviously a horrible design flaw on AMD's side.Īnyway, thanks to everyone that helped, all your suggestions were appreciated.
#Uninstall samsung nvme controller driver windows 10 install
But instead Windows loaded the driver normally and applied it to the Intel NVMe controller automatically! WTF?! I know it did this, because in my list of drives available to install Windows to, my NVMe drive plugged into the Intel system disappeared, just like what was happening on the AMD system. Now, anyone that has done this before knows that normally if you try to load a driver this way that isn't compatible with any hardware in your system, Windows installer won't let you.
#Uninstall samsung nvme controller driver windows 10 drivers
I selected the option to load more drivers and loaded the AMD NVMe drivers, and to my surprise it took them.
#Uninstall samsung nvme controller driver windows 10 windows 10
So I fired up my Windows 10 install media on my Intel system. I force removed the device and it's drivers through Device Manager, rebooted Windows and BAM I can see the VNMe Drive now!īut this got me wondering. I just happened to be running through Device Manager and saw something under Storage Controllers called AMD RAID something something(I don't remember exactly what it said, I was just happy to find it and quicly right clicked on it and uninstalled it). As far as Windows was concerned, everhthing was perfectly normal. The odd part is there wasn't any error in device manager. But the controller wasn't functional with that driver. So, you guessed it, the AMD RAID driver was still loading for the NVMe controller. Well guess what, AMD in their infinite wisdom, deciced to not change the device ID of the NVMe controller when you change it from RAID to nromal NVMe mode and vise versa. That's why when I changed the SATA controller form RAID to AHCI, the standard AHCI driver just loaded automatically the next time I booted Windows. ALSO, normally when you change a controller from RAID back to AHCI/NVMe, the device ID changes so the OS identifies it as a different device entirely. So, AMD is stupid(are we surprised?) Even though I uninstalled all the drivers(I thought), the NVMe Controller driver is separate and doesn't get uninstalled when you uninstall all the other drivers. So this finally got me in the right direction and I figured it out!