... these -107 errors seem to be related to a specific version of windows. A number of people have reported that the problem started after an upgrade, and went away after a second upgrade. In any case the programmers will find it sooner or later. Fortunately it is not a high frequency error.

They ARE!!!!! ARGH ARGHHHHHHHHHHHHHHHHHHHHHHHHHH!!!!

https://boinc.bakerlab.org/rosetta/result.php?resultid=20152456

Insert sticking-tongue-at Moderator 9-emotie here: Infrequent, my foot!!!

Tell the programmers to get their collective behinds in gear or they will be receiving a visit from my electronic lover, power supply eating, power cords chewing, Fila brasileiro. The dog is big, the dog is dumb and I can easily convince him the programers are nice power supplies to be had for snacks ,

Let me tell you that there are days I believe that "the programmers" you talk about are like the 'big pumpkin', Santa Claus, the tooth fairy ...you get my drift : they do not exist. Can you post a picture of them, and a notarized sworn statement that they are THE programers.?

ROFL


Jose

PS: For the record I do not drink :P My brain circuits are just slightly toasted.

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

i'm currently using a geforce 4600.

I just read a post from another user who is also a savvy tester for BOINC development. He mentioned that lockups were caused in just the way you describe on older versions of BOINC client software. Today anything older than BOINC version 5.4.9 could have the problem. I did not check your BOINC version number but if you are not running 5.4.9 you might want to consider upgrading. The latest version is available here.

thank you very much that has fixed the problem for me.

apparently i spoke to soon as in the past 2 days i have had 2 of 3 workunites have the same problem. this time it is slightly diffrent as i can have the screensaver open sometimes up to 2 hours before it dies. Once again it appears as if i prevent the screensaver from coming up it does just fine.

---

I have used both the screen saver and the screen graphics from the command. Most of the time the screen saver. The screen saver is kept on all the time I don't use the computer. Since my life is exciting as that of a drunk slug: I find myself cheering for the molecule during full atom relax.

Ah graphics card.... You really want me to find out? I'll check latter.

I have decided not to download anything (except vital upgrades) during CASP time period. I just don't want to risk it. Even with my new and improved speed it will take me a full month to hit a RAC of a 100 , LOL LOL LOL I don't want to be slower than my team's turtle. :P

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

[quote]...https://boinc.bakerlab.org/rosetta/result.php?resultid=20152456

Insert sticking-tongue-at Moderator 9-emotie here: Infrequent, my foot!!!

...Jose

[color=darkred][b]Jose,
I am sure I must have asked at some point, but what kind of graphics card are you using? Also, do you run the screen graphics display at all? If so do you use the screen saver or the display graphics function?

Akma,

When you display the graphics, are you using the screen saver or clicking on the "Display Graphics" function for the work unit from the "Task" tab of the BOINC Manager?

i'm also using both ways of seeing the screensaver and it seems to do it both ways of viewing it.

---

(Rosetta v5.13) + (BOINC v5.4.9) + (Computer ID 219653) = Near 100% error rate.

Fortunately, most of the errors are within the first few hundred seconds of CPU time, so we're not wasting good science on a buggy client.

I do not run the graphics at all (neither screen saver nor in a window), having inferred from numerous posts in this and other threads that the graphics are quite problematic.

Any suggestions?

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

Addendum to the post below:

41 errors today (5/14/06) all with less than 1000 seconds CPU time.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

Addendum to the post below:

41 errors today (5/14/06) all with less than 1000 seconds CPU time.

I see you have computers that use Windows XP! Are those the computers presenting the errors?

I had a lot of hassles prior to 5.13 . After I reinstalled Windows, and updated it all my problems basically went out.

Are you using an optimized client?

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

I really wish that Rosetta@home will work on my machine. I have been running seti@home since the classic days, and added Eienstein@home about a year ago, with zero problems.
My father in law was diagnosed with cancer 6 months ago and has just died. His diagnosis promted me to add rosetta@home to my BOINC projects.
Rosetta@home has never, ever, run without freezing.
I'm very disappointed. I've removed the project from my BOINC projects, installed and am running Folding@home flawlessly. After the 'appeal' newsletter, I decided to give rosetta@home one more try, and after upgrading to BOINC 5.4.9, reattaching to the project, it still freezes.
Obviously, I'm not the only one who has these problems as there are numerous posts that describe several problems.
What are the differences between rosetta, seti, and einstein @home, and why does rosetta freeze so much?
Now, I have resumed all my BOINC projects in the hopes that I'll be able to copy the rosetta error message so that someone can help me fix this.
-Seth (Los Angeles, CA)

I see you have computers that use Windows XP! Are those the computers presenting the errors?

I had a lot of hassles prior to 5.13 . After I reinstalled Windows, and updated it all my problems basically went out.

Are you using an optimized client?

Yes, at this time it is only one of the Windows machines that is erroring out of every work unit. Interestingly, the other Windows machine is running the older BOINC manage (5.2.xx)

The troublesome computer is operating with a fresh install of WinXp. To my knowledge, it is fully updated with all high priority updates and relevant optional updates.

I am using only the client(s) that I have downloaded from Rosetta/BOINC.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

I've had these two work units error out:

https://boinc.bakerlab.org/rosetta/result.php?resultid=20024272
https://boinc.bakerlab.org/rosetta/result.php?resultid=19924537

Both have been run by someone else and have also errored. For me, and it just may be a coincidence, both of the above errors happened within two minutes of the BOINC client sending a scheduler request to report results.

---

Every one of your errors is at the same point in the process. Can I assume you have rebooted (cold started) the system? If not please try that. IF you still see an error then try resetting the project (after the cold boot).

Also most of your errors (not all) seem to be on the same work unit type. Is this machine using graphic displays at all?

I have rebooted repeatedly (cold starts and warm starts both).

At this point, I have my fingers crossed: One of the workunits currently in process is at 100% and declares itself "Ready to report." If it goes through successfully, the curse may be broken.

I won't be watching Rosetta graphics until the chatter on the boards here indicates that the outstanding issues have been resolved. While they (the graphics) are interesting and informative to watch, I don't want to risk corrupting the result.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

https://boinc.bakerlab.org/rosetta/result.php?resultid=20207298

Another 107 type error. My second with version 5.13. Both 5.13 errors were produced approximately about the same time into the computing process: there Wu's produced and they seem to be related with an incompatibility with Windows XP video drivers. I basically keep the screen saver most of the time ( I like it) and the failures occurred when the computer tried to use another video application in one case the DVD reader and in another the Windows Media Player.

IMHO some effort into investigating why that incompatibility is occurring will yield results. On the positive side: I am finding that the time allotted estimates work better, the graphics are better (the information box format needs to be tweaked so all could be read) , and the new manager is more user friendly. Overall. I give it a B+ ( I was a hard grader.)

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

[/ Unfortunatly a lot of the Rosetta power users were away visiting their mothers today.

What!!!! and leave us without guidance.!!!

PS

I do apologize for the lame attempt at humor but my evil twin forced me.

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

I was doing a little research on my problems over the weekend, following the links to see if anybody else had been successful with the WU's that errored on my computer.

I found at least one other computer that had a huge spate of errors this weekend. Check the results on this one: CPU ID = 217873

EDIT: Unfortunately, I don't know what version of the Rosetta client this individual is using, so this post may be misplaced.

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

Well, Mac's are beautifiual machines. However, the problems here are mainly Windows XP based. Hmm, I wonder of -107 errors would occur on a MacTel machine running Windows XP and Boot Camp. ((sigh)). Anyway, what about the issue at heart here?
-Seth

[/ Unfortunatly a lot of the Rosetta power users were away visiting their mothers today.

What!!!! and leave us without guidance.!!!

PS

I do apologize for the lame attempt at humor but my evil twin forced me.

Well there was me. And I do have a solution for all these problems. Think Different!! Macs don't get -107 errors. :>)

Well there was me. And I do have a solution for all these problems. Think Different!! Macs don't get -107 errors. :>)

The mayority of applications I do run cannot be run in a Mac.

Also, Mac is a cult. I dont belong to cults . :P :P :P

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

i for one i'm very pleased with the response i have received here. it is far and above what i have delt with with other projects. however i disagree with you when you say credit is still given for the work done on the problem workunites. here are a few examples where i have returned some with finished models but didn't receive any due to client error.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16575261
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16652606
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16652921
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16653053

---

i for one i'm very pleased with the response i have received here. it is far and above what i have delt with with other projects. however i disagree with you when you say credit is still given for the work done on the problem workunites. here are a few examples where i have returned some with finished models but didn't receive any due to client error.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16575261
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16652606
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16652921
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=16653053

Welcome Akma, indeed you did get credit. Instead of looking at the automated "results" page for it, look at the 2nd and 3rd lines from the bottom of the "result ID". Manual and script generated credits are posted there. This is the first WU you listed:

Result ID 19945622
Name HOMOLOG_ABRELAX_hom001_t283__505_751_0
Workunit 16575261
Created 11 May 2006 21:06:51 UTC
Sent 11 May 2006 22:50:18 UTC
Received 12 May 2006 4:05:38 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741811 (0xc000000d)
Computer ID 218656
Report deadline 25 May 2006 22:50:18 UTC
CPU time 4669.1875
stderr out <core_client_version>5.3.12.tx36</core_client_version>
<message> - exit code -1073741811 (0xc000000d)
</message>
<stderr_txt>
# random seed: 3126230
# cpu_run_time_pref: 10800

</stderr_txt>


Validate state Invalid
Claimed credit 26.2506026151631
Granted credit 26.2506026151631
application version 5.13