Interpreting CHKDSK log file

[feanor1024]

My PC froze with a 0x000000f4 stop error. I was just browsing in Firefox and chatting in AIM at the time.

I rebooted and checked the event viewer and found this: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume C:.

I ran CHKDSK, but it said C: was locked and asked if it could run at boot. I hit N and rebooted. Windows ran CHKDSK anyway. The results are at the bottom of my post. I'm running XP Pro SP2 and the hard drive in question is a Western Digital 160GB IDE (listed as WD1600JB-00EVA0 under device manager). I'm wondering if this is just a one time thing or if my hard drive is going south. Should I run the Western Digital diagnostics or a surface test in Scandisk or something else?

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


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
Deleting orphan file record segment 136907.
The multi-sector header signature for VCN 0x1 of index $I30
in file 0x49a5 is incorrect.
24 7b 24 80 24 8c 4a 87 6f a5 7d 87 5e a7 34 80 ${$.$.J.o.}.^.4.
22 a0 25 79 22 a0 30 79 63 a1 97 73 ad 83 96 77 ".%y".0yc..s...w
Correcting error in index $I30 for file 18853.
The index bitmap $I30 in file 0x49a5 is incorrect.
Correcting error in index $I30 for file 18853.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 77 44 00 00 00 00 01 00 ........wD......
00 8e 00 ea de 05 c4 01 00 8e 00 ea de 05 c4 01 ................
Sorting index $I30 in file 18853.
The multi-sector header signature for VCN 0x1 of index $I30
in file 0x21512 is incorrect.
56 78 29 82 24 80 24 80 24 75 23 80 28 78 59 84 Vx).$.$.$u#.(xY.
9f 7d c3 87 ce 78 be 83 9d 8a 85 8e 91 9f bc 88 .}...x..........
Correcting error in index $I30 for file 136466.
The index bitmap $I30 in file 0x21512 is incorrect.
Correcting error in index $I30 for file 136466.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff d4 fe 28 1d ec 88 c5 01 ..........(.....
32 5f a3 e4 eb 88 c5 01 00 80 02 00 00 00 00 00 2_..............
Sorting index $I30 in file 136466.
Index entry A0025763.inf of index $I30 in file 0x214d1 points to unused file 0x216ca.
Deleting index entry A0025763.inf in index $I30 of file 136401.
Index entry A0025764.PNF of index $I30 in file 0x214d1 points to unused file 0x216cb.
Deleting index entry A0025764.PNF in index $I30 of file 136401.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file S32LUWI1.DLL (18857) into directory file 18853.
Recovering orphaned file S32LIVE1.DLL (18858) into directory file 18853.
Recovering orphaned file S32LUIS1.DLL (18859) into directory file 18853.
Recovering orphaned file S32LUCP1.CPL (18860) into directory file 18853.
Recovering orphaned file README.TXT (18867) into directory file 18853.
Recovering orphaned file SYMANT~1.EXE (18875) into directory file 18853.
Recovering orphaned file SymantecRootInstaller.exe (18875) into directory file 18853.
Recovering orphaned file SYMANT~1.LOG (19087) into directory file 18853.
Recovering orphaned file SymantecRootInstaller.log (19087) into directory file 18853.
Recovering orphaned file PRODUC~1.DLL (130379) into directory file 18853.
Recovering orphaned file ProductRegCom_2_6.DLL (130379) into directory file 18853.
Recovering orphaned file PRODUC~2.DLL (130652) into directory file 18853.
Recovering orphaned file ProductRegComPS_2_6.DLL (130652) into directory file 18853.
Recovering orphaned file SETTIN~1.LIV (130658) into directory file 18853.
Recovering orphaned file Settings.Default.LiveUpdate (130658) into directory file 18853.
Recovering orphaned file NETDET~1.DLL (130731) into directory file 18853.
Recovering orphaned file NetDetectController_2_6.DLL (130731) into directory file 18853.
Recovering orphaned file PEGCLI~1.DLL (130734) into directory file 18853.
Recovering orphaned file pegclient.DLL (130734) into directory file 18853.
Recovering orphaned file PEGCOM~1.DLL (130735) into directory file 18853.
Recovering orphaned file pegcommon.DLL (130735) into directory file 18853.
Recovering orphaned file WINLUP~1.JAR (130737) into directory file 18853.
Recovering orphaned file winluproviderinst.jar (130737) into directory file 18853.
Recovering orphaned file PROVID~1.JAR (130739) into directory file 18853.
Recovering orphaned file providerInst.jar (130739) into directory file 18853.
Recovering orphaned file SESASE~1.LIV (130740) into directory file 18853.
Recovering orphaned file SESA.Settings.LiveUpdate (130740) into directory file 18853.
Recovering orphaned file UNRAR.DLL (130741) into directory file 18853.
Recovering orphaned file tcscan7.dat (136676) into directory file 136466.
Recovering orphaned file tcscan8.dat (136678) into directory file 136466.
Recovering orphaned file tcscan9.dat (136698) into directory file 136466.
Recovering orphaned file v.grd (136811) into directory file 136466.
Recovering orphaned file v.sig (136812) into directory file 136466.
Recovering orphaned file virscan1.dat (136909) into directory file 136466.
Recovering orphaned file virscan2.dat (136929) into directory file 136466.
Recovering orphaned file virscan3.dat (136935) into directory file 136466.
Recovering orphaned file virscan4.dat (136937) into directory file 136466.
Recovering orphaned file virscan5.dat (136938) into directory file 136466.
Recovering orphaned file virscan6.dat (137133) into directory file 136466.
Recovering orphaned file virscan7.dat (137153) into directory file 136466.
Recovering orphaned file virscan8.dat (137162) into directory file 136466.
Recovering orphaned file virscan9.dat (137163) into directory file 136466.
Recovering orphaned file virscan.inf (137164) into directory file 136466.
Recovering orphaned file whatsnew.txt (137165) into directory file 136466.
Recovering orphaned file technote.txt (137167) into directory file 136466.
Recovering orphaned file zdone.dat (137168) into directory file 136466.
Recovering orphaned file tinf.dat (137170) into directory file 136466.
Recovering orphaned file tinfidx.dat (137171) into directory file 136466.
Recovering orphaned file tinfl.dat (137172) into directory file 136466.
Recovering orphaned file tscan1.dat (137173) into directory file 136466.
Recovering orphaned file tscan1hd.dat (137174) into directory file 136466.
Cleaning up 73 unused index entries from index $SII of file 0x9.
Cleaning up 73 unused index entries from index $SDH of file 0x9.
Cleaning up 73 unused security descriptors.
CHKDSK discovered free space marked as allocated in the
master file table (MFT) bitmap.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

156280288 KB total disk space.
119280828 KB in 148721 files.
51540 KB in 9439 indexes.
0 KB in bad sectors.
231784 KB in use by the system.
65536 KB occupied by the log file.
36716136 KB available on disk.

4096 bytes in each allocation unit.
39070072 total allocation units on disk.
9179034 allocation units available on disk.

Internal Info:
80 74 02 00 db 69 02 00 8a 90 03 00 00 00 00 00 .t...i..........
4a 08 00 00 00 00 00 00 1a 02 00 00 00 00 00 00 J...............
06 59 cd 05 00 00 00 00 3c ea 3d 73 00 00 00 00 .Y......<.=s....
74 00 4c 03 00 00 00 00 00 00 00 00 00 00 00 00 t.L.............
00 00 00 00 00 00 00 00 0a 96 0b 86 00 00 00 00 ................
99 9e 36 00 00 00 00 00 80 35 08 00 f1 44 02 00 ..6......5...D..
00 00 00 00 00 f0 52 70 1c 00 00 00 df 24 00 00 ......Rp.....$..

 

[zandor]

Have you done anything to Symantec/Norton Antivirus lately? Looks like the affected files are all in 2 directories, and the names indicate they have something to do with Norton. Sometimes viruses, etc. try to disable or eliminate antivirus software.
First thing I'd do is check for viruses, etc. Then run the WD diag utility.
It's possible your disk is going, but since its not reporting any bad sectors you'll have to rely on the diagnostic to find out unless it's exhibiting other strange behaviour. Of course, it's entirely possible that the whole mess was caused by a software error. AV programs tend to dig around in the guts of the OS a bit, and it's entirely possible your AV program caused the problem & blasted itself in the process.

 

[feanor1024]

For the past few days one of its executables, ccapp, has been freezing when I restart or shut down. I haven't changed anything though. Just now I uninstalled and reinstalled Symantec, but ccapp still freezes.

I really don't like Symantec, but my university provides it for us for free. You have to run both of these registry files after installing it
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005042710304248
http://service1.symantec.com/SUPPORT/ent-security.nsf/pfdocs/2002071208532048

 

[barrubba]

same 0000f4 error, so 5 and 11 event id in event viewer, no error during WD datalife test, but chkdsk show that mwssage:

Tipo evento: Informazioni
Origine evento: Winlogon
Categoria evento: Nessuno
ID evento: 1001
Data: 02/01/2010
Ora: 17.22.21
Utente: N/D
Computer: QUAD
Descrizione:
Checking file system on C:
The type of the file system is NTFS.


One of your disks needs to be checked for consistency. You
may cancel the disk check, but it is strongly recommended
that you continue.
Windows will now check the disk.
The multi-sector header signature for VCN 0x0 of index $I30
in file 0xd3d is incorrect.
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Correcting error in index $I30 for file 3389.
The index bitmap $I30 in file 0xd3d is incorrect.
Correcting error in index $I30 for file 3389.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00 ................
ff ff ff ff ff ff ff ff 00 4e 25 b6 0f 0c c8 01 .........N%.....
00 4e 25 b6 0f 0c c8 01 d2 3c f2 42 2e 4f c9 01 .N%......<.B.O..
Sorting index $I30 in file 3389.
Index entry c9207.ipi of index $I30 in file 0x12f1 points to unused file 0x16f78.
Deleting index entry c9207.ipi in index $I30 of file 4849.
Index entry MSIA.tmp of index $I30 in file 0x12f1 points to unused file 0x17993.
Deleting index entry MSIA.tmp in index $I30 of file 4849.
Index entry MSIEXEC.EXE-054243A6.pf of index $I30 in file 0x2f92 points to unused file 0xe43b.
Deleting index entry MSIEXEC.EXE-054243A6.pf in index $I30 of file 12178.
Index entry MSIEXE~2.PF of index $I30 in file 0x2f92 points to unused file 0xe43b.
Deleting index entry MSIEXE~2.PF in index $I30 of file 12178.
Unable to locate the file name attribute of index entry change.log
of index $I30 with parent 0xb667 in file 0x732.
Deleting index entry change.log in index $I30 of file 46695.
Unable to locate the file name attribute of index entry resume.dat
of index $I30 with parent 0xd8f3 in file 0xe5ee.
Deleting index entry resume.dat in index $I30 of file 55539.
Index entry resume.dat.old of index $I30 in file 0xd8f3 points to unused file 0xe43b.
Deleting index entry resume.dat.old in index $I30 of file 55539.
Index entry RESUME~1.OLD of index $I30 in file 0xd8f3 points to unused file 0xe43b.
Deleting index entry RESUME~1.OLD in index $I30 of file 55539.
Cleaning up minor inconsistencies on the drive.
CHKDSK is recovering lost files.
Recovering orphaned file CHANGE~1.3 (1842) into directory file 46695.
Recovering orphaned file change.log.3 (1842) into directory file 46695.
Recovering orphaned file resume.dat (10575) into directory file 55539.
Recovering orphaned file RESUME~1.OLD (58862) into directory file 55539.
Recovering orphaned file resume.dat.old (58862) into directory file 55539.
Recovering orphaned file E1783F~1 (58872) into directory file 56952.
Recovering orphaned file E1783F54d01 (58872) into directory file 56952.
Cleaning up 182 unused index entries from index $SII of file 0x9.
Cleaning up 182 unused index entries from index $SDH of file 0x9.
Cleaning up 182 unused security descriptors.
CHKDSK is verifying Usn Journal...
The USN Journal length 0x185016768 in file 0x130ae is less the
largest USN encountered, 0x185018b10, plus eight in file 0x2f79.
Repairing Usn Journal $J data stream.
Usn Journal verification completed.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.
Windows has made corrections to the file system.

72597703 KB total disk space.
67879236 KB in 210203 files.
85596 KB in 20317 indexes.
0 KB in bad sectors.
392319 KB in use by the system.
65536 KB occupied by the log file.
4240552 KB available on disk.

4096 bytes in each allocation unit.
18149425 total allocation units on disk.
1060138 allocation units available on disk.

Internal Info:
b0 d6 03 00 81 84 03 00 5d bc 05 00 00 00 00 00 ........].......
39 03 00 00 02 00 00 00 8f 03 00 00 00 00 00 00 9...............
7e 2f 53 13 00 00 00 00 0c 87 a0 62 00 00 00 00 ~/S........b....
78 11 de 15 00 00 00 00 00 00 00 00 00 00 00 00 x...............
00 00 00 00 00 00 00 00 8a 67 fc 8e 00 00 00 00 .........g......
40 63 59 8f 00 00 00 00 bc 41 0a 00 01 00 00 00 @cY......A......
d8 1b 00 00 01 00 00 00 60 3d 0b 00 00 00 00 00 ........`=......


It' a cable problem? software? mb? power supply or i need to reinstall windows ???

help me..i must work on pc!