Data Recovery Case File · Cameras, Drones & Cards · Nothing Was Happening
Failing With No Operation in Progress Points at the Card Rather Than at Anything Done to It
His enquiry contains a detail that removes a whole class of explanation. A card that "whilst turned off overnight went bad", so that the device now reports no card inserted and six thousand photographs and videos are unreachable. Nothing was running when it failed, and that matters: almost every common card failure happens during an operation, and this one demonstrably did not.
| Media | Memory card used as expansion storage — not detected by its host device following a period during which the device was powered off; approximately six thousand photographic and video files held |
| Reported situation | Memory card functioning normally before the device was switched off · device powered down overnight · card not detected on the device being switched on · host reporting no card present · approximately six thousand photographs and videos held · contact requested in writing |
| Fault class | Card not enumerating with no operation in progress at failure — controller or contact fault indicated; write interruption and filesystem damage excluded by circumstance |
| Equipment used | Absence of any operation at the time of failure treated as excluding write-related causes · card removed and read on fixed contact equipment independent of host enumeration · contacts examined under magnification for wear and contamination · memory read past the controller where the card did not present · translation layer reconstructed and content validated by opening |
The decode: what the circumstances rule out, and what remains
Why the timing is genuinely informative: most card failures happen during use. Interrupted writes, removal while active and power loss mid-operation account for a large share of them, and every one requires something to have been running.
What his circumstances exclude: all of those at once. A device powered off overnight was performing no writes, holding no volume open and updating nothing.
Why that also excludes the commonest structural damage: filesystems are damaged by interruption. Structures become inconsistent when an update stops partway, which cannot happen when no update is occurring.
What that leaves: the card itself. Either its contacts are no longer making connection, or its controller is no longer running.
Why a controller can fail while idle: it is not idle in the way the device is. A card retains its own management structures, and a controller that could not read them on its next start-up will not present the card at all.
Why the host reporting no card at all is consistent with that: nothing answered. A device reporting an absent card received no response, which is different from receiving a response it could not interpret.
Why that distinction matters for the outlook: it separates two situations. An unreadable volume is a structural problem; nothing answering is a controller or contact problem, and the memory behind it is usually untouched.
Why contacts are worth checking first: they are the cheapest explanation. A card resident in a device for a long period accumulates wear and contamination at the contact surfaces.
Why the quantity held is worth stating in the enquiry: it shapes the delivery. Six thousand files need somewhere to go and an arrangement that makes them usable.
What must not happen now: no repeated insertion. Where contacts are marginal, each attempt wears them further, and the device has already told him what it can.
On the bench
Absence of any operation at the time of failure was treated as excluding write-related causes — interrupted writes, active removal and power loss mid-operation accounting for a large share of card failures and all requiring something to be running, while filesystem structures become inconsistent only when an update stops partway. A host reporting no card received no response at all, which distinguishes controller and contact faults from unreadable volumes. Memory was read past the controller.
The outcome
Failure circumstances treated as excluding write-related causes, contacts examined under magnification, and memory read past the controller. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: nothing was running when it failed, which rules out most of what usually goes wrong. No card detected means nothing answered — and the memory behind a controller that will not start is generally untouched.
A card that failed with nothing running
Say so when you describe it, because the circumstances rule out a great deal. Interrupted writes, removal while active and power loss mid-operation account for most card failures and all need something to have been running — so a device switched off overnight excludes them, along with the structural damage that comes from an update stopping partway. What's left is contacts or a controller, and the memory behind either is usually untouched. Stop reinserting it meanwhile.
That narrows it — call Cambridge Data Recovery on 01223 655015; write-related causes excluded by circumstance, contacts examined under magnification, memory read past the controller.
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.