ink Posted July 19, 2009 Report Share Posted July 19, 2009 I read other topics about this and how it is usually a sign that the HD is dying.But this is the first time this error happens, so i was wondering if it really is a death sentence to my HD. If the HD is really dying, can i copy the stuff that i have on it to my other HD or the files will get corrupted in the process?This happened when i was downloading using µTorrent, does that mean the file i was downloading got corrupted? Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 Safest way is to not use the drive as much as possible, and get everything off it NOW. If you punch in the drives serial on the manufacturers site it might still be under warranty.I read SMART data can be used to tell if a drive is failing, you can try downloading speedfan and go to the S.M.A.R.T. section, see if any data comes up with anything other then the OK mark.What OS? Link to comment Share on other sites More sharing options...
ink Posted July 19, 2009 Author Report Share Posted July 19, 2009 Vista 64bitIs it possible that the file i was downloading did not get corrupted even though this error occurred? Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 Depends on what the torrent is doing now.Has the error occurred again? If it hasn't might be alright. Have you made any backups of your files? Try Vistas "reliability monitor", Start > type in "perfmon" and press enter > Reliability MonitorIf the drive is going to fail, you should get everything off, now. Link to comment Share on other sites More sharing options...
ink Posted July 19, 2009 Author Report Share Posted July 19, 2009 I copied all the files from the HD to my other HD just in case it really is faulty.When the error occurred, i just told the torrent to start again and it has been normal since then. Is there anything i can do to check if what i already downloaded is corrupted? Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 Stop a torrent, right-click, force re-check.Could fail drive faster if it's going to. Did you check perfmon? Link to comment Share on other sites More sharing options...
ink Posted July 19, 2009 Author Report Share Posted July 19, 2009 I forced a re-check and the error occurred again, it may be a coincidence but after that Firefox was freezing a bit.I did what you told me to do, run perfmon and reliability monitor, but what am i looking for?I only have 2 hard drives, the one this error occurred is the one i am running Windows. I was thinking about transferring all my files from my storage HD to the "faulty" one, install Windows on the storage HD and then get the files back from the faulty HD. Do you think this would be a risky thing to do? Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 It does carry risk, what brand drive is the possibly faulty one? That it happened again isn't really a good sign Link to comment Share on other sites More sharing options...
ink Posted July 19, 2009 Author Report Share Posted July 19, 2009 They are both Western Digital 6400AAKS hard drivesIm going to restart Windows so the reliability tool will display today's date Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 Ok, also check out WD's diagnostic tools: http://support.wdc.com/product/download.asp?wdc_lang=enThat (should) tell you if it really has problems. Be sure to read the test descriptions before you run them. Link to comment Share on other sites More sharing options...
ink Posted July 19, 2009 Author Report Share Posted July 19, 2009 Ok the reliability tools still doesn't show anything about today's date, but the July 18th doesn't seem to have any hardware errors.Shouldn't it be displaying today's events? July 19th? Link to comment Share on other sites More sharing options...
GTHK Posted July 19, 2009 Report Share Posted July 19, 2009 Mine doesn't show today either so it seems to be standard behavior. Try out WD's diagnostic tools, that should be definitive. Link to comment Share on other sites More sharing options...
ink Posted July 20, 2009 Author Report Share Posted July 20, 2009 I did a check disk with Windows and this is what i gotLog Name: ApplicationSource: Microsoft-Windows-WininitDate: 7/19/2009 10:26:02 PMEvent ID: 1001Task Category: NoneLevel: InformationKeywords: ClassicUser: N/AComputer: Description:Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. 105088 file records processed. 349 large file records processed. 0 bad file records processed. 2 EA records processed. 42 reparse records processed. 139682 index entries processed. 0 unindexed files processed. 105088 security descriptors processed. Cleaning up 501 unused index entries from index $SII of file 0x9.Cleaning up 501 unused index entries from index $SDH of file 0x9.Cleaning up 501 unused security descriptors. 17298 data files processed. CHKDSK is verifying Usn Journal... 34904104 USN bytes processed. Usn Journal verification completed.CHKDSK is verifying file data (stage 4 of 5)...Read failure with status 0xc000009c at offset 0x7076e72000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076e76000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076e77000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076e83000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f14000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076f1c000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fad000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fb6000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fb7000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fb9000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fba000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fbb000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fbc000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fbf000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc0000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc1000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc2000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc3000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc4000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc6000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc7000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc8000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc9000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fca000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcb000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcb000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcc000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcc000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcd000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcd000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fce000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcf000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fd0000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fd1000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fd2000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fd4000 for 0x1000 bytes.Windows replaced bad clusters in file 104836of name \Users\Isaac\DOWNLO~1\PROTOT~1\rzr-prot.044. 105072 files processed. File data verification completed.CHKDSK is verifying free space (stage 5 of 5)... 120227297 free clusters processed. Free space verification is complete.Adding 19 bad clusters to the Bad Clusters File.CHKDSK discovered free space marked as allocated in themaster file table (MFT) bitmap.CHKDSK discovered free space marked as allocated in the volume bitmap.Windows has made corrections to the file system. 625129471 KB total disk space. 143946328 KB in 80145 files. 48452 KB in 17299 indexes. 76 KB in bad sectors. 225423 KB in use by the system. 65536 KB occupied by the log file. 480909192 KB available on disk. 4096 bytes in each allocation unit. 156282367 total allocation units on disk. 120227298 allocation units available on disk.Internal Info:80 9a 01 00 ad 7c 01 00 f2 aa 02 00 00 00 00 00 .....|..........49 00 00 00 2a 00 00 00 00 00 00 00 00 00 00 00 I...*...........e0 64 03 77 00 00 00 00 50 23 98 ff 00 00 00 00 .d.w....P#......Windows has finished checking your disk.Please wait while your computer restarts.Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" /> <EventID Qualifiers="16384">1001</EventID> <Version>0</Version> <Level>4</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-07-20T01:26:02.000Z" /> <EventRecordID>2037</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Isaac-PC</Computer> <Security /> </System> <EventData> <Data>Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. 105088 file records processed. 349 large file records processed. 0 bad file records processed. 2 EA records processed. 42 reparse records processed. 139682 index entries processed. 0 unindexed files processed. 105088 security descriptors processed. Cleaning up 501 unused index entries from index $SII of file 0x9.Cleaning up 501 unused index entries from index $SDH of file 0x9.Cleaning up 501 unused security descriptors. 17298 data files processed. CHKDSK is verifying Usn Journal... 34904104 USN bytes processed. Usn Journal verification completed.CHKDSK is verifying file data (stage 4 of 5)...Read failure with status 0xc000009c at offset 0x7076e72000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076e76000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076e77000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076e83000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f14000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076f1c000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fad000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fb6000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076f5d000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fb7000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fb9000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fba000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fbb000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fbc000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fbf000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc0000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc1000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc2000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc3000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc4000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc6000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc7000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fc8000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fc9000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fca000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcb000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcb000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcc000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcc000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fcd000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcd000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fce000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fcf000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fd0000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fd1000 for 0x1000 bytes.Read failure with status 0xc000009c at offset 0x7076fd2000 for 0x10000 bytes.Read failure with status 0xc000009c at offset 0x7076fd4000 for 0x1000 bytes.Windows replaced bad clusters in file 104836of name \Users\Isaac\DOWNLO~1\PROTOT~1\rzr-prot.044. 105072 files processed. File data verification completed.CHKDSK is verifying free space (stage 5 of 5)... 120227297 free clusters processed. Free space verification is complete.Adding 19 bad clusters to the Bad Clusters File.CHKDSK discovered free space marked as allocated in themaster file table (MFT) bitmap.CHKDSK discovered free space marked as allocated in the volume bitmap.Windows has made corrections to the file system. 625129471 KB total disk space. 143946328 KB in 80145 files. 48452 KB in 17299 indexes. 76 KB in bad sectors. 225423 KB in use by the system. 65536 KB occupied by the log file. 480909192 KB available on disk. 4096 bytes in each allocation unit. 156282367 total allocation units on disk. 120227298 allocation units available on disk.Internal Info:80 9a 01 00 ad 7c 01 00 f2 aa 02 00 00 00 00 00 .....|..........49 00 00 00 2a 00 00 00 00 00 00 00 00 00 00 00 I...*...........e0 64 03 77 00 00 00 00 50 23 98 ff 00 00 00 00 .d.w....P#......Windows has finished checking your disk.Please wait while your computer restarts.</Data> </EventData></Event>Can anyone translate this? I also noticed that there is something about bad clusters in the file i was downloading? Link to comment Share on other sites More sharing options...
GTHK Posted July 20, 2009 Report Share Posted July 20, 2009 0xC000009C or STATUS_DEVICE_DATA_ERROR: Bad blocks on the hard disk.You're toast. Link to comment Share on other sites More sharing options...
ink Posted July 20, 2009 Author Report Share Posted July 20, 2009 Dang, well what do you think i should do? I have like 111gb of data in my storage drive and that would take like 30 dvd's to backup.Do you think i should copy them to the faulty drive and do what i said before? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.