His WD Blue NVMe SSD failed and took "several years' worth of personal photos" with it. The account is precise: it "stopped working without warning", is "no longer recognized by any system", and he has tried "different PCs, cables, and interfaces" to find it "completely unresponsive" — the failure arriving "without any prior signs of malfunction". Sudden, total unresponsiveness across every machine is the signature of a controller or firmware failure, not worn-out memory — which is the more workable of the two, because the photographs are almost certainly intact behind a component that has simply stopped answering.
| Media | WD Blue SN570-class NVMe SSD — sudden complete failure, unrecognised across multiple PCs, cables and interfaces; several years of personal photographs the target |
| Reported situation | Drive stopped working with no warning · no prior symptoms of any kind · unresponsive on multiple computers and interfaces · standard troubleshooting exhausted by the owner · irreplaceable personal photos at stake |
| Fault class | Electronic failure at NVMe controller or firmware level — the memory almost certainly intact behind a controller that has stopped enumerating, distinct from progressive wear-out |
| Equipment used | Power and thermal behaviour profiled on a current-monitored bench supply before host connection · PC-3000 SSD with NVMe support and the controller family's technological modes and loaders · safe-mode access where the controller part-responds, firmware and translator structures rebuilt · chip-off by hot-air rework where it does not, with the caveat that WD controllers encrypt internally · full image taken at first stable access, hash-verified |
Sudden versus gradual points cleanly at different parts of the drive. Worn NAND announces itself over time — slowdowns, errors, files that stop opening. A drive perfect one moment and completely gone the next has lost the component that speaks for it: the controller, or the firmware it runs. His emphasis on "no prior signs" is exactly the pattern of an electronic failure rather than memory wear, and it is the more hopeful diagnosis.
His thorough troubleshooting already proved where the fault lies. Trying multiple PCs, cables and interfaces and finding the drive unresponsive everywhere rules out the computer, the port, the cable and the connection. When nothing anywhere detects the drive, the fault is in the drive itself — and specifically in the part responsible for announcing it, since a drive that never enumerates gives software nothing to scan.
An NVMe that never enumerates is beyond every consumer method, which is why nothing he tried helped. Detection is the drive's own first act — firmware boots, the controller identifies itself, a capacity is reported. When that handshake never begins, there is no drive for any software to see, and access must be re-established beneath the standard interface, in the controller's technological modes on professional equipment.
NVMe firmware failures are recognised and, on many families, addressed. The system-area structures that map logical addresses to physical NAND corrupt in known ways, and professional SSD platforms carry loaders and technological modes to wake the controller in a service state, rebuild those structures, and bring the drive up long enough to image completely. First stable access is spent immediately on a full image, because a revived controller cannot be relied upon to hold.
One WD-specific caveat is stated honestly up front. WD NVMe controllers commonly encrypt the NAND internally as standard, keyed within the controller. That makes reviving the controller the viable route — reading the memory chips directly around a dead controller would yield ciphertext — and it is why the assessment establishes the controller's state early, before committing to an approach.
The realistic outcome is good, and the memory is the reason. If the fault is the controller or firmware, as the sudden failure strongly suggests, the NAND holding his photographs is intact and the recovery turns on restoring access to it. The honest exception — a genuine NAND failure — is far less consistent with a drive that died instantly and cleanly, and is established rather than assumed.
Power and thermal behaviour were profiled on a current-monitored bench supply before host connection, distinguishing a dead-short board from a controller that powers but never boots firmware. The drive was brought up on PC-3000 SSD using its NVMe controller family's loader, safe-mode access used where available and the translator and firmware structures rebuilt. With stable access, the drive was imaged in full and the photographs extracted from the verified image.
Controller revived in technological mode, firmware structures rebuilt, and a full image taken at first stable access with the photos extracted. The assessment is free and the quote is a single fixed figure inclusive of VAT; if the data cannot be recovered, there is nothing to pay. The decode: no warning is the signature of an electronics failure, and electronics can be worked with. Your NAND is almost certainly fine — it has simply lost the controller that introduces it, and reviving that controller is what reaches your photographs.
Stop power-cycling it and stop trying more machines — repeated attempts exercise the failed controller and on some families worsen the firmware state, and software cannot scan a drive no computer can see. Keep it cool, dry and unpowered. Note the exact make and model, because on NVMe drives the controller family determines the recovery route before the drive is even connected, and WD controllers in particular encrypt internally, which makes reviving the controller the necessary path.
Our case files are written up from genuine enquiries our lab has handled for customers across Staines, Surrey and the surrounding area, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.