Windows 7 chkdsk help and bsod error

exocytosisbc

New Member
Joined
Dec 21, 2013
I've always been getting blue screens, but they're starting to become more and more frequent. I haven't been able to use my laptop for more than a day without one showing up! The stop codes I've been getting are 0x0000000A and 0x0000001E. I tried running a chkdsk and it told me it would during the next start up because the volume is in use. So at the next start up it ran chkdsk without fixing or repairing anything. The event properties for the last check is:

Chkdsk was executed in read-only mode. A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.

Checking file system on C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
253696 file records processed. File verification completed.
770 large file records processed. 0 bad file records processed. 0 EA records processed. 45 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
324886 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
253696 file SDs/SIDs processed. Cleaning up 6 unused index entries from index $SII of file 0x9.
Cleaning up 6 unused index entries from index $SDH of file 0x9.
Cleaning up 6 unused security descriptors.
Security descriptor verification completed.
35596 data files processed. CHKDSK is verifying Usn Journal...
37438680 USN bytes processed. Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

609840127 KB total disk space.
76615276 KB in 217140 files.
160092 KB in 35597 indexes.
0 KB in bad sectors.
376491 KB in use by the system.
65536 KB occupied by the log file.
532688268 KB available on disk.

4096 bytes in each allocation unit.
152460031 total allocation units on disk.
133172067 allocation units available on disk.




Is there any way to close the processes that prevent chkdsk from working manually? Because it won't fix anything at the reboots. I just can't for the life of me figure out how to make chkdsk c: /f work.
I'm really new to trying to fix things like this, excuse me for not knowing what something may mean. Please help, thank you.
 
Just ran chkdsk once more and came up with this




Chkdsk was executed in read-only mode on a volume snapshot.

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

WARNING! F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
253952 file records processed. File verification completed.
773 large file records processed. 0 bad file records processed. 0 EA records processed. 45 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)...
325208 index entries processed. Index verification completed.
0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 3)...
253952 file SDs/SIDs processed. Cleaning up 18 unused index entries from index $SII of file 0x9.
Cleaning up 18 unused index entries from index $SDH of file 0x9.
Cleaning up 18 unused security descriptors.
Security descriptor verification completed.
35629 data files processed. CHKDSK is verifying Usn Journal...
34959984 USN bytes processed. Usn Journal verification completed.
Windows has checked the file system and found no problems.

609840127 KB total disk space.
76449436 KB in 212736 files.
158004 KB in 35630 indexes.
0 KB in bad sectors.
374455 KB in use by the system.
65536 KB occupied by the log file.
532858232 KB available on disk.

4096 bytes in each allocation unit.
152460031 total allocation units on disk.
133214558 allocation units available on disk.
 
The fact that you have no bad sectors is a good sign. For the repair to the filesystem to take place you should follow @kemical's instructions. Should you start receiving bad sector reports, this would indicate a serious physical malfunction with the disk. The filesystem corruption is likely happening as a result of the kernel crashes (BSOD).
 
Back
Top Bottom