{"id":10709,"date":"2019-08-16T06:59:13","date_gmt":"2019-08-16T01:29:13","guid":{"rendered":"http:\/\/198.58.113.91\/blog\/?p=10709"},"modified":"2023-08-05T23:08:00","modified_gmt":"2023-08-05T17:38:00","slug":"fix-device-harddisk-dr0-has-a-bad-block-error-in-event-viewer","status":"publish","type":"post","link":"https:\/\/www.winhelponline.com\/blog\/fix-device-harddisk-dr0-has-a-bad-block-error-in-event-viewer\/","title":{"rendered":"Fix: Device Harddisk DR0 has a “bad block” Error in Event Viewer"},"content":{"rendered":"

Of late, one of my Windows 10 computers has been running sluggishly, hangs frequently or shuts down abruptly. The malware scans turned out to be normal and there are no processes consuming<\/a> huge CPU time or memory. The disk usage<\/a> remained at 100% though, regardless of the app I open.<\/p>\n

The System<\/strong> event log showed multiple disk<\/strong> error entries. Here is one such event:<\/p>\n

Log Name: System\r\nSource: disk\r\nDate: 15-08-2019 17:37:49\r\nEvent ID: 7\r\nTask Category: None\r\nLevel: Error\r\nKeywords: Classic\r\nUser: N\/A\r\nComputer: DESKTOP-3V7LVDA\r\nDescription:\r\nThe device, \\Device\\Harddisk0\\DR0, has a bad block.<\/pre>\n
\"hard<\/p>\n
After restarting Windows, the following event log entry gets added.<\/p>\n
Log Name: System\r\nSource: Microsoft-Windows-Kernel-Power\r\nDate: 15-08-2019 19:28:09\r\nEvent ID: 41\r\nTask Category: (63)\r\nLevel: Critical\r\nKeywords: (70368744177664),(2)\r\nUser: SYSTEM\r\nComputer: DESKTOP-3V7LVDA\r\nDescription:\r\nThe system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.<\/pre>\n
The same error occurred for my secondary hard drive (Disk 1<\/code>), and the error message read The device, \\Device\\Harddisk1\\DR1, has a bad block<\/strong>.<\/p>\n
If you have multiple hard drives and want to know which hard drive has a bad block, note down the Disk # indicated in the event log. Open Disk Management to see the list of drives and the corresponding drive #.<\/p>\n
\"disk<\/p>\n
A bad block is an area of the hard drive that is no longer reliable for storing and retrieving data. Bad block<\/strong> may indicate corruption or physical damage.<\/p>\n
There are two types of bad blocks: A physical bad block comes from damage to the storage medium. A soft, or logical, bad block occurs when the operating system (OS) is unable to read data from a sector. Examples of a soft bad block include when the cyclic redundancy check (CRC), or error correction code (ECC), for a particular storage block does not match the data read by the disk. (TechTarget.com<\/a>)<\/em><\/p>\n
And, I couldn’t clone the drive using Macrium Reflect<\/a> or EaseUS ToDo Backup. Macrium Reflect threw the error “clone failed” code 9, and EaseUS software stalled at 51% while cloning the disk.<\/p>\n
In this article, I’ll tell you how I resolved the hard drive “bad block” error.<\/p>\n
Fix: Device Harddisk DR0 has a “bad block” Error in Event Viewer<\/h2>\n
The first thing I did was run Error Checking (which is not comprehensive as Chkdsk) on the drive. It showed no errors.<\/p>\n
\"hard<\/p>\n
The next ideal thing any on would do is to run Chkdsk on each partition (chkdsk \/r c:<\/code>), and press Y<\/code> when you see this message:<\/p>\n
Chkdsk cannot run because the volume is in use by another process. Would you like to schedule this volume to be checked the next time the system restarts? (Y\/N)<\/strong><\/em><\/p>\n
However, I didn’t run Chkdsk.\u00a0Instead, I ran CrystalDiskInfo utility.<\/p>\n
\"hard<\/p>\n
In CrystalDiskInfo, the drive’s health status was showing up as Caution<\/strong>, with the following entries marked in yellow:<\/p>\n