CRC ERROR = Cylic Redundancy Check -- WHY

[MatrixmaN]

I've been getting alot of errors over the last couple months but it has been escalating to the point of major irritation and it is halting any productive efficiency I could possibly muster.

It started with some game CD's....games wouldnt install due to a CRC error in relation to (usually) .cab files... like Data1.cab for instance. This problem only happened on a select few game CD's so I let it pass as a fluke on the cd or cdrom. I could install the software fine on the other networked computers...only mine was the Evil CRC Demon.

Now recently a newer, more irritating problem has arisen.

The CRC errors now affect Zip files....and has even currently escalated to installers...STILL involving .cab files, tho sometimes others. I can't even open some zip files any more due to these Cylic Redundancy Check errors. This nullifies the idea that it could have been my CDROM drives since I downloaded some CRC Zips off the net.

Help me, Im confused, bewildered and pissed.

Thanks.

[rpertusio]

Suggestions/ideas:

(1) You may have corruption on your hard drive, which makes the files 'wrong'. Check your event logs for errors/warnings (Start Menu -> Run... -> eventvwr.msc )

(2) Your downloads are corrupt... just re-download. It could be coincidental that they are giving a CRC error. Might also be your ISP/modem/line quality, etc...

(3) Check the jumpers on the back of your drives, and make sure they are correct. (Slave/Master/CS, etc)

- rp

[kronkus]

I've been getting inconsistent CRC errors from winRAR, for example I'll retest the archive and each time different files within the archive will return a CRC error. Could it be similar problems to the ones rpertusio suggested to MatrixmaN?
My drives are seagate about a year old for one and about 6 months old for the other, the jumpers are correct as far as i can tell.

[rpertusio]

Does sound like you have a similar problem. It isn't the RAR files that are corrupt (if they sometimes report corrupt, and sometimes not). It's gotta be a hardware/driver issue, from my experience.

Check the event logs. (See above for instructions)

- rp