NVMe SSD Not Showing Up In Windows on AMD System

[newtekie1]

This all relates to my previous thread on my struggles with running RAID on AMD here.

This is on my AMD Rig4 in my signature, but I'll give a brief rundown on system specs just in case my signature or the rig changes in the future:

Ryzen 5 2600
X470 Taichi Ultimate
16GB DDR4-2933
GTX1060
850W Corsair HX850
240GB SATA SSD - OS(Inland Professional)
1TB NVMe SSD - Cache Disk(ADATA SX8200 Pro)
HighPoint 2722 SAS RAID Controller

-5x6TB HDDs in RAID6​

-6x3TB HDDs in RAID5​

-2 Random HDDs running as stand alone drives​

​

Now, originally I had the NVMe drive and 2x120GB SSDs in RAID1 connected to the motherboard. That experiment failed thanks to AMD not supporting TRIM when their controllers are in RAID mode, and all the drives becoming painfully slow(it came to a head when it took over an hour to install Windows 10 Updates). Also, the Cache disk was pretty much worthless because writes directly to the RAID arrays were quicker than writes to the NVMe SSD I was using as a cache.

So, I cloned the OS from the 2x120GB SSDs over to a single 240GB SSD using Acronis True Image. System booted just fine. Then I went into the BIOS and switched the SATA controller from RAID to AHCI and disabled RAID mode on the NVMe(you have to do it in two different placed in the BIOS for some stupid reason). I booted into Windows, it auto installed the AMD SATA driver and asked me to reboot, and it booted just fine.

That's when I noticed the NVMe drive wasn't showing up in Windows. Not that it wasn't showing up in This PC, it wasn't showing up anywhere. It wasn't in Disk Management and it wasn't in Device Manager, no where in Windows.

So, things I've tried:

Uninstalled everything AMD I could find in Programs and Features and Apps.
Re-installed the standard AMD Chipset driver.
Reset the BIOS to defaults.
Flashed the latest BIOS.
Removed the Highpoint card to make sure it wasn't interfering somehow.
Changed the NVMe drive to a different NVMe slot.
Moved the NVMe drive to another computer to confirm it is working.

So now I'm stumped... Any ideas?

 

[milewski1015]

Reinstall Windows? Seems like you've already tried everything I would logically suggest. It doesn't show up in the BIOS?

 

[Sammyfed1]

Sounds like it's not showing up in BIOS.

 

[newtekie1]

Reinstall Windows?

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.

Reinstall Windows? Seems like you've already tried everything I would logically suggest. It doesn't show up in the BIOS?

Sounds like it's not showing up in BIOS.

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

 

[TheLostSwede]

Did you try disabling CSM and fast boot options?
Also, can you see it in Disk Management? You might have to "enable" it there.

 

[newtekie1]

Did you try disabling CSM and fast boot options?

Yes.

Also, can you see it in Disk Management? You might have to "enable" it there.

No, as I said in the first post, it is not in Disk Management or Device Manager.

 

[nailzer]

If it doesn't show up in Disk Management you might want to RMA the drive.

 

[TheoneandonlyMrK]

Yes.



No, as I said in the first post, it is not in Disk Management or Device Manager.

Could it be that it's a Gpt partition tied to an OS that doesn't recognize it.
I have been having similar issues after using a 8Tb externally plugged in initially to copy the old drive contents.
When internalised it wasn't recognized by the same Os that effing made it externally.
It took deleting via diskpart on another pc to fix it for me.

Gpt is a pain if used.

My phone's one more niggle from getting f'd up against a wall.

 

[newtekie1]

If it doesn't show up in Disk Management you might want to RMA the drive.

It shows up in the BIOS, it showed up just fine before I changed the BIOS option to disable NVMe RAID, and it shows up on every other computer I have tried it on. So I don't think it is the drive.

Could it be that it's a Gpt partition tied to an OS that doesn't recognize it.
I have been having similar issues after using a 8Tb externally plugged in initially to copy the old drive contents.
When internalised it wasn't recognized by the same Os that effing made it externally.
It took deleting via diskpart on another pc to fix it for me.

Gpt is a pain if used.

The drive should still be listed in Disk Management, but with an unknown partition.

Even still, it doesn't show up even in diskpart.

 

[TheoneandonlyMrK]

It shows up in the BIOS, it showed up just fine before I changed the BIOS option to disable NVMe RAID, and it shows up on every other computer I have tried it on. So I don't think it is the drive.




The drive should still be listed in Disk Management, but with an unknown partition.

Even still, it doesn't show up even in diskpart.

I don't suppose you have a usb to nvme adapter so you can try it in another pc easily.

Mine didn't show either initially took deleting the original partitions on another pc to bring it back to visible and more staring about in diskpart to get it working.

Could be a bios option you missed possibly disabling it ie pciex lane allocation or nvme support and also now you have Sata working right can't you try re enabling nvme raid to see if it shows up , it should still boot fine From SATA ahci despite enabling that.

Nvme 2.2 goes missing with some settings on mine I by it disabled now in fact on purpose.

 

[newtekie1]

I don't suppose you have a usb to nvme adapter so you can try it in another pc easily.

Mine didn't show either initially took deleting the original partitions on another pc to bring it back to visible and more staring about in diskpart to get it working.

Could be a bios option you missed possibly disabling it ie pciex lane allocation or nvme support and also now you have Sata working right can't you try re enabling nvme raid to see if it shows up , it should still boot fine From SATA ahci despite enabling that.

Nvme 2.2 goes missing with some settings on mine I by it disabled now in fact on purpose.

I've already tried it on another computer, it shows up just fine.

Literally the only setting in the BIOS I have changed is changing NVMe RAID from enabled to disabled. I could see it in Windows before changing that option.

 

[TheoneandonlyMrK]

I've already tried it on another computer, it shows up just fine.

Literally the only setting in the BIOS I have changed is changing NVMe RAID from enabled to disabled. I could see it in Windows before changing that option.

I think it's possible wiping it would fix it as I said , just throwing you ideas bro it shows in another pc as mine did.
Your OS is seeing it as a drive you have no rights to see or something IMHO, I've had this twice only wiping got it working for me.

 

[newtekie1]

I think it's possible wiping it would fix it as I said , just throwing you ideas bro it shows in another pc as mine did.
Your OS is seeing it as a drive you have no rights to see or something IMHO, I've had this twice only wiping got it working for me.

I forgot to say I ran a clean command on it when it was in the other machine.

 

[TheoneandonlyMrK]

I forgot to say I ran a clean command on it when it was in the other machine.

Good lord bro you have my issues beat in the wtaf domain then sorry.
Have you tried re enabling nvme raid , checked pciex allocation stuff , I realize you have only moved one setting but sometimes odd stuff happens elsewhere unexpectedly.

 

[newtekie1]

Good lord bro you have my issues beat in the wtaf domain then sorry.
Have you tried re enabling nvme raid , checked pciex allocation stuff , I realize you have only moved one setting but sometimes odd stuff happens elsewhere unexpectedly.

Yeah, I did a BIOS flash and reset.

 

[Aquinus]

If you want to rule out Windows as the issue, have you tried booting a relatively new Linux distro from a flash drive to see if it shows up there? I'd feel better about calling it a BIOS issue if it could be reproduced with either a clean installation or another OS.

 

[TheoneandonlyMrK]

Yeah, I did a BIOS flash and reset.

You said it worked in another pc , did you try creating a drive on it , copy some files to definitively destroy the last partition then put it back in yours.
Mine misrepresented a fair few times it took me three days and a fair few attempts to get it alive.

 

[newtekie1]

If you want to rule out Windows as the issue, have you tried booting a relatively new Linux distro from a flash drive to see if it shows up there? I'd feel better about calling it a BIOS issue if it could be reproduced with either a clean installation or another OS.

I've got a few WindowsPE flash drives floating around, heck I can probably boot into a Windows 10 install drive and see if it sees it there. I'll try that.

You said it worked in another pc , did you try creating a drive on it , copy some files to definitively destroy the last partition then put it back in yours.
Mine misrepresented a fair few times it took me three days and a fair few attempts to get it alive.

Yes, the drive is fully functional in another machine. In fact, when I put it in the other machine, the partition that was on it showed up on that PC and I could read files and write files to it normally. I did a clean command on the drive and re-initialized it and created a new partition just to be safe.

 

[TheoneandonlyMrK]

I've got a few WindowsPE flash drives floating around, heck I can probably boot into a Windows 10 install drive and see if it sees it there. I'll try that.



Yes, the drive is fully functional in another machine. In fact, when I put it in the other machine, the partition that was on it showed up on that PC and I could read files and write files to it normally. I did a clean command on the drive and re-initialized it and created a new partition just to be safe.

Write a smallish file to it too though?

 

[newtekie1]

Write a smallish file to it too though?

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

 

[oobymach]

Dumb question have you tried the mobo manufacturer nvme driver? It'll be on the mobo install disc somewhere. Does anything show in device manager with a yellow or red icon?

 

[xvi]

I can probably boot into a Windows 10 install drive and see if it sees it there. I'll try that.

I would be curious to know this too. Should hopefully point us in the direction of it being an issue with that particular Windows install or if it still doesn't show up, maybe some kind of incompatibility with that NVMe driver and the mobo's AHCI?

 

[DAPUNISHER]

Should hopefully point us in the direction of it being an issue with that particular Windows install

That was the problem in my case. Had a similar issue with a WD Black NVMe not being seen by windows, but appearing in the UEFI. I installed WD SSD dashboard, and fortunately it did see it. It allowed me to erase and format it, which then made it show up in windows. ADATA has their own toolbox, worth a try if it has not already been efforted http://www.adata.com/en/ss/software-6/

 

[newtekie1]

Dumb question have you tried the mobo manufacturer nvme driver? It'll be on the mobo install disc somewhere. Does anything show in device manager with a yellow or red icon?

The only NVMe driver the manufacturer provides is the NVMe RAID driver. I guess the normal NVMe driver is bundled with the chipset, which is just AMD's chipset driver zipped up. Which I've already tried installing.

Nothing with a yellow or red icon.

I would be curious to know this too. Should hopefully point us in the direction of it being an issue with that particular Windows install or if it still doesn't show up, maybe some kind of incompatibility with that NVMe driver and the mobo's AHCI?

I'll try to get this done today.

That was the problem in my case. Had a similar issue with a WD Black NVMe not being seen by windows, but appearing in the UEFI. I installed WD SSD dashboard, and fortunately it did see it. It allowed me to erase and format it, which then made it show up in windows. ADATA has their own toolbox, worth a try if it has not already been efforted http://www.adata.com/en/ss/software-6/

No dice, the tool didn't detect the drive at all.

 

[TheLostSwede]

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.