Event Id 7 - The device, \Device\Harddisk0\DR0, has a bad block - this was asked BUT solution does NOT work and thread IS LOCKED

[I M L8]

The solution posted for this error has been posted. The number indicating that many people are experiencing this. And PRIOR to the thread being locked, SEVERAL people had posted that thie solution posted does NOT work. Please reopen this thread or start a new one. To be clear, the error in the System event log is:

Event ID 7 - The device, \Device\Harddisk0\DR0, has a bad block.​

Even before looking for support, I performed the solution the actions indicated in the solution proposed. In fact, this is not a new solution AND I tried using CHKDSK several times with zero luck. Running of chkdsk is indicated for this problem. From a command prompt, CHKDSK /F /R was run with a necessary reboot in order to use the disk before mounting. This appeared to run. Admittedly I did not babysit the chkdsk for the entire time it ran. Here is what is indicated in Event Viewer when looking at the tabs.


General tab.

The Details tab in Friendly View (as copied, NOT wordwrapped):​

Note: this was how it was copied using the copy option within Event Viewer.​

-


System



-


Provider


[ Name]


disk


-


EventID


7


[ Qualifiers]


49156


Level


2


Task


0


Keywords


0x80000000000000


-


TimeCreated


[ SystemTime]


2020-03-28T05:53:16.005385800Z


EventRecordID


35844


Channel


System


Computer


DimScrum


Security


-


EventData


\Device\Harddisk0\DR0


030080000100000000000000070004C0000100009C0000C0000000000000000000C00E1C02000000C231000000000000FFFFFFFF010000005800008402000000ED200AFF4207204000000000410000000000000000000000A0D7E9490F80FFFF000000000000000010F0C44B0F80FFFF000000000000000060070E01000000002800010E076000000800000000000000F00003010E07600000000000110000800000000000000000


Binary data:

In Words

0000: 00800003 00000001 00000000 C0040007
0010: 00000100 C000009C 00000000 00000000
0020: 1C0EC000 00000002 000031C2 00000000
0030: FFFFFFFF 00000001 84000058 00000002
0040: FF0A20ED 40200742 00000000 00000041
0050: 00000000 00000000 49E9D7A0 FFFF800F
0060: 00000000 00000000 4BC4F010 FFFF800F
0070: 00000000 00000000 010E0760 00000000
0080: 0E010028 00006007 00000008 00000000
0090: 010300F0 0060070E 00000000 80000011
00a0: 00000000 00000000

In Bytes


0000: 03 00 80 00 01 00 00 00 .......
0008: 00 00 00 00 07 00 04 C0 .......À
0010: 00 01 00 00 9C 00 00 C0 ......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 C0 0E 1C 02 00 00 00 .À......
0028: C2 31 00 00 00 00 00 00 Â1......
0030: FF FF FF FF 01 00 00 00 ÿÿÿÿ....
0038: 58 00 00 84 02 00 00 00 X......
0040: ED 20 0A FF 42 07 20 40 í .ÿB. @
0048: 00 00 00 00 41 00 00 00 ....A...
0050: 00 00 00 00 00 00 00 00 ........
0058: A0 D7 E9 49 0F 80 FF FF ×éI.ÿÿ
0060: 00 00 00 00 00 00 00 00 ........
0068: 10 F0 C4 4B 0F 80 FF FF .ðÄK.ÿÿ
0070: 00 00 00 00 00 00 00 00 ........
0078: 60 07 0E 01 00 00 00 00 `.......
0080: 28 00 01 0E 07 60 00 00 (....`..
0088: 08 00 00 00 00 00 00 00 ........
0090: F0 00 03 01 0E 07 60 00 ð.....`.
0098: 00 00 00 00 11 00 00 80 .......
00a0: 00 00 00 00 00 00 00 00 ........

The Details tab in XML View (as copied, wordwrapped):​

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="disk" />

<EventID Qualifiers="49156">7</EventID>

<Level>2</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2020-03-28T05:53:16.005385800Z" />

<EventRecordID>35844</EventRecordID>

<Channel>System</Channel>

<Computer>DimScrum</Computer>

<Security />

</System>

- <EventData>

<Data>\Device\Harddisk0\DR0</Data>

<Binary>030080000100000000000000070004C0000100009C0000C0000000000000000000C00E1C02000000C231000000000000FFFFFFFF010000005800008402000000ED200AFF4207204000000000410000000000000000000000A0D7E9490F80FFFF000000000000000010F0C44B0F80FFFF000000000000000060070E01000000002800010E076000000800000000000000F00003010E07600000000000110000800000000000000000</Binary>

</EventData>

</Event>

Additional Issue for CHKDSK output​

Perhaps the location of the CHKDSK output has changed. I cannot find it. Where is the output from CHKDSK especially for NTFS volumes using the /V option? Is it in the System Volume Information\chkdsk subdirectory, or is it posted as text within one of Windows Logs (and if so, which one)?


Example: I have found a file on this system called C:\System Volume Information\Chkdsk\Chkdsk20190713050120.log with a Date Modified of 7/12/19 23:01 and it contains useful information from July of 2019. The file is in plain text except that after the last line of text, the file appears to be padded with binary zeros (appearing as "NUL" with the editor that I use). Here are the contents of that file containing information that I would like to have when I run Chkdsk for the current problem:

Checking file system on C:​

The type of the file system is NTFS.​

Volume label is OS.​

One of your disks needs to be checked for consistency. You​

may cancel the disk check, but it is strongly recommended​

that you continue.​

Windows will now check the disk.​

Stage 1: Examining basic file system structure ...​

1170688 file records processed.​

File verification completed.​

Deleting orphan file record segment 4410.​

Deleting orphan file record segment 4411.​

Deleting orphan file record segment 4412.​

Deleting orphan file record segment 4413.​

Deleting orphan file record segment 48D4.​

Deleting orphan file record segment 48D5.​

Deleting orphan file record segment 48D6.​

Deleting orphan file record segment 48D7.​

Deleting orphan file record segment 48F8.​

Deleting orphan file record segment 48F9.​

Deleting orphan file record segment 48FA.​

Deleting orphan file record segment 48FB.​

Deleting orphan file record segment 48FC.​

Deleting orphan file record segment 48FD.​

Deleting orphan file record segment 48FE.​

Deleting orphan file record segment 48FF.​

11154 large file records processed.​

​

0 bad file records processed.​

​

Stage 2: Examining file name linkage ...​

64828 reparse records processed.​

1526680 index entries processed.​

Index verification completed.​

CHKDSK is scanning unindexed files for reconnect to their original directory.​

1 unindexed files scanned.​

0 unindexed files recovered to original directory.​

CHKDSK is recovering remaining unindexed files.​

1 unindexed files recovered to lost and found.​

Lost and found is located at \found.000​

64828 reparse records processed.​

Stage 3: Examining security descriptors ...​

CHKDSK is compacting the security descriptor stream​

Cleaning up 13659 unused security descriptors.​

177997 data files processed.​

CHKDSK is verifying Usn Journal...​

Usn Journal verification completed.​

Correcting errors in the master file table's (MFT) BITMAP attribute.​

Correcting errors in the Volume Bitmap.​

Windows has made corrections to the file system.​

No further action is required.​

485625454 KB total disk space.​

438553720 KB in 787040 files.​

294140 KB in 178001 indexes.​

16 KB in bad sectors.​

1257274 KB in use by the system.​

65536 KB occupied by the log file.​

45520304 KB available on disk.​

4096 bytes in each allocation unit.​

121406363 total allocation units on disk.​

11380076 allocation units available on disk.​

Internal Info:​

00 dd 11 00 e0 b1 0e 00 4e cd 11 00 00 00 00 00 ........N.......​

c9 0e 00 00 73 ee 00 00 00 00 00 00 00 00 00 00 ....s...........​

Windows has finished checking your disk.​

Please wait while your computer restarts.​

NULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNULNUL​

Where can this information be found or how can this location designated when using Chkdsk? Will standard redirection ">" "2>" be used? Are there restrictions on what the file location is? Does Chkdsk run as a single process? If not, should the append form of redirection ">>", etc. be used instead?

Continue reading...