CHKDSK giving different statements?

[Arbiter1170]

So my computer BSOD yesterday, which I found out was due to a faulty driver. This morning I woke up and just figured I would run a chkdsk just for the hell of it, so I did /chkdsk
after it scanned I got this..

The master file tables' attribute is incorrect.
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.

So when I ran chkdsk /scan I got
Windows has scanned the file system and found no problems. No further action is required.

I'm confused, it just said I was going to need to repair them... so why now don't I need to?

 

[Jwpanz]

Try chkdsk /f and see if anything changes. If not, then try chkdsk /offlinescanandfix.

 

[Arbiter1170]

Try chkdsk /f and see if anything changes. If not, then try chkdsk /offlinescanandfix.

Thanks for responding
How long does chkdsk /f take?

 

[Jwpanz]

It depends on how bad the problem is and how much data needs to be processed and corrected. It usually takes some time to finish but it's worth saving your data.

 

[Arbiter1170]

It depends on how bad the problem is and how much data needs to be processed and corrected. It usually takes some time to finish but it's worth saving your data.

Ok, when the scan is done, what should I do then?

 

[Arbiter1170]

Results



Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.


A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
652800 file records processed. File verification completed.
13048 large file records processed. 0 bad file records processed.
Stage 2: Examining file name linkage ...
779088 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered to lost and found.
Stage 3: Examining security descriptors ...
Cleaning up 35 unused index entries from index $SII of file 0x9.
Cleaning up 35 unused index entries from index $SDH of file 0x9.
Cleaning up 35 unused security descriptors.
Security descriptor verification completed.
63145 data files processed. CHKDSK is verifying Usn Journal...
38165032 USN bytes processed. Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

2846028 MB total disk space.
545538908 KB in 576657 files.
331876 KB in 63146 indexes.
0 KB in bad sectors.
850023 KB in use by the system.
65536 KB occupied by the log file.
2312121 MB available on disk.

4096 bytes in each allocation unit.
728583423 total allocation units on disk.
591903222 allocation units available on disk.

Internal Info:
00 f6 09 00 c9 c2 09 00 7e 6d 12 00 00 00 00 00 ........~m......
bc 03 00 00 73 90 00 00 00 00 00 00 00 00 00 00 ....s...........

Windows has finished checking your disk.
Please wait while your computer restarts.

 

[Jwpanz]

Ok, now run chkdsk again to see if you get the same error message you got before.

 

[Arbiter1170]

Ok, now run chkdsk again to see if you get the same error message you got before.

http://i.imgur.com/lEs1q2e.png

 

[Jwpanz]

From the looks of it, your problem seems to have been fixed. That error message is not popping up anymore.

 

[Arbiter1170]

Ok cool! Hopefully that's the end of it!
I'm a little confused though, what exactly even happened if you don't mind me explaining?

Thanks for your help either way .

 

[Jwpanz]

Running a chkdsk /scan performs an "online scan" meaning the disk is mounted. The problem must have only been present when the disk was "offline." Doing a chkdsk /f unmounts the drive and fixes issues. That may have been the reason for the weird returns you were getting. This is also the reason your computer had to restart because chkdsk /f took the disk offline. Rebooting places the disk back online.