NVMe SSD Not Showing Up In Windows on AMD System

[ne6togadno]

what happens when you turn back sata mod to raid. does win find your drive

Advanced Host Controller Interface - Wikipedia

en.wikipedia.org

 

[bug]

And what happens if you force remove the NVMe RAID driver? As it seems that it might be the cause of the problem at this point.

I was about to say: remove all chipset drivers in Windows, install then again clean.

 

[newtekie1]

what happens when you turn back sata mod to raid. does win find your drive

Advanced Host Controller Interface - Wikipedia

en.wikipedia.org

Windows doesn't boot because it doesn't have drivers for SATA RAID anymore. You have to force load AMD's SATA RAID drivers during Windows install because Windows doesn't have the drivers built in, if you remove them later like I did, you can't go back. I tried.

 

[ne6togadno]

uh. i got a bit lost in the drive switching and win mirroring
let me see if i got it right
during raid era windows was installed on raid made out of 1 nvme and 2 120gb ssd.
you copied this windows to 240ssd (which is different from nvme from raid array)
then you boot windows from 240ssd (sata mod is changed from raid to achi) and windows that is loaded from 240gb ssd cant see nvme drive you've used in the raid.

you said also that you've used clear on nvme drive when it was in other pc for test. the same clear command that bios notes you it will remove everything from your drive? so nvme drive is completely empty. no left overs from raid or other windows installs right?
if nvme drive is visible in other pcs what drive letter it has assigned.
could it be that drive letter of the drive is in conflict with existing drive letters in your amd system?

 

[newtekie1]

uh. i got a bit lost in the drive switching and win mirroring
let me see if i got it right
during raid era windows was installed on raid made out of 1 nvme and 2 120gb ssd.
you copied this windows to 240ssd (which is different from nvme from raid array)
then you boot windows from 240ssd (sata mod is changed from raid to achi) and windows that is loaded from 240gb ssd cant see nvme drive you've used in the raid.

you said also that you've used clear on nvme drive when it was in other pc for test. the same clear command that bios notes you it will remove everything from your drive right? so nvme drive is completely empty. no left overs from raid or other windows installs right?
if nvme drive is visible in other pcs what drive letter it has assigned.
could it be that drive letter of the drive is in conflict with existing drive letters in your amd system?

The NVMe drive was never in a RAID array. It was always a stand alone data drive, only the two 120GB SSDs were every used in a RAID array. Windows was never installed to the NVMe drive, Windows was only on the 120GB SSDs in RAID and the 240GB SSD. 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. So the NVMe drive was running in RAID mode, but not in a RAID with other drivers.

I've dealt with drive letter conflict before, the drive should still be showing up in Drive Manager.

And what happens if you force remove the NVMe RAID driver? As it seems that it might be the cause of the problem at this point.

So this finally got me in the right direction and I figured it out!

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. 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. 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. 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. So, you guessed it, the AMD RAID driver was still loading for the NVMe controller. But the controller wasn't functional with that driver. The odd part is there wasn't any error in device manager. As far as Windows was concerned, everhthing was perfectly normal. 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). I force removed the device and it's drivers through Device Manager, rebooted Windows and BAM I can see the VNMe Drive now!

But this got me wondering. So I fired up my Windows 10 install media on my Intel system. I selected the option to load more drivers and loaded the AMD NVMe drivers, and to my surprise it took them. 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. 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. This is obviously a horrible design flaw on AMD's side.

Anyway, thanks to everyone that helped, all your suggestions were appreciated.

 

[ne6togadno]

amd had amddrivercleaner.exe (or some similar name) tool for removing drivers. i cant find it now on their cite but if you have it downloaded from your 8350 times it still works.
so far it is the best tool for amd drivers removal i've used.

edit: i've found it. name is amdcleanuputility.exe

https://www.amd.com/en/support/kb/faq/gpu-601

 

[davepl]

I was in the same boat, here's what I did:

ENABLED NvME Raid
Run RAIDEXpert2
Deleted all arrays
Cleaned Metadata (THAT is what made the drives reappear in Disk Management)
Continue from there...

 

[jazzaddict]

nvme visible in bios but not in windows under disk manager..
Here is one easy solution that what worked for me:

1. Boot with windows installation disc/usb flas drive.
2. Choose new custom installation, no need to enter product key.
3. Create new partition on nvme drive and format it.
4. Exit installer.

 

[jesdals]

On some boards using certain sata ports vil disable a nvme slot and visa versa - could perhaps be that issue if none of the above mentioned works out

 

[Kapone33]

I can read and write to the drive normally when it is in the other computer.

Format the drive in the other computer without assigning a letter. That should solve whatever files Windows wrote on that drive to make it unreadable. I have had this issue before and doing that solved it for me. It has to be a NVME adapter attached to another PC though.

The NVMe drive was never in a RAID array. It was always a stand alone data drive, only the two 120GB SSDs were every used in a RAID array. Windows was never installed to the NVMe drive, Windows was only on the 120GB SSDs in RAID and the 240GB SSD. 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. So the NVMe drive was running in RAID mode, but not in a RAID with other drivers.

I've dealt with drive letter conflict before, the drive should still be showing up in Drive Manager.



So this finally got me in the right direction and I figured it out!

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. 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. 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. 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. So, you guessed it, the AMD RAID driver was still loading for the NVMe controller. But the controller wasn't functional with that driver. The odd part is there wasn't any error in device manager. As far as Windows was concerned, everhthing was perfectly normal. 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). I force removed the device and it's drivers through Device Manager, rebooted Windows and BAM I can see the VNMe Drive now!

But this got me wondering. So I fired up my Windows 10 install media on my Intel system. I selected the option to load more drivers and loaded the AMD NVMe drivers, and to my surprise it took them. 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. 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. This is obviously a horrible design flaw on AMD's side.

Anyway, thanks to everyone that helped, all your suggestions were appreciated.

It is nice to see there is more than one work around for this problem.

 

[wwpadina]

The NVMe drive was never in a RAID array. It was always a stand alone data drive, only the two 120GB SSDs were every used in a RAID array. Windows was never installed to the NVMe drive, Windows was only on the 120GB SSDs in RAID and the 240GB SSD. 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. So the NVMe drive was running in RAID mode, but not in a RAID with other drivers.

I've dealt with drive letter conflict before, the drive should still be showing up in Drive Manager.



So this finally got me in the right direction and I figured it out!

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. 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. 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. 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. So, you guessed it, the AMD RAID driver was still loading for the NVMe controller. But the controller wasn't functional with that driver. The odd part is there wasn't any error in device manager. As far as Windows was concerned, everhthing was perfectly normal. 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). I force removed the device and it's drivers through Device Manager, rebooted Windows and BAM I can see the VNMe Drive now!

But this got me wondering. So I fired up my Windows 10 install media on my Intel system. I selected the option to load more drivers and loaded the AMD NVMe drivers, and to my surprise it took them. 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. 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. This is obviously a horrible design flaw on AMD's side.

Anyway, thanks to everyone that helped, all your suggestions were appreciated.

Thank you!

 

[davepl]

Are there enough lanes? I have 4NvME drives, a x16 video card, and that's all the lanes there are. I don't know if this card can work when you have 4 nvme in the board as well.

 

[BasementComputing]

I had the same problem with a brand new XPG Gammix S50 lite on an AsRock X570 board.
Formating the SSD or anything like that didnt help in my case. But I found a solution:

Solution:
In Device Manager, under Storage controllers, there was a device called "AMD RAID Bottom Device". 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.

How I got there:
After 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. Then I compared what was in device manager between the 2 installations. I installed the Chipset driver and GPU driver, and after that this was the main thing that stood out. 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 made this forum account just to post this btw. Hope it helps some of you.

 

[thethinker]

I had the same problem with a brand new XPG Gammix S50 lite on an AsRock X570 board.
Formating the SSD or anything like that didnt help in my case. But I found a solution:

Solution:
In Device Manager, under Storage controllers, there was a device called "AMD RAID Bottom Device". 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.

How I got there:
After 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. Then I compared what was in device manager between the 2 installations. I installed the Chipset driver and GPU driver, and after that this was the main thing that stood out. 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 made this forum account just to post this btw. Hope it helps some of you.

Thank you! I tried everything else. This worked just fine! Had to delete the driver twice, because the first time it was reinstalled again with the "AMD RAID Bottom Device". Windows installed it automatically with the "Standard NVM Express Controller".
Wish I had read this 5h before...


What lead to my problem:
I changed my NVMe SSD due to lack of space. Of course the previous SSD worked fine.


What I've tried:
1. GParted Live (Create new partition table and format to ntfs)
2. Using diskpart with Windows Installer (Alt+F10), which worked but the drive didn't show up because of the fault driver
2.5 Using windows installer to delete and create a new partition
3. Windows Safe mode. Considering the problem this couldn't work.
4. Uninstalling every MB driver, chipset driver, even RAID driver (I don't use RAID)
4.5 Using the "AMD Cleanup Utility"
5. SSD manufacturer service program
6. 3 different partition tools


After attempt nr. 1, 2 and 4.5 I'd had hope, but it didn't work.

 

[n0M3n]

I had the same problem with a brand new XPG Gammix S50 lite on an AsRock X570 board.
Formating the SSD or anything like that didnt help in my case. But I found a solution:

Solution:
In Device Manager, under Storage controllers, there was a device called "AMD RAID Bottom Device". 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.

How I got there:
After 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. Then I compared what was in device manager between the 2 installations. I installed the Chipset driver and GPU driver, and after that this was the main thing that stood out. 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 made this forum account just to post this btw. Hope it helps some of you.

Just gotta tell you, thank you! It was driving me nuts!
THANK YOU!

 

[SenditMakine]

That's what I'm trying to avoid. This would be the second re-install thanks to this fight, because the system freaked out when I added the NVMe drive and somehow Windows was corrupted.




It shows up in the BIOS normally. It is just not in Windows.

thats a relief, means it is working

 

[skadiknmebllz]

I just made an account to thank you! I installed latest AMD drivers for my GFX, was gonna start to play and saw that my NVME was gone and could not find it in device manager. Tried ye old sfc /scannow and everything. Nothing worked! Resetting bios, clear cmos, hard reset, remove and add nvme NOTHING.

And then I found this glorious post. I CANT THANK YOU ENOUGH BasementComputing!

I had to delete the device and uninstall it and reboot and it showed up after restart.

I am very sure that latest AMD Radeon software installed and fucked this.

 

[Vector79]

I also made an account to thank you guys for figuring it out.

Today I installed the latest AMD chipset software (Version 2.13.27.501) and my NVMe Samsung SSD 970 EVO Plus was gone in Windows, with my whole game library... I deleted the driver under "Storage Controllers" > "AMD RAID Bottom Device" in the device manager, rebooted and the NVMe is back again.

 

[gwizdzius]

This Solution is best. Works beautiful.

 

[BasementComputing]

Glad it helped you guys! It's always horrible when basic stuff like this doesnt work and there are no solutions.

 

[AsRock]

I had some thing like this with a SSD, even though it was working without issue one day it decided not to work in the PC, so i plugged it in another and it was working perfectly how ever putting it back in the original PC still would not work so i put it back in the other and formatted it and to this day it still works in both PC's.

 

[INSTG8R]

This hit me yesterday after a bad driver install. Wish I’d seen this solution yesterday. Good too know there’s a pretty easy fix if it happens again.

 

[zomgw00t]

I had the same problem with a brand new XPG Gammix S50 lite on an AsRock X570 board.
Formating the SSD or anything like that didnt help in my case. But I found a solution:

Solution:
In Device Manager, under Storage controllers, there was a device called "AMD RAID Bottom Device". 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.

How I got there:
After 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. Then I compared what was in device manager between the 2 installations. I installed the Chipset driver and GPU driver, and after that this was the main thing that stood out. 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 made this forum account just to post this btw. Hope it helps some of you.

oh my god, thank you so much!!