PC Building

[flyafar]

This was extremely disruptive as the only solution was to reboot the PC until I discovered a workaround. Running the AMD autodetect drivers application seems to force the system to detect the missing drive and reinitialize it. It otherwise doesn't appear in windows explorer or the disk management tool whatsoever, but once the driver utility scans my hardware, the drive pops up as connected and functions completely normally. I've reseated it multiple times but the issue persists.

Ideally, I'd like to avoid this problem altogether, so I'm posting here to see if anyone has a similar problem or has a better solution.

Specs:

Motherboard: Asus x670e-e strix gaming wifi w/ 2403 (latest) BIOS and latest chipset drivers

CPU: Ryzen 7950x3d

Ram: G.Skill Flare X 2x32GB DDR5-6000

GPU: ASUS Nvidia RTX 4080

Storage: 2x Samsung 980 PRO 2TB m.2 SSDs in slots m2_1 (this is the one that frequently disappears) and m2_3 (OS Drive), 2x 870 EVO 4TB SATA SSDs, 2x Seagate IronWolf 8TB HDDs

PSU: Corsair RM850x

[FunkZ]

Check Windows Power & Sleep settings to make sure that the power profile you are using does not have the "hard drive" set to sleep.

[flyafar]

Oh, does that apply to SSDs as well? I thought it only allowed mechanical drives to shut down to reduce wear and tear. I'll give that a try. It's weird that none of my other drives disappear, if that's the issue.

EDIT: Apparently it was already set to never allow the drives to sleep, since I use process lasso and the power profile is set to "Bitsum Highest Performance". I appreciate the suggestion though!

[elstaci]

I see by your Asus Motherboard Specs that M.2-1 through M.2-3 slots are enabled by the CPU (supports PCIe 5.0 x4 mode) while M.2_4 (PCIe 4.0 mode) is enabled by the AMD Chipset.

Looking at your Asus QVL LIST for Devices it doesn't show any Samsung M.2 drives.

According to Samsung concerning the 980 Pro w/ Heatsink PCIe@4.0 NVme (1 tb) run at PCIe 4.0 while the M.2 is rated at PCIe 5.0.

But that shouldn't be an issue since PCIe 5.0 is backwards compatible with PCIe 4.0.

To see if the problem is with slot M.2_1 or your Samsung NVme 980 Pro device. Since the second same drive on M.2_3 doesn't disappear try switching the M.2_3 drive with the M.2_1 Drive and see if the M.2_3 drive now starts to disappear instead of the M.2_1 drive.

If M.2_1 drive starts having the same issue than it might be a problem with the Motherboard or CPU or a compatibility issue with your Samsung 980 Pro NVme drive.

Note: In my opinion, I would connect your Windows OS Drive to M.2_1 slot rather than on the M.2_3 slot.

[flyafar]

So I tried different slots over the past week (an extremely annoying task, having to remove the GPU every time, lemme tell you), and it really seems like the m.2_3 slot is the only one that persistently shows the connected drive when waking up from sleep. When I had my OS drive in any other slot, I would sometimes just have a black screen upon waking from sleep, and have to restart to get into windows. Whenever it did properly wake up, when the non OS drive was connected to the m.2_3 slot, it always showed up. So something must be wrong with every other m.2 slot besides the 3rd one, right? What other reason could there be for this. I have no other system stability issues so I'm really hesitant to RMA the motherboard, especially since I don't have a backup board on hand atm.

HOWEVER!! Something really strange is that, if I keep Samsung Magician (Samsung's drive monitoring/updating software) running in the background, the non OS drive is always present after sleep resume. I've had it running for two days, and woke from sleep over a dozen times to be sure. Every time, the drive shows up without me having to run the AMD auto detect software or restart my PC to get the drive to appear, where as if I closed the software, it was almost 50/50 whether the drive would appear. I can't imagine what's going on that causes the drive to disappear completely, even from windows disk management, unless it's either constantly monitored or forced to be detected (the occupied slot, that is) by AMD's hardware scan.

As long as the Samsung magician utility keeps this from happening, I guess I can live with this annoying quirk until something more serious presents itself. Needless to say I have everything important backed up lol

[BigAl01]

Glad you found a solution.