Log Dejargonizer

Windows System Log · Event 7

Event 7: The device has a bad block

A drive reported a sector it could not read or write reliably. On a mechanical disk this is often the first warning of a failure; on a solid-state drive it is more unusual and more urgent. Back up before doing anything else.

Also written as Event ID 7disk 7The device has a bad block

What it means for you

On a personal computer

Part of your hard drive is failing. Copy anything you care about to another drive or to cloud storage now, before troubleshooting. Drives that report bad blocks often get worse quickly.

For an analyst

Check whether it is a single sector or a spreading pattern. On virtualised storage the guest may be reporting a problem that actually lives on the array or the path, so check the storage layer before condemning a virtual disk.

What it looks like

Sanitised. Addresses come from the RFC 5737 documentation ranges.

Sample
The device, \Device\Harddisk1\DR1, has a bad block.

The fields that decide it

Everything else in the log line is context.

Device
Which physical drive reported it, written as \Device\Harddisk0\DR0 or similar. The number identifies the disk, not the drive letter.
Frequency
Not a field, but the thing that matters. One entry may be a transient read error; a rising count means the drive is degrading.

Ordinary reasons this happens

Most of the time it is one of these.

  • A single transient read error on an otherwise healthy drive, particularly after an unclean shutdown.
  • A failing or loose cable rather than the drive itself.
  • Storage array or path problems presenting as disk errors inside a virtual machine.
  • An external drive disconnected while in use.

What to do next

  1. Back up the data first. Everything else can wait.
  2. Read the drive's SMART data for reallocated sector and pending sector counts — those numbers are the real health indicator.
  3. Run chkdsk to map out the bad sector, but understand this hides the symptom rather than fixing the drive.
  4. Check the cable and the port before condemning the drive, particularly if the machine was recently moved.
  5. On a virtual machine, check the underlying storage and paths rather than the guest.
  6. If reallocated sectors are climbing, replace the drive.

Queries to run

powershell All disk provider events together — bad blocks, timeouts, and controller errors usually arrive as a group. 
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='disk'} -MaxEvents 50 | Select-Object TimeCreated, Id, Message | Format-List
powershell Windows' own health view alongside the error counters. Faster than reading raw SMART attributes. 
Get-PhysicalDisk | Select-Object DeviceId, FriendlyName, MediaType, HealthStatus, OperationalStatus; Get-StorageReliabilityCounter -PhysicalDisk (Get-PhysicalDisk) | Select-Object DeviceId, ReadErrorsTotal, WriteErrorsTotal, Wear

Common questions

Does Event 7 mean my hard drive is failing?

Often, yes — particularly if it repeats. A single entry can be a transient error or a cable problem, but a drive reporting bad blocks repeatedly is degrading. Check the SMART reallocated and pending sector counts: if those are climbing, replace the drive rather than trying to repair it.

Can chkdsk fix a bad block?

It can mark the sector as unusable so Windows stops trying to use it, which stops the errors. It does not repair the drive — the physical damage remains and usually spreads. Treat chkdsk as a way to keep working long enough to migrate the data, not as a fix.

Read next

Vendor documentation

Last reviewed 28 August 2026