I just finished building a new computer and have installed a fresh copy of Windows XP on it. It is an Athlon 64 3700. It runs everything fine but Boinc. The Boinc/Rosetta App installs perfectly, but will not download a valid workunit. It keeps telling me that the MD5 checkums are invalid.

I have tried using just the plain Boinc client and also the Reux and crunch3r clients, all give the same error.

HELP!

---

I got about the same problem here.
On my new Athlon 64 X2 4200 computer with Windows XP I installed Boinc to crunch some Rosetta.
But I kept getting MD5 checksum errors on all wu's.
I removed Rosetta and attached to it, again getting MD5 errors.
After removing and attaching an other time I got some valid wu's and some with MD5 download errors. After some time the problem seemed over with all new wu's downloaded without errors.
But today again I got MD5 checksum errors on about half of the new downloaded wu's.
I was wondering if there is something wrong on my side or that it's a Rosetta thing I have to live with?

---

To help with diagnosis.. how much ram do each of these machines have? What version of Boinc are you running, and which version of Rosetta? (4.82 or 4.83?)
Have you tried installing the latest device driver for your NIC (Network interface card?)

Have you run Memtest86 (from www.memtest86.exe ) on your system to prove that all the ram is working fine? And then SuperPI (available from sites such as http://www.visionengineer.com/ref/pi.php ) to test the cpu - by choosing the 4M or 8M (or larger) test that takes 15-30 mins on your system?

If hardware is ruled out.. and your NIC drivers are up to date (modem drivers if you use dialup) - then a quick run through the online scans at the following sites: www.bitdefender.com, www.pandasoftware.com, and www.trendmicro.com to verify that you're not infected with spyware/trojan horses/or worms.

Uninstalling Boinc and Rosetta; rebooting, and then downloading and installing new copies of Boinc and Rosetta into a new directory.. C:program filesBoinc2 - for example might be a good idea as well.

And if all those steps fail.. try the Ralph client, and see if the MD5 checksum errors also occur there.

---