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.

---

5/12/2006 11:08:59 PM|rosetta@home|Unrecoverable error for result HOMOLOG_ABRELAX_hom007_t283__505_10758_0 ( - exit code -1073741811 (0xc000000d))

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

Boinc 5.4.9

Stu

---

My results:
https://boinc.bakerlab.org/rosetta/results.php?hostid=219533

---

Yes, you were right. Upgrading to the new BOINC version solved my problem. I didn't know it was out today. I checked every other day for the last 3 months and it is finally out now. Thanks

---

I got this error https://boinc.bakerlab.org/rosetta/result.php?resultid=20014963.

Anders n

---

I got this error https://boinc.bakerlab.org/rosetta/result.php?resultid=20014963.

Anders n

These crop up randomly from time to time. This is the last type of known error, and they are now so rare, and random, they are having trouble finding the cause. You probably will not see another one, at least for a while.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

These crop up randomly from time to time. This is the last type of known error, and they are now so rare, and random, they are having trouble finding the cause. You probably will not see another one, at least for a while.

There seem to be alot of info in the error message :)

Anders n

---

These crop up randomly from time to time. This is the last type of known error, and they are now so rare, and random, they are having trouble finding the cause. You probably will not see another one, at least for a while.

There seem to be alot of info in the error message :)

Anders n

Yes there is. And it is very valuable to solving the problem. 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.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

... 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.

---

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

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

...Jose

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?


PS - Jose, look here for video of some of the programers VIDEO. One in particular might interest you.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

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.

---

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)

Currently the only problems (I am aware of) related to Rosetta, are -107 errors which are random and infrequent. Most people never see them at all. The other relates to certain versions of windows and is related to the display of graphics. This problem has been clear on all but a very few systems by installing the latest upgrade for what ever version of windows you may be running.

Please do provide us with more information so we can get you going. We currently have a new project called RALPH. In Ralph the application has more expansive error reporting information. If we can't get you started in a few tries, we can have you attach to ralph and solve your problem.

I would like to move this thread and your post to the number crunching forum, where more people will see it. There are some really sharp people among the users here, and they could help you as well, but they do not all frequent the Cafe. Let me know if I can move your thread. In the mean time please do provide more information. I will try to look at your results and see if I can find anything as well.

EDIT: I see the error you have is in fact a -107 error. More than likely the work unit you have now will complete ok if history is any guide. While this may not matter to you, the project does award credit for all work even when there are errors. It will show up in the RESULT display for the work unit not the work unit level display, and it should sow up by morning.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact