Hard Drive Clicking Noise: Bad Sectors vs Head Crash Fixes
A clicking hard drive usually means physical failure. But sometimes it's just bad sectors. Here's how to tell the difference and what actually works.
1. Bad Sectors Causing Clicking (Most Common)
What's actually happening here is the read/write head is trying to access a damaged area of the platter, failing, retrying, and making that telltale clicking sound. The head itself isn't broken—it's just confused. This usually happens after the drive has been running for a while, not on cold boot. You'll hear the click during file reads or writes, not when the system powers on.
The fix here is to remap those bad sectors. Windows' built-in chkdsk can do this, but I've found it's too aggressive and can cause more issues on drives that are already borderline. Use the manufacturer's own tool instead.
Step-by-step fix
- Back up your data immediately. If the drive clicks during reads, it's only going to get worse. Use a tool like
robocopyor a GUI like TeraCopy—don't use Windows copy, it stops on errors. - Run a non-destructive read test. For Western Digital drives, use Data Lifeguard Diagnostic (DLG) in extended test mode. For Seagate, use SeaTools for Windows in the long generic test. Both will scan every sector and attempt to reallocate bad ones to spare sectors.
- If the test reports reallocated sectors (look at S.M.A.R.T. attribute 05), the drive has spare sectors left. The clicking should stop after the remap.
- If it doesn't stop, the spare pool is exhausted. The drive is toast. Replace it.
The reason step 3 works is that modern drives reserve a pool of spare sectors. When the firmware detects a bad sector during a read or write, it transparently remaps it. But this only happens if the drive's firmware is actively scanning—hence the need for a proper diagnostic tool rather than just running chkdsk /r (which does a similar scan but at filesystem level, often missing remaps).
2. Head Crash (Less Common, More Serious)
A head crash is when the read/write head physically contacts the platter. You'll know it's a head crash if the clicking starts immediately on power-up, before the OS even loads. The sound is sharper—like a metallic tapping—and often accompanied by a grinding noise. The drive won't be recognized in BIOS.
There is no software fix for a head crash. Anyone telling you otherwise is selling snake oil. The only fix is professional data recovery, which costs $500–$2000+ and requires opening the drive in a clean room. But before you go that route, there's one thing to try.
What to check first
- Power supply: A dying PSU can cause voltage drops that make the head actuator stutter. Swap the drive into another machine and see if it still clicks. If it's silent on another machine, your PSU is the problem.
- Frozen bus: On some Dell and HP desktops from 2016–2019, a buggy BIOS causes the SATA controller to timeout during POST, leading to a clicking retry loop. Update the BIOS or disable hot-plug for that SATA port.
- If neither helps, it's a real head crash. Freeze the drive? Don't. That trick from the 1990s works for stuck spindles, not crashed heads. You'll only contaminate the platters further.
For a head crash, your only realistic hope is a donor drive of the exact same model and firmware version. But you need a clean room. I've done it twice, and it failed both times—the alignment tolerances are microns. Pay the pros.
3. Firmware Glitch or Logical Error (Rare)
This one's rare, but I've seen it on Seagate Barracuda 7200.11 drives from 2008 and some Toshiba MQ01 series. The firmware gets confused and the head parks repeatedly, making a clicking sound. Unlike a head crash, the drive is still detected—just slow.
Fix it with a firmware update
- Check the drive's S.M.A.R.T. data with CrystalDiskInfo. Look for attribute 09 (power-on hours). If it's under 2000 hours and the drive clicks, firmware is suspect.
- Download the manufacturer's firmware update tool. For Seagate, it's the SeaChest utilities. For Western Digital, WD Dashboard.
- Boot into a WinPE environment (like Hiren's Boot CD) and flash the firmware. Do not interrupt the process—a bricked drive is worse than a clicking one.
The reason firmware issues cause clicking is some early drives had a bug where the motor controller would lose sync with the head positioning servo. The head would slam into the ramp repeatedly. A firmware patch fixes the timing algorithm.
Quick-Reference Summary Table
| Cause | When Clicking Occurs | Drive Detected? | Fix |
|---|---|---|---|
| Bad sectors | During file access, under load | Yes, but slow | Run manufacturer's diagnostic to remap sectors |
| Head crash | On power-up, even before BIOS | No | Replace drive or professional data recovery |
| Firmware glitch | Occasional, random intervals | Yes, with errors | Flash updated firmware |
Bottom line: if your drive clicks on startup, it's probably dead. Clicking during use means you might have time to save your data. Don't waste that time on internet forums—get a backup tool running now.
Was this solution helpful?