[Relocated] Hard drive help! with sectors and clusters.

AzureEd · 11-13-2007, 04:56 PM

Hi all..Does anyone know what this means? I ran CHKDSK and had this log file and my internet browser[firefox] started hanging after I ran CHKDSK. Spybot search and destroy also stopped working as well.

Heres the CHKDSK log..alot of hard drive errors..And my laptop running microsoft windows xp is relatively new..1 year.

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

A disk check has been scheduled.
Windows will now check the disk.
Cleaning up minor inconsistencies on the drive.
Cleaning up 64 unused index entries from index $SII of file 0x9.
Cleaning up 64 unused index entries from index $SDH of file 0x9.
Cleaning up 64 unused security descriptors.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
Read failure with status 0xc000009c at offset 0xc0b6d9000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xc0b6d9000 for 0x1000 bytes.
Windows replaced bad clusters in file 7144
of name \PROGRA~1\SPYBOT~1\SpybotSD.exe.
Read failure with status 0xc000009c at offset 0xc05ffb000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xc05ffe000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xc0673f000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xc0674c000 for 0x1000 bytes.
Windows replaced bad clusters in file 22214
of name \DOCUME~1\Ed\MYDOCU~1\AZUREU~1\THEGRU~1.XVI\SPH-TH~1.R02.
Read failure with status 0xc000009c at offset 0xade040000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade046000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade087000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade094000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade0d5000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade0e1000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade122000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade12f000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade170000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade17c000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade1bd000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade1c9000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade1ca000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade1ca000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade20b000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade217000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade258000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade264000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade305000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade308000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade349000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade356000 for 0x1000 bytes.
Read failure with status 0xc000009c at offset 0xade397000 for 0x10000 bytes.
Read failure with status 0xc000009c at offset 0xade3a3000 for 0x1000 bytes.
Windows replaced bad clusters in file 27227
of name \DOCUME~1\Ed\MYDOCU~1\AZUREU~1\HARRYP~1.INT\TD-HP3~1.R20.
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
Adding 302 bad clusters to the Bad Clusters File.
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.

72589670 KB total disk space.
48709532 KB in 44284 files.
20772 KB in 4631 indexes.
1208 KB in bad sectors.
233446 KB in use by the system.
65536 KB occupied by the log file.
23624712 KB available on disk.

4096 bytes in each allocation unit.
18147417 total allocation units on disk.
5906178 allocation units available on disk.

Internal Info:
c0 f3 00 00 1f bf 00 00 b8 08 01 00 00 00 00 00 ................
18 2f 00 00 01 00 00 00 f2 00 00 00 00 00 00 00 ./..............
12 1c 4b 04 00 00 00 00 e0 97 2b 2a 00 00 00 00 ..K.......+*....
6a 74 26 05 00 00 00 00 10 49 ef 52 05 00 00 00 jt&......I.R....
da d5 30 7d 06 00 00 00 f4 90 2e 18 0c 00 00 00 ..0}............
99 9e 36 00 00 00 00 00 a0 38 07 00 fc ac 00 00 ..6......8......
00 00 00 00 00 70 fe 9c 0b 00 00 00 17 12 00 00 .....p..........

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

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---------------------------------------------------------------
Firefox hangs, I found the information in the event viewer.

Hanging application firefox.exe, version 1.8.20071.2514, hang module hungapp, version 0.0.0.0, hang address 0x00000000.

Faulting application firefox.exe, version 1.8.20071.2514, faulting module unknown, version 0.0.0.0, fault address 0x00000002.

One of them was not a hang but an application error
--------------------------------------------------------------
Spybot hangs, Kernel32.dll failing seems like a bad sign.=/

Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.

Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33.
----------------------------------------------------------
Seems the three errors originate in the same address and offset, These spybot errors are all individual.
-----------------------------------------------------------

Could these errors be here because the installed applications are installed in 'marked' clusters when I ran chkdsk?

This all happened today.

Thanks in advance for your advice and knowledge all.

11-13-2007, 04:56 PM	#1 (permalink)
AzureEd Registered User Join Date: Nov 2007 Posts: 3 OS: Windows	[Relocated] Hard drive help! with sectors and clusters. Hi all..Does anyone know what this means? I ran CHKDSK and had this log file and my internet browser[firefox] started hanging after I ran CHKDSK. Spybot search and destroy also stopped working as well. Heres the CHKDSK log..alot of hard drive errors..And my laptop running microsoft windows xp is relatively new..1 year. Checking file system on C: The type of the file system is NTFS. Volume label is IBM_PRELOAD. A disk check has been scheduled. Windows will now check the disk. Cleaning up minor inconsistencies on the drive. Cleaning up 64 unused index entries from index $SII of file 0x9. Cleaning up 64 unused index entries from index $SDH of file 0x9. Cleaning up 64 unused security descriptors. CHKDSK is verifying Usn Journal... Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Read failure with status 0xc000009c at offset 0xc0b6d9000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xc0b6d9000 for 0x1000 bytes. Windows replaced bad clusters in file 7144 of name \PROGRA~1\SPYBOT~1\SpybotSD.exe. Read failure with status 0xc000009c at offset 0xc05ffb000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xc05ffe000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xc0673f000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xc0674c000 for 0x1000 bytes. Windows replaced bad clusters in file 22214 of name \DOCUME~1\Ed\MYDOCU~1\AZUREU~1\THEGRU~1.XVI\SPH-TH~1.R02. Read failure with status 0xc000009c at offset 0xade040000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade046000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade087000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade094000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade0d5000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade0e1000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade122000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade12f000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade170000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade17c000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade1bd000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade1c9000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade1ca000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade1ca000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade20b000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade217000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade258000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade264000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade305000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade308000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade349000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade356000 for 0x1000 bytes. Read failure with status 0xc000009c at offset 0xade397000 for 0x10000 bytes. Read failure with status 0xc000009c at offset 0xade3a3000 for 0x1000 bytes. Windows replaced bad clusters in file 27227 of name \DOCUME~1\Ed\MYDOCU~1\AZUREU~1\HARRYP~1.INT\TD-HP3~1.R20. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. Adding 302 bad clusters to the Bad Clusters File. 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. 72589670 KB total disk space. 48709532 KB in 44284 files. 20772 KB in 4631 indexes. 1208 KB in bad sectors. 233446 KB in use by the system. 65536 KB occupied by the log file. 23624712 KB available on disk. 4096 bytes in each allocation unit. 18147417 total allocation units on disk. 5906178 allocation units available on disk. Internal Info: c0 f3 00 00 1f bf 00 00 b8 08 01 00 00 00 00 00 ................ 18 2f 00 00 01 00 00 00 f2 00 00 00 00 00 00 00 ./.............. 12 1c 4b 04 00 00 00 00 e0 97 2b 2a 00 00 00 00 ..K.......+*.... 6a 74 26 05 00 00 00 00 10 49 ef 52 05 00 00 00 jt&......I.R.... da d5 30 7d 06 00 00 00 f4 90 2e 18 0c 00 00 00 ..0}............ 99 9e 36 00 00 00 00 00 a0 38 07 00 fc ac 00 00 ..6......8...... 00 00 00 00 00 70 fe 9c 0b 00 00 00 17 12 00 00 .....p.......... Windows has finished checking your disk. Please wait while your computer restarts. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. --------------------------------------------------------------- Firefox hangs, I found the information in the event viewer. Hanging application firefox.exe, version 1.8.20071.2514, hang module hungapp, version 0.0.0.0, hang address 0x00000000. Faulting application firefox.exe, version 1.8.20071.2514, faulting module unknown, version 0.0.0.0, fault address 0x00000002. One of them was not a hang but an application error -------------------------------------------------------------- Spybot hangs, Kernel32.dll failing seems like a bad sign.=/ Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33. Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33. Faulting application spybotsd.exe, version 1.5.1.15, faulting module kernel32.dll, version 5.1.2600.2180, fault address 0x0001eb33. ---------------------------------------------------------- Seems the three errors originate in the same address and offset, These spybot errors are all individual. ----------------------------------------------------------- Could these errors be here because the installed applications are installed in 'marked' clusters when I ran chkdsk? This all happened today. Thanks in advance for your advice and knowledge all.