Data Recovery Case File · NVMe SSD · Creative Work

The drive the PC refused to boot with: a budget NVMe's half-life, and the modding archive inside it

The stakes in this enquiry weren't invoices or photographs but something recovery labs see more of every year: creative work with no employer and no duplicate. Years of a modder's projects for a long-running shooter — custom maps, scripts, source files, assets — lived on a 2TB budget NVMe SSD with no backup. The drive's decline was distinctive: installed in the motherboard, it was detected by the BIOS but the PC would no longer boot with it present; moved to a USB enclosure, it flickered — Device Manager always saw it, a drive letter sometimes appeared with the correct capacity, and opening anything went nowhere.

Reading the two symptoms together

His two test environments told one story from two angles. A PC that hangs at boot only when a particular drive is installed is a PC waiting on that drive: start-up pauses while every disk is asked to report ready, and a drive stalling on its own initialisation holds the whole ceremony hostage — the same held-hostage pattern this archive documents on failing spinning drives, translated into silicon. The enclosure's flicker was the finer-grained view: the controller booting far enough to state its name and size, sometimes far enough to accept a drive letter, never far enough to serve data — a firmware limping through its own start-up and collapsing at the first real question. On drives from the value end of the market this temperament is a known trade-off: capable controllers running lean firmware with slim margins, superb value while healthy, and brittle in exactly this way when their internal management structures degrade. None of which touches the flash itself — the maps and scripts sat intact behind a front desk that kept fainting.

The recovery

The drive went onto the PC-3000 in NVMe technological mode, where the conversation happens below the level at which the firmware was failing. Its unstable management structures — the translation records the controller was choking on at every boot — were stabilised and reconstructed from the metadata across the memory itself, and with the drive held in a state where it could no longer stall anyone, Data Extractor imaged the full 2TB in one disciplined pass. The NTFS volume mounted from the image complete: project folders spanning years, extracted with structure intact, spot-verified the only way that means anything for a modder — by confirming the projects open — and delivered on new media.

Outcome

Full recovery of a body of work that existed nowhere else on Earth. The closing word goes to every creative community running on donated evenings: mod projects, indie games, music, art assets — this work is real work, it's usually uniquely irreplaceable, and it deserves the boring protections commercial work gets by default. Source files belong in a repository or synced folder as they're made; a budget drive is a fine workhorse and a terrible archive; and "no backup" plus "years of projects" is a sentence this lab would rather read in fewer enquiries. His had a good ending. The habit is cheaper than the recovery.

Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.