Hi,
I've started to see a rash of single-bit errors on my system. I first noticed this when I had to copy the contents of a disk to a new one. In order to make sure the copy was good, I ran md5deep across the source before I copied, and then on the destination after the copy. This started to show some weird results where I'd get different checksums for the same file, If I ran it multiple times. After finding a few files that really were different between source and destination, I compared them and found single-bit errors between them.
My first thought was a memory issue, so I ran both Microsoft's memory checker and Memtest+. Both ran flawlessly over an extended period of time. However, the issue with different checksums for the same file persisted.
Next I pulled the 2 sticks of "no name" brand memory from the system, leaving behind the 2 sticks of Corsiar. Again the memory tests worked perfectly. But this time, so did the checksums on the disks. I was able to run those many times, without a single "mismatch". Problem solved, or so I thought.
Yesterday I downloaded some stuff from Usenet and was surprised to see a high percentage of the files failing a par2 check. Running the par2 recovery didn't seen to help, as it still reported many errors. By using WinRAR's recovery I was able to compare a bunch of the "broken" files with the recovered ones. Yep, every single one of them had a single-bit error.
So, how do I track down what's causing this, and is there a good tool to detect, as Memtest+ doesn't seem to find them.
My system specs are:
Asus Crosshair II Formula
AMD Phenom X4 9600 Black Edition
(Currently) 2 X Corsair CM2X2048-6400C5DHX
Cheers.
I've started to see a rash of single-bit errors on my system. I first noticed this when I had to copy the contents of a disk to a new one. In order to make sure the copy was good, I ran md5deep across the source before I copied, and then on the destination after the copy. This started to show some weird results where I'd get different checksums for the same file, If I ran it multiple times. After finding a few files that really were different between source and destination, I compared them and found single-bit errors between them.
My first thought was a memory issue, so I ran both Microsoft's memory checker and Memtest+. Both ran flawlessly over an extended period of time. However, the issue with different checksums for the same file persisted.
Next I pulled the 2 sticks of "no name" brand memory from the system, leaving behind the 2 sticks of Corsiar. Again the memory tests worked perfectly. But this time, so did the checksums on the disks. I was able to run those many times, without a single "mismatch". Problem solved, or so I thought.
Yesterday I downloaded some stuff from Usenet and was surprised to see a high percentage of the files failing a par2 check. Running the par2 recovery didn't seen to help, as it still reported many errors. By using WinRAR's recovery I was able to compare a bunch of the "broken" files with the recovered ones. Yep, every single one of them had a single-bit error.
So, how do I track down what's causing this, and is there a good tool to detect, as Memtest+ doesn't seem to find them.
My system specs are:
Asus Crosshair II Formula
AMD Phenom X4 9600 Black Edition
(Currently) 2 X Corsair CM2X2048-6400C5DHX
Cheers.