F5F Stay Refreshed Hardware Desktop After switching the CPU to 3900X, no NVMe SSD was recognized.

After switching the CPU to 3900X, no NVMe SSD was recognized.

After switching the CPU to 3900X, no NVMe SSD was recognized.

M
marzing22
Member
191
07-19-2019, 06:36 AM
#1
I recently upgraded my CPU from the R5 2600 to the R9 3900X on an ASUS Strix B450i motherboard. After the swap, the PC started working normally in BIOS, showing all components correctly, but it no longer recognizes the NVMe Samsung 960 Pro drive and can't boot into Windows since it's installed on the NVMe SSD. The BIOS doesn’t even detect the drive at all. I experimented with disabling/activating CSM, clearing the CMOS, and reinserting the SSD without touching it during installation. Anyone have suggestions for further troubleshooting? Your question might be a bit off-topic here, but I appreciate your patience.
M
marzing22
07-19-2019, 06:36 AM #1

I recently upgraded my CPU from the R5 2600 to the R9 3900X on an ASUS Strix B450i motherboard. After the swap, the PC started working normally in BIOS, showing all components correctly, but it no longer recognizes the NVMe Samsung 960 Pro drive and can't boot into Windows since it's installed on the NVMe SSD. The BIOS doesn’t even detect the drive at all. I experimented with disabling/activating CSM, clearing the CMOS, and reinserting the SSD without touching it during installation. Anyone have suggestions for further troubleshooting? Your question might be a bit off-topic here, but I appreciate your patience.

X
xSneik
Member
178
07-20-2019, 12:21 PM
#2
If another drive can be used to boot and functions, you may remove the 3900X CPU entirely as the cause, since it should work with NVMe but it's worth verifying. Clearly, the motherboard must support NVMe; otherwise, the issue wouldn't have resolved with the older CPU. You might also reinstall the R5 2600 CPU to determine if your 960 Pro remains operational. If it does, then the NVMe problem and the motherboard itself are ruled out, allowing you to concentrate on BIOS adjustments. This suggestion isn’t a complete fix, but it can significantly reduce possible causes. I’m sorry, I can't offer better options at the moment.
X
xSneik
07-20-2019, 12:21 PM #2

If another drive can be used to boot and functions, you may remove the 3900X CPU entirely as the cause, since it should work with NVMe but it's worth verifying. Clearly, the motherboard must support NVMe; otherwise, the issue wouldn't have resolved with the older CPU. You might also reinstall the R5 2600 CPU to determine if your 960 Pro remains operational. If it does, then the NVMe problem and the motherboard itself are ruled out, allowing you to concentrate on BIOS adjustments. This suggestion isn’t a complete fix, but it can significantly reduce possible causes. I’m sorry, I can't offer better options at the moment.

B
Blazer444
Member
146
07-25-2019, 03:23 AM
#3
Same here. X370 Taichi. Changed the 2700x to 3900x. The NVME card isn't showing up in BIOS anymore. Dafuq? Anyone?
B
Blazer444
07-25-2019, 03:23 AM #3

Same here. X370 Taichi. Changed the 2700x to 3900x. The NVME card isn't showing up in BIOS anymore. Dafuq? Anyone?

A
AlpFG
Member
142
07-28-2019, 11:20 AM
#4
Maybe adjusting the Gen speed during startup could help. It seems like an issue that might get fixed later, but we can't say for sure yet.
A
AlpFG
07-28-2019, 11:20 AM #4

Maybe adjusting the Gen speed during startup could help. It seems like an issue that might get fixed later, but we can't say for sure yet.

T
160
07-28-2019, 11:38 AM
#5
Returned to 2700x resolution. NVMe is recognized properly. Are you wondering if my CPU is faulty? It doesn’t appear to be an MB or SSD problem.
T
TheWheatherMan
07-28-2019, 11:38 AM #5

Returned to 2700x resolution. NVMe is recognized properly. Are you wondering if my CPU is faulty? It doesn’t appear to be an MB or SSD problem.

I
ItsSlippy
Junior Member
4
07-30-2019, 05:21 AM
#6
You seem to be facing the same issue as before, but you confirmed your NVMe still functions with the older CPU. It’s likely the CPU isn’t faulty. The most probable fix is updating the AMD BIOS. There might also be a temporary manual adjustment you can try.
I
ItsSlippy
07-30-2019, 05:21 AM #6

You seem to be facing the same issue as before, but you confirmed your NVMe still functions with the older CPU. It’s likely the CPU isn’t faulty. The most probable fix is updating the AMD BIOS. There might also be a temporary manual adjustment you can try.

D
DrBrokenBones
Senior Member
378
08-07-2019, 12:38 AM
#7
Uncertain about the issue. Disabled CSM in BIOS didn’t help. Windows isn’t recognizing the NVME either.
D
DrBrokenBones
08-07-2019, 12:38 AM #7

Uncertain about the issue. Disabled CSM in BIOS didn’t help. Windows isn’t recognizing the NVME either.

T
Th_MineCrafter
Junior Member
9
08-07-2019, 09:09 AM
#8
Any update on this issue? I'm assuming this was on the lastest BIOS? I have this board as well and ordered a 3900x without knowing whether it would work or not. Fingers crossed.
T
Th_MineCrafter
08-07-2019, 09:09 AM #8

Any update on this issue? I'm assuming this was on the lastest BIOS? I have this board as well and ordered a 3900x without knowing whether it would work or not. Fingers crossed.

F
Frealer
Member
62
08-08-2019, 10:24 AM
#9
F
Frealer
08-08-2019, 10:24 AM #9

S
Skyrocker
Member
55
08-14-2019, 08:51 AM
#10
Set up an account to contribute thoughts on a previous discussion, in case this comes up from Google. I experienced the same problem (with a recently installed Ryzen 3800xt). After some adjustments, my issue was fixed by updating the chip and changing the BIOS settings. Specifically, re-seating the old chip, updating to F51 instead of F40, and then flashing the BIOS again worked for me.
S
Skyrocker
08-14-2019, 08:51 AM #10

Set up an account to contribute thoughts on a previous discussion, in case this comes up from Google. I experienced the same problem (with a recently installed Ryzen 3800xt). After some adjustments, my issue was fixed by updating the chip and changing the BIOS settings. Specifically, re-seating the old chip, updating to F51 instead of F40, and then flashing the BIOS again worked for me.