Data Recovery Case File · Laptops & SSDs · The Rescue That Wrote

"The SSD appears intact — it's mainly a case of copying the files": a hopeful diagnosis corrected kindly, and a cascade unwound in the right order

His account was chronological and complete, which made the cascade legible. For weeks the laptop had frozen at the logon stage — Windows logo, password screen, or just after — where a few restarts used to shake it loose, until they didn't. He then ran the manufacturer's support tool, which walked him through decrypting BitLocker with his key and "repairing" the system to an image it had taken a month earlier. Result: the machine now never reaches logon at all, blue-screening with error 0xc000021a. The tool could still see his files — around 150GB — but copying them out "runs up to 4+ hours, failing at some point." His own summary was the hopeful one this page must gently correct: "The SSD appears intact, so this is mainly a case of copying across the files." The hangs were the SSD. They always were.

Reading the cascade in order — disease, treatment, aftermath

The disease was announced weeks before any tool ran: logon is when Windows reads hardest — profile, services, caches, all at once — and a machine that freezes precisely there, intermittently, then reliably, is describing a drive whose reads are stalling under load. That was the moment for copying files out, and hindsight's only fair note is that the symptom never says its own name. The treatment then did two big things to a failing patient. Decrypting BitLocker was actually the accidentally-wise half — done with his own key, it removed a whole layer of later complexity, and it worked because he had the key to hand. The restore-to-image half was the wound: rolling the system back to a month-old snapshot is a massive write session — gigabytes of system state pressed onto exactly the degrading medium, carrying two costs at once: heavy writes on failing hardware, and the calendar question of what a month-old system image overwrites. (The honest version of that question, resolved at assessment: such restores target the system's territory — Windows, programs, configuration — and his user files largely sat outside the blast radius; the month's true casualties were bounded, and itemisable.) The aftermath reads cleanly from there: 0xc000021a is Windows reporting a critical process dying at boot — a system left internally inconsistent, half restored snapshot, half stalling reads — and the tool's 4+ hour failing copies were the diagnosis he'd been offered all along: software politely re-asking a drive that cannot reliably answer. "Appears intact" is what a failing SSD looks like from above. The hangs are what it is.

The recovery — the copy, done the way copies work on failing drives

His framing — "mainly a case of copying across the files" — was, in the end, honoured almost verbatim; only the method changed. On the PC-3000 in NVMe technological mode, the SSD was imaged with the stall management its condition demanded: cooperative regions banked at pace, the stalling territory negotiated in bounded, managed passes rather than four-hour hopeful hangs — the drive never asked to succeed twice at anything. Coverage closed high; the volume (helpfully already decrypted, his one lucky intervention) mounted from the image, and the ~150GB the support tool could see but never deliver came off verified: profile, documents, the working life of the machine — plus the honest month-audit, the short itemised list of what the restore's footprint had genuinely taken, closed out in the report instead of left as a nagging unknown. Delivered on new media; the SSD retired with its cascade documented.

Outcome

Full practical recovery of everything the freezing, the restore and the blue screen had between them held hostage — and the cascade's lesson, offered without blame because every step of it was reasonable-looking at the time. When a machine starts freezing at logon, the first tool to run is a copy of your files — not a repair. Support utilities assume healthy hardware; their restores, resets and repairs are all writes, and writes are treatment administered to the wrong patient when the drive itself is the disease. The tell to remember: repairs that make things differently worse — freeze becomes blue screen, slow becomes hang — are reporting that they operated on a moving table. And his one keeper habit, worth the whole page: he knew where his BitLocker key was. On the day everything else went sideways, that alone kept every door open.

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.