Data Recovery Case File · Formatted & Logical Faults · The Most Time-Critical Fault Here
The Water Leaves and the Salt Stays Behind
Her enquiry describes an immersion of a kind that behaves differently from every other liquid case in this archive. A computer "submerged in seawater for quite a while — our car was flooded in a tidal area — and now won't turn on. Before I send it" she wants to know what to do. Salt water conducts far better than fresh, and it does not go away when the water does. Drying it changes very little, and time is costing her something every day.
| Media | Laptop computer subjected to prolonged saltwater immersion — not powering; conductive and corrosive residue present throughout; storage condition undetermined |
| Reported situation | Vehicle flooded in a tidal area · computer submerged in seawater for an extended period · machine not powering on · owner seeking advice before dispatching the device · contents required |
| Fault class | Saltwater ingress with ongoing electrochemical corrosion — residue active after drying; storage medium potentially separable and independently assessable |
| Equipment used | Device kept unpowered and cool throughout · treated as time-critical from receipt · board residue removed by solvent washing before any electrical assessment · storage assessed independently of the host board · chip-level read at the memory package where the board could not be restored |
The decode: why seawater is a different problem
The first difference — conductivity. Pure water is a poor conductor; salt water is a good one. A powered board immersed in seawater suffers immediate short-circuit damage across paths that fresh water might have left alone, so the initial harm is greater.
The second difference, and this is the one that matters most: evaporation does not remove salt. When the water dries, the salt remains as a crust on and under every component — and salt draws moisture from the air, so it stays damp, stays conductive, and keeps a corrosion reaction running.
What that means practically: a dried board is not a stabilised board. It is a board with an active corrosion process on it, eating copper tracks and component legs continuously, whether or not it is switched on and whether or not it looks dry.
Why that makes this genuinely time-critical: most faults in this archive are stable — a drive with a failed head is no worse next month. This one deteriorates measurably by the day, and the difference between acting this week and next month is the difference between a repairable board and one whose tracks have gone.
What must not happen, in order of importance: do not apply power. Conductive residue plus voltage is how surviving components are destroyed, and a machine that will not turn on is a machine that has not yet had that happen to it.
What does not help, despite being universally recommended: rice. It absorbs a little ambient humidity and nothing from inside a sealed assembly, and it does nothing whatever about salt, which is the actual problem. Days spent on it are days of corrosion.
What actually stabilises it: washing the residue off. The board is cleaned in a solvent that displaces salt and water, then dried properly — which stops the reaction rather than waiting for it to finish. That is a bench operation and it should happen soon.
Why the storage is a separate and more hopeful question: on many machines the drive is a discrete component, sealed or packaged, and may have escaped the worst. It is assessed independently of whether the computer will ever run again — and the machine working is not the objective.
What to do while arranging it: keep it cool, keep it unpowered, and do not attempt to dry it with heat.
On the bench
The device was kept unpowered and cool throughout and treated as time-critical from receipt — salt remaining after evaporation, drawing atmospheric moisture and sustaining an active corrosion reaction that consumes tracks and component legs continuously irrespective of power. Board residue was removed by solvent washing before any electrical assessment, displacing salt rather than waiting for the reaction to complete, and storage assessed independently of the host board.
The outcome
The device kept unpowered and treated as time-critical, residue removed before any electrical assessment, and storage assessed independently. Free assessment, one fixed written figure including VAT; where a board has to be worked at component level, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: the water leaves and the salt stays. It draws moisture from the air, stays conductive, and keeps corroding — so a dried board is still being eaten, and this is one of the few faults that genuinely worsens by the day.
Device flooded with seawater
Act this week rather than this month, and do not apply power — conductive residue plus voltage is how the components that survived get destroyed. Salt water is a different problem from fresh: it conducts far better, so the initial damage is worse, and evaporation doesn't remove the salt. What's left draws moisture from the air, stays damp, stays conductive, and keeps a corrosion reaction running that eats copper tracks continuously whether the device is on or off. That's why drying doesn't stabilise anything, and why rice is useless here — it does nothing about salt. What helps is washing the residue off in a solvent. Keep it cool and don't apply heat.
Don't power it and don't wait — call Oxford Data Recovery on 01865 593000; treated as time-critical from receipt, residue removed before any electrical assessment, storage assessed independently of the board.
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.