NVMe modules are the quickest consumer storage ever sold and much the most abrupt about stopping. There is no warning noise and no gradual slowing down; a working machine one minute, and the next a boot error standing where the drive ought to be. M.2 sticks and PCIe cards from every maker come in from home machines, gaming builds and the research and engineering offices along the A11.
Every nvme job is diagnosed free. The quote follows in writing, fixed, before a screwdriver is picked up.
No fix, no fee all jobs except electronic and mechanical failures, chip level work, DVR and Forensic jobs. Full pricing is on the data recovery cost page.
The first job on any nvme is matching the symptom to the fault — and after twenty-odd years, these thirty account for very nearly everything that comes through the door.
Controller or firmware trouble cleared the bus overnight. Behind that silence the data is complete and waiting on something to manage it properly again.
Dead controller, failed power stage or damaged boot code, with dead memory being by far the least likely of the four. The odds favour recovery; the module simply has no way of saying so.
Translator collapse makes a module answer with a figure that appears on no price list anywhere. Service-mode repair, and it is well signposted.
The system module stopped mid-sentence. Taken out of the machine, it gives up its files on the bench directly and without much argument.
Bare modules throttle, then disappear under load, then scramble their tables over a run of hot spells. They get imaged cold, which alone solves a surprising number.
Windows update or vendor tool, the outcome is the same: a module that can no longer state its own name. Reflashed here, or else read around entirely.
Flash keeps no diary and gives no notice. Perfect service right up to the moment of collapse is the standard biography, which is why backups matter more here than anywhere.
Thin boards lose to upgrade levers and stiff envelopes. Track repair covers small breaks and chip-off covers everything else.
Surge damage to the power circuitry is rebuilt at board level before anybody attempts a read at all. The sequence is the whole job.
Background erasure of freed blocks begins at deletion and pauses only when the power is off. Pull the plug and the clock stops where it is.
WD's flagship shipped with firmware that stalled and vanished under particular loads until it was patched. The unpatched population keeps the booking sheet interesting.
The 980 and 990 generation spent NAND life at a rate that needed correcting by update. Never-updated examples still arrive with their endurance largely gone.
Kingston's NV2 ships with whichever controller and flash were available that quarter, and two drives with the same label can need entirely different methods. What is actually inside decides the route.
Steam Deck and similar handhelds bake their little modules inside crowded enclosures with nowhere for the heat to go. Tiny format, completely conventional recovery.
DRAM-less modules borrow host memory to hold their maps, and a single bad interaction corrupts what was borrowed. Service mode puts that ledger straight.
Fast modules run hot bare and age quickly for it. The dropouts come first and the disappearance comes later, and the imaging window is during the dropouts.
Sustained shader compilation and cache thrashing put a year on a gaming module every season. The stutters are the notice period and the absence is the deadline.
Several budget designs corrupt their mapping after sleep or a crash because of how they use borrowed host memory. It is a documented failure class with a documented way out.
Budget drives hammer their pseudo-SLC region until it fails, then stall or brick outright. The slower flash behind it usually still answers perfectly well.
Over-tightened heatsink screws and mangled thermal pads flex the board and crack joints. Reworked under the scope, then imaged.
After a BIOS update, or on a marginal riser, the module and the slot stop agreeing terms and it appears to have vanished. Proven out on known-good lab sockets rather than by swapping cables.
One die failing shrinks the drive, throws errors across its stripes, or locks it read-only. Imaging works around whichever die has gone and its neighbours carry the data out.
Power lost during housekeeping leaves the map half rewritten, so the drive mounts, loops and sulks in turn. Service-mode reconstruction restores order.
Counterfeit modules get recovered for what they actually are rather than what the label claims, and the label fools nobody at this end.
Cracked socket latches and lost PCIe lanes leave a module limping along at a fraction of its width and then absent altogether. Imaged on an intact lab socket.
NVMe drives can be reformatted to a different sector layout with a single command, and doing so discards the mapping wholesale. It is quick, it is quiet, and it looks like a blank drive afterwards. Recovery works from the raw memory and rebuilds the arrangement.
Both commands are designed to be irreversible and both are genuinely good at it. A sanitize that completed leaves nothing for anybody to find. One that was interrupted sometimes leaves a great deal, and the free diagnostic establishes which happened rather than guessing.
Aggressive low-power states have caused documented dropouts on certain module and platform combinations, particularly on Linux, where the drive falls asleep and does not come back. It looks terminal. Frequently the module is fine and the tables need rebuilding after the crash it caused.
A drive filled to the last block cannot perform its own housekeeping, because moving data around needs somewhere to move it to. Write performance collapses, errors accumulate, and some drives lock read-only rather than continue. That read-only state is inconvenient to live with and helpful to image.
M.2 sockets carry different signals depending on the machine, and a stick that fits mechanically may not be connected to anything it can talk to. Nothing appears, nothing is broken, and hours get spent on a fault that does not exist. Worth ruling out before the drive is written off.
An M.2 module speaks to the processor over PCIe with nothing mechanical in between, which is what makes it quick and also what makes its failures so sudden — there is no noisy limping stage to warn anybody. Dense firmware manages stacked NAND, and when either the controller or that code loses its footing the module simply stops replying, while your files sit in the memory behind that silence entirely intact. The way in runs through the maker's service mode where the controller can still be persuaded to talk, and directly to the chips with a rebuilt translation layer where it cannot. Neither route improves after a further dozen restarts at the kitchen table, understandable though the impulse is.
Modules in 2280, 2242 and 2230 lengths plus PCIe add-in cards, anywhere from Gen3 to Gen5, from Samsung, WD, Crucial, Kingston, SK hynix, Kioxia, Sabrent and Solidigm, are all workable so long as the module unplugs and can be posted. Soldered NVMe remains the standing exception and gets declined. Heat deserves a mention of its own. Worked hard with no heatsink, a bare stick throttles, then falls off the bus entirely, and across repeated episodes it can scramble its own mapping tables; small form factor builds and slim laptops produce a run of exactly that every summer. Whatever started yours, the free assessment names it and attaches a figure before anything is spent.
Controller, firmware and chip surgery at PCIe speeds, with the bench specified so the work never waits on equipment:
Silent modules are raised in the maker's own service mode, the firmware corrected and the translator rebuilt, then imaged without the memory ever being gambled with.
PCIe modules that stall or wander get captured under hardware-enforced timeouts, using retry behaviour that no software tool has access to.
From 2230 stubs to full-length 2280s, add-in cards to enterprise U.2, all connected natively — with active cooling for modules that faint when they get warm.
Where service mode cannot reach, the the packages are lifted clear and read one by one. A longer road to an identical destination.
Interleave, XOR and ECC are solved out of the dumps until the mapping stands up again, and the volume then stands on it.
Burnt power stages rebuilt component by component, and cracked boards reworked under the scope before imaging is attempted at all.
Reputations on this page were earned the hard way. Early SN850X firmware wobbled under sustained load until WD patched it; 980-generation Samsungs that were never updated still arrive with their endurance largely spent; the NV2 is a lucky dip whose contents pick the method for us; and Gen4 modules fitted where a heatsink was thought optional cook themselves gradually. From 2230 up to 2280, add-in cards, U.2, and Gen3 through to Gen5: all workable, on the single condition that the module unplugs so it can be posted. Soldered-down NVMe is the one refusal, and phones and tablets are the other.
Most of what reaches this bench arrived by tracked, insured post. It is the steadiest way to move a poorly drive, and a parcel posted in Norfolk is usually on the bench the next working day.
Is the drive still bolted inside a laptop, desktop, MacBook, iMac, server or CCTV / DVR recorder? The hard drive or SSD needs to come out first, and only the bare drive travels — taking drives out of machines is not something we do here. Storage soldered to a motherboard (Apple Silicon Macs, one or two very thin laptops) is the single thing beyond us: if it will not come out, it cannot come in.
↓ Print the shipping & booking-in form (PDF)
Mark the parcel for the attention of Cambridge Data Recovery. From Norwich it is about an hour and twenty down the A11, then two minutes off the A14 at Junction 32 — or next working day by tracked post. You hear from us as soon as it is booked onto the bench.
Unsure what to put in the box? Ring 0800 689 0668 before you seal it, or run the free online diagnostic.
Diagnosis free, one figure written down, most work under no fix no fee. Start online, or ring us.