Technical Anshu
Tutorials Blog
Drive Health Testing

Failing Hard Drive Can Look Like a Slow PC How to Check Drive Health Inside the Testing Method

Here is the cruellest disguise in PC repair: a hard drive in its last months does not usually die loudly. It slows down - reads that took milliseconds take seconds of silent retries, and every program, update and boot inherits the wait. Owners blame Windows, RAM, viruses - everything except the one part quietly failing. That is why the engineer's method includes a drive health check before deep software testing: no other measurement on a dying drive can be trusted.

Technical AnshuWindows 10 / 11Step-by-step testing guide
Watch the video to see the health check placed inside the full testing method

The check itself is a reading, not a repair: the drive keeps its own health diary, called SMART, and your job is simply to read it. Two routes give the same diary - the free tool CrystalDiskInfo draws it as a clear health verdict, or PowerShell asks Windows directly. Run Get-PhysicalDisk | Select-Object FriendlyName, MediaType, HealthStatus and Windows will answer Healthy, Warning or Unhealthy in one line. But the headline verdict is only the summary - the numbers beneath it tell the real story.

Drive health - SMART summary (example reading)
Health status ACT SOONCaution
Reallocated sectors BAD SIGN148 and rising
Current pending sectors UNREADABLE AREAS32
Power-on hours OLD AGE41,000 plus
Rule on a suspect drive: data backup BEFORE any stress test or full scan
A cautious SMART summary is the drive confessing inside the slow-PC method. Example values from a tired mechanical drive.
1

The Attributes That Actually Matter

In the SMART detail, three readings carry the conviction on a mechanical drive:

  1. Reallocated Sector Count - sectors that failed and were replaced by spares. A handful on an ancient drive is history; a count that grows between checks is a drive spending its last reserves
  2. Current Pending Sectors - areas the drive currently cannot read and is waiting to retry. Any stable non-zero figure here matches the freezing-and-waiting symptom exactly
  3. Reported Uncorrectable Errors - reads that failed outright. These are the moments the user felt as hangs

On an SSD the diary speaks differently: a health percentage counting down its write life, and wear figures instead of sector drama. A low percentage with no errors is an old age warning, not a corruption verdict - read which language your drive speaks.

2

Match the Diary to the Symptoms

Now connect the paperwork to the pain. A Caution drive plus the classic pattern from the disk case page - 100% active time, tiny MB/s, enormous response time - is a conviction, not a coincidence. Add the supporting witnesses: freezes where the disk light stays solid, Event Viewer System log errors from source disk (Event ID 7 for bad blocks, 51 for paging errors, 153 for retried IO), and files that open on the second attempt.

One witness can lie; three agreeing witnesses inside one week is the drive telling you its retirement date.

3

The Safety Rule - Backup Before Stress

This is the rule this whole method is strictest about: on a suspect drive, data comes off before any further testing. No full-surface scans, no chkdsk marathons, no defragmenting a drive that is already retrying reads - every hour of heavy work can be the hour it stops answering entirely.

Copy the irreplaceable data first - documents, photos, accounts data - to another device, and confirm the copies open. Only then continue diagnosing, in the calm knowledge that even a total failure tomorrow is now an inconvenience, not a loss.

4

Reading the Verdict Honestly

  1. SMART bad or caution, symptoms matching - the slow PC mystery is solved, and it was hardware all along. The fix path is replacement and data migration, in that order of urgency
  2. SMART healthy, symptoms elsewhere - the drive leaves the suspect list with honours, and the meters take over again. A clean diary is genuinely useful evidence
  3. SMART healthy but mechanical noises - clicking, grinding, repeated spin-up - believe your ears over the diary. SMART is a warning system, not a lie detector, and some drives die unrecorded
🔴 Honest line: SMART predicts some deaths, not all - a drive can pass every health check and still fail next month, which is why the method never treats a good reading as a reason to skip backups. It treats a bad reading as a fire alarm: never argued with, always acted on.

Watch the Full Testing Method in the Video

Watch the video read a real drive's diary and match it against the slowness the owner described.

Watch Full Video
Frequently Asked Questions

SMART says my drive is Good - so the drive cannot be the problem?

A Good reading clears the drive of the known, recorded failures - it does not guarantee the future or catch every fault. If the symptom pattern still matches a struggling drive (100% active time, huge response times), keep the evidence from all readings together and watch whether the numbers move between checks.

Should I run chkdsk to test the drive properly?

Not on a suspect drive, and not as a first test. A full chkdsk works the drive hard for a long time - exactly the stress a failing drive may not survive. Read SMART first, back up the data, and only then consider heavier scans with the data already safe.

My SSD shows a health percentage dropping - is it dying?

That percentage is a fuel gauge for the SSD's rated write life, not a fault counter. 90% after years of use is normal ageing. Worry when it falls fast, reaches very low figures, or arrives with errors and disappearing data - and keep backups regardless, because gauges do not schedule failures politely.

This guide is based on the Technical Anshu PC slow testing method video - stuck on any step, ask in the video comments and you will get an answer.