Windows 10: Bad block in Event Viewer which CHKDSK doesn't find

I have reviewed the many posts found about this issue. I have taken the suggested steps CHKDSK, DISM, etc. including running the Seagate Utilities. I've even replaced the hard drive. I'm still seeing the events appearing in Event Viewer. Window 10 PRO seems to think my system is ill but all of the utility programs used to diagnose and or repair the issue find nothing. Even after the hard disk replacement the events are still appearing. So what's the deal? It's easy to say just ignore them but it seems to be affecting the performance of my machine. Now I'm get the following event : The s

:)

 

chkdsk and event viewer

Chkdsk /F just checks the file system integrity. Stage 4 of Chkdsk is checking for bad blocks in used sectors. Stage 5 checks for bad blocks in the unused sectors. This can be very time consuming, especially so if any bad blocks are found. These stages only run if you use the /R option for chkdsk, or the /B option for an ntfs volume. Type CHKDSK /? to see the full help.

To read the chkdsk results, see this tutorial.

Read Chkdsk Log in Event Viewer in Windows 10

Alternatively, Chkdsk run at boot stores its results in the hidden and protected Syatem Volume Information Folder. You do not have permission to explore this folder, but if you run TreeSizeFree as an adminitrator you can see its contents and read the Chkdsk logs.

 

there are no chkdsk logs in event viewer

i have run a few chkdsk commands on my hdd and on a few usb sticks, however i can't find any log in the event viewer regarding the chkdsk output.

the commands complete successfully (as i see in the CMD window), it's only the logs that never appear in the event viewer.

 

disk reportedly has bad block but chkdsk can't seem to decide if it does or not

My computer was on last night but off this morning. Looking in event viewer, I see a number of rows stating that "The device, \Device\Harddisk2\DR2, has a bad block.".

I determined which drive was "Harddisk2" and then I ran chkdsk. It also reported errors:

The Volume Bitmap is incorrect.

Windows has checked the file system and found problems.

Please run chkdsk /scan to find the problems and queue them for repair.

Then, as suggested, I ran chkdsk /scan. It reported that everything is fine.

Windows has scanned the file system and found no problems.

No further action is required.

So I ran chkdsk again, and it still thinks there are errors. Same message as before.

Any ideas why chkdsk might be disagreeing with itself?

Thanks!

Moved from: Windows / Windows 10 / Files, folders, & storage