Nothing sold to consumers is faster than an NVMe module, and nothing stops more abruptly. No warning noise. No slow decline. A machine that worked, and then a boot error standing where the drive used to be. Every maker's M.2 sticks and PCIe cards land here, pulled out of home machines, gaming builds, and the design and engineering offices round the city.
Every nvme job is diagnosed free. The fixed figure reaches you in writing first, before any tools come out.
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.
First job on any nvme is matching the symptom to the fault. Twenty-odd years in, these twenty-five cover nearly every one that reaches this bench.
Overnight, a controller or firmware fault cleared the bus. Your data sits complete behind that silence, waiting on something capable of managing it again. Commonest way these modules go.
Dead controller, failed power stage, damaged boot code. Of the four possibilities, dead memory is far and away the least likely. Odds favour recovery. The module has no means of telling you that.
When the translator collapses, a module answers with a size that has never appeared on anybody's price list. Repair in service mode corrects it, along a well signposted road.
A bare module throttles, disappears under load, and eventually scrambles its own tables across a run of hot spells. Image it cold and a surprising number sort themselves out.
Windows update or vendor tool, the result is identical: a module unable to state its own name. Reflashed here where that can be done, worked around completely where it cannot.
Flash keeps no diary and issues no notice. Faultless service until the second it collapses is the standard biography, and that is why backups count for more here than anywhere else.
Thin boards come off worst against upgrade levers and stiff envelopes. Small breaks near the edge are track repair under the scope. Everything beyond that is chip-off.
Surge damage inside the power circuitry gets rebuilt at component level first, and only then does anybody attempt a read. Sequence is the whole job. Reverse it and the module is wasted.
Erasure of freed blocks runs in background from the instant of deletion, pausing only when power goes. Pull the plug and that clock halts precisely where it stands. Best thing you can do for it.
WD's flagship shipped carrying firmware that stalled, then vanished, under certain loads, until a patch arrived. Unpatched examples keep our booking sheet interesting most months of the year.
That 980 PRO and 990 PRO generation consumed NAND life fast enough to require a corrective update. Examples that never got it still arrive with most of the endurance already gone.
Whichever controller and flash were going that quarter is what a Kingston NV2 shipped with, so two modules under identical labels can demand entirely different methods. The contents pick the route.
Handhelds such as the Steam Deck bake small modules inside crowded shells where heat has nowhere to go. Tiny format, and a wholly conventional recovery on the bench.
Modules without DRAM borrow host memory to keep their maps in. A single bad interaction following sleep, or a crash, corrupts what was borrowed. Service mode straightens that ledger.
Fast modules run hot when bare and age quickly for it. Dropouts arrive first, disappearance follows later, and the window for imaging is open during the dropouts.
A budget drive hammers its pseudo-SLC region until that gives out, then either stalls or bricks completely. The slower flash behind it normally answers perfectly well.
Heatsink screws done up too far, thermal pads mangled, board flexed, and the joints beneath the controller crack. Reworked under the scope, then imaged.
Following a BIOS update, or on a riser that is marginal, module and slot stop agreeing terms and the drive appears to have gone. Proven out on lab sockets known to be good, rather than by swapping cables.
One failing die shrinks the drive, scatters errors across its stripes, or locks the whole thing read-only. Imaging routes round the die that has gone, and the neighbouring dies carry your data out.
Lose power during garbage collection and the map is left half rewritten, so the module mounts, loops and sulks by turns. Service-mode reconstruction restores order to the tables.
One command reformats an NVMe drive to a different sector layout, and doing so discards the mapping wholesale. Quick, quiet, and afterwards it presents as a blank drive. Recovery starts at the raw memory and rebuilds the arrangement from there.
Irreversibility was the design goal for both commands, and both achieve it. Where a sanitize ran to completion, nothing remains for anyone to find. Where it was interrupted, a great deal sometimes remains. Guessing helps nobody, so the free diagnostic establishes which of the two happened.
Documented dropouts follow aggressive low-power states on particular module and platform combinations, Linux especially, where the drive falls asleep and never wakes up. Looks terminal. Frequently the module is sound, and the tables want rebuilding after the crash that state caused.
A module filled to the final block cannot perform housekeeping, because shifting data about requires somewhere to shift it to. Write performance collapses, errors gather, and certain drives lock themselves read-only instead of continuing. Awkward to live with. Helpful to image.
Depending on the machine, an M.2 socket carries different signals, so a module can fit mechanically without being wired to anything it is able to talk to. Nothing shows up, nothing is broken, and hours disappear chasing a fault that was never there. Rule that out before writing off the drive.
There is nothing mechanical between an M.2 module and the processor. It talks over PCIe, which is what makes it fast and also what makes the failures so abrupt: nothing limps noisily first. Stacked NAND is managed by dense firmware, and as soon as the controller or that firmware loses its footing the module goes quiet while your files sit behind the silence in perfect order. Two routes exist. Service mode, when the controller will still hold a conversation. Or the chips themselves, with the translation layer rebuilt from scratch, where it cannot. Neither improves with another dozen restarts at the kitchen table, however natural that impulse is.
2280, 2242 and 2230 lengths. PCIe add-in cards. Gen3 up to Gen5. Samsung, WD, Crucial and Kingston. Kioxia, SK hynix, Sabrent, Solidigm. All of it is workable so long as the module unclips and can go in an envelope. Soldered NVMe is the standing exception and gets refused. Heat earns a note of its own. Driven hard with no heatsink at all, a bare stick throttles, then leaves the bus entirely. Enough of those episodes and its mapping tables corrupt. Small form factor builds and slim laptops generate a steady supply. Whatever caused yours, the free assessment names it and puts a figure to it before you have spent anything.
Controller work, firmware work and chip surgery at PCIe speeds. The bench is specified so that no job ever waits on equipment:
Silent modules come up in the manufacturer's service mode. Firmware gets corrected, the translator rebuilt, and an image taken before anybody gambles with the memory.
A PCIe module that stalls, or wanders off, gets captured behind timeouts enforced in hardware, using retry behaviour that no downloadable tool can reach.
Short 2230 stubs up to full-length 2280s, add-in cards, enterprise U.2, every one of them connected natively, with forced cooling for anything that faints once warm.
Beyond the reach of service mode, packages come off the board and get read one at a time. A longer road ending at an identical destination.
Interleave, XOR and ECC worked out from the dumps until a mapping exists once more, with your volume standing above it.
Burnt power stages rebuilt one component at a time, cracked boards reworked under the scope, torn tracks repaired. All of that precedes any read.
Every reputation on this page was earned the hard way. SN850X firmware wobbled under sustained load in its early days, until WD published a patch. Samsung modules of the 980 PRO and 990 PRO generation that never received their update still turn up with the endurance largely spent. An NV2 is a lucky dip, and its contents choose our method for us. Gen4 modules fitted somewhere a heatsink was judged optional cook themselves slowly, then vanish. Every size from 2230 to 2280, plus add-in cards, U.2, and everything from Gen3 to Gen5: workable, on a single condition. The module has to unplug so it can travel by post. Soldered-down NVMe is one refusal here. Phones and tablets are the other.
Nearly everything on this bench came by tracked, insured post. It is the safest way to shift a failing drive, and a parcel handed in at a North-East post office is usually here the next working day.
Still bolted into a laptop, desktop, MacBook, iMac, server or CCTV / DVR box? Get the hard drive or SSD out first. The bare drive travels on its own. Stripping machines down is not a job this lab takes on. Flash soldered to a motherboard, as on Apple Silicon Macs and a couple of very thin laptops, is our one flat no: if it will not unbolt, it cannot be worked on.
↓ Print the shipping & booking-in form (PDF)
Address it for the attention of Edinburgh Data Recovery. From Aberdeen that is roughly 130 miles and two and a half hours down the A90, or next working day by tracked post if you would rather not make the run. You get a call the moment it is booked onto the bench.
Not sure what belongs in the box? Ring 0800 689 0668 before you tape it shut, or work through the free online diagnostic.
Free diagnosis, one number written down, no fix no fee on the bulk of jobs. Start online or phone it in.