Data Recovery Case File · Second Fixes & Trade Handoffs · A Working Machine on a Failing Drive
Reinstalling Made It Start and Never Addressed Why It Stopped
His enquiry describes the same remedy applied twice with the same result. A machine that blue screened and would not load, taken to a local shop who "reinstalled the system onto the hard drive, and I managed to copy some info over to an external drive. Then the machine failed again, and I took it back to them." A reinstall produces a machine that starts. It does not produce a drive that works — which is why the fault came back, and why the reinstall itself was written across the very thing he wanted.
| Media | Internal hard drive subjected to repeated operating system reinstallation — original fault unaddressed; partial user recovery achieved between failures |
| Reported situation | Machine producing stop errors and failing to load · taken to a local provider · operating system reinstalled onto the existing drive · some content copied off by the owner afterwards · machine failing again subsequently · returned to the same provider · contents required |
| Fault class | Underlying drive fault with reinstallation write activity superimposed — original content partially overwritten; fault recurrence indicating hardware rather than software cause |
| Equipment used | Recurrence treated as evidence of an unaddressed hardware fault · reinstallation write extent measured against capacity · Atola Insight Forensic error-rate assessment across the surface · imaged write-blocked under strict per-sector timeouts · previous structures recovered from surviving copies |
The decode: what a reinstall does, and what the recurrence proves
What reinstalling actually achieves: it replaces the operating system with a fresh copy. A machine that would not start because its system files were damaged will start afterwards, which is why it is such a common first response and why it so often appears to work.
What it never does: examine the drive. It writes a new system onto whatever storage is there, healthy or otherwise, and asks no questions about why the previous one stopped working.
Why the recurrence is the finding: the machine failed again. Software that has been replaced does not fail again for the same reason — so a fault that returns after a reinstall was never a software fault. The drive was failing before, it was failing during, and it is failing now.
Why the stop errors pointed there from the beginning: a system that crashes repeatedly and then will not load is frequently a system whose storage is returning unreliable data. The symptom was consistent with the drive from the first day, and the reinstall treated the consequence rather than the cause.
Now the cost, which is the part nobody mentions: installing an operating system writes a substantial quantity to the drive. It replaces the filesystem structures and writes system files across the beginning of the free space — which is precisely where a previous installation's content and structures lived. Everything he had is now underneath a fresh system, or partly overwritten by it.
Why doing it twice matters: the second reinstall wrote over whatever the first one had left. Each repetition consumes more of what remains, and each was performed on a drive that was physically failing, which is also sustained write activity on a surface that cannot support it.
What he did right in the middle of it: copied some material off to an external drive when the machine was briefly working. That material is safe and it is the baseline — what remains to be recovered is whatever that copy missed.
What should have happened instead: the drive imaged before anything was installed, then a reinstall onto a replacement. The order is the whole of it — capture first, repair second, on a different device.
On the bench
Recurrence was treated as evidence of an unaddressed hardware fault — replaced software not failing again for the same reason, so a fault returning after reinstallation was never a software fault. Reinstallation write extent was measured against capacity, installation replacing filesystem structures and writing system files across the beginning of free space, which is where previous content and structures resided. The Atola Insight Forensic assessed error rates across the surface, with imaging write-blocked under strict per-sector timeouts.
The outcome
The recurrence read as an unaddressed hardware fault, the reinstallation extent measured, and previous structures recovered from surviving copies. 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: a reinstall gives you a machine that starts. It never examines the drive, which is why yours failed again — replaced software does not break twice for the same reason.
Machine that failed again after a reinstall
Treat the recurrence as the diagnosis: replaced software doesn't fail twice for the same reason, so a fault that returns after a reinstall was never a software fault. The drive was failing before, during and after. Worth understanding what the reinstall cost as well — installing a system writes a substantial amount, replacing filesystem structures and laying system files across the start of free space, which is exactly where your previous content and its structures were. Doing it twice wrote over what the first attempt left. If a machine needs recovering and repairing, the order matters: image the drive first, then install onto a replacement.
That recurrence is the finding — call Oxford Data Recovery on 01865 593000; error rates measured across the surface, write extent measured against capacity, previous structures recovered from surviving copies.
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.