Data Recovery Case File · Formatted & Logical Faults · Do Not Copy Through Bad Memory
Two Test Results, and Which One Explains the Symptom
His enquiry includes the machine's own verdict on itself, and the two halves of it point in opposite directions. A laptop showing a recovery screen with an input/output error and a boot configuration failure, where "the start-up test states that a memory module has failed but the hard disk check passed the test." He then took it to a shop, who removed the drive. Those results are not in conflict — failing memory produces symptoms that look exactly like a failing disk, for a reason worth understanding. And it changes how the data should be copied.
| Media | Laptop internal hard drive — machine reporting an input/output error and boot configuration failure; manufacturer diagnostics reporting a failed memory module and a passing hard disk |
| Reported situation | Machine failing to start with a recovery screen · input/output error and boot configuration error reported · manufacturer start-up diagnostics reporting a memory module failure · hard disk check passing the same diagnostic · drive removed by a repair shop |
| Fault class | Host memory failure producing storage-like symptoms — drive condition reported sound; data transfer through the affected machine contraindicated |
| Equipment used | Drive read on separate known-good equipment rather than through the affected machine · imaged write-blocked · contents verified by opening · original machine excluded from any transfer path |
The decode: why bad memory looks like a bad disk
What sits between the disk and everything else: memory. Data read from storage is placed into RAM before anything uses it, and data written to storage passes through RAM on the way. Every byte that moves to or from the disk is handled by memory first — which means faulty memory can corrupt data that the disk read perfectly.
Why that produces exactly his errors: a boot configuration error means the machine read the small structure describing how to start and found it invalid. If that structure was read correctly from a healthy disk and then corrupted in a bad memory cell on the way, the machine would report precisely that — an unreadable boot configuration and an input/output error, on a disk that is perfectly fine. The error is generated at the point of use, not at the point of storage, and nothing in the message distinguishes them.
Why the diagnostics deserve to be believed: both tests ran from firmware before any operating system loaded, talking to the hardware directly. The memory test exercises the modules and reports a genuine failure; the disk check queries the drive's own self-monitoring and runs low-level access. Neither is guessing. So the honest reading is that his machine has a failed memory module and a sound drive.
The critical instruction, and it is the reason this case matters: do not use that machine to copy the data off. This is the thing people do next — put the drive back, boot from something else, and transfer the files. But every byte would pass through the failing memory, and corruption introduced there is written faithfully to the destination. You would end up with a complete-looking copy containing silently damaged files, and no indication that anything went wrong. It is one of the few ways to lose data while successfully backing it up.
What to do instead: read the drive on a different machine entirely. The shop removing it was the right move — it can be connected to any known-good computer through a caddy and copied normally, with the faulty machine excluded from the path.
The good news he may not have registered: if the drive is sound and the memory has failed, this is a cheap repair. A replacement memory module is an inexpensive part, and the machine may well work normally afterwards with all his data still on it.
On the bench
The drive was read on separate known-good equipment rather than through the affected machine — every byte moving to or from storage passing through memory, so a machine with a failed module can corrupt data in transit and write a complete-looking copy containing silently damaged files. It was imaged write-blocked and contents verified by opening. The original machine was excluded from any transfer path throughout.
The outcome
The drive read on known-good equipment with the affected machine excluded, imaged and verified. 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, for anyone whose diagnostics blame the memory and clear the disk: those results agree rather than conflict. Everything read from or written to storage passes through memory first, so a faulty module corrupts data the disk read perfectly — and a boot configuration error is exactly what you get when that structure is damaged in transit. Above all, do not copy your data through that machine.
Diagnostics say the memory failed and the disk passed
Don't use that machine to copy your data off — this is the important part and it's what people do next. Everything read from or written to storage passes through memory on the way, so a faulty module can corrupt data that the disk read perfectly, and the corruption gets written faithfully to wherever you're copying. You'd finish with a complete-looking backup full of silently damaged files and no indication anything went wrong. It's one of the few ways to lose data while successfully backing it up. Take the drive out and read it on a different computer through a caddy instead. And take some encouragement: if the disk is sound and a memory module has failed, that's an inexpensive part, and the machine may work normally afterwards with everything still on it.
Don't copy through it — call Newcastle Data Recovery on 0191 406 1051; drive read on separate known-good equipment, imaged write-blocked, affected machine excluded from the transfer path.
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.