Data Recovery Case File · SSD · Controller Failure

The SSD that took the whole computer hostage: burst-imaging a failing Samsung 850 EVO

Some failed drives merely absent themselves. This one held the room. After failing during a Windows update, the customer's 500GB 850 EVO — his C: drive — didn't just stop booting: with it connected, the machine would hang at the loading screen with keyboard and mouse dead, as if the SSD's failure were contagious. In a sense, it was.

The enquiry

“My PC was undergoing an update when my C: drive — a Samsung 850 EVO 500GB — supposedly failed, and Windows rebooted to scan and repair it. After that it loaded for a very long time, then a black screen. The machine simply won't boot at all, and even the keyboard and mouse stop responding once it reaches the Windows loading icon. Diskpart suggests it's corrupted.”

How one drive freezes a whole machine

The frozen keyboard was the diagnosis wearing a disguise. When a storage device accepts a command and then never answers, the system's storage layer waits — dutifully, indefinitely — and everything queued behind that wait piles up until the machine is a statue with its fans running. This SSD had developed exactly that habit: it would wake, respond normally for a stretch, then hit whatever internal trouble the update-era failure had left behind and simply stop mid-sentence, taking the bus with it. Windows' automatic scan-and-repair — hours of intensive reading and writing against a drive in precisely this condition — had been the worst possible medicine at the worst time, and the customer's decision to stop rebooting and ask for help was the first thing that went right.

Recovery in bursts

A drive that works in episodes gets imaged in episodes. On the bench, its behaviour was first characterised: how long after power-on it would answer, how much sequential reading it would tolerate before wedging, and — the crucial part — that a full power cycle, not a polite reset, was the only thing that brought it back. That profile became the plan. Behind the USB Stabilizer's hardware power control, with Data Extractor keeping the ledger, the drive was run through the loop a failing SSD demands: power on, wait out its waking ritual, read hard from exactly where the last burst ended, and the instant it went silent — cut power, breathe, begin again. No operating system in the loop to hang, no scan-and-repair "helping", just hundreds of disciplined cycles, each banking its stretch of the drive, the map of recovered territory growing burst by burst until the image was whole enough to matter and then, patiently, whole.

From the completed image, the aftermath of the interrupted update and the repair attempt was untangled at filesystem level — the volume's structures reconciled from their redundant copies — and the customer's user profile, documents and working files extracted and verified. The SSD itself was retired with a plain verdict: a drive that has learned to hang buses does not unlearn it, and its remaining career is as a paperweight with a story.

Outcome

A near-complete recovery of the volume, delivered on new media, from a drive most setups can't even keep a computer conscious next to. The general lesson outranks the specific one: when a failing drive is connected, everything slows or stalls — long boots, frozen file windows, a machine that hangs with one particular disk attached. That pattern is a drive talking. Repeated reboots and repair scans answer it with exactly the punishment it can't take; a power-off and a phone call answer it with a future.

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.