I finally got around to running the tools (C:\ drive, properties\tools\error checking). It said it fixed errors.
Then for good measure, I ran chkdsk /r from an elevated cmd prompt. By the time I took a look at it, the chkdsk had finished and it was back to the log-in screen.
Here's is what was reported in the event log after I ran the error checking tool:
OK. I ran the error checking tool on my 2 other internal drives (d:\ and e:\, both spinners). No errors were found.
I assume that is sufficient and equivalent to running chkdsk /r on them? If not, chkdsk wants to dismount those drives before running. I'm not sure of the implications of dismounting a drive.
Chkdsk /r scans the hard drives for bad sectors and in case there are bad sactors it recovers the readable data.
Yes, it is sufficient to run it.
Thanks a lot for your help. I'm not sure exactly what we found, other than the memory tests good and the C:\ drive (SSD) did a successful repair... whatever that issue was. Oh, and by run it, I assume you mean the windows tool found in the drive properties, not the specific chkdsk /r command?
Shall I mark this solved?
The reason I wonder if there's a difference is that the UI command seems to operate quicker than the chkdsk /r command does. Or maybe I didn't watch long enough to notice.
I'm not sure what command the UI uses and if it even really checks every sector.
Usually a used sector cannot be accessed twice as that could cause trouble.
No more BSODs. I don't know if the original was a fluke or just what.
Let's called it fixed, but not really solved. I consider it solved when I know what caused the issue and apply the appropriate fix!
Quote
