F5F Stay Refreshed Hardware Desktop Nvme fails to power on with Windows 10.

Nvme fails to power on with Windows 10.

Nvme fails to power on with Windows 10.

H
Hoewls
Member
145
09-26-2019, 10:59 AM
#1
I have a peculiar problem. I assembled a new computer and combined old and new components to create a system for my wife. She is functioning perfectly, while mine isn't. My previous setup consisted of a Gigabyte B450 AorusM with a Ryzen 5 2600X, 16GB Corsair Vengeance LPX, EVGA 1660 Super, and a 970evo (2280) 250GB drive. My new build features an Asrock X570 Riptide PG, a Ryzen 5 3600X, 32GB Corsair Vengeance RGBProSL, EVGA 1660TI, and the old drive along with storage. My boot process worked on the previous system but not here. My wife received all my original parts except a 970evo (2280) 1TB for storage and booting. She successfully uses Windows 10 and her NVMe drives. In contrast, my new system only recognizes the 1TB drive as a bootable unit. I've upgraded to a newer BIOS (version 2.0), but no bootable drives appear when I apply my storage configuration. After troubleshooting, I removed the MX500 drive, suspecting a software conflict. Now I think the issue might be related to a Windows 10 registry mismatch following the hardware changes.
H
Hoewls
09-26-2019, 10:59 AM #1

I have a peculiar problem. I assembled a new computer and combined old and new components to create a system for my wife. She is functioning perfectly, while mine isn't. My previous setup consisted of a Gigabyte B450 AorusM with a Ryzen 5 2600X, 16GB Corsair Vengeance LPX, EVGA 1660 Super, and a 970evo (2280) 250GB drive. My new build features an Asrock X570 Riptide PG, a Ryzen 5 3600X, 32GB Corsair Vengeance RGBProSL, EVGA 1660TI, and the old drive along with storage. My boot process worked on the previous system but not here. My wife received all my original parts except a 970evo (2280) 1TB for storage and booting. She successfully uses Windows 10 and her NVMe drives. In contrast, my new system only recognizes the 1TB drive as a bootable unit. I've upgraded to a newer BIOS (version 2.0), but no bootable drives appear when I apply my storage configuration. After troubleshooting, I removed the MX500 drive, suspecting a software conflict. Now I think the issue might be related to a Windows 10 registry mismatch following the hardware changes.

C
C0mboDombo
Member
62
09-26-2019, 11:47 AM
#2
Yes, the drive is included in the motherboard support list.
C
C0mboDombo
09-26-2019, 11:47 AM #2

Yes, the drive is included in the motherboard support list.

S
SonyVegas_
Member
179
09-26-2019, 06:19 PM
#3
The manual mentions M Key M.2 2280 compatibility. My 970evo 250gb uses 2280, and my wife’s device is a 970evo 1tb 2280.
S
SonyVegas_
09-26-2019, 06:19 PM #3

The manual mentions M Key M.2 2280 compatibility. My 970evo 250gb uses 2280, and my wife’s device is a 970evo 1tb 2280.

A
AlphaCat77
Junior Member
3
10-01-2019, 12:13 PM
#4
I located the reference you talked about. Samsung 970Evo (MZ-V6E250)(NVME) is included. My drive details are MZ-V7S250B/AM, and the new NVME part number is MZ-V7S1T0B/AM.
A
AlphaCat77
10-01-2019, 12:13 PM #4

I located the reference you talked about. Samsung 970Evo (MZ-V6E250)(NVME) is included. My drive details are MZ-V7S250B/AM, and the new NVME part number is MZ-V7S1T0B/AM.

J
JASurtino
Member
70
10-01-2019, 05:07 PM
#5
I located the reference you talked about. Samsung 970Evo (MZ-V6E250)(NVME) appears in the list. My drive's part/model is MZ-V7S250B/AM. The NVME part number that functions on my system is MZ-V7S1T0B/AM.
J
JASurtino
10-01-2019, 05:07 PM #5

I located the reference you talked about. Samsung 970Evo (MZ-V6E250)(NVME) appears in the list. My drive's part/model is MZ-V7S250B/AM. The NVME part number that functions on my system is MZ-V7S1T0B/AM.