Event ID 7, "The device, \Device\Harddisk1\DR1, has a bad block", is logged by Windows when a drive fails to read or write a block of data. It can mean a real bad sector on a hard drive or SSD, but it is also logged by card readers, failing USB sticks and loose cables. To deal with it, find out which drive the Harddisk number refers to, check that drive's SMART health, and if the health readings confirm a problem, back up immediately. A single old event on a healthy drive is not a crisis; repeated events on your main drive are.
This guide shows how to read the event, match it to a physical drive, decide how serious it is and what to do next.
Where the event appears
- Right-click Start and choose Event Viewer.
- Open Windows Logs → System.
- In the right pane, click Filter Current Log.
- In the Event IDs box type
7, and in Event sources tick disk. Click OK.
You now see only bad block errors. Note three things: how many there are, when they started, and which Harddisk number they name. If they all name the same disk and started recently, that disk is your focus.
How to tell which drive it is
The path in the message has two numbers, for example \Device\Harddisk1\DR1.
- Harddisk1 matches Disk 1 in Disk Management in most cases. Disk 0 is usually the drive Windows is installed on.
- DR1 can be a higher number than the Harddisk number, especially for USB devices. It increases each time a removable device is reconnected, so DR5 does not mean five drives.
To confirm, open Disk Management (right-click Start) and look at the gray box on the left of each disk row, which shows Disk 0, Disk 1 and so on, with the size and type. A drive labeled Removable or showing No Media is often a card reader or USB stick. You can also run Get-Disk in Terminal to see each disk number alongside its model name and serial number.
Disk numbers can change when you add or remove drives. If you have plugged drives in and out since the events were logged, match the timing of the events to when each drive was connected.
How serious is it?
| Situation | How worried to be |
|---|---|
| One or two events months ago, none since, drive healthy | Low. Likely a one-off. Keep backups current. |
| Events from a card reader, often with no card in it | Low. A known quirk of some readers. Not a data risk. |
| Events from a USB stick or external drive | Medium. Check the cable and port, then the drive. |
| Repeated events on your internal system drive | High. Back up today and check drive health. |
| Events increasing day by day, with freezes or slow file access | Very high. The drive is likely failing. |
Step 1: Back up the affected drive
If the events point to a drive with files you care about, copy those files to another drive first, before running any scans or repairs. Start with the files you cannot replace. If some files fail to copy, skip them and keep going. Our guide on how to back up a failing hard drive covers how to do this gently.
Step 2: Check the drive's SMART health
The event log tells you a read failed. SMART tells you whether the drive itself has recorded bad sectors, which separates a real disk fault from a connection glitch.
Disk Detector reads SMART for hard drives, SSDs and NVMe drives, lists each drive with its model and serial number so you can match it to the Disk Management number, and rates it Good, Caution or Bad with the reasons explained. The values to look at are:
- Reallocated Sectors Count (5): sectors already replaced with spares.
- Current Pending Sector Count (197): sectors that cannot currently be read. This is the closest match to event ID 7.
- Reported Uncorrectable Errors (187) and Offline Uncorrectable (198).
- UDMA CRC Error Count (199): errors on the cable, not the disk. If this is rising and the sector counts are zero, replace the SATA cable.
For SSDs, check media errors and available spare instead. Our guide to SMART attributes explains each value.
Step 3: Check the connection
If SMART shows no sector problems, the bad block event may come from the path between drive and PC:
- For an internal drive, reseat or replace the SATA data cable and try a different SATA port.
- For a USB drive, try another port and cable, and avoid hubs.
- For a card reader that logs events with no card inserted, the events can usually be ignored, or the reader can be disabled in Device Manager if you never use it.
Step 4: Scan the surface
Once your files are safe, a full surface scan shows how many bad areas there are and whether they are spreading. A read-only scan is the safer choice on a drive that may be failing, because it does not change anything. Disk Detector's surface scan reads every block with a live map of bad and slow areas. See how to check a hard drive for bad sectors for how to run one and read the results.
After the scan, chkdsk X: /r can mark bad sectors so the file system stops using them, but only run it after your backup is complete.
Related events to look out for
| Event ID | Source | Meaning |
|---|---|---|
| 7 | disk | The device has a bad block |
| 11 | disk or a controller driver | The driver detected a controller error, often cable or connection related |
| 51 | disk | An error was detected during a paging operation |
| 153 | disk | An I/O operation was retried. A softer warning, but repeated 153s deserve a health check |
| 55 or 98 | Ntfs | File system corruption was detected, often a result of bad blocks |
When to replace the drive
Replace it if SMART shows pending or growing reallocated sectors, if the surface scan finds bad blocks that increase between scans, or if events keep appearing after you have changed the cable and port. Bad blocks on a hard drive are worked around, not repaired, and a growing number means more failures are coming.
Frequently asked questions
How do I find which drive is Harddisk1?
The number matches the disk number in Disk Management, so Harddisk1 is usually Disk 1.
Can event ID 7 come from a USB stick or card reader?
Yes. Card readers and flash drives often log it, sometimes even with no card inserted.
Is event ID 153 the same as event ID 7?
No. Event 153 means a read was retried, which is a softer warning, but repeated 153 events still deserve a health check.
