Unsolved
1 Rookie
•
7 Posts
0
124
February 11th, 2025 22:05
SSD Compatibility (nvme 1.4 & Precision 7510)
Hello.
I have a Precision 7510 laptop running on a Samsung MZ-V8P2T0B SSD (980 Pro 2TB). It's a PCIe-4 drive and behaves great on a PCIe-3 bus.
I got me (a headache of) a Kingston Fury Renegade SFYRD/4000G drive for an upgrade do discover it doesn't play smooth with my laptop.
I updated my BIOS/UEFI ROM to the latest version, but that's about all I did. Having cloned the drive contents from Samsung onto this Kingston I expected a smooth reboot with a lot more space to spare yet keeping all the system state. How foolish of me. The new drive shows up in the UEFI Setup only if the original drive is attached via USB-C port through an SSK External SSD enclosure. Whatever its presence does, it provokes the system to post the new drive that's in the m.2 slot. Remove that and the result is likely to be negative. Anyhow, a bootable windows PE image I run from a Ventoy USB stick doesn't boot when this drive is the one in the m.2 The dots wheel spins a couple of times under the Windows 10 logo (the installed OS is also Win 10, latest updates) and the machine resets. Please note: it's the WinPE bootable media we're talking about, it shouldn't care much about the drivers -- either a device is recognized or it isn't, but a reset? If I run the Windows 10 22H2 installation iso from Ventoy, the same thing happens. And I know that image to be good on this machine: I've used it for installation and disaster recovery.
The only striking difference I see between the Samsung SSD and the Kingston is that the former is nvme 1.3
Perhaps I can force the Kingston to run in a fallback mode? It seems to be compatible on paper, but in reality it's been a 200 dollars spent for unknown result and still an unsolved problem of lacking nvme speed space.
If someone has walked this path, please advise.
Thank you.
ejn63
10 Elder
•
28.6K Posts
0
February 12th, 2025 01:04
Unless the drive isn't recognized, it's unlikely the source of the problem. What happens if you prepare install media with the MS Media Creation tool -- will that install correctly?
At minimum, if you try re-cloning, turn OFF the secure boot the first time you try booting the cloned drive. What tool are you using to clone the drive?
parahumanoid
1 Rookie
•
7 Posts
0
February 13th, 2025 11:14
@ejn63 are you running a combination of this laptop and the Phison PS5018-E18 based SSD?
If you read my message carefully, you'll see I mention booting from a Windows 10 22H2 image fails in exactly the same manner as booting the WinPE rescue distribution. The 22H2 image is official. It's been used to install and recover a number of times (having all realatives come to you for PC help give you the chance to make sure how your tools behave on different hardware). So the cloned system is off the table of issues for now. If it can only consistently show in BIOS and not cause an installation distro to reset before getting to "choose drive to install windows onto" dialog, we'd already be speaking of progress. Secure boot is OFF, I should have written that. This message will be updated in a couple of hours when I run a boot step by step. I'll also be visiting a pc shop in the meantime where I might get a chance to run some comparisons if the guys aren't too busy.
(edited)
parahumanoid
1 Rookie
•
7 Posts
0
February 15th, 2025 12:50
As another thread shows, Samsung PRO is one of the few lines of SSD products that have shown to behave well with the PCIe 3.0 bus (that is, having true and solid backward compatibility), so I'll be putting this disaster of a purchase out for sale and getting the Samsung 990 PRO instead. Apparently, it's as simple as backward compatibility is not really being a feature but a mere declaration on the part of Kingston.
Topic closed.