BSOD: Possibly caused by Errors on Hard Drive. Not sure...

axe0 said:

The same way you did earlier Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums +

Okay. Doing that now.

@axe0, here is the Event Log.

Attachment 81370

axe0 said:

The last time I saw that message, in 1 of my VMs last week, I did following to get back in Windows in order

1. 3x startup repair with reboot between each,
2. 2x chkdsk C: /r
3. 1x startup repair
4. Reboot from the troubleshooting options

Yes, I followed this list.

It's not freezing up anymore.

axe0 said:

You performed chkdsk offline before the automatic repair problem right? Is the log you uploaded from the chkdsk before the automatic repair problem came?

The log you uploaded is saying that a corrupted record has been deleted, but I have no idea what effect it could have on the performance & health.

Code:

Examining 1 corruption record ...

Record 1 of 1: Unused file metadata marked as used ... The multi-sector header signature in file 0x73c is incorrect.
a5 25 a8 65 66 ca 04 0f ?? ?? ?? ?? ?? ?? ?? ??  .%.ef...........
Deleting corrupt file record segment 1852.
The multi-sector header signature in file 0x73d is incorrect.
10 00 00 00 02 00 00 00 ?? ?? ?? ?? ?? ?? ?? ??  ................
Deleting corrupt file record segment 1853.
corruption found and fixed.


1 corruption record processed in 0.2 seconds.


Windows has fixed all previously identified issues with this drive.
No further action is required.

Yes, I did perform chkdsk before the automatic repair problem. This is from today after I ran all of the tests on it.

Where can I find that at in the Event Viewer?