Data Recovery Case File · Cameras, Drones & Cards · Reviewing Is Not Passive
A Camera Browsing Its Own Images Is Writing as Well as Reading
Her enquiry pins the failure to a moment, and the moment is the useful part. A wedding shot that day, a card that would not upload, and — "I was flicking through the images on the camera when it corrupted." Reviewing feels like the safest thing you can do with a card, and it is not passive: cameras update their own records as they browse, and a card at the edge of failing is at its most vulnerable when something writes to it.
| Media | Camera memory card holding a full day's professional coverage — volume not presenting; failure occurring during in-camera image review on the day of the shoot |
| Reported situation | Full wedding shot on the day of the enquiry · card reviewed in the camera afterwards · failure occurring during that review · card not working on upload · card inserted directly into a computer slot · storage management showing nothing · content required urgently |
| Fault class | Failure during an in-camera write to management structures — index or file allocation left inconsistent; image data written earlier and retained |
| Equipment used | Failure during review identified as coincident with a write rather than with reading · card removed from the camera as the immediate priority · read on fixed contact equipment independent of host enumeration · imaged write-blocked before any scanning · signature carving performed across the whole card independently of directory entries |
The decode: what a camera does while you look, and why the timing matters
Why reviewing is not read-only: cameras keep records. Marking an image as viewed, updating a protection flag, refreshing a thumbnail cache or writing a rating are all small writes to the card, and they happen without any prompt.
Why that makes review a risk on a marginal card: writing is the demanding operation. A card that reads adequately can fail during a write to its management structures, and those structures are what describe everything else.
Why the timing she reports is therefore diagnostic: it names the operation. Failing during review points at a structural write rather than at a read of image data.
Why that is the encouraging reading: the photographs were written hours earlier. Image data laid down during the shoot is not touched by a review, and remains where the camera wrote it.
What is likely to be damaged instead: the index. A structural update interrupted partway leaves the card describing something inconsistent, which is why nothing presents.
Why the storage management view showing nothing fits: the system reads structures before offering a volume. Structures it cannot interpret produce no volume rather than a damaged one.
Why inserting the card directly into the computer was reasonable and worth noting: built-in slots differ from readers. Some are connected through a different interface with its own quirks, so a card that fails in one may behave differently in the other.
Why that is worth trying once and no more: each insertion is another connection to a card in an unknown state. One alternative reader is a test; several are attrition.
Why the same-day timing is the strongest thing in her favour: nothing has been written since. The card has not been back in a camera, so no new frames have displaced anything.
What must not happen given the professional stakes: no formatting, no repair, and no further shooting on that card. Whatever offer appears, the card should be set aside exactly as it is.
On the bench
Failure during review was identified as coincident with a write rather than with reading — cameras updating view state, protection flags, thumbnail caches and ratings as images are browsed, all of which are small writes to the card's management structures. Writing is the demanding operation, so a marginal card fails there while reading adequately. Image data written during the shoot is untouched by review. Carving ran across the whole card independently of directory entries.
The outcome
Failure during review identified as coincident with a write, the card removed from the camera, and carving performed independently of the directory. Free assessment, one fixed written figure including VAT; on cards where content has been deleted or overwritten, the figure is payable upfront. The decode: looking through images is not a passive act. Cameras write as they browse — so the failure landed on the structures describing your photographs, not on the photographs, which went down hours earlier.
Reviewing images on a card you are relying on
Copy first and review afterwards. Browsing in the camera writes as well as reads — view state, protection flags, thumbnail caches and ratings all update the card's management structures without asking — and writing is the operation a marginal card fails during. If it has already happened, take the card out and leave it out: the photographs were written hours earlier and aren't touched by a review, so what's damaged is the index describing them. Try one alternative reader, not several.
Take it out and leave it — call Cambridge Data Recovery on 01223 655015; failure identified as coincident with a write, read on fixed contact equipment, carving performed independently of the directory.
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.