HD Tune: Ultra DMA CRC Error Count

[bagrata]

hi 🙂
I have same problem like subhendu
I bought seagate hdd 3 weeks ago, it's works fine, but after several days, his speed in hd tune benchmark dropped from 118mb/s to 3mb/s!!
I check hdd health status and i saw this

Ultra DMA CRC Error Count
Number of interface communication errors:2

I changed my hdd, but after several days, new hdd started same problem
I changed cables and test in another sata port, but problem did not solved
can you help me?

Sorry for my English.

 

[bagrata]

up 🙁

 

[bagrata]

up

 

[imaheadcase]

Might just be a bad hardrive, did you run chkdisk?

 

[Rifter]

Check the RAM, run memtest overnight and see what it says.

Also it could be a bad controller/motherboard.

 

[bagrata]

Might just be a bad hardrive, did you run chkdisk?

what that mean?

Check the RAM, run memtest overnight and see what it says.

ok

 

[Rifter]

that means you either have a bad hard drive or a bad hard drive controller. However RAM could still be the problem.

 

[bagrata]

that means you either have a bad hard drive

I test two hdds.

bad hard drive controller

oh no.

Have you heard solve that problem with smart log? (what is it?)

 

[Nothinman]

That just means you ran chkdsk on a mounted volume, you need to run it with /F to actually fix things and it'll need to dismount the volume in order to do so. If it's the system volume this will require a reboot.

The most likely culprit of CRC errors is cabling, interference or environment like heat. Do you have other cables to try?

 

[Rifter]

That just means you ran chkdsk on a mounted volume, you need to run it with /F to actually fix things and it'll need to dismount the volume in order to do so. If it's the system volume this will require a reboot.

The most likely culprit of CRC errors is cabling, interference or environment like heat. Do you have other cables to try?

I believe he said in the OP he had tried multiple ports and cables, which is why i think its mobo or ram related.

 

[Nothinman]

I believe he said in the OP he had tried multiple ports and cables, which is why i think its mobo or ram related.

Could be, but that chkdsk output isn't an indication of anything more than having run chkdsk on a mounted volume.

 

[Rifter]

Could be, but that chkdsk output isn't an indication of anything more than having run chkdsk on a mounted volume.

true, but it is the second HDD with issues.

 

[Nothinman]

true, but it is the second HDD with issues.

Then it's even more worthless since he ran it on the C: drive...

 

[Rifter]

Then it's even more worthless since he ran it on the C: drive...

wow English failed me. I was trying to say this is the second hard drive he was having the same issue with on the same system, not that it was the second physical drive in the system.

 

[Nothinman]

wow English failed me. I was trying to say this is the second hard drive he was having the same issue with on the same system, not that it was the second physical drive in the system.

Wow, talk about communication issues. =) If that's the case, then yea it's probably the motherboard that's the root cause. A BIOS/firmware update or even just drivers might be able to work around the problem though.