Data Recovery Case File · Cameras, Drones & Cards · Travelling With a Failure
The Waiting Is Free and the Carrying Is Not
Her enquiry arrives from partway through a journey. Travelling across Europe when "my SD card suddenly stopped working. My computer won't recognise it and my camera says card error, meaning I have lost all of my memories from this trip. I have taken it into a place along the way and he said the reader part of the card isn't working." She is moving countries in March. The months in between will cost her nothing at all — which is unusual in this archive — but how the card travels does.
| Media | 64GB SD card from travel photography — not enumerating on a computer; originating camera reporting a card error; controller failure diagnosed by a third party |
| Reported situation | Card in use during extended travel · card ceasing to function · computer not recognising the card · camera reporting a card error · assessed in transit by a third party · controller failure indicated · specialist attention deferred until relocation |
| Fault class | Controller failure with memory unaffected — content stable indefinitely; handling and transport the only material risks during the interval |
| Equipment used | Card removed from all devices and stored unpowered · enumeration state read write-blocked under strict timeouts · chip-level read past the controller · translation layer reconstructed in software · media validated by rendering |
The decode: what the diagnosis means and what the interval costs
What "the reader part isn't working" describes: the controller. Every card contains memory and a small processor that presents it — the memory holds the pictures and the controller is the only thing that can describe them to a host. When it fails, the card cannot introduce itself, and nothing downstream can reach the memory through it.
Why her two observations agree: the computer not recognising the card and the camera reporting an error are the same finding seen from opposite directions. Two independent devices reaching the same conclusion confirms the card rather than either of them, which is worth more than most single tests.
Why the memory is almost certainly fine: a controller that has stopped answering has not written to or erased anything. The pictures sit exactly where they were written, and the failure is in the component that speaks for them.
Why the delay genuinely does not matter, and this is the reassuring part: flash memory holds its charge for years without power. A card sitting in a drawer until March is in the same condition in March as it is today. There is no clock running here — unlike a mechanical drive with adhered heads, or a liquid-damaged board where corrosion is progressing, or a drive that somebody keeps connecting.
What does carry risk during the interval, and all of it is handling: keep it in hand luggage rather than posting it internationally, because a card in the post is a card that may not arrive. Keep it out of hold baggage for the same reason. Store it in a case rather than loose, so the contacts are not scraped and the card is not flexed.
And the thing that would cost her most: continuing to try it. Every insertion into another camera or another reader along the way is a chance for a device to offer to format it, and some do so without asking. The card should go into a case now and stay there.
What will be done when it arrives: the memory is read directly through the manufacturer's test points, bypassing the controller entirely, then descrambled, error-corrected and reassembled with the addressing pattern reconstructed from the contents. Controller failures are among the more routinely recoverable faults here.
On the bench
The card was removed from all devices and stored unpowered — flash memory retaining charge for years without power, so an interval before assessment carries no cost, while every further insertion risks a device offering to prepare the card for use. Enumeration state was read write-blocked under strict timeouts, and the memory read at chip level past the controller with the translation layer reconstructed in software. Media was validated by rendering.
The outcome
The card stored unpowered until assessment, then read past the controller with the addressing reconstructed in software. 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 decode: the diagnosis you were given sounds right — the controller is the part that presents the card, and when it fails nothing can reach the memory through it. The months of waiting cost nothing, because flash holds its charge for years. The handling is what matters.
Card that failed while you are travelling
Put it in a case now and stop trying it — the waiting genuinely costs you nothing, and every further insertion is a chance for some device to offer to format it, which a few do without asking. Flash memory holds its charge for years without power, so a card sitting in a drawer until you reach a specialist is in identical condition when it gets there. That's unusual: a mechanical drive with stuck heads or a liquid-damaged board both get worse while you wait. What does carry risk is the journey. Carry it in hand luggage rather than posting it internationally, keep it out of hold baggage, and store it so the contacts aren't scraped.
Case it and carry it — then call Oxford Data Recovery on 01865 593000; enumeration read under strict timeouts, memory read at chip level past the controller, addressing reconstructed in software.
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.