Rosetta@Home: Computational Errors

[Smoke]

I've started getting quite a few Computational Errors over the last few days on both of my home office machines.

A quick check of the ?Rosetta Forums? indicates that quite a few people are having similar problems. It might be a good idea for all of us to RESET PROJECT so we get rid of all our 5.89 and 5.90 WUs so we can be issued the newer 5.91 WUs.

Ack, I did this a few minutes ago and it appears I have gotten a full boat of 5.90 WUs.

The worst part of the errors is that they seem to hang with about 10 minutes to go. It takes awhile before they get the error designation. So almost 100% of the time spent crunching is for naught. 🙁

Check your BOINC MANAGER and see if you are having any problems.

 

[networkman]

Yeah, I'm going to have to check the BOINC Manager on my work PC, as that one is definitely the oldest of my fleet. And I've been seeing compuational errors on the Enigman@Home project - no Rosetta units running at all at the moment. 😕

Edit: I just checked and found my BOINC Manager on the work PC was 5.8.16, so I've upgraded to the latest, which is 5.10.30 and will see how that goes. 🙂

 

[Pokey]

I just now noticed your post. I seem to have all "Rosetta_beta_5.89" clients. And I don't recall any major problems. If I had any, they cleared without my doing anything. Of course I have been pre-occupied with F@H this month. 😀

 

[Fardringle]

My dual Xeon server is having lots of memory problems (multiple copies of the app in memory that won't close unless I kill them manually) with 5.90. Unfortunately, I have reset the project several times and it just keeps getting 5.90's back so I don't have any way to tell if it's a BOINC/server problem, or a Rosetta 5.90 problem.

 

[Smoke]

Fardringle,

I've been following your "Rosetta memory usage" thread and though anything is possible I don't believe the computation errors have much to do with memory settings. As far as getting 5.91 WUs ... I haven't seen one of those yet.

I did the reset project trick a few days ago and things have improved. I did have one error this morning. I am made aware of the problem only because I get a popup asking if I want to report the problem to Microsoft and BOINC is listed as the activity having troubles.

The system having the most problems is my Q6600 overclocked to 3.2GHz. If I have many more of these computation errors I may drop back on the FSB and the vCore voltage.