Strange harddisk problem: always different files give CRC errors

[Slaanesh]

I'm experiencing some very strange problems.

When copying multiple files on my HD, or when unzipping multiple files from a ZIP/RAR archive, I'm getting multiple corrupt files. The strange is, when I repeat exactly the same command, I'm getting multiple, DIFFERENT corrupt files! But no matter how many times I try, I can never succesfully complete the copying or unzipping without file errors.

Since I thought this was caused by a HD failure (it's a Maxtor 80GB PATA IDE HD), I ran multiple scan disks but no error was ever found. I even changed my PATA IDE cable but same thing.

Yesterday I installed a second, recently formatted SATA hard disk drive (which works perfecly on my other pc), and I'm having exactly the same problems!!

I just don't know what to think about this. Any suggestions?



Specs:
Intel C2D Q6600 (stock speed)
2 GB RAM
Asus PQ5-E motherboard
Antec SmartPower 2.0 450W ATX12V v2.01
Maxtor 80GB IDE HD
Western Digital 250GB SATA HD
Windows Vista 32bit

 

[nboy22]

Your RAM is bad.

Do a memtest86 and I'm almost 100 percent sure it's going to come back with a load of errors (if it even shows one error, your RAM is bad.

I had this problem like 10 years ago and I replaced the RAM under warranty and everything was back to normal.

 

[Slaanesh]

Thanks for the answer.

I already checked my RAM with Windows Memtest 4.0 (http://www.softpedia.com/get/Tweak/Memory-Tweak/MemTest.shtml) and it gave me no errors (checked 100% of RAM for 1h).
But maybe I should try Memtest86 tonight.

 

[nboy22]

I've never used Windows Memtest 4.0, but I would recommend Memtest86 for sure.

 

[RebateMonger]

nboy22 is correct that memory errors are the most common cause of file corruption like you are seeing.

 

[Slaanesh]

Hmm... Memtest86 is now running for about 2h, still no errors.
Could it be something else?

 

[nboy22]

We can think about this problem logically and say there are about three main components that could be the culprit.

here's a list from most likely to least likely

#1. RAM is bad
#2. Something with HDD is bad
#3. Something with motherboard is bad.

At this point, if you have the option available to you, I would try different RAM.

I have seen weird issues with an ASUS motherboard and the hard drive click of death. Every time an HDD was hooked up to the Motherboard it would have the click of death, but when I'd take the HDD out and put it in a different computer, no click of death.



I would first try different RAM, and then different hard drive, and then different hard drive controller via the a PCI sata controller card. You've already tried a different hard drive so that knocks one off the list.

 

[Slaanesh]

Thanks for the help.
I'll restart memtest and let it run through the night.

It's getting weirder though: I connected a third HD (eSATA) to the external SATA connector at the back and this one doesnt give the error anymore!! The other 2 drives (IDE and SATA) still produce the same errors, and the SATA drive still works perfecty in my other PC (can't try the IDE drive in another pc though).

Are we sure it can't be software/driver related?

I have Vista 32bit with all latest updates.

 

[nboy22]

Hmm.. I don't really think it's software related. Best you can do there is make sure you have newest chipset drivers, etc... Check your motherboard manufacturer's website to see if you're missing any drivers of course.

We know one thing for sure now though, that you're connecting into your eSATA at the back of your motherboard and it's working fine. I would now rule out your RAM because it would affect EVERY hard drive and extracting archives on all drives.

We can factor out your hard drives too, because your hard drives work in other computers.

I would really lean towards something may be wrong with the SATA/IDE controller card that is built onto the motherboard, but the tricky thing is I would think that it would also affect your eSATA drive.

Reading upon this further, it could be a problem with the particular RAM slot you're using. If you have more than one RAM stick, then try each individual RAM stick one at a time, and then if you have the capability to, go ahead and try to put one RAM stick in the second RAM slot and see if that fixes the issue.

 

[Slaanesh]

OK, so I did some more tests.

My configuration:
- 1 IDE port: 80GB Maxtor ATA HD and 1 DVDR/W drive
- 6 internal SATA ports:
port 1: 250GB WD SATA disk
port 2: 2TB WD SATA disk (the drive I had previously connected via the eSATA port)

Test:
I copy an archive file split into 40 RAR files from another PC to the 3 drives. Results: multiple corrupt files on the IDE and 250GB SATA drives, no errors on the 2TB drive.
I delete all files, copy all the files another time, and again the 80GB and 250GB get multiple corrupt files (other files this time), while the 2TB drive has no errors.

Then I open my computer, switch the 2 SATA cables (2TB to SATA1 and 250GB to SATA2) and restart the test: the results stay the same! (2TB no errors).

As said before, scandisk couldn't find any errors on the 3 drives and Memtest86 didn't find errors in 14 hours. Also, the 250GB drive works perfectly in another PC.

Finally, I disconnected all hard drives except the 250GB SATA drive, launched the Vista installation DVD, formatted the drive and reinstalled a clean Vista 32bit (this worked!).
I boot Vista, again copied the files to the 250GB and AGAIN I have multiple corrupt files!!!!!!!
WHAT IS GOING ON?



* Another interesting observation:
Before installing Vista, I wanted to install Win7 64x on the formatted 250GB drive, but every time the installation gave a read error at 12 percent of copying the Windows files to the harddisk. This is using my internal DVDRW IDE drive. I tested the disc on my second PC and the disc works flawlessly. Then I switched the DVDRW drives from both PC's (they'r both IDE drives) and tried again to install Win7, which again failed at 12 percent.
Installing Vista 32bit however was no problem at all....

 

[ElenaP]

The motherboard manual says there is a Drive Xpert function built-in. This seems to imply that there are different types of SATA ports, i.e. not all SATA ports are equal. Please clarify if this function is in use, and also exactly what SATA ports are involved in your tests.

 

[Slaanesh]

The motherboard manual says there is a Drive Xpert function built-in. This seems to imply that there are different types of SATA ports, i.e. not all SATA ports are equal. Please clarify if this function is in use, and also exactly what SATA ports are involved in your tests.

I was looking through the manual yesterday and I wanted to try the SATA ports of the Drive XPert function when I noticed I was mistaken; my other PC has the Asus P5Q-E motherboard, this one has the Asus P5E motherboard which has only the 6 regular SATA ports.
Sorry!

 

[Modelworks]

If it is rar files that are corrupting it is your memory/cpu no matter what memtest says.
I have found rar decompressing to be the best indicator of memory or cpu problems because the compression it uses taxes multiple parts of the system in ways memtest does not.
Memtest is good for finding most errors but take a large file, compress it with rar at max compression level and verify the file. Then put that file on the problem pc and try to extract it, every time I have done that a pc with memory or cpu problems will say the file is corrupt.

You can rule out if it is the hard drive by doing a CRC/sha on the file before you copy it and after you copy it to confirm the file is intact and not being copied wrong.

You can use hashtab for this, you can get it here. After install right click the file and pick properties, then the file hashes tab, write down the values and compare them on the target pc.
http://beeblebrox.org/
If the CRC do not match after copy look in event viewer under system for errors. Windows will say CRC error on hard drive

 

[Slaanesh]

Thanks for the response.

So I guess I should try some other memory sticks and see if the problems persists.
Is there a way to differentiate between CPU and memory errors, besides from replacing one or the other?

I'll do the CRC test tonight when I come home.

 

[nboy22]

I don't think there's a way to differentiate whether the issue is coming from CPU or the RAM, other than replacing one or the other.

I would definitely start with RAM first though.