Unfortunately, I'm just leaving for a family weekend trip so can't figure things out right away. Please bear with us for a couple of days.

I guess the moral of the story is, make new releases early in the week when project people are available to help if that becomes necessary. Hindsight is of course wonderful, but perhaps a useful suggestion for the future. :)

---

Regards,
Bob P.

all 4.97's ive done with this machine have been erroring out, stopped crunchin to save on power bills til its fixed

https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=197500

---

https://boinc.bakerlab.org/rosetta/result.php?resultid=16647818
https://boinc.bakerlab.org/rosetta/result.php?resultid=16647880
https://boinc.bakerlab.org/rosetta/result.php?resultid=16647868
https://boinc.bakerlab.org/rosetta/result.php?resultid=16647860

All of the first four wu's I got with 4.97 failed. Three out of four within 85 seconds...

Sam-TNO-
Team-SciFi

---

Only one of my machines has made it to these work units. So far 6 out of 8 have failed on that machine.

---

I just started this today... and I was getting Unrecoverable error for result HBLR 1.0 s after about 10 minutes for 6 tries, then one ran for about 3 hours before giving that error... then another one ran about 90 minutes before a different error: Unrecoverable error for result FARELAX_NOFILTERS_1aiu....
I an turning this time waster off... someone might reply to me IF these results are somewhat usable, otherwise I am not going to donate my spare computer time to filling up a BIT bucket!

Don Jones

---

Linux v4.97 seems to work OK sofar (even for 8-hour long WUs).

Windows keeps having problems.

Sofar I've reduced WU runtime to just 1-hr WUs as suggested (to get through the weekend), although I'll probably just set the "No new work" flag for the project on Win PCs and crunch for my backup projects, until it gets fixed.

That's another good thing about BOINC projects.

---

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

Exit status -1073741819 (0xc0000005)
at address 0x00599FF4 read attempt to address 0x0ACFFB34
https://boinc.bakerlab.org/rosetta/result.php?resultid=16646578
Rosetta 4.97 Windows
Messages related to above error ...
Date Location Project ID Message
4/8/2006 4:37:40 PM carlos.cp3 rosetta@home 130 Starting result HBLR_1.0_2tif_426_5745_0 using rosetta version 497
4/8/2006 4:37:41 PM carlos.cp3 --- 131 request_reschedule_cpus: process exited
4/8/2006 5:16:26 PM carlos.cp3 rosetta@home 132 Started download of aa1dcj_09_05.400_v1_3.gz
4/8/2006 5:34:15 PM carlos.cp3 rosetta@home 133 Finished download of aa1dcj_09_05.400_v1_3.gz
4/8/2006 5:34:15 PM carlos.cp3 rosetta@home 134 Throughput 2698 bytes/sec
4/8/2006 5:34:16 PM carlos.cp3 --- 135 request_reschedule_cpus: files downloaded
4/8/2006 6:15:09 PM carlos.cp3 rosetta@home 136 Unrecoverable error for result HBLR_1.0_2tif_426_5745_0 ( - exit code -1073741819 (0xc0000005))
4/8/2006 6:15:09 PM carlos.cp3 --- 137 request_reschedule_cpus: process exited
4/8/2006 6:15:09 PM carlos.cp3 rosetta@home 138 Computation for result HBLR_1.0_2tif_426_5745_0 finished

---

Click signature for global team stats

Stopped running Rosetta........... again. Somebody ring a bell when this mess is fixed.... In the meantime I'll be Grid.org...

I am new here and using version 4.97. I too have almost all my WU's failing with similar codes. ***unrecoverable error for result HBLR_1.0_2reb_426_1061_0 (-exit code -1073741819 (0xc0000005))***

I'm really sorry about these problems. I checked yesterday on RALPH and everything seemed fine, but there clearly is a problem. Unfortunately, I'm just leaving for a family weekend trip so can't figure things out right away. Please bear with us for a couple of days.

Nothing wrong with your trip. But I wonder if you do realize the consequences if nobody else seems to react to serious problems

---

List of results that erroed out using Rosetta 4.97 on my Windows PC's
*Until the date of this post only - tommorrow I will make a new list !

Exit status -1073741819 (0xc0000005)
https://boinc.bakerlab.org/rosetta/result.php?resultid=16623409

Exit status -1073741819 (0xc0000005)
https://boinc.bakerlab.org/rosetta/result.php?resultid=16525178

Exit status -1073741819 (0xc0000005)
https://boinc.bakerlab.org/rosetta/result.php?resultid=16525161

Exit status -1073741819 (0xc0000005)
https://boinc.bakerlab.org/rosetta/result.php?resultid=16646341

Exit status -1073741819 (0xc0000005)
https://boinc.bakerlab.org/rosetta/result.php?resultid=16518794

Exit status -1073741819 (0xc0000005) [
https://boinc.bakerlab.org/rosetta/result.php?resultid=16523459

---

Click signature for global team stats

David What is up with all the BAD W/U I must have close to 500
4/8/2006 3:22:39 PM|rosetta@home|Unrecoverable error for result HBLR_1.0_1hz6_426_5085_0 ( - exit code -1073741819 (0xc0000005))
messages on all of my nodes running Rosetta.
You Asked for my/our help here Well you must realize that if you continue to give out W/U that stall our PC, or that can not complete the DC'ers here WILL lose faith in this project and the quality of the data we produce.
As I see it you must do some or more in-house testing before a new Ver.# or WU batch.
And as stated below you should NOT do any releases at a time that you can not be a full staff to make fixes.
This project cost Me/us a lot of money to run Not counting my time. And I do expect a lot more the 1 week of good W/U's to keep running
Please remove the bad W/U's or Ver# that is causing this so we/I can stop spinning or Cooling fans

---

If You Want The Best You Must forget The Rest
---------------And Join Free-DC----------------

David What is up with all the BAD W/U I must have close to 500
4/8/2006 3:22:39 PM|rosetta@home|Unrecoverable error for result HBLR_1.0_1hz6_426_5085_0 ( - exit code -1073741819 (0xc0000005))
messages on all of my nodes running Rosetta.
You Asked for my/our help here Well you must realize that if you continue to give out W/U that stall our PC, or that can not complete the DC'ers here WILL lose faith in this project and the quality of the data we produce.

This is what hurts the project when no one is around to respond, like on a weekend. As I mentioned below, new releases should be made when the project team is immediately available and on high alert to respond quickly to any problems (they probably should be on extra high alert the first day or so of any new release, even one that has been beta tested).

With so many people making so many contributions in energy, time, and effort, a project needs to be extra prudent with any changes.

Just my 2 cents! :)

---

Regards,
Bob P.

OK, "new" v4.98 downloaded for Win and running already.

Meanwile, for the last 4 hours, I had set WU-runtime = 1hr and all WUs completed OK without errors on Win too.

Btw, I just re-connected to RALPH (Rosetta's ALPHA test project), which I had set to "No new work" recently, as my PCs never had any problems for the past 2 months anyway LOL

---

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

since last night ver .97 is causing TONS of errors on all my computers. this is why people avoid this project. i have had about enough of these bugs myself. about to cross the line and crunch for something else more stable.

---

I am new here and using version 4.97. I too have almost all my WU's failing with similar codes. ***unrecoverable error for result HBLR_1.0_2reb_426_1061_0 (-exit code -1073741819 (0xc0000005))***

I'm really sorry about these problems. I checked yesterday on RALPH and everything seemed fine, but there clearly is a problem. Unfortunately, I'm just leaving for a family weekend trip so can't figure things out right away. Please bear with us for a couple of days.

Nothing wrong with your trip. But I wonder if you do realize the consequences if nobody else seems to react to serious problems

Yeah, sorry we didn't catch something sooner, but on the WU types we were testing earlier, everything was going up and validating successfully. That was until we got the HBLR units in the morning, and only then did failures start comming out...

A couple HBLR units did validate on my machine here (over on RALPH), but the vast majority were a no go, with many of them getting 3 failures, and some 2 with 1 success. Others didn't have a report then, so not sure what became of them...

Until we got the newer WU types, wasn't able to report on any problems with them obviously, and could only report on the older types... Sorry us testers weren't able to catch this problem before it started rolling out...

---

WU 13577480 produced:

<core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# random seed: 1359430
# cpu_run_time_pref: 7200
No heartbeat from core client for 31 sec - exiting
# cpu_run_time_pref: 7200

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x007022EA read attempt to address 0x0EB4FC6C


Dump of the Worker(offending) thread:
1: 04/09/06 15:06:25


Dump of the Timer thread:
2: 04/09/06 15:06:25


Dump of the Graphics thread:
3: 04/09/06 15:06:25


Exiting...

</stderr_txt>

Only BOINC running, apps sent to be pre-empted.

Errored out three times now so WU has cancelled.

---

since last night ver .97 is causing TONS of errors on all my computers. this is why people avoid this project. i have had about enough of these bugs myself. about to cross the line and crunch for something else more stable.

Before rushing to condemn, let's summarise yesterday's event: it was a problem with v4.97 under Windows (as far as I could tell from my machines, Linux v4.97 had no problems) which lasted about 16 hours, until D.Kim rolled-back the executable to the previous stable version.

IMHO it was much less of a *real* issue than the "stuck at 1%" issue (which btw I encountered just ONCE in 3 months of crunching on 3x P4 PCs, but I realise it occurs much more often for other people), because yesterday WUs simply errored out for several hours, but NO manual intervention whatsoever was/is needed by the operator.

End result: probably about half a day of crunching lost for Win PCs.

So, my Win PCs spent about half a day crunching for nothing.

But, I look it this way: Currently all other BOINC projects use a "quorum" of 3 or 4, and initial replication 3-5, i.e. send the very same WU to 3-5 (!!!) PCs, effectively using just 1/3rd to 1/5th (and sometimes even less) of raw donated CPU time donated by us the BOINC donors.

PS: Ofcourse I'm unhappy that the project did an upgrade this way, without someone monitoring it closely for the next 6-12 hours. But it's Murphy's law and I try to keep things in perspective.

---

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

Until we got the newer WU types, wasn't able to report on any problems with them obviously, and could only report on the older types... Sorry us testers weren't able to catch this problem before it started rolling out...

I disagree of the quoted above

I started the thread at ralph@home announcing the new version 4.97 to test
on 7 April at 09:37 UTC

by 12:52 UTC 7 April, I have already reported this error on Windows 4.97

by 00:24 UTC 8 April, Son Goku posted that 4.97 was working fine

After that time ... 8 April, is that 4.97 go to rosetta@home ...


I wonder why 4.95 that was working very well ... fixed several problems.
is not what was placed into rosetta@home instead -:(
http://www.fadbeens.co.uk/phpBB2/viewtopic.php?t=53&start=165

Now, that was rolled back to 4.83, I know why I crunched all the day
w/o completing only one WU of 4.98 into two of my pcs

-> see my signature ... my rac is failing down on rosetta -:(

So, I will STOP crunching to rosetta again, until a new version that
checkpoint enough to allow swapping apps removing from ram, comes in.

4.95 was that version !!! 4.96 too

---

Click signature for global team stats

What is interesting here is that the RALPH testers are usually running BOINC version 5.2.32 and most Rosetta users are running BOINC 5.2.13. This may be part of the issue.

5.2.32? I can't find that build anywhere. I know I never tested it. 5.3.31 is the latest alpha build. Here's a list of all V5 builds from Boinc to date and release dates/times
(note: I trimmed mac, apple, and pdbs' from the list to shorten it):

boinc_5.1.1_i686-pc-linux-gnu.sh 30-Aug-2005 21:37 2.8M
boinc_5.1.1_windows_intelx86.exe 30-Aug-2005 21:37 9.9M
boinc_5.1.2_i686-pc-linux-gnu.sh 07-Sep-2005 11:35 2.8M
boinc_5.1.2_windows_intelx86.exe 07-Sep-2005 11:26 10M
boinc_5.1.3_i686-pc-linux-gnu.sh 09-Sep-2005 11:16 2.8M
boinc_5.1.3_windows_intelx86.exe 09-Sep-2005 11:17 10M
boinc_5.1.4_i686-pc-linux-gnu.sh 20-Sep-2005 14:48 2.8M
boinc_5.1.4_windows_intelx86.exe 20-Sep-2005 14:48 10M
boinc_5.1.5_i686-pc-linux-gnu.sh 29-Sep-2005 00:46 2.8M
boinc_5.1.5_windows_intelx86.exe 29-Sep-2005 00:46 10M
boinc_5.1.6_i686-pc-linux-gnu.sh 01-Oct-2005 02:53 2.8M
boinc_5.1.6_windows_intelx86.exe 01-Oct-2005 02:54 10M
boinc_5.1.8_i686-pc-linux-gnu.sh 05-Oct-2005 19:28 2.8M
boinc_5.1.8_windows_intelx86.exe 05-Oct-2005 19:28 10M
boinc_5.1.9_i686-pc-linux-gnu.sh 09-Oct-2005 18:42 2.9M
boinc_5.1.9_windows_intelx86.exe 09-Oct-2005 18:42 10M
boinc_5.1.10_i686-pc-linux-gnu.sh 10-Oct-2005 12:27 2.9M
boinc_5.1.10_windows_intelx86.exe 10-Oct-2005 12:27 10M
boinc_5.2.0_i686-pc-linux-gnu.sh 10-Oct-2005 16:48 2.9M
boinc_5.2.0_windows_intelx86.exe 10-Oct-2005 16:48 10M
boinc_5.2.1_i686-pc-linux-gnu.sh 10-Oct-2005 19:55 2.9M
boinc_5.2.1_windows_intelx86.exe 10-Oct-2005 19:56 10M
boinc_5.2.2_i686-pc-linux-gnu.sh 17-Oct-2005 14:33 2.9M
boinc_5.2.2_windows_intelx86.exe 17-Oct-2005 14:34 10M
boinc_5.2.3_i686-pc-linux-gnu.sh 19-Oct-2005 19:59 3.4M
boinc_5.2.4_i686-pc-linux-gnu.sh 19-Oct-2005 23:22 3.4M
boinc_5.2.5_i686-pc-linux-gnu.sh 27-Oct-2005 14:01 3.4M
boinc_5.2.5_windows_intelx86.exe 27-Oct-2005 14:02 10M
boinc_5.2.6_i686-pc-linux-gnu.sh 31-Oct-2005 17:05 3.4M
boinc_5.2.6_windows_intelx86.exe 31-Oct-2005 17:06 10M
boinc_5.2.7_i686-pc-linux-gnu.sh 08-Nov-2005 00:52 3.4M
boinc_5.2.7_windows_intelx86.exe 08-Nov-2005 00:53 10M
boinc_5.2.8_i686-pc-linux-gnu.sh 22-Nov-2005 17:47 3.4M
boinc_5.2.8_windows_intelx86.exe 22-Nov-2005 17:48 10M
boinc_5.2.9_windows_intelx86.exe 25-Nov-2005 20:06 10M
boinc_5.2.10_windows_intelx86.exe 26-Nov-2005 01:08 10M
boinc_5.2.11_windows_intelx86.exe 26-Nov-2005 03:48 10M
boinc_5.2.12_windows_intelx86.exe 26-Nov-2005 18:22 10M
boinc_5.2.13_i686-pc-linux-gnu.sh 29-Nov-2005 02:46 3.5M
boinc_5.2.13_windows_intelx86.exe 29-Nov-2005 02:47 10M
boinc_5.2.14_windows_intelx86.exe 04-Dec-2005 03:51 10M
boinc_5.2.15_i686-pc-linux-gnu.sh 28-Dec-2005 06:14 3.5M
boinc_5.2.15_windows_intelx86.exe 28-Dec-2005 06:14 10M
boinc_5.3.2_windows_intelx86.exe 06-Dec-2005 03:32 10M
boinc_5.3.3_windows_intelx86.exe 19-Dec-2005 05:59 10M
boinc_5.3.6_windows_intelx86.exe 28-Dec-2005 05:50 10M
boinc_5.3.15_i686-pc-linux-gnu.sh 30-Jan-2006 15:27 3.5M
boinc_5.3.15_windows_intelx86.exe 27-Jan-2006 13:22 10M
boinc_5.3.16_i686-pc-linux-gnu.sh 30-Jan-2006 19:19 3.5M
boinc_5.3.16_windows_intelx86.exe 30-Jan-2006 19:09 10M
boinc_5.3.17_windows_intelx86.exe 02-Feb-2006 13:19 10M
boinc_5.3.20_i686-pc-linux-gnu.sh 23-Feb-2006 00:57 3.5M
boinc_5.3.20_windows_intelx86.exe 23-Feb-2006 00:49 10M
boinc_5.3.21_i686-pc-linux-gnu.sh 24-Feb-2006 00:21 3.5M
boinc_5.3.21_windows_intelx86.exe 24-Feb-2006 00:24 10M
boinc_5.3.22_i686-pc-linux-gnu.sh 24-Feb-2006 17:35 3.5M
boinc_5.3.22_windows_intelx86.exe 24-Feb-2006 18:00 10M
boinc_5.3.23_i686-pc-linux-gnu.sh 01-Mar-2006 03:08 3.5M
boinc_5.3.23_windows_intelx86.exe 01-Mar-2006 03:05 10M
boinc_5.3.24_i686-pc-linux-gnu.sh 06-Mar-2006 13:14 3.5M
boinc_5.3.24_windows_intelx86.exe 06-Mar-2006 12:39 10M
boinc_5.3.26_i686-pc-linux-gnu.sh 14-Mar-2006 01:21 3.5M
boinc_5.3.26_windows_intelx86.exe 14-Mar-2006 01:11 10M
boinc_5.3.27_i686-pc-linux-gnu.sh 17-Mar-2006 02:18 3.6M
boinc_5.3.27_windows_intelx86.exe 17-Mar-2006 02:14 10M
boinc_5.3.28_i686-pc-linux-gnu.sh 21-Mar-2006 15:20 3.6M
boinc_5.3.28_windows_intelx86.exe 21-Mar-2006 15:03 10M
boinc_5.3.29_i686-pc-linux-gnu.sh 28-Mar-2006 00:09 3.6M
boinc_5.3.29_windows_intelx86.exe 28-Mar-2006 00:32 10M
boinc_5.3.30_i686-pc-linux-gnu.sh 28-Mar-2006 23:26 3.6M
boinc_5.3.30_windows_intelx86.exe 29-Mar-2006 00:02 10M
boinc_5.3.31_i686-pc-linux-gnu.sh 30-Mar-2006 18:37 3.6M
boinc_5.3.31_windows_intelx86.exe 30-Mar-2006 19:54 8.6M


Perhaps you've some new source I'm not aware of, and I'd like to try it. I've seen you mention it a couple times.

It seems like BOINC v5.3.31 is latest, to see the BETA versions one can use the URL

http://boinc.berkeley.edu/download.php?dev=1

whereas the "official" stable versions are at

http://boinc.berkeley.edu/download.php

---

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