Data Recovery Case File · Trust, Practice & Honest Limits · The Crash Is the Measurement
A Drive That Hangs the Computer Is a Drive That Has Stopped Answering
Her enquiry describes a drive that takes the machine down with it. A portable drive carrying doctoral research where "it takes ages to load, and eventually crashes it. If I try to click on it it also just crashes my laptop. I have tried it in two other computers and the same thing happens." A computer does not crash because a drive is empty — it crashes because it asked for something and nothing came back, and a system waiting indefinitely on a device that has gone quiet eventually stops responding.
| Media | Portable external hard drive holding doctoral research material — extended delays followed by host lock-up on access; behaviour reproduced across three machines |
| Reported situation | Portable drive holding research data · extended delay when listing contents · host locking up on access · same behaviour reproduced on two further machines · funds limited and alternatives sought · contents required |
| Fault class | Severe read latency causing host lock-up — drive failing to return requests within any usable interval; reproduced across hosts, excluding a machine-side cause |
| Equipment used | Host lock-up interpreted as unreturned requests rather than a computer fault · cross-machine reproduction accepted as excluding a host cause · drive addressed through hardware with imposed timeouts rather than the host stack · imaged write-blocked with retries capped and healthy regions taken first |
The decode: what the crashing tells you, and what it costs to wait
Why a computer locks up over a drive: when a program asks for data, the system passes the request to the device and waits. Ordinarily the answer comes back in milliseconds; if it never comes back, the system keeps waiting — and a machine with a request outstanding that will not resolve becomes unresponsive.
Why listing the contents is enough to trigger it: simply displaying a folder means reading the structures that describe what is in it. Those structures sit in specific places, and if those places are the difficult ones, the most ordinary action becomes the one that hangs — which is why she cannot even browse without the machine stopping.
What the delay before the crash actually is: retries. The drive is attempting a difficult read repeatedly before giving up, and the ages she waits are the drive working extremely hard to return something it eventually cannot.
Why testing on three machines was the right thing to do: it settles a question that would otherwise be guessed at. The same behaviour on three different computers means the fault travels with the drive, and no amount of work on any laptop will change it. That is a clean, free diagnostic and she already has the result.
What the severity indicates, said plainly: a drive that cannot return a folder listing within a usable time is in serious difficulty. This is not a drive with a small problem, and the reads still being attempted are consuming what remains.
Why the cheapest useful action is to stop: every connection is another set of retries on a drive already struggling. Nothing about repeated attempts improves the position, and the difference between a drive that can be imaged and one that cannot is often the amount of work it was asked to do first.
What is worth knowing about cost, honestly: the assessment establishes what is actually wrong and what the recovery would be, and that costs nothing — so the price is a known figure rather than a guess before anything is committed to. Finding out is free, and it is the step that replaces speculation with a number.
Why the tempting cheap options are the expensive ones: consumer recovery software run against a drive in this state produces days of retries and frequently finishes the drive off. A failed attempt does not leave the position unchanged; it leaves it worse, and a drive that has been scanned to exhaustion is a harder and dearer job than one brought in untouched.
What is worth pursuing alongside: for research material specifically, an institution frequently has provision for exactly this situation, and a supervisor or department is worth asking before any personal expense.
On the bench
Host lock-up was interpreted as unreturned requests rather than a computer fault — a system passing a read to a device and waiting indefinitely when no answer returns, so extended delays represent retry cycles and lock-up represents a request that never resolves, with folder listing sufficient to trigger it because directory structures occupy specific regions. Cross-machine reproduction was accepted as excluding a host cause. The drive was addressed through hardware with imposed timeouts rather than the host stack, and imaged with healthy regions taken first.
The outcome
The lock-ups read as unreturned requests, the cross-machine result accepted as excluding a host cause, and the drive addressed through hardware with capped retries. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: your computer is not the problem, and your own three-machine test proved it. A system that hangs is one waiting on a device that stopped answering — which means severe read difficulty, and every further attempt spends what is left.
A drive that freezes the computer you plug it into
Stop connecting it, even though that feels like doing nothing — each attempt is another round of retries on a drive already in difficulty, and a drive scanned to exhaustion is a harder job than one brought in untouched. The lock-ups aren't a fault in your computer: a system passes a read request to the device and waits, and when nothing ever comes back it stops responding. If it happens on more than one machine, you've already proved the fault travels with the drive. Don't run consumer recovery software on it. And find out what's actually wrong before worrying about cost — an assessment replaces guesswork with a figure and costs nothing.
Stop connecting it — call Easy Data Recovery on 028 9002 0144; lock-ups read as unreturned requests, addressed through hardware with imposed timeouts, imaged with healthy regions taken first.
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.