Data Recovery Case File · Cameras, Drones & Cards · Two Cards, One Suspect
Can corruption spread between cards? The contagion hypothesis examined properly — the shared reader named as the real vector, both cards recovered on their own merits, and "what if you can't?" answered with the only honest number: nothing
Her enquiry did two rare things at once: it proposed a theory, and it asked the pricing question people swallow. The situation: two SD cards, both misbehaving — one "mostly in a camera, seems to have deleted or corrupted some images," the other "in a laptop, with a similar situation — images, files and folders." Her hypothesis: "I have put the card from the camera into the laptop at a couple of points, so the problems may be related." And her question: a quote for recovering as many files as possible — "and also how much you would charge if they weren't recoverable?" This page honours both halves. The theory gets the examination it deserves: corruption doesn't leap card-to-card like an infection — but her instinct that the cases are connected is very possibly right anyway, because the thing the two cards genuinely shared is the laptop and its reader, and a faulty reader or port is the one household object that corrupts every card it touches. And the pricing question gets the shortest answer in this archive: nothing —; on cards and sticks where content has been deleted or overwritten, the figure is payable upfront — stated up front because she was brave enough to ask.
| Media | Two SD cards — one camera-resident, one laptop-resident — both exhibiting deleted/corrupted images and damaged files and folders; cards have shared the laptop's reader |
| Reported situation | Parallel corruption across two cards · owner's cross-contamination hypothesis stated · quote requested for maximum recovery, and explicitly for the cost of failure |
| Fault class | Dual filesystem corruption with a plausible common cause — shared reader/port under suspicion; per-card imaging and recovery; environment guidance to stop the pattern |
| Equipment used | Both cards imaged write-blocked (DeepSpar USB Stabilizer 10Gb) — the suspect reader never used again · per-card filesystem reconstruction and signature carving (OSForensics), validation by rendering · recovered sets reconciled and verified · reader-elimination guidance in writing |
The decode: how corruption travels, and what "not recoverable" costs
The contagion hypothesis, examined: filesystem corruption is damage to a card's own filing structures — torn bookkeeping, not an agent — so one corrupt card cannot infect another by proximity or even by sharing a slot: there is nothing to transmit. But her theory survives in a stronger form, because two cards failing the same way in one household is a pattern, and patterns have causes. Three candidates, in the order a bench weighs them: the shared reader or port — a failing card reader, a marginal laptop slot, or an unstable USB path corrupts writes on every card it handles, one by one, and is far and away the most common explanation for serial card trouble in a single home; the removal habit — cards pulled mid-write (from camera or laptop) collect the same torn-structure damage independently; and coincidence — two aging cards simply reaching their own troubles in the same season. Her observation that the cards shared the laptop doesn't convict the cards of infecting each other; it indicts the laptop's card path as the common suspect — which is exactly why, from the moment of this enquiry, that reader's card-handling career is over: neither card, nor any future card, goes back into it until it's been eliminated. The pattern stops with the diagnosis, not after the next casualty.
The question nobody asks, answered plainly: "how much would you charge if they weren't recoverable?" deserves to be answered in the first sentence, not the small print: nothing. The structure this archive states on every page exists precisely for her question — the assessment is free, the figure is fixed in writing before any work, and if the recovery fails, no fee is owed. That's not a promotional flourish; it's the risk allocation an honest trade runs on: the lab bets its work on its own judgement, and the customer's downside is a postage cost and an answer. Asking the failure question out loud, as she did, is the mark of a careful buyer — and any firm that answers it vaguely has answered it.
Two cards, two recoveries, one reconciliation: operationally the cards are separate patients — each imaged once, write-blocked, on trusted equipment (never the suspect reader); each filesystem reconstructed and its images carved and validated on the copy; each with its own written figure and its own no-recovery-no-fee standing independently. And because photographs migrate between cards in a two-card household, the recovered sets are reconciled at the end — duplicates resolved, the union delivered as one collection with nothing counted twice and nothing missed between them.
On the bench
Both cards were imaged write-blocked behind the DeepSpar USB Stabilizer 10Gb — on bench equipment, the suspected reader's involvement ended for good — and the work ran per patient on the copies: filing structures reconstructed where their remains allowed, OSForensics carving the images by signature beneath, every recovered photograph validated by rendering. The two sets were reconciled — the camera card's shoot and the laptop card's archive compared, duplicates resolved — and the union verified and delivered as one collection. Alongside it went the written elimination guidance her theory had earned: the reader test to run, the habit checks, and the instruction that stops serial card loss in any household — when two cards fail in one home, retire the reader first and ask questions second.
The outcome
Both cards recovered on their own merits, the collections reconciled and delivered verified — and the shared reader retired pending elimination, so the pattern ends here. Free assessment, one fixed written figure per card including VAT, and the answer to her bravest question honoured in full: no recovery, no fee — nothing owed on failure, ever. The decode, posted for every household with more than one misbehaving card: corruption doesn't spread card-to-card — there's nothing to catch — but serial failures share causes, and the commonest is the reader or port every card passes through; stop using the shared path the moment a second card falters; and always ask the failure-cost question out loud — the honest answer is short, and the length of the answer tells you who you're dealing with.
Second memory card starting to corrupt in the same household
Treat the pattern as the patient: cards can't infect each other, but they can share a faulty reader, a marginal laptop slot, or a mid-write removal habit — and the reader is the usual culprit, quietly corrupting everything it handles. Retire the shared card path now: no more cards into that slot or reader until it's been tested with expendable media, and never put a misbehaving card back in to "check it again." Stop using both affected cards immediately — every further session risks overwriting recoverable images — and have each imaged once, write-blocked, on trusted equipment. And ask any lab the question this owner asked: "what do I pay if you fail?" The only honest answer is nothing, in writing, before you commit.
The reader's the usual suspect — call Leeds Data Recovery on 0113 322 3083; both imaged write-blocked, recovered and reconciled, the pattern stopped — one written figure per card, and nothing owed if we fail.
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.