This thread is for reporting errors that are NOT workunit Hangs (1% errors). Many of you have more than one computer, so Please include the type of error in your report, and a link to the RESULT in your stats page. This thread replaces the original thread located here. , and the second thread located here

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Two additional errors Up to now it has been 4 errors . Frusrtation levels keep going up

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

Result ID 17763320
Name PROD_ABINITIO_ALPHABETABAR_1tul__447_36410_0
Workunit 14609883
Created 20 Apr 2006 19:50:27 UTC
Sent 21 Apr 2006 1:57:54 UTC
Received 21 Apr 2006 19:01:10 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741795 (0xc000001d)
Computer ID 198415
Report deadline 5 May 2006 1:57:54 UTC
CPU time 208.734375
stderr out <core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741795 (0xc000001d)
</message>
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 2903651
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126

2. https://boinc.bakerlab.org/rosetta/result.php?resultid=17763303
Name
PROD_ABINITIO_9STRANDBAR_1tul__447_36407_0
Workunit
14609867
Created
20 Apr 2006 19:50:21 UTC
Sent
21 Apr 2006 1:57:54 UTC
Received
21 Apr 2006 18:56:45 UTC
Server state
Over
Outcome
Client error
Client state
Computing
Exit status
-1073741819 (0xc0000005)
Computer ID
198415
Report deadline
5 May 2006 1:57:54 UTC
CPU time
2406.890625
stderr out
<core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# random seed: 2703654
# cpu_run_time_pref: 21600
# cpu_run_time_pref: 21600
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126

---

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

First 5.01 error:

17794627

Error code (an oldie):

<message> - exit code -1073741811 (0xc000000d)
</message>

Regards.

---

Another ONE!!!!!!!!!!!!!!! ARGH What is goin on!!!! I am going to abort ALL the FULLSTRANDBARS I have in line to be processed.


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

17763271
Name PROD_ABINITIO_9FULLSTRANDBAR_1tul__447_36402_0
Workunit 14609838
Created 20 Apr 2006 19:50:21 UTC
Sent 21 Apr 2006 1:57:54 UTC
Received 21 Apr 2006 19:40:20 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741819 (0xc0000005)
Computer ID 198415
Report deadline 5 May 2006 1:57:54 UTC
CPU time 2246.6875
stderr out <core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 2603659
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126

---

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

Jose, these "dll" errors are pretty puzzling. I'm looking into it now. Has every job from 5.01 failed on your computer?

(Also, have you attached your client to Ralph? We get better error reports from there.)

Another ONE!!!!!!!!!!!!!!! ARGH What is goin on!!!! I am going to abort ALL the FULLSTRANDBARS I have in line to be processed.


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

17763271
Name PROD_ABINITIO_9FULLSTRANDBAR_1tul__447_36402_0
Workunit 14609838
Created 20 Apr 2006 19:50:21 UTC
Sent 21 Apr 2006 1:57:54 UTC
Received 21 Apr 2006 19:40:20 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741819 (0xc0000005)
Computer ID 198415
Report deadline 5 May 2006 1:57:54 UTC
CPU time 2246.6875
stderr out <core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 2603659
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126

---

[quote]Jose, these "dll" errors are pretty puzzling. I'm looking into it now. Has every job from 5.01 failed on your computer?

(Also, have you attached your client to Ralph? We get better error reports from there.)


ONLY ONE worked. First thing I am doing is aborting ALL the work units That there were pending and see what happens with new work.

To say that these two last days have been frustrating is an understatement. I need a beer.

---

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

Thanks. Please post here what happens to your new work.

The "dll" error looks like it might have something to do with the BOINC api -- I'll contact Rom with your error report.

[quote]Jose, these "dll" errors are pretty puzzling. I'm looking into it now. Has every job from 5.01 failed on your computer?

(Also, have you attached your client to Ralph? We get better error reports from there.)


ONLY ONE worked. First thing I am doing is aborting ALL the work units That there were pending and see what happens with new work.

---

I will

Thanks. Please post here what happens to your new work.

The "dll" error looks like it might have something to do with the BOINC api -- I'll contact Rom with your error report.

[quote]Jose, these "dll" errors are pretty puzzling. I'm looking into it now. Has every job from 5.01 failed on your computer?

(Also, have you attached your client to Ralph? We get better error reports from there.)


ONLY ONE worked. First thing I am doing is aborting ALL the work units That there were pending and see what happens with new work.

---

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

I seem to have a WU which in an "endless loop" which has been running for 15hr 27min sofar

HLBR_1.0_1mky_420_5362, with Rosetta v5.01

right now it's at 5.1261%, Model 1, Step 34312

Everything seems to be in order, i.e. steps incrementing normally, protein chain moving in the graphics etc

But, at some point, it just "resets" and starts over, Model 1 / step 1. Running for 15.5hr already.

This is the 2nd time I encounter an "error" on this PC (WinXP) in 3months, so it's probably a WU issue.

Should I just abort it?

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

I seem to have a WU which in an "endless loop" which has been running for 15hr 27min sofar

[url=https://boinc.bakerlab.org/rosetta/result.php?resultid=17753171HLBR_1.0_1mky_420_5362[/url], with Rosetta v5.01

right now it's at 5.1261%, Model 1, Step 34312

Everything seems to be in order, i.e. steps incrementing normally, protein chain moving in the graphics etc

But, at some point, it just "resets" and starts over, Model 1 / step 1. Running for 15.5hr already.

This is the 2nd time I encounter an "error" on this PC (WinXP) in 3months, so it's probably a WU issue.

Should I just abort it?

I had a similar 4.99 HBLR result in Ralph. They asked me to abort the 4.99 one. If you click the link keep in mind that my next 10 posts are talking about the same results and it's progression for 100+ hours.

Dimitris, thanks for posting. I really wanted to know about these jobs -- they ran beautifully on ralph, but (to be careful) we've only sent out a few here with Rosetta v5.01 to test. It sounds like its running fine -- the 5.1261% complete indicates that Rosetta got past at least one model. Can you let it run? The slow progress may be due to the funny way we calculate % complete; the job may jump to 100% complete after this next model is finished. By the way, in your Rosetta preferences,have you specified a fixed CPU run time (say 8 hours)?

I seem to have a WU which in an "endless loop" which has been running for 15hr 27min sofar

HLBR_1.0_1mky_420_5362, with Rosetta v5.01

right now it's at 5.1261%, Model 1, Step 34312

Everything seems to be in order, i.e. steps incrementing normally, protein chain moving in the graphics etc

But, at some point, it just "resets" and starts over, Model 1 / step 1. Running for 15.5hr already.

This is the 2nd time I encounter an "error" on this PC (WinXP) in 3months, so it's probably a WU issue.

Should I just abort it?

---

Jose, David K. and I just took a more careful look at your error output. We realized that this is the same error that we've seen occasionally in past apps. In fact, your computer encountered this several times previously, and you posted about it (and I replied that it was mysterious!). The new error reports have more information from the new BOINC runtime error manager (that's why I initially got confused and thought this was a new error) -- I've forwarded your e-mail to Rom to see if he can interpret it. In the meanwhile, thanks for keeping us posted on your work currently in progress.

I will

Thanks. Please post here what happens to your new work.

The "dll" error looks like it might have something to do with the BOINC api -- I'll contact Rom with your error report.

[quote]Jose, these "dll" errors are pretty puzzling. I'm looking into it now. Has every job from 5.01 failed on your computer?

(Also, have you attached your client to Ralph? We get better error reports from there.)


ONLY ONE worked. First thing I am doing is aborting ALL the work units That there were pending and see what happens with new work.

---

I see, but I think it's in a endless loop, because

1/ It has "switched" from Full-atom-relax Model 1 / Step 34k+, back to Ab-initio and Model 1 / Step 1 in front of my eyes (I enabled the graphics to monitor it for a while). In the past it was always Ab-initio -> Full-atom-relax -> done this model, process next Model, right?

Oddly, the WU graphics show several (~14) red-dots (energy min), which afaik should mean that at least 14 Models were processed. But Model # remains at 1.

2/ It's been running for 15.5hr already (my time setting is 8hr/WU) on a P4 CPU which has never exceeded 4hr/model in the past.

Dimitris, thanks for posting. I really wanted to know about these jobs -- they ran beautifully on ralph, but (to be careful) we've only sent out a few here with Rosetta v5.01 to test. It sounds like its running fine -- the 5.1261% complete indicates that Rosetta got past at least one model. Can you let it run? The slow progress may be due to the funny way we calculate % complete; the job may jump to 100% complete after this next model is finished. By the way, in your Rosetta preferences,have you specified a fixed CPU run time (say 8 hours)?

I seem to have a WU which in an "endless loop" which has been running for 15hr 27min sofar

HLBR_1.0_1mky_420_5362, with Rosetta v5.01

right now it's at 5.1261%, Model 1, Step 34312

Everything seems to be in order, i.e. steps incrementing normally, protein chain moving in the graphics etc

But, at some point, it just "resets" and starts over, Model 1 / step 1. Running for 15.5hr already.

This is the 2nd time I encounter an "error" on this PC (WinXP) in 3months, so it's probably a WU issue.

Should I just abort it?

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

[quote]Jose, David K. and I just took a more careful look at your error output. We realized that this is the same error that we've seen occasionally in past apps. In fact, your computer encountered this several times previously, and you posted about it (and I replied that it was mysterious!). The new error reports have more information from the new BOINC runtime error manager (that's why I initially got confused and thought this was a new error) -- I've forwarded your e-mail to Rom to see if he can interpret it. In the meanwhile, thanks for keeping us posted on your work currently in progress.

OK... The first one from the new batch came with error. THE SAME ERROR
https://boinc.bakerlab.org/rosetta/result.php?resultid=17838269
ARGHHHHHHHHHHHHHHHHHHHHHHHH
17838269
Name PROD_ABINITIO_ALPHABETABAR_1tul__447_47760_0
Workunit 14678383
Created 21 Apr 2006 13:36:17 UTC
Sent 21 Apr 2006 19:59:11 UTC
Received 21 Apr 2006 20:47:20 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741819 (0xc0000005)
Computer ID 198415
Report deadline 5 May 2006 19:59:11 UTC
CPU time 2425.59375
stderr out <core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# random seed: 2892301
# cpu_run_time_pref: 21600
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 12

It seems I have become the poster boy for errors in WUs .... I think RALPH doesnt like me (or he is a member of the DPC :P [Private Joke)

---

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

Gues What????
Another WU that went down the beaten Path: ( At this rate I may break the Record in WUs that have been in error, if not in credits not originally granted and CPU time not resulting in sucess...

I feel like crying...

https://boinc.bakerlab.org/rosetta/result.php?resultid=17838235
17838235
Name PROD_ABINITIO_9STRANDBAR_1tul__447_47754_0
Workunit 14678349
Created 21 Apr 2006 13:36:16 UTC
Sent 21 Apr 2006 19:59:11 UTC
Received 21 Apr 2006 21:37:41 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status -1073741819 (0xc0000005)
Computer ID 198415
Report deadline 5 May 2006 19:59:11 UTC
CPU time 2458.96875
stderr out <core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# random seed: 2692307
# cpu_run_time_pref: 21600
LoadLibraryA( symsrv.dll ): GetLastError = 126
LoadLibraryA( srcsrv.dll ): GetLastError = 126


BOINC Windows Runtime Debugger Version 5.5.0

---

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

I've got the following three work units running at a snails pace but running all the same. Perhaps they are resetting themselves as above, don't know as this is the first time I've looked at them. An Athlon64 3200+ and Sempron 3300+ running FC4 2.6.15-1.1831_FC4 and Sempron 2500+ running Mandrake linux 2.6.9-1.667. They are respectively running 19 hours 32 minutes at 38.52 percent done, 16 hours 50 minutes at 7.83 percent and 17 hours 31 minutes at 3.96 percent. All on 5.01
boinc.bakerlab.org/rosetta/result.php?resultid=17756250
boinc.bakerlab.org/rosetta/result.php?resultid=17794722
boinc.bakerlab.org/rosetta/result.php?resultid=17766055

---

Jose, just a thought, but seeing your PC has plenty of RAM and WinXP, could it be it's overclocked?

Because your PC's P4/2.26GHz CPU benchmarks 50% higher 1854 MFLOPS (host1) vs e.g. 1229 of a P4/2.53GHz CPU of mine (host2).

Are you sure your PC is stable?

Because, I've just had my 2nd "bad" WU in 3.5months of crunching with 3xP4s...

Gues What????
Another WU that went down the beaten Path: ( At this rate I may break the Record in WUs that have been in error, if not in credits not originally granted and CPU time not resulting in sucess...

I feel like crying...

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

[quote]Jose, just a thought, but seeing your PC has plenty of RAM and WinXP, could it be it's overclocked?

Over what?!!!! Although I belong to a team known for overclocking , I have not done a thing to my computer that can be considered overclocking. I basically know how to turn the computer on and off. You should see my face when I try to understand the messages regarding overclocking, benchmarks and floating decimal points , etc that are posted in my Team's Message Board...

The only thing I have done was to basically make my computer a Rosetta only Computer... Other than my Operating System ( and the basic tools that it come from them) , my Internet Service , the software printer , my DVD software , My anti virus and my word processor suite ( I use WP 10 ), the only other active program I am running is Rosetta via BOINC. I allotted 80% of my physical memory to Rosetta.

As to stability..the only thing that is becoming unstable in my household is me :).

PS

Wait: Yes I did something to "overclock" my computer: hanging from the monitor there is a voodoo doll in the shape of a cow with a lot of pins through it. The cow is named after my favorite DPC member. ( I kid you not.) Since to me intentional overclocking stuff is akin to voodoo, I performed a nice voodoo ceremony (that included chanting and ritual dancing) to get my computer "overclocked". Let's say after the effect of the beers passed , the hangover was painful.

---

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

Forgot to add. Rosetta is run 24/7 and my Internet connection 's speed is 100.0 Mbps (whatever that means)

---

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

Over what?!!!! Although I belong to a team known for overclocking , I have not done a thing to my computer that can be considered overclocking. I basically know how to turn the computer on and off. You should see my face when I try to understand the messages regarding overclocking, benchmarks and floating decimal points , etc that are posted in my Team's Message Board...

OK, never mind, I had to ask about overclocking, because of your computer's benchmarks (which are obviously due to some optimised BOINC client).

If I may give you some advice, I'd suggest that

1/ You download and install the latest BOINC client v5.4.x software from http://boinc.berkeley.edu/download.php?dev=1

and

2/ since your computer seems to be prone to errors, attach to RALPH (Rosetta's alpha test project). Just put the URL in BOINCMgr -> then to Projects &#8594; Attach to Project. The URL is http://ralph.bakerlab.org/

This way, you'll help track the errors which apparently arise on some PCs (none of my own PCs ever had similar problems)

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity