Data error (cyclic redundancy check)

I

IsaacMM

Gawd
Joined
Jun 9, 2008
Messages
646
I was downloading a file on µTorrent and i got this error. I've read a bit about it on µTorrent forums, but people there were kinda making a huge deal out of it, saying this means the HD is dying, like a death sentence.

I want to know if it really is that big of a deal and if, considering that it is the first time i get this error and everything is running fine, it actually means that the HD is dying.

My HD is not even 1 year old :(
 
Force a recheck on the torrent. Not always does the data come in correctly. Or the software was ripped improperly because most contributors to public trackers usually don't have a clue. If it was your hard drive there would be more issues than just this.
 
With SATA drives, CRC is used on command and data packets transferred to and from the disk mainly to insure integrity of the data bus. A bad or faulty cable (or connection) would result in a CRC error. I'm sure your disk is OK.
 
Auzner said:
Force a recheck on the torrent. Not always does the data come in correctly. Or the software was ripped improperly because most contributors to public trackers usually don't have a clue. If it was your hard drive there would be more issues than just this.
Click to expand...

I forced a re-check on the torrent and the error appeared again, what does that mean?
 
I did a check disk with Windows and this is the log i got

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 7/19/2009 10:26:02 PM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer:
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 104836
of 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 the
master 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 104836
of 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 the
master 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>
Click to expand...

It reported something about bad clusters on the file i was downloading, other then that i don't really know what that report is saying, can anyone help me?
 
Files do not have clusters.
It reported that your hard drive has bad clusters/sectors and has removed any data from them and marked them as bad so they cannot be used again.
The data that was copied from them (and placed elsewhere on the drive) may have had errors.
If the error correction wasnt able to handle the corruption, it will still have errors and you may need to get those file(s) again.

Note that the bad sectors have been replaced with spare sectors set aside for when some go bad, so your drives capacity shouldnt reduce.
This means that the drive should operate fine now.

Sometimes bad sectors (which are parts of the magnetic surface that dont hold the magnetic charge as well as they should) can spread to adjacent sectors if they are due to a defect in the magnetic medium preventing it from holding its magnetic charge for very long.
This can be from physical damage or from a bad platter in the drive.
This is unfortunate if it happens.
You will know because more bad sectors will appear.

It is expected that there will be bad sectors that are mapped out so they cannot be used.
If not, there would be a hell of a lot more drive failures.
 
I only own 2 hard drives, one for Windows and one for storage, do you think it would be risky to transfer all the files from the storage drive to the Windows drive, then install Windows on the storage drive and then transfer all the files from the faulty HD to the other?
 
Is there a need?
If the drive is not giving any more errors, then its working fine.
 
What if new errors pop up later? Better be safe than sorry. Make you monitor the status of your drive carefully. And have backups if the data is important.
 
You must log in or register to reply here.
Back
Top