Data Recovery Case File · Memory Cards & Camera Media · Eight Kilobytes a Second

Flat-out and delivering nothing: the most diagnostic pair of numbers an enquirer ever sent — a card saturated by its own retries, and the failure month's photos recovered from its most tired territory

His enquiry did something rare in these files: it skipped adjectives and submitted instrumentation. A 64GB microSD card, "seemingly corrupted" — with the alibi entered before anyone asked: "it's not had any water damage." The history: "it started malfunctioning in my phone in July 2020" — and, in the way this genre loves to twist the knife, "I now have some photos I need from July 2020." The behaviour: "I can get it to appear in Disk Management and File Explorer briefly." And then the measurements that give this case its title: "Task Manager shows it at 100% disk usage with read speeds up to 8kbps — mostly around 0." How much to recover the photos he needs? Answered structurally below — but first the decode his numbers deserve, because that pairing — fully busy, delivering nothing — is one of the most precise portraits of a dying flash device an owner has ever sent in.

The decode: what "100% busy at zero throughput" measures, and why phone cards die from the inside

The pairing, translated: "disk usage" measures how occupied a device is; "read speed" measures what it delivers. A healthy card idles at low usage and answers at tens of megabytes a second. His card showed the inversion: working at absolute capacity to deliver almost nothing — the signature of a controller fighting its own memory for every sector: read, fail, retry, error-correct, retry again, occasionally win a kilobyte, mostly lose. The card wasn't idle or absent; it was drowning in effort. His "appears briefly" completes the picture — the mount succeeds on the card's few easy reads before the retry storm swamps everything behind it. Feelings would have said "slow and flaky"; his numbers said exhausted memory behind a still-fighting controller, which is a diagnosis — and, helpfully, the recoverable kind.

Why phone-resident cards wear out: a card living in a phone never rests — beneath the photographs sit years of app caches, thumbnails, logs and background churn, a write workload that consumer flash meets by spending its finite endurance. Cells degrade; reads that once succeeded first time start needing correction, then retries, then heroics. July 2020 wasn't an accident's date; it was the month the margins ran out. And the twist in his request — needing photos from the failure month — carries an honest note the ledger below resolves: the newest photographs live in the card's most recently written, most marginal territory, which is exactly where the patient harvest earns its keep.

The alibi, saluted: "no water damage" — negative evidence, volunteered. It ruled a whole fault family out before assessment and cost him one sentence. Reporting what didn't happen is underrated diagnostics, and this page notes it so the habit spreads.

The recovery: outlasting the retries, July first

The card went to managed card-level imaging — timeouts extended far beyond any operating system's patience, reads verified rather than trusted, the surface mapped into cooperative and exhausted regions and harvested accordingly, with the chip-level route standing ready had the controller given up entirely. It didn't: over long, patient passes, the drowning card yielded its contents at its own pace. His priority ran first — the July 2020 photographs, pulled from the marginal recent territory with the heaviest retry budget, then opened, every needed one, to verify — before the rest of the card's years followed behind them.

On the bench

An eight-kilobyte-per-second card is exactly the patient the DeepSpar USB Stabilizer 10Gb exists for: its inline hardware sat between card and host, terminating each struggling read at a tight timeout, issuing resets the instant the controller wedged, and re-powering the card automatically when resets stopped answering — the churn her telemetry had measured, managed rather than endured. Sector-level imaging ground through to completion at whatever pace each region allowed, with PC-3000 Flash standing by for chip-level escalation the card never quite required. The July onset stayed in the report as the wear chronology it was.

The outcome

The photographs he named delivered verified — the failure month recovered from the failure's own ground — with the card's wider archive behind them on new media. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The card itself was retired with its telemetry quoted in the report as the epitaph it earned: one hundred percent effort, eight kilobytes a second — and, at the end, everything that mattered, delivered anyway.

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.