Home / Case Studies / Second Fixes & Trade Handoffs
Second Fixes & Trade Handoffs · case file

The IT Company Said a Specialist Is Needed

The laptop went on the floor and came back with a blank screen. An IT company took it as far as sensible, established that the hard drive itself kept failing during reads, and told the owner it needed a specialist. That referral was correct, and it is worth saying so, because the alternative is an IT firm running a copy job overnight and finishing the drive off. A disk that has taken an impact reads unreliably rather than not at all: it returns data, then stalls, then recovers, then stalls for longer. Ordinary copying tools respond to a stall by retrying the same sector indefinitely, which keeps a damaged mechanism working at full stretch in exactly the wrong spot. The right tool does the opposite — it takes the easy material first and comes back for the difficult parts later, gently.

Laptop / PCHard DriveDropped / ImpactFirmware / SMART
// case at a glance
MediaHard drive from a dropped laptop with a blank screen. An IT company had found the drive failing repeatedly during reads and referred it on.
Reported situationLaptop · dropped · blank screen on power-up · IT company found the hard drive keeps failing · referred to a specialist · recovery sought.
Fault classImpact damage leaving a drive reading unreliably. The data is normally largely present. Reached by removing the drive from the machine and imaging read-only in controlled passes. Continued ordinary use, and any tool that retries aggressively, are the risks.
Equipment usedDrive removed from the laptop and read on PC-3000 UDMA through a hardware write-blocker, read behaviour and weak regions mapped before anything was copied · imaged read-only on DeepSpar in controlled passes, healthy areas captured first, weak areas revisited gently, unstable heads managed and the drive rested between passes · filesystem reassembled in R-Studio from the image, contents validated and written to fresh media.
// the decode

The decode

Two separate problems are wrapped up in a dropped laptop and they need separating. The blank screen is a machine fault — the display, the board, the graphics, the power section — and it has nothing whatever to do with the data. The drive failing during reads is the fault that matters. The first is irrelevant to a recovery; the second decides everything.

A drive that reads intermittently after an impact has usually taken slight head or surface damage. It works, then meets a region it cannot manage, and stalls while it retries. Left alone in a machine, it will keep retrying until it times out, then get asked again by whatever software is running. Each of those attempts is mechanical work in a place where the mechanism is already struggling.

The correct method is imaging in controlled passes, and the difference is not cosmetic. The good regions are captured first, at speed, while the drive is at its healthiest — because a failing drive gets worse as it runs, and whatever you read first is what you are most likely to keep. Only then are the difficult regions revisited, in short attempts, with the drive rested in between and head behaviour watched. It is the reverse of what a file copy does, and it is the reason a specialist is worth the referral rather than a well-meaning overnight copy.

The IT company's instinct was sound and worth repeating: the moment a drive is failing during reads, stop reading it. Anything else is spending the drive's remaining working life on the wrong material. The assessment here costs nothing and completes within 2 working days of arrival, and a drive that needs opening is priced as physical work with half the figure due before that stage.

// on the bench

On the bench

The drive came out of the laptop, so the failed screen and the rest of the machine stopped being part of the problem. It was read on PC-3000 UDMA through a hardware write-blocker and its behaviour mapped before anything was copied — which regions read cleanly, which stalled, and how the heads behaved when they did. It was then imaged read-only on DeepSpar in controlled passes: healthy material captured first at full speed, weak regions revisited in short attempts afterwards with rests between them, and head instability managed rather than driven through. The filesystem was rebuilt in R-Studio from the completed image and the files validated by opening them before anything went to fresh media.

// the outcome

The outcome

Drive removed, imaged in controlled passes, and the data brought back onto fresh media. The assessment cost nothing and ended with one fixed written figure, VAT included before any work started. The band followed from what the drive needed: work confined to imaging is logical work and runs under no fix, no fee, while a drive that has to be opened in clean air takes half the quote before that stage with the balance owed only on success. It is worth recording that the machine never mattered. The laptop is still broken and always will be; the drive inside it was the whole job.

A dropped laptop whose drive keeps failing

Take the referral at face value and stop using the machine. A drive that fails repeatedly during reads has a limited amount of working life left, and every boot, every scan and every copy attempt spends some of it. Do not run chkdsk, do not clone it with ordinary software, and do not let anybody try an overnight copy in the hope of getting lucky — that is precisely the pattern that turns a mostly complete recovery into a partial one. Take the drive out and send that alone; there is no need to post a broken laptop, and machines are not stripped here in any case. Say when it was dropped and what has been tried since, because both change how the imaging is planned.

Got one of these on your desk right now? Everything here follows the same route: an assessment you are not charged for, completed inside 2 working days of the box reaching the bench, after which you get one written figure that never climbs afterwards. Logical faults are handled on no fix, no fee. Should the casing need opening, or the electronics rebuilding after a drop, a surge, a soaking or a fire, half of that figure falls due first and the rest only once your data is in hand. Ransomware, camera and DVR recorders, BitLocker volumes and anything else classed as forensic get settled in advance, in full. Where the files live inside a machine — laptop, desktop, Mac, server — pull the drive or the SSD and post that by itself. Computers are not dismantled here, and flash fixed permanently onto a logic board (the newer Apple laptops among them) is the one category refused outright. Unscrews or unplugs and we will take it. Send it tracked and insured to Edinburgh Data Recovery, 4 Redheughs Rigg, Westpoint, South Gyle, Edinburgh EH12 9DQ, arrange and pay for a courier of your own, or bring it to the counter there. No device is ever fetched from a customer. Packing notes and the shipping form sit here.
Start a free diagnostic

Each file below comes from a genuine enquiry taken from households and firms across Aberdeen, Aberdeenshire and the wider north-east, anonymised so nobody can be identified. Each one sets out how the fault was reasoned through, what was done about it, and which equipment did the work.

// related case files

Nearby files worth a look

Browse all case studies →

Recognise your own drive in this one?

Assessment is free and takes 2 working days at most once it lands, the figure is fixed in writing, and logical work carries no fix no fee. Begin online, or lift the phone.