At wits end... more than 80% of my work ends with errors. I've tried keeping project in memory (even though I only run Rosetta). I get a 'Rosetta not responding to screensaver, exiting" message along with "5/18/2006 3:54:14 PM|rosetta@home|Unrecoverable error for result t283_HOMOLOG_ABRELAX_hom003__515_4011_0 ( - exit code -1073741811 (0xc000000d))"

The project then crashes.

I have no desire to contribute results that are bad, and have no desire to waste cpu time on creating those errors.

I have disabled all power management other than screensaver activation. NOTHING has helped so far. I'd like to contribute to this project, but so far it has been disappointing.

Canis Major

---

I see you already have the new BOINC version, and have plenty of memory. It seems these "-107" errors are becoming common for some people's machines. There have been a number of such reports and the project team is working hard to solve that issue. I don't know the cause, but there is a lengthy discussion, much of which is about this error in the 5.16 problem reports thread. Keep your eyes there for when a solution is posted.

Since you seem to generate the error with ease, your system is probably one they would like to study further (if you are willing to help work through the problem). You can help them do that by joining Ralph (the test project for Rosetta). When they DO have a fix, they will test it on Ralph first and try and determine if it indeed resolves the -107 errors... and YOU are in a good position to know! So, your feedback would be very helpful there. I mean ME saying I don't get them doesn't help much, because I haven't been seeing such an error... but if YOU can say that, then it gives them confidence they have indeed corrected the problem.

The recommendation is for testers to join Ralph and leave it active just as you would Rosetta... but set it to a low resource share... like 10% (resource share is set in the project's preferences, either Rosetta or Ralph). And be aware that there is only work available there when they have a new version or a new batch of WUs they need to test. But, by joining now, you'll have everything set up to be ready when a fix and some new WUs are made available there.

Be sure to report any problems on the Ralph boards, as described on the Ralph homepage under "news".

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Please if you do have the inclination to help above and beyond crunching, join Ralph and see if they can fix this as Feet1st says it may well help a lot of people.

---

Team mauisun.org

But the solution at the moment (hopfully)
Is not to use the screensaver and

either let it run in the background, idle time
or
set you preferences to run when the computer is not in use after xx minutes
https://boinc.bakerlab.org/rosetta/prefs.php?subset=global

---

Team mauisun.org

Well I am a new user as well. recently I have bought a Dell dual core machine and I get on a regular basis "computation error" together with "client error". So I am wondering too what the problem is. Anyone ideas??

---

Well I am a new user as well. recently I have bought a Dell dual core machine and I get on a regular basis "computation error" together with "client error". So I am wondering too what the problem is. Anyone ideas??

You picked up an old thread here Shark. So, your issue is not likely related to this older one. But it looks like you are running with BOINC set as your Windows screensaver. I say "looks like" because you are seeing the same error codes reported back. The recommendation is to run with screensaver set to NONE, until a fix is made. If you have further questions, please post in the Number Crunching board.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/