DISK-READ-ERROR

Disk read error at startup

Critical Severity Category: Storage Errors (SSD/HDD)• Last updated: June 2026• Verified by: ErrorsFixer Technical Board

Description

Windows reports 'A disk read error occurred' when booting. PC won't boot.

Common Causes

  • Faulty disk or SATA cable causing a read error on the boot sector.
  • Corrupted MBR (Master Boot Record) caused by a virus, overwrite, or failed operation.
  • Faulty boot sector or corrupted BCD (Boot Configuration Data).
  • Loose or faulty SATA data cable causing communication interruption with the disk.

Recommended Solutions

  • Solution: Reconnect the SATA or NVMe cable — unplug and firmly reconnect the data cable at both ends.
  • Solution: Boot from a Windows USB and in the Recovery environment run: 'bootrec /fixmbr' and 'bootrec /fixboot'.
  • Solution: Run 'Startup Repair' from a Windows installation USB (Repair your computer → Troubleshoot → Startup Repair).
  • Solution: Connect the disk as secondary in another PC and verify it is readable — check SMART in CrystalDiskInfo.
  • Solution: If the disk is physically faulty and SMART reports critical errors, replace the disk and perform a clean Windows install.

Diagnostic Commands

  • bootrec /fixmbr
  • bootrec /fixboot
  • chkdsk C: /f /r

    • Understanding Severity: Disk Data Failures

    Storage errors pose a major risk to data safety and system functionality. If a storage drive (SSD or HDD) contains bad sectors, degraded flash memory, or corrupted file system structures, Windows cannot read or write required system files. This causes slow system performance, long application load times, file write errors, or full system freezes. If the system boot drive fails to communicate, the OS will crash with an inaccessible boot device error. Resolving disk errors quickly is necessary to prevent permanent loss of documents and programs.

    Safety & Prevention Guidelines

    Immediately back up all critical files to an external drive or cloud storage if you suspect drive failure. When replacing a storage drive, handle the drive by its edges and do not touch the interface connector contacts. For M.2 NVMe SSDs, install a suitable heatsink to prevent thermal throttling, as these drives run hot. Avoid sudden computer power shutoffs, as interrupting disk write operations corrupts partition tables and MFT records.

    Windows Version & Compatibility Notes

    Modern OS installations like Windows 11 require partition tables formatted in GPT (GUID Partition Table) mode and UEFI boot configurations to support security features like Secure Boot and BitLocker. Older MBR partition styles on legacy drives will face boot issues on modern hardware platforms.

    Diagnostic Tools & Log Analysis

    For disk diagnostics, check SMART health using CrystalDiskInfo. Test write speeds using CrystalDiskMark. Run the built-in Windows Check Disk utility (chkdsk C: /f /r) to scan and repair logical file system errors, and use SSD manufacturer dashboard utilities to monitor write endurance limits.

    When to Seek Professional Hardware Help

    If a drive's SMART status shows 'Caution' or 'Bad', if the bad sector count increases weekly, or if the drive continuously drops connection during large file transfers, the drive is physically failing. Backup your data immediately and replace the storage hardware.

    Frequently Asked Questions

    Q: What do S.M.A.R.T. reallocated sector counts mean?

    Reallocated sectors are bad blocks that the drive controller has marked as damaged and moved to spare disk sectors. While this self-healing mechanism keeps the drive running temporarily, a rising reallocated sector count indicates physical platter or NAND flash wear, meaning disk failure is imminent.

    Q: What causes an SSD to run slowly or thermal throttle?

    SSDs slow down when filled above 80-85% capacity because the controller struggles to find free blocks for write operations. Lack of cooling in M.2 slots (causing temps above 70°C) and disabled TRIM command configurations also degrade write performance over time.

    Q: Can a faulty motherboard SATA cable cause drive errors?

    Yes, damaged or poorly shielded SATA data cables cause signal loss and data corruption during transfer. In CrystalDiskInfo, this shows up as a high UltraDMA CRC Error Count. Often, replacing the cheap cable fixes disk errors without replacing the drive.

    Detailed Troubleshooting Guide Available

    We have written a comprehensive, step-by-step diagnostic guide covering these types of issues in depth.

    Read the SSD & HDD Diagnostics Guide
    EF
    Verified Expert Guide

    ErrorsFixer Technical Team

    This troubleshooting guide was reviewed and verified by our hardware diagnostics department to ensure step-by-step resolution accuracy.

    Need more help?

    If these steps didn't resolve your issue, try searching our database for related symptoms or hardware components.

    Back to Search