Volume bitmap is incorrect - just an error in the error checking diagnostics or symptomatic of a deeper issue?
My system is:
Vista Home Premium SP2 on a Dell Inspiron Pentium (R) Dual-Core CPU T4200 @2.00Ghz 2.00 Ghz, Ram is 3.00 GB. Machine is one year and seven months out of the box, had a minor run in with some malware trying to pass itself off as a virus scanner back in January but that was easily got rid of [or appears to have been easy to get rid of], and apart from this I've had no problems with my machine...
However, since installing the windows live 2011 update back in September a number of issues have affected my laptop, initially they were limited to messenger not working [simple change of LAN settings sorted this out, and now works irrespective of LAN settings] and Soulseek becoming inoperative [still not working for me despite a number of attempts at finding a solution, seems to be a port/router related issue, perhaps], recently I had a brief encounter with a blue screen [fraction of a second before vanishing and not returning since] and some significant slow down issues after logging in during startup, this latter issue may have been to do with a cycbot infection which hung around for a while no matter what I tried to do with it in Security Essentials, but now appears to have finally disappeared [I hope actually disappeared as in no longer infecting my machine].
Since the messenger issue I've run a number of chkdsk and similar diagnostics via f8 and booting from disc options as initially chkdsk would reach 9% then stop and my C: error checking or defrag options went nowhere.
I persisted with attempting to get a full error check and defrag via Defraggler and running various permutations of f8 diagnostic/repair options including the windows memory diagnostic tool and start up repair [worked a few times, now see below] as well as the most thorough of the disk scan options [name escapes me] and things appear to be ok, however whenever I try and get chkdsk to run at start up it displays this message:
This type of volume is NTFS
Cannot open for direct access
Windows has finished checking the disc
When I run chkdsk after start up and login is complete I get this message:
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
185856 file records processed.
File verification completed.
759 large file records processed.
0 bad file records processed.
0 EA records processed.
66 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
234524 index entries processed.
Index verification completed.
0 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
185856 security descriptors processed.
Security descriptor verification completed.
24335 data files processed.
CHKDSK is verifying Usn Journal...
36513376 USN bytes processed.
Usn Journal verification completed.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.
140888919 KB total disk space.
50447388 KB in 143921 files.
90476 KB in 24336 indexes.
0 KB in bad sectors.
297563 KB in use by the system.
65536 KB occupied by the log file.
90053492 KB available on disk.
4096 bytes in each allocation unit.
35222229 total allocation units on disk.
22513373 allocation units available on disk.
What does 'The Volume Bitmap is incorrect' mean, how would it become 'incorrect' and how do I go about attempting to fix it?
Running sfc /scannow produces this result:
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
even though no other issue besides the bitmap problem is reported by any of the diagnostics, on attempting to run:
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >%userprofile%\Desktop\sfcdetails.txt
in the cmd I'm told:
FINDSTR: Cannot open Stay
FINDSTR: Cannot open Puft\Desktop\sfcdetails.txt
Could the problem be in the error checking and in some way this glitch is affecting other things?
When I try to repair my system from disc I'm told there's no saved pre-problem setting the repair can refer back to.
The problem with my f8 options is that startup repair is saying it cannot do anything due to something recently having been plugged in to the laptop...
I'm not keen on going for a complete reinstall unless it's absolutely necessary.
Have cleared my registry, deleted any redundant files including the sneaky ones that hide out of sight from uninstall options etc. and got a 100% defrag process done...
At present besides these [slight?] chkdsk type issues and the Soulseek problem nothing else appears to be affected on my machine.
Thanks for any advice in advance.