Laptop disks · on the log · ADR-2025-2884
Every Way In Ended at the Same Blue Screen.
The video she was watching stopped, and the image was frozen
at that point. She pressed and held the power button down and turned the computer back on. When it finally started up, a grey screen appeared, and the cut-down version of Windows that appears when you need to fix things got further along and then finished with the blue screen
. At this point, no matter how many different ways she tried to access her computer, she ended up at the same screen. She tried the repair option and then the standard boot option in succession, and repeated the cycle numerous times. Each time through, it asked a disk that had already refused once to read and write a little more.
Same story on yours? Tell us what it does — the look is free.
0203 0868633
What failed, and why.
A machine that freezes, but will not boot again presents two options at once; both need to be separated before anything else happens. Either the file system became inconsistent when power was lost mid-film (common and repairable) or the disk beneath it has begun failing and this freeze is the first sign of failure. They appear identical in terms of a blue screen. Measurement determines which, and measurement is the one thing a restart cannot do. Meanwhile, the loop is not neutral. Every ordinary start, every cut-down start, and every repair option Windows offers writes to the disk while it works; repair tools given a failing disk spend reads on ground that has very few reads available. The sequence appears to be progress because something is happening. What is actually happening is the thing you are trying to keep is being used up.
What the bench did with it.
The order of the job →| Equipment used | Its work on this job | The reason for it |
|---|---|---|
| DeepSpar Disk Imager 4 | One retry-capped copy created off the disk before it answers another start request | Mapped the heads first, then imaged one face of a platter per pass, with every reset, timeout and the power itself kept under our own control |
| PC-3000 Data Extractor | Health measured first, so the choice between corruption and wear could be determined | Instead of working around the drive's firmware and controller, it works with the two natively |
| R-Studio Technician | Damage identified using the NTFS read off the completed copy | Constructs an array from the images, and reads nearly every file system |
What the bench did with it.
Take the disk out before it is asked again
The laptop was set aside unopened, and the hard drive was removed from the laptop because all requests that were possible to ask of the machine had been requested of it multiple times. When placed on the bench it answered, and thus allowed us to settle our first concern: this was not a dead disk. However, it would not respond at a constant rate of speed and therefore brought us to a place where instead of asking another question through a restart we were forced to make use of measurement.
Measure it, then copy it once
Health came before anything else, so health influenced everything that followed. The service area responded, the defect log was read out, and the picture showed a disk carrying wear rather than an otherwise healthy disk that had simply been disrupted. This defined the copying policy as follows: a short, fixed allowance would be given on each read operation, nothing would ever be retried twice, and any areas of difficulty encountered during the initial operation would be documented and scheduled for a less aggressive (gentle) pass at some future date. There would only be one copy made, and one copy only, and the disk would never be required to load an operating system again.
Everything after that ran on the copy
There were no repair tools run against the disk itself. The NTFS records were taken out of the completed copy, the inconsistency caused by the freeze was found within these records, and the file tree was reconstructed using whatever information remained within those records. Files were then opened and read (as opposed to being counted), since a name and length are not necessarily indicative of what may or may not exist within that file.
What went home.
The user folders were placed onto new media (under their original names) in the same order as she had maintained them. It was determined that the freeze had damaged the description of the volume (not the files described by said description). Since the structure of the documents and pictures could be rebuilt from the previously created copy, they functioned normally upon opening here. Nothing was called recovered based solely upon a listing. Whether to repair the laptop itself now becomes a separate question which she can take at her own pace. Pricing was derived from published bands (one disk, £300 + VAT), and she saw this number in writing prior to any chargeable step.
Begin here if yours is doing the same thing.
Other desktop disks on the log.
Yours doing something similar? Power it down first.
Published prices are fixed. Memory cards and USB sticks are £250 + VAT. Any stand-alone drive is £300 + VAT. Drive configurations containing multiple disks (RAID, NAS or server) start at £500 + VAT. First assessments are always complimentary. Thereafter, data recovery charges are also fixed in advance and in writing, so you'll always know how much you owe before paying any money. Shut it down, get a quote first (by phone or with the form), then send it in or drop it off at our Guildford intake laboratory, Monday to Friday, 9am to 5:30pm (no appointment needed). On most jobs you only pay if we recover your data.