Technical Anshu
Tutorials Blog
⚡ Drive Diagnosis Guide

Windows Problem or Hard Drive Failure How to Find Out Before You Lose Data

A recovery screen or a corrupt Windows does not always mean Windows is the problem. Very often the hard disk or SSD underneath is quietly failing, and reinstalling Windows on it only wastes time. This is the exact order to test in, so you know which one it is before your data is at risk.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 15 minute diagnosis
Video Tutorial Thumbnail
🎥 Watch the full video - Windows fault or drive fault, live diagnosis step by step

Here is the trap most people fall into: Windows gets corrupted, they format and reinstall, and two weeks later it is corrupted again. The reinstall was never the cure, because the drive was the disease. A failing drive corrupts whatever is written to it - including a brand new Windows. So before you repair or reinstall anything, run these five checks in order. They take about fifteen minutes, they cost nothing, and they end with a clear decision: fix Windows, or rescue data and replace the drive.

Event Viewer — Windows Logs → System (example from a failing drive)
❌ Error  disk  Event ID 7 — The device, \Device\Harddisk0\DR0, has a bad blockHardware
⚠️ Warning  disk  Event ID 153 — The IO operation at logical block address 0x188973c8 for Disk 0 was retriedHardware
❌ Error  Ntfs  Event ID 55 — A corruption was discovered in the file system structure on volume C:Check drive
ℹ️ These three together, repeated daily, are a failing drive's signature — not a Windows bugVerdict

👆 Example Event Viewer entries from a PC whose HDD was dying — the exact wording Windows logs when the drive, not Windows, is at fault.

1

First Split the Symptoms — Software Pattern vs Hardware Pattern

Before opening any tool, look at how the PC misbehaves. The pattern itself already points one way:

  1. Points to Windows (software): one specific app crashes, one error after one update or one driver install, Safe Mode works perfectly, the PC is fast again right after a clean install and stays fast
  2. Points to the drive (hardware): freezes where even the mouse stops, everything slow including the BIOS/boot screen, clicking or grinding sounds, files that were fine yesterday now refuse to open, problems return after a full format, error is different every time
  3. The single strongest clue: you already reinstalled Windows once and the same corruption came back. Software does not survive a format. A dying drive does.
2

Check the Drive's Own Health Report — SMART

Every HDD and SSD continuously monitors itself. This self-report is called SMART, and it is the fastest honest answer you will get:

  1. Download CrystalDiskInfo (free) and open it — it shows a big health verdict: Good, Caution or Bad
  2. No download possible? Open PowerShell as administrator and run Get-PhysicalDisk — the HealthStatus column gives a basic Healthy / Warning / Unhealthy
  3. For the detailed counters, run Get-PhysicalDisk | Get-StorageReliabilityCounter and look at ReadErrorsTotal and Wear
  4. Caution or Bad means the drive itself is reporting damage. That is not a Windows opinion — it is the drive's own firmware. Skip straight to Step 5's rescue decision
3

Read the Evidence Windows Already Recorded — Event Viewer

Windows quietly logs every struggle the drive has. Most users never look; technicians look here first:

  1. Press Windows + R, type eventvwr.msc and open Windows Logs → System
  2. Click Filter Current Log and tick sources disk and Ntfs
  3. The IDs that mean hardware trouble: 7 (bad block), 51 (error during a paging operation), 153 (I/O operation retried), 129 (device reset — the drive stopped answering), and 55 from Ntfs (file system corruption discovered)
  4. One lonely entry months ago can be a one-off. The same IDs repeating every day is a drive asking for help. Note the disk number in the message — Harddisk0 is usually your Windows drive
4

Rule Out the Cheap Culprit — SATA Cable and Port

Honest diagnosis includes the 200-rupee part everyone forgets. A loose or damaged SATA data cable produces exactly the same Event 129 and 153 timeouts as a dying drive, because from Windows' side both look identical — the drive stopped answering in time.

  1. Shut down fully and unplug the PC
  2. Re-seat the SATA cable at both ends, or better, swap in a known-good cable and a different SATA port on the motherboard
  3. On a laptop with a 2.5-inch drive, re-seat the drive in its bay or caddy
  4. Use the PC for a day. If the errors stop completely, it was the connection — you just saved a drive replacement. If they continue on a new cable and port, the drive itself stands convicted
5

Make the Decision — Repair Windows or Rescue and Replace

Now decide with evidence, not hope:

  1. SMART says Caution/Bad, or disk errors repeat on a good cable: stop repairing Windows. Do not run chkdsk, do not format, do not reinstall — every write stresses a dying drive. Copy your important data to another drive first (documents and photos before big files), then replace the drive, then install Windows on the new one
  2. SMART says Good and the System log is clean: it really is Windows. Now the normal repairs make sense — sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, and a clean reinstall if those fail
  3. Mixed result (Good health but a few old errors): back up your data anyway, then repair Windows and watch the log for a week. New disk errors = replace the drive

The full live walkthrough of this diagnosis — SMART check, health tools and safe data recovery from a failing drive — is shown in the video above.

🔴 The one rule that protects your data: if the drive clicks, grinds, or its health shows Caution/Bad, data rescue comes before every repair. A corrupt Windows can always be reinstalled. Data on a dead drive often cannot be recovered at any price.

🎥 Watch the Complete Process in the Video

The complete diagnosis — how to tell a Windows fault from a dying HDD or SSD, and how to pull your data off safely — demonstrated live, step by step.

▶️ Watch Full Video
❓ Frequently Asked Questions

Can a failing hard drive really corrupt Windows again and again?

Yes, and this is the most common reason a reinstall 'does not fix it'. Windows constantly writes system files, updates and registry data to the drive. If sectors are failing, some of those writes land on damaged areas or are read back wrongly, so corruption keeps returning in new places. Fixing Windows without testing the drive treats the symptom, not the cause.

My SMART health shows 100 percent Good, but the PC still freezes. Now what?

Then the drive is probably not your problem — but check the Event Viewer System log anyway for repeated disk IDs 7, 51, 129 or 153, because a bad SATA cable can cause freezes with a perfectly healthy drive. If the log is clean too, move on to RAM testing, temperatures and drivers.

Is it safe to run chkdsk on a drive I suspect is failing?

No — not before your data is safe. Chkdsk with repair switches writes heavily to the disk while it relocates data from bad sectors, and that stress can push a weak drive over the edge. First copy or image your important files to another drive. After the data is safe, chkdsk results become useful diagnosis instead of a gamble.

This guide is based on the Technical Anshu hard drive diagnosis video • Stuck on any step? Ask in the video comments — you will get a reply there 🙏