- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Error Checking (Local C:) through File Explorer vs. Going through the CMD Prompt and using ChkDsk C: /X /R

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I ran the Avast Boot-scan ... 2 hrs 15 min ... 1,388,333 files ... 30,668 folders ... 147.1 GB tested ... and it said that some files could not be scanned! . . .

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

File C:\Windows\System32\DriverStore\FileRepository\
prncacla.inf_x86_a1db56e3f12f57a9\
I386\
CNBJ2530.DPB|>_5_Kolt50vpJyqlets20vm3zt2n4b Error 0xC000009C {STATUS_DEVICE_DATA_ERROR}
Error: Data error (cyclic redundancy check)(23)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

It appears to be a Canon printer, with a hashtag mismatch, from a faulty Win 8.1 Update. There are lots of question about this out there, but I think with other errors.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I ran the following, and this didn't fix it:

C:\>dism /online /cleanup-image /restorehealth

and

C:\>sfc /scannow

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I found this link . . . Boot Scan discovers these errors . . . https://forum.avast.com/index.php?topic=141883.0

I ran chkdsk c: /x / r . . . and that fixed it:

avast boot scan ... 2 hrs 12 min ... 1,385,205 files ... 30,331 folders ... 147.6 GB tested

QUESTION #1
There are no useful statistics for "chkdsk c: /x / r" shown in the Event Viewer that I can find. Just that the drive is healthy. Why?

QUESTION #2
Is the /x switch necessary in my case, or is that for something else?

QUESTION #3
Is there a way to see what ChkDsk is doing when running, or has done, after completed? Info used to flash on the screen, now, it just gives you a percentage completed. It's better if they let you see that it's doing something, and what it is, so you know that it hansn't hung.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

I quit running ChkDsk when I got Win 8 / 8.1, because it looked like they had changed it . . . Error Checking only took 1 minute vs. 90 minutes, to run through the File Explorer . . . It looked like the drive was being kept perpetually Error free, just like Defrag was doing . . . I used to run ChkDsk monthly. I think I'll start doing that again, maybe, once every 6 months.

QUESTION #4
What's the difference between these two ways of error checking?

QUESTION #5
Why does the File Explorer way give you statistics in the Event Viewer (please see below), and tell you that nothing is wrong (I just look to see if there are and BAD Sectors), when there *is* something wrong . . . and then the Command Prompt way fixes it, but doesn't give you any useful info in the Event Viewer, other than that the drive is "healthy?"

- - - - - - - - - - - -

I used to run this:

C:\WINDOWS\system32\defrag.exe m: -v>"c:\Documents and Settings\Administrator\Desktop\defrag m.txt"
ECHO y|CHKDSK M: /X/R
SHUTDOWN -r

Defrag has the -v switch for verbose output, but not Chkdsk . . . I forget how I found out to use a hyphen in front of -v, and the rest of ths Syntax, this was back with XP.

- - - - - - - - - - - -

QUESTION #6
Is the drive really being kept Defragged below 2% all the time per looking at it in File Explorer, or is that another lie? LOL

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Log Name: Application
Source: Chkdsk
Date: 10/11/2014 8:10:52 AM
Event ID: 26226
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: USER
Description:
Chkdsk was executed in scan mode on a volume snapshot.

Checking file system on C:

Stage 1: Examining basic file system structure ...

288768 file records processed.

File verification completed.

2067 large file records processed.

0 bad file records processed <------- I LOOK AT THIS, IT USED TO SAY IN THE NUMBERS BELOW, BUT I DON'T THINK IT'S THERE ANYMORE

Stage 2: Examining file name linkage ...

343672 index entries processed.

Index verification completed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.

27453 data files processed.

CHKDSK is verifying Usn Journal...

36290752 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

155929599 KB total disk space.
64693408 KB in 161072 files.
100556 KB in 27454 indexes.
397503 KB in use by the system.
65536 KB occupied by the log file.
90738132 KB available on disk.

4096 bytes in each allocation unit.
38982399 total allocation units on disk.
22684533 allocation units available on disk.

----------------------------------------------------------------------