Data Recovery Case File · Solid State & Flash · Which Part Is Failing
Repeated Crashing Is Not Proof That the Software Is What Is Broken
His enquiry proposes a remedy before the diagnosis, which is worth pausing on. A laptop that "won't go two minutes without crashing and giving various errors that all suggest corruption", with the system on a solid-state drive and a secondary drive available — and he asks whether the system can be reinstalled without losing his files. It can, and it may not be the right thing to do.
| Media | Solid-state system drive in a laptop, with secondary storage present — repeated host crashes with errors indicating system corruption |
| Reported situation | Laptop crashing within minutes of starting · various errors reported suggesting system corruption · operating system installed on a solid-state drive · secondary storage drive present in the machine · reinstallation of the system requested without loss of personal content |
| Fault class | Repeated host instability with cause unestablished — system corruption and failing storage producing identical symptoms; reinstallation inadvisable until distinguished |
| Equipment used | Storage health assessed before any reinstallation was considered · device addressed through hardware with imposed timeouts rather than the host stack · controller state assessed in vendor technological modes · imaged write-blocked at the block level before any change to the drive · personal content extracted from the image and preserved separately |
The decode: why the two causes look the same, and why the order matters
What system corruption produces: instability, varied errors and crashes, because components the system depends on cannot be read correctly. Different failures each time, because different components are involved — which is exactly what he describes.
What a failing drive produces: the same thing. A drive returning errors on reads causes whatever needed that data to fail, and since the system reads constantly and variously, the errors are varied too.
Why the symptoms cannot separate them: corruption is what a failing drive causes. The errors he is seeing are consistent with both, because one is frequently the consequence of the other.
Why the distinction decides everything: a reinstall fixes corrupted software and does nothing for failing hardware. Installed onto a drive that is failing, a fresh system will develop the same symptoms — usually sooner, because installation itself writes heavily.
Why the reinstall is also the riskiest available action: it writes across the drive. On a degrading device that is the most demanding operation there is, and it is aimed at the drive whose health is in question.
What should happen first, and it is quick: the drive's own health reporting read directly, and its behaviour assessed through hardware rather than through the crashing system. That answers the question before anything is committed.
Why his crashing machine cannot answer it: a system that fails within two minutes cannot run diagnostics reliably. Anything measured through it is measured through the fault.
What should happen regardless of the answer: his content copied off before any reinstallation. An installation offering to preserve personal files is doing so on a best-effort basis, and it is not a backup.
Why the secondary drive he mentions is worth checking separately: it may be perfectly healthy. If his content sits there rather than on the system drive, this becomes a much smaller problem — and that is worth establishing before anything else.
What must not happen meanwhile: no repeated restarting to see whether it improves. If the drive is failing, each start-up cycle and each crash is another demand on it, and the machine's willingness to try again is not evidence that trying again is free.
On the bench
Storage health was assessed before any reinstallation was considered — system corruption and failing storage producing identical symptoms because corruption is frequently the consequence of a drive returning read errors, and a system reading constantly and variously produces varied errors either way. Reinstallation addresses software only and writes heavily across the drive, which is the most demanding operation available on a degrading device. Imaging ran write-blocked before any change.
The outcome
Storage health assessed before reinstallation was considered, the device addressed through hardware, and personal content extracted from an image and preserved separately. Free assessment, one fixed written figure including VAT; where a chip has to be removed, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: a reinstall can preserve your files and may be aimed at the wrong thing. Corruption is what a failing drive causes — so the symptoms cannot tell the two apart, and installing writes heavily across the drive in question.
Before reinstalling to fix repeated crashing
Have the drive's health checked first, and copy your content off before anything is installed. Varied errors and crashes are what system corruption looks like — and also what a failing drive looks like, because corruption is frequently the consequence of read errors, so the symptoms can't separate them. That matters because a reinstall fixes software and does nothing for hardware, while writing heavily across the very drive in question. Check your secondary drive separately too: if your files live there, this is a much smaller problem. And stop restarting to see if it improves.
Check the drive before reinstalling — call Manchester Data Recovery on 0161 871 0788; storage health assessed first, addressed through hardware, content extracted from an image and preserved separately.
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.