I am currently running BOINC CPDN on two machines. Both are AMD64 / Windows XP 64 machines, so BOINC is running under WOW. Both of these machines have an extremely hard time completing work units, erroring out in phase 1 (usually) with the error 0xc0000005 (General Protection Fault). One machine has been particularly bad: 320810, maroon-xp, has failed 7 times, and only now has managed to get into phase 2 of a work unit.

The particular problem that I am facing is this: This machine now has a total of 7 partial WU occupying almost 2GB of disk space. Some of these WU may be useful. What should I do with them?

In particular: I believe WU 1093016 (sulphur_iyi9_000884529) completed phase 1 at least, as it ran for 870,000 sec. Similarly WU 1549933 (sulphur_hek9_000812025) ran for almost 350,000 seconds and may have useful data. Because of this I don\'t waht to just erase them... but there is so much disk space being used that I cannot do any other BOINC projects on this machine.

---

Hi, I wouldn\'t worry about deleting directories of models that did not complete successfully. The one that completed phase 1 uploaded the important information from that phase the scientists needed already. The others, if needed, will be rerun.

As for the errors, that error has been associated with hardware faults, and some antivirus software faults. Are you running antivirus on these PCs, and if so, what type?

Check for heating problems, update vid drivers and runthese tests;


Prime95 Torture test

Memtest86+

---

BOINC Wiki

Hi, I wouldn\'t worry about deleting directories of models that did not complete successfully.

Thank you for that information; I will deal with that. That will help a lot, I think.

As for the errors, that error has been associated with hardware faults, and some antivirus software faults. Are you running antivirus on these PCs, and if so, what type?

There are no AV packages running on these machines; the office uses ServerProtect that does not have a 64-bit version, and I have been looking without success for something that will run native 64-bit. Another post in this thread mentioned a couple of hardware test packages; I\'ll try them and see what happens.

---