Question History of issues leading up to (assumed) failure of Samsung 990 Pro 2tb

Jun 10, 2025
2
0
10
I wish I could say for sure I missed something here but I just assume I'm down 250$ at this point. I'll do my best to throw down the specs and what's been going on...

Product Name: MAG B650 TOMAHAWK WIFI
OS: Microsoft Windows 11 Pro 64-bit Ver.2009 (OS build 26100.4202)
BIOS Version: 1.N1
BIOS Release Date: 04/29/2025
CPU: AMD Ryzen 5 7600X 6-Core Processor
Memory: 32 GB @
- 16 GB DDR5-4800, Corsair
- 16 GB DDR5-4800, Corsair
Graphics: AMD Radeon RX 6800 XT
Graphics: AMD Radeon(TM) Graphics
NVME Drive C: SSD, Samsung SSD 970 EVO Plus 2TB, 1863.02 GB (BOOT DRIVE)
USB Ext Drive G: HDD, Ext HDD 1021, 1863.01 GB
SATA Drive E: SSD, Samsung SSD 870 QVO 4TB, 3726.02 GB
Network: Realtek Gaming 2.5GbE Family Controller
Network: RZ616 Wi-Fi 6E 160MHz #2
Power Plan: GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)

*The drive I am posting about is NOT visible in the above export from MSI center. Normally the 990Pro 2tb is D:*

So back in December 2024 I bought a Samsung 990 Pro 2tb nvme to replace a crappy ADATA nvme I had been running as my gaming drive. The drive installed and ran fine (at first). After about a week of use I sat down at my computer, opened Steam, and no games were installed, same with Epic. I opened the File Explorer thinking maybe my folder was deleted or corrupted. Went to the Drive list, C: boot, D: gaming, E: backup\junk drive, my USB drive is not normally plugged in like you see in the export above, and I saw the D: drive with my games on it, double clicked and saw the Steam folder, tried to click on it and poof the D: vanished entirely. I rebooted my computer and it re-appeared...weird.

This would start a pattern. I would NEVER have a game crash due to the D: disappearing, but every couple days I would open Steam...no games...reboot...D: is back. Then it started getting worse where rebooting wouldn't bring it back. I would have to click off the manual PSU switch then hold the power button to fully suck any remaining juice out, then power up...D: back.

At that point it was becoming really annoying and clearly not something that should be going on. Steps I took:

1)Full windows update scan. Installed anything that was in the queue.
2)Using samsung magician updated the firmware on the D: (990Pro).
3)Ensured I had the latest chipset\mobo drivers.
4)Downloaded the latest stable bios flash and flashed.
5)I moved the nvme to the other open slot.

A day or two went by...drive vanishes. Wtf.

So I'm trying to figure out if this is RMA time, but it's hard when I can't force it to happen, you just need to use it for a day or so in a PC.

Then in January I notice a BIOS update from MSI that mentions fixing some compatibility issues with some nvme drives. Aha! I repeat steps 1-4 listed above including this new bios.

Fixed! For a couple months there were no issues....then last night...all my steam games are gone, except this time rebooting doesn't fix it, steps 1-4 above don't fix it, step 5 doesn't fix it. I can't see the drive in ANYTHING.

So here's what I'm at now:
-When I go into the BIOS I can see the 990Pro listed in the drive list. If I move the drive from one nvme slot to a different one then go back into the BIOS I see it sitting in the new slot.
-When I go into windows however it's like it doesn't exist. Samsung magician doesn't see it. Win11 Disk manager doesn't see it. Device Manager doesn't see it. It's completely invisible\undetectable.

I did notice in Device Manager that under Storage Controllers there's 2x Standard NVM Controller's and one of them has the "!" error on it. I tried un-installing it and then re-scanning. Everytime it re-installs it goes right back to "!".

Inside it's details it says:
This device cannot start. (Code 10)
An I/O adapter hardware error has occurred.

I dug through the BIOS. The drive is, and always has been, set to AHCI only, never RAID. Everything in the BIOS looks fine.

I even got to grasping at straws here and read some obscure posts about certain SATA drive slots interfering with NVME slots. So I moved the QVO SATA drive connector to S 3\4 just to see, didn't help.

So am I missing anything? The drive is junk I'm guessing?

EDIT: The drive was bought in person at Best Buy and was still sealed, and Magician had no issues with it when it was working. So there's virtually 0 chance it is a knock off.
 
Last edited:
Welcome to the forums, newcomer!

So am I missing anything?
In order to rule out your motherboard being the source of the issue(of your drive vanishing) you might want to drop the drive onto another platform and see if the drive behaves the same way.

You mentioned updating the firmware for the SSD which should've resolved any rapid deterioration of the drive's health.

BIOS Version: 1.N1
You state being on the latest BIOS version, which when cross referencing I noticed that it's a Beta version, for the sake of troubleshooting, did you clear the CMOS after you'd verified your BIOS was successfully flashed to 1.N1?

The drive is junk I'm guessing?
I would assume so, if the drive is also behaving the same on another platform or other platforms. If you're yet within warranty, you can pass on this thread and your experience(including photos and maybe a video) of the issue as supporting info for your RMA process with Samsung.

One other observation;
Memory: 32 GB @
- 16 GB DDR5-4800, Corsair
- 16 GB DDR5-4800, Corsair

If the ram is meant to be at DDR5-6000MHz, might want to see if AMD's E.X.P.O is enabled in BIOS. If the ram doesn't go to that speed, then you've got performance left on the table on your AM5 platform.
 
  • Like
Reactions: Guyfromthenorth
Welcome to the forums, newcomer!

So am I missing anything?
In order to rule out your motherboard being the source of the issue(of your drive vanishing) you might want to drop the drive onto another platform and see if the drive behaves the same way.

You mentioned updating the firmware for the SSD which should've resolved any rapid deterioration of the drive's health.

BIOS Version: 1.N1
You state being on the latest BIOS version, which when cross referencing I noticed that it's a Beta version, for the sake of troubleshooting, did you clear the CMOS after you'd verified your BIOS was successfully flashed to 1.N1?

The drive is junk I'm guessing?
I would assume so, if the drive is also behaving the same on another platform or other platforms. If you're yet within warranty, you can pass on this thread and your experience(including photos and maybe a video) of the issue as supporting info for your RMA process with Samsung.

One other observation;
Memory: 32 GB @
- 16 GB DDR5-4800, Corsair
- 16 GB DDR5-4800, Corsair

If the ram is meant to be at DDR5-6000MHz, might want to see if AMD's E.X.P.O is enabled in BIOS. If the ram doesn't go to that speed, then you've got performance left on the table on your AM5 platform.
Thanks for the quick reply, I appreciate any help I can get.

1)Unfortunately I don't have another system with me or nearby that could test a NVME drive. I debated on ordering a USB enclosure for it just to see if it suddenly worked that way. I realize it wouldn't make the drive useable as a game drive anymore, but I've already got a 2tb WD Black on it's way to me via amazon to replace this one.

2)Good catch on the Beta bios. I downloaded and flashed that late last night and didn't even notice MSI put a beta version at the top of the public list. The flash didn't change anything for better or worse so it probably won't matter. I did clear the cmos yes. I plan to re-flash with 7D75v1M in a bit here just because I don't like beta testing BIOS for mobo manufacturers. I just need my system to be reliable.

3)Thanks for the RMA tips, I can't find my best buy receipt unfortunately. I know the day it was bought so maybe if I go to a best buy they can look it up and re-print.

4)Another good catch on the missing EXPO setting. I like that you actually READ posts, alot of forum people don't seem to do that lol. That's because I flashed\wiped the bios during all this testing and never took the time to set EXPO and all the other fine tunes I had previously as I figured I may be doing a few flashes while sorting this out. Once I flash to the non-beta version I'll get my settings dialed back in as that'll be the end of troubleshooting for the foreseeable.