ReadSpeed helped me troubleshoot a slow laptop

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


Active member
Sep 20, 2020
I was working on a customer's laptop last night and the Hard drive performance was in the toilet.

To give you an idea of the slowness, I was going to create a 2H2 Windows 10 ISO. After the download had finished it started to create the ISO and it took over 1 hour when it normally just takes a couple of mins.

I checked the smart data and it had a clean bill of health (That's not to say there wasn't still a bad sector(s) on the drive.

He had not used the laptop in a while and it still had windows 10 version 1709. So I was going to format and reinstall windows.

This would give him the newest version of windows, plus see if the reinstall makes things go any faster.

But then I thought, let me first run Readspeed on the hard drive and see what kind of performance it currently has.

The results were in.

Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
81   2.0TB ST2000LM007-1R8174            130.6   124.4    49.5    89.1    61.1

                  Benchmarked: Thursday, 2020-12-24 at 09:55

As you can see around the 50% mark the speed peter pan's off a cliff and does not trail down gently as expected.

Seeing those numbers I said screw it and sent him out to Walmart to get an SSD. After the SSD the system ran much better (Obviously)

Very handy little tool.

I also ran it on a 750GB 2.5 inch hard drive I had laying around and it was a
A MUCH more gradual decline in speed, at 50% it was still in the 80's.

Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
81   750GB TOSHIBA MK7559GSXF            106.9    96.4    87.4    71.4    53.7

                  Benchmarked: Thursday, 2020-12-24 at 09:51
Last edited by a moderator:
On a side note, is the Driv column suppose to be missing the E on the word "Drive"
You're probably going to get tired of people sending in the "typo." Might change it to "Drv" instead. (Or Dryv? The British spelling. :) )
That's what I was thinking. Make it DRV, then it looks much less of a typ. Looks more intentional.