Many of these encrypt at rest by default, often with BitLocker layered on top, and that decides whether recovery is possible before anything technical begins. It is established at the diagnostic rather than discovered after a bill.
Samsung makes the controller, the firmware and the flash, so everything must be reached through its own stack. What decides most of these jobs is not the hardware but whether encryption sits between you and the result.
Samsung SSDs have a good reputation and largely deserve it, which shapes how they arrive here. These are not drives that degrade visibly over months. They work perfectly and then, with no warning and frequently no prior symptom, they are absent from the BIOS entirely.
The failure is nearly always the controller rather than the flash. That is good news: the NAND behind it usually holds the data intact, and the work is reaching it either through Samsung's vendor mode or by reading the memory directly.
Thermal history matters more than people expect. NVMe drives in thin laptops and unventilated M.2 slots run hot for years, and heat is the most consistent factor across the Samsung failures we see.
870 EVO and 860 EVO SATA workhorses. Controller failure with the drive vanishing from the BIOS. See the dedicated 860 EVO page for that model's specific pattern.
850 PRO and 870 QVO Older SATA and QLC respectively. The QVO range shows wear sooner under sustained write load.
970 EVO Plus and 980 NVMe consumer drives. Sudden disappearance with no SMART warning at all. Thermal exposure is a recurring factor.
990 PRO Current high performance. Early production units attracted attention for health readings declining faster than expected.
PM991, PM9A1 OEM modules Fitted by Dell, HP and Lenovo rather than sold retail. Vendor-mode access is more restricted on OEM firmware.
Spinpoint HD103SJ and F3 Legacy mechanical drives, now mostly out of industrial equipment rather than desktops.
Samsung SSDs support hardware encryption and several configurations enable it without the user being aware — through BitLocker hardware offload, or through a vendor utility switched on during setup. Where that has happened, the NAND holds ciphertext and reading it achieves nothing without the key.
So the first question on a Samsung job is not what failed but whether encryption was ever enabled. Check BitLocker status and Samsung Magician settings before assuming a recovery is straightforward, because the answer changes what is possible rather than what it costs.
Controller failure, most likely. The flash behind it is usually intact and reachable through vendor mode or directly. Do not keep power-cycling it.
Yes, as with any Samsung NVMe. Tell us at the diagnostic whether BitLocker or Samsung Magician encryption was ever enabled, because that decides what is achievable.
Controller lock-up. The drive has lost the tables describing its own geometry. Firmware class rather than physical damage, and often recoverable.
It is the most consistent factor we see across Samsung NVMe failures. It does not change the recovery method, but it explains why drives fail with no warning.
From £300 +VAT, fixed in writing after the free diagnostic. Direct NAND reads are the same class as vendor-mode work.