Case file · SSD & flash · EDR-2025-2639
Weeks of Minute-Long Freezes, Then Boot Device Not Found.
For weeks the HP ProBook had frozen for a minute at a time
; one morning it stopped at Boot Device Not Found
. Her son's laptop was tried, then a cheap caddy, and the 850 EVO never showed up anywhere
. The campus help desk could only offer a reinstall
— no use to a part-written MA thesis and the interviews behind it.
Sound familiar? Talk to us.
0800 6890668
In plain English.
Her round of borrowed machines had already done the heavy diagnostic lifting: a drive invisible to every host carries the fault inside itself, and on an SSD that means the controller — the processor that answers the computer and keeps the ledger linking each logical address to a physical page of flash. Controllers die long before the memory they manage; looking back, those minute-long freezes were the ledger already failing. Reaching flash without its controller is nothing like platter work — nothing spins, nothing is mechanical, nothing answers on the ordinary interface.
The tools this job took.
See how your case runs →| System | The part it played | Why we rate it |
|---|---|---|
| PC-3000 SSD | Held the controller in its maker's service state while the memory read out | Built to address SSD controllers directly on platterless media |
| PC-3000 Flash | Recognised the V-NAND from its chip library and carried the raw dump | Reads the memory chips themselves, matching each one against an up-to-date identification library |
| UFS Explorer Professional Recovery | Turned the remapped image back into folders, chapters and interviews | Handles the harder filesystems well — APFS, ReFS, XFS, ZFS and Btrfs |
On the bench.
Settle whether flash had worn out or the front end had died
No host port was involved again; the drive was questioned at controller level on the bench. Its start-up was collapsing at a telling spot — the stage where an SSD loads its translation tables before presenting itself. The wear indicators, meanwhile, were modest: this flash had life left in it.
Put the controller into the state reserved for its maker
Vendor commands took the chip into technological mode, a service condition no desktop ever sees, where it surrenders the raw contents it refuses to serve normally. Everything that separates recovering this drive from binning it happened in that one manoeuvre.
First restore the order, then ask for files
A raw dump of NAND is shuffled by design — wear-levelling scatters every file — so the translation layer had to be reconstructed before anything readable existed. From that ordered image the NTFS volume came back whole, folders where she kept them, chapters carrying their names.
How it ended.
The thesis, the interview audio and the reference library returned complete on new media. The ProBook itself was blameless and runs again on a new SSD — and she has promised the finished thesis will live in three places at once.
More like this in the casebook.
Elsewhere in SSD & flash.
Sound like your drive?
Every case here points the same way: power the device down, take the free diagnosis, then make your decision.