Data Recovery Case File · Games & Consoles · The Update That Never Finished
Seen by the BIOS, served to no one: the sole-storage SSD that quit under a download's write-load — his "not fully dead" reading upgraded to a diagnosis, and the folders that matter brought home first
The failure picked its moment the way this genre always does: under load. "Yesterday my M.2 NVMe SSD, which I used as my only storage on my PC, had randomly seemed to die when updating a game — giving me the 'Reboot and Select Proper Boot Device' when rebooting." His observation, offered with exactly the right instinct: "The SSD is still recognized within BIOS, which I think means it's not fully dead." His request was a model of prioritised clarity: two partitions from the day he built the PC — C: and D: — and a ranked list: "I mostly need files that were on my desktop and the Pictures/My Documents folders, as well as a couple of small things from the D partition." Could it be done? Yes — and the decode below pays his hopeful reading the respect of upgrading it: BIOS-visible-but-unbootable is not merely "not fully dead." It is a specific, recognisable state with a specific, favourable meaning — and "randomly… when updating a game" was not random at all.
| Media | M.2 NVMe SSD — sole storage of a self-built PC, partitioned C:/D: · priority: Desktop, Pictures, My Documents, plus selected items from D: |
| Reported incident | Failure mid-game-update · "Reboot and Select Proper Boot Device" on restart · drive still enumerated in the BIOS · no reinstalls, repairs or recovery tools attempted |
| Fault class | Internal translation failure under sustained write-load — the controller answering to its name, unable to serve its contents |
| Equipment used | Service-level controller access · reconstruction of the drive's internal mapping · full imaging · priority-first extraction of the named folders, the remainder behind them |
The decode: why it died mid-update, and what the BIOS sighting really promises
The moment, convicted: a game update is one of the heaviest sustained write workloads a home PC ever generates — gigabytes arriving fast, the drive's controller shuffling its internal arrangements flat-out to place them. For a drive with a developing weakness, that is precisely the hour of exposure: the marginal region gets exercised, the internal ledger gets its most aggressive workout, and the flaw that idled harmlessly for months finally tears under load. "Randomly, while updating a game" is the genre's standard confession — not coincidence, but the workload finding the weakness.
His reading, upgraded: "still recognized within BIOS… not fully dead" — correct, and worth sharpening into the diagnosis it almost is. Enumeration means the controller wakes and states its identity; refusal to boot or serve means it cannot make sense of its own internal map — the translation layer recording where every piece of data physically lives — torn mid-update. Identity intact, service collapsed: a drive that knows its name but has lost its own address book. And that split is the favourable version of this failure, because a controller that answers is a controller that can be reached, worked with, and walked back through its own records — a materially better starting position than the drives elsewhere in this volume that vanished from every BIOS entirely.
The sole-storage arithmetic, noted gently: one drive carrying boot, games, and life — Desktop, Pictures, Documents — is the modern default and the modern exposure. His ranked list did the triage bench's first job for it, and named, incidentally, exactly where a PC's irreplaceable things congregate: the trio of user folders, plus a couple of small known items. Everything else on a gaming machine re-downloads; those folders do not.
The recovery: reached through the identity it still had
Because the controller still answered, the bench could take the service-level road: the drive brought up in its maintenance state, the torn internal mapping reconstructed from the memory's own records, and the contents imaged in full. Extraction then ran his list in his order — Desktop first, then Pictures and My Documents, each verified by opening; the couple of small things fetched from D: by name — with the balance of both partitions imaged out behind them for completeness. The update that broke the drive was, naturally, not among the things worth keeping.
The outcome
The folders that mattered delivered first and verified, the full estate behind them, ready for the rebuilt machine — this time with its life split across more than one basket. Free assessment, one fixed written figure including VAT, no recovery, no fee. His closing question — "would it be possible to do this?" — answered the way the archive prefers: past tense.
Sole drive died under a big download — but the BIOS still sees it
Take the BIOS sighting as the good sign it is — identity without service usually means a torn internal map, and mapped drives can be walked back through service-level recovery. Then protect that advantage: no reinstalls, no repair utilities, no boot-media experiments against the drive — every write risks the records the reconstruction needs. Rank your folders when you send it in; on a sole-storage PC the Desktop-Pictures-Documents trio is where the irreplaceable lives. And give the replacement build a second basket: heavy write-loads will come again, and drives keep choosing them.
That's the recoverable version — call Edinburgh Data Recovery on 0131 202 0491; service-level access, your folders first, one written figure, no recovery, no fee.
Request a quote online →
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.