Fix Hard Drive Crash in Windows 10

When Windows 10 suddenly freezes, shows a blue screen, or refuses to boot, the cause is often a hard drive crash—either a logical error in the file system, a failing physical disk, or a corrupted boot record. This guide walks you through safe, step-by-step methods to diagnose the problem, recover your data, and get the drive working again. Start with the least invasive checks and only move to more advanced tools if needed. Before you begin, back up any data you can access, and have a second working computer available to create recovery media if the system won’t start.

What You’ll Need

A Windows 10 installation USB or recovery drive (if the PC won’t boot normally)
Another working computer (to create recovery media or test the drive externally)
A SATA-to-USB adapter or external enclosure (optional, for data recovery from a dead system)
Administrator access to the affected PC

Step-by-Step

Determine if the drive is detected. Boot the PC and press the key to enter BIOS/UEFI (usually Del, F2, F10, or Esc during startup). Look for the storage or boot section. If the drive does not appear, check cables and power connections (if it’s a desktop), or reseat the drive in its slot (laptop). If it still doesn’t show, the drive may be physically dead—skip to the data recovery section and then plan for replacement.
Boot into Windows if possible. If the system starts but is unstable, immediately copy important files to an external drive or cloud storage. Use a program like robocopy in Command Prompt (run as administrator) to batch-copy folders: robocopy C:\Users\YourName\Documents D:\Backup\Documents /E /R:1 /W:1.
Run CHKDSK from Windows. Open Command Prompt as administrator and type chkdsk C: /f /r. If the drive is in use, you’ll be asked to schedule it for next restart. This scans for file system errors and bad sectors. It can take hours on a large or failing drive—let it finish.
If Windows won’t boot, use the recovery environment. Insert your installation USB, boot from it, choose “Repair your computer” → “Troubleshoot” → “Advanced options” → “Command Prompt”. Then run chkdsk C: /f /r (replace C: with the actual Windows partition letter—often D: in this environment; run diskpart → list volume to find it).
Repair the boot configuration. In the same Command Prompt, run these commands one by one: bootrec /fixmbr, bootrec /fixboot, bootrec /scanos, bootrec /rebuildbcd. Answer Y when prompted to add the installation. Reboot and see if Windows starts.
Check drive health with SMART. After booting, download a free tool like CrystalDiskInfo (or use wmic diskdrive get status in Command Prompt). If the SMART status says “Caution” or “Bad”, the drive is failing physically—plan to replace it soon. Back up everything now.
Use System Restore or Startup Repair. In the recovery environment, try “Startup Repair” first—it can fix boot files automatically. If that fails, try “System Restore” to roll back to a point before the crash.
Recover data from a dead system. Remove the drive and connect it to another PC via a USB adapter. If the drive appears as a letter, copy files off. If it doesn’t appear, run chkdsk on it from that PC (without /f first, just read-only) to see if the file system is intact. For deeper recovery, use free tools like Recuva or TestDisk—but stop using the drive immediately if you hear clicking or grinding noises; that signals severe physical damage and further use may destroy data.
If the drive is logical-only (no physical noise), wipe and reinstall. Once your data is safe, open Disk Management (right-click Start → Disk Management). Delete all partitions on the failing drive, create a new one, format it NTFS, and reinstall Windows 10 from the installation USB.
If the drive is physically failing, replace it. Buy a new SSD or HDD, install it, and do a fresh Windows 10 install. Restore your data from backup. Do not keep using a drive that shows SMART errors or makes unusual sounds.

Common Mistakes

Running CHKDSK on a drive that is making clicking noises—this can worsen physical damage. Stop and seek data recovery help.
Assuming “crash” always means hardware failure. Many crashes are caused by corrupted Windows files, bad drivers, or power issues. Run the software checks first.
Writing new data to a failing drive before recovering old files—this can overwrite the data you want to save.
Ignoring SMART warnings until the drive dies completely. A “Caution” status is a red flag, not a suggestion.
Using the wrong drive letter in the recovery Command Prompt—always verify with diskpart → list volume to avoid running CHKDSK on your recovery USB or another disk.

Tips

Keep a recent full system image backup (File History or third-party tool) so a crash becomes a minor inconvenience, not a disaster.
Enable System Protection (System Restore) so you have restore points to fall back on.
If the drive is over 3–4 years old, consider proactive replacement—SSDs and HDDs have limited lifespans.
Use a surge protector or UPS to prevent power-related crashes.
Monitor drive temperature and SMART data monthly using free tools.

Troubleshooting

CHKDSK gets stuck at a certain percentage. This is common on failing drives. Wait at least 2–3 hours; if it hasn’t moved, cancel (Ctrl+C) and try running it with only /f (no /r) to fix file system errors without scanning sectors. If it still hangs, the drive is likely too damaged—focus on data recovery.
Windows still won’t boot after bootrec commands. Try “Startup Repair” again, then “System Restore”. If neither works, the Windows installation may be too corrupted—reinstall Windows but choose “Keep my files” during setup (this preserves personal data but removes installed apps).
The drive appears in BIOS but not in Windows. Open Disk Management and see if the drive shows as “Unallocated” or “Offline”. Right-click and “Online”, then assign a drive letter. If it shows as “RAW” or “Unallocated”, the partition table may be damaged—use TestDisk to rebuild it, or format the drive (data loss).
Blue screen error codes vary. Common ones like CRITICAL_PROCESS_DIED or KERNEL_DATA_INPAGE_ERROR often point to disk issues. Search the exact code online, but the steps above still apply—run CHKDSK and check SMART first.
External USB drive crashes. Try a different cable and port (preferably USB 3.0 directly on the motherboard). If it works, the cable was the problem. If not, follow the same CHKDSK and SMART steps.

Frequently Asked Questions

Can I fix a physically damaged hard drive?

Only in rare cases (e.g., a stuck read/write head) and only by professionals in a cleanroom. If you hear clicking, grinding, or the drive is not detected, do not attempt DIY repairs—send it to a data recovery service if the data is worth the cost.

How long does CHKDSK take?

On a healthy 1 TB drive, a full /f /r scan can take 2–5 hours. On a failing drive, it can take over 24 hours or never finish. Let it run overnight if possible.

Will reinstalling Windows fix a hard drive crash?

Only if the crash was caused by corrupted system files, not by physical drive failure. Reinstalling does not repair bad sectors or a dying mechanism. Always check SMART status before reinstalling.

How do I know if my hard drive is failing?

Signs include: frequent freezes or blue screens, strange noises (clicking, whirring), very slow file access, files that won’t open or disappear, and SMART warnings. Use CrystalDiskInfo to see the SMART health status.

Can I recover data from a drive that won’t boot?

Yes, often. Remove the drive and connect it to another PC via a USB adapter. If the drive is recognized, copy files off. If not, try read-only CHKDSK or data recovery software like TestDisk or Recuva. If the drive is physically failing, stop and seek professional help.

What is the difference between a logical and physical crash?

A logical crash means the file system or boot records are corrupted—the hardware still works. A physical crash means the drive’s mechanical or electronic parts are failing. Logical issues are often fixable with CHKDSK and bootrec; physical issues require replacement.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →