Data Recovery Case File · Desktop Externals & Aging Drives · Capture Built Around the Window
A Drive That Works for Half a Minute Works for Half a Minute at a Time
This enquiry came from a computer business on behalf of a client and it contains an unusually precise measurement. A 1TB drive that "will occasionally read but appears to power off after around thirty or forty seconds. We have completed basic diagnostics with no option to read or recover data" — around 900GB required. A consistent, repeatable window is not a dead drive. It is a resource with a known size, and capture is designed around it rather than fighting it.
| Media | 1TB mechanical hard drive — reading successfully for a consistent interval of approximately thirty to forty seconds before power cessation; approximately 900GB required |
| Reported situation | Drive received by a computer business from a client · drive reading intermittently · power ceasing consistently after approximately thirty to forty seconds · basic diagnostics completed without result · approximately 900GB of content required |
| Fault class | Thermal or protection-triggered cut-out with reads succeeding during the interval — capture sequenced in bounded sessions with recovery periods between |
| Equipment used | Cut-out interval measured and treated as a capture budget · current draw monitored across the interval on a controlled bench supply · imaging performed in bounded sessions with cooling between · capture resumed from the last completed position each session · sequenced to prioritised regions first |
The decode: what a consistent interval indicates, and how to spend it
Why the consistency is the important detail: a drive that fails randomly is unpredictable. One that fails at the same point every time is being stopped by something that accumulates — and the two commonest are heat and current.
The thermal explanation: a component on the board warms while working, and at a certain temperature it either fails to function or a protection circuit intervenes. Thirty to forty seconds is a plausible warm-up interval, and it explains why the drive works again after being left alone.
The current explanation: the drive draws more than it should, and either the host port protection or the supply itself cuts out. That is measured directly on a controlled bench supply, which also removes the host's protection from the equation.
Why the distinction matters practically: a thermal cut-out can be extended by cooling, sometimes substantially. An overcurrent condition cannot, and calls for the board fault to be addressed first.
Now the part that decides the outcome: the window is a budget. Thirty seconds of reading, repeated, adds up to a complete capture if nothing is wasted — and everything depends on wasting nothing.
What wastes it: starting from the beginning each time. A tool that restarts a copy re-reads what it already has, so the second session covers the same ground as the first and nothing accumulates. That is why ordinary copying achieves nothing here.
What works instead: imaging that records its position and resumes from where it stopped. Each session extends the captured region, and the image is built up across as many sessions as it takes.
Why sequencing matters as much as resuming: the material that matters should be reached first, so that if the number of viable sessions turns out to be finite, they were spent on the right regions rather than on whatever happened to be at the start of the disk.
What must stop meanwhile: further diagnostics. Every diagnostic run consumes an entire window and produces information already established — the drive reads for thirty to forty seconds, and that is the finding.
On the bench
The cut-out interval was measured and treated as a capture budget — consistent timing indicating an accumulating cause, either thermal rise to a protection threshold or excess draw triggering supply cut-out, distinguishable by monitoring current across the interval on a controlled bench supply. Imaging was performed in bounded sessions with cooling between, and capture resumed from the last completed position each session, since any tool restarting from the beginning re-reads captured ground and accumulates nothing.
The outcome
The interval measured and treated as a budget, draw monitored to distinguish thermal from overcurrent, and capture accumulated across resumed sessions. Free assessment, one fixed written figure including VAT, 50% of parts and labour upfront with the balance only on successful recovery. The decode: a consistent window is a resource rather than a failure. Thirty seconds of reading, repeated and never re-covering the same ground, adds up to a complete image — which is why the tool must resume rather than restart.
Drive that works for a fixed period then cuts out
Stop running diagnostics — each one consumes a whole window to confirm what you already know. The consistency is the useful part: a drive failing at the same point every time is being stopped by something that accumulates, usually heat rising to a protection threshold or excess current draw triggering a cut-out. Either way that window is a budget, and thirty seconds repeated adds up to a full capture provided nothing is wasted. What wastes it is any tool that restarts from the beginning, since the second session re-reads the first and nothing accumulates. You need imaging that records its position and resumes.
Stop the diagnostics — call Oxford Data Recovery on 01865 593000; interval measured as a capture budget, draw monitored on a controlled bench supply, imaging accumulated across resumed sessions.
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.