https://boinc.bakerlab.org/rosetta/result.php?resultid=228610191
<core_client_version>6.6.5</core_client_version><![CDATA[<message>
- exit code -1073741819 (0xc0000005)
</message><stderr_txt>
# cpu_run_time_pref: 28800
# random seed: 3595866

---

Exceptions at various addresses on two different computers. ONly one of these tasks had a wingman but that person also had an exception death.

230043321 0x008BB97B read attempt to address 0x060A0000
230072124 0x008BB9A5 read attempt to address 0x0BA5A000
229964104 0x008BB97B read attempt to address 0x0A082000
229979933 0x008BB92B read attempt to address 0x0BB38000
230017643 0x008BB92B read attempt to address 0x0A23C000

resultid=230017087 Wing man still to return result.
resultid=230017086 Wing man also crashed

---

Have a crunching good day!!

Another crash like the ones below 230072124 and 230089446

And more crashes ... you know, this was the reason I stopped RaH a couple years ago ... non-stop errors ... and some of these tasks are wasting in the region of 10-20 minutes ...

230171238
230225023

bunch of faults, maybe 5, windows xp, vista 64, etc. Started about 3 days ago. These faults are the type that show up over the desktop and ask if microsoft should be informed.

from xp event log
Faulting application rosetta_beta_5.98_windows_intelx86.exe, version 0.0.0.0, faulting module rosetta_beta_5.98_windows_intelx86.exe, version 0.0.0.0, fault address 0x0084fcf3.

Yeah, That is what I am getting too ... I keep forgetting to check to see if that pop-up is locking the CPU meaning until you dismiss it you lost the CPU ... if you get it again, let us know ... I keep making a mental note to check and keep forgetting ...

Today's list:
230306967 0x008BB92B read attempt to address 0x0BECC000
230288293 0x008BB955 read attempt to address 0x0B6D3000
230192144 0x008BB9A5 read attempt to address 0x0DD3F000
230089446 0x008BB97B read attempt to address 0x0C06A000
230018563 0x008BB92B read attempt to address 0x09D7A000

Only one today:

230534122 0x008BB955 read attempt to address 0x0C07C000

Yeah, That is what I am getting too ... I keep forgetting to check
to see if that pop-up is locking the CPU meaning until you dismiss it you
lost the CPU ... if you get it again, let us know ... I keep making a
mental note to check and keep forgetting ...

The same to me, on my Quad, 3 days 2 cores was doing nothing until today I
press "don't send".....

Here are:

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

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

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

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

so it is 2p64...

2p64__BOINC_SYMM_FOLD_AND_DOCK_RELAX-2p64_-native_frag2__7622_18636_1
Exit status -1073741819 (0xc0000005)
CPU time 207.6563
# random seed: 2816709
Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x008BB955 read attempt to address 0x1383C000

231014076 0x008BB97B read attempt to address 0x0A7ED000

Very strange result:
https://boinc.bakerlab.org/rosetta/result.php?resultid=230979688
and respective WU:
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=208222634
Why canonical result do 108 decoys and mine do 12 decoys? And why I got 'Workunit error - check skipped'? And why there are three results?

Very strange result:
https://boinc.bakerlab.org/rosetta/result.php?resultid=230979688
and respective WU:
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=208222634
Why canonical result do 108 decoys and mine do 12 decoys? And why I got 'Workunit error - check skipped'? And why there are three results?

The difference is in the:

# cpu_run_time_pref: 86400

yours is 10,800 ...

8 times more runtime gets more decoys ...

Very strange result:
https://boinc.bakerlab.org/rosetta/result.php?resultid=230979688
and respective WU:
https://boinc.bakerlab.org/rosetta/workunit.php?wuid=208222634
Why canonical result do 108 decoys and mine do 12 decoys? And why I got 'Workunit error - check skipped'? And why there are three results?

The difference is in the:

# cpu_run_time_pref: 86400

yours is 10,800 ...

8 times more runtime gets more decoys ...

Ok, but why more runtime?

With Rosetta@home, you can configure a runtime preference. This is done via the "[Participants]" link at the top of this forum page. And then click on the Rosetta preferences. The result of increasing the runtime is less bandwidth and scheduler requests on the server, and then the tasks just run more models until the target runtime is approached.

The particular WU you show suffers from the dreaded bug in the BOINC server code where a result is accepted after the deadline is reached but the task has already been reissued. There has been a BOINC trac item open to fix this for over a year.
http://boinc.berkeley.edu/trac/ticket/276

---

Rosetta Moderator: Mod.Sense

With Rosetta@home, you can configure a runtime preference. This is done via the "[Participants]" link at the top of this forum page. And then click on the Rosetta preferences. The result of increasing the runtime is less bandwidth and scheduler requests on the server, and then the tasks just run more models until the target runtime is approached.

The particular WU you show suffers from the dreaded bug in the BOINC server code where a result if accepted after the deadline is reached but the task has already been reissued. There has been a BOINC trac item open to fix this for over a year.
http://boinc.berkeley.edu/trac/ticket/276

Thank you for explanation!

2p64__BOINC_SYMM_FOLD_AND_DOCK_RELAX-2p64_-native_frag2__7622_17767_0
got %5 done before faulting. I went and aborted it as it was hung after the app faulted.

Faulting application rosetta_beta_5.98_windows_intelx86.exe, version 0.0.0.0, faulting module rosetta_beta_5.98_windows_intelx86.exe, version 0.0.0.0, fault address 0x0084fcf3.

====

I monitor my farm using boincview and when it shows a yellow background I know there is a problem. When I logged in remotely, I was greeted with a fault report and was asked if I wanted to report it to microsoft.

There have been 3 separate rosetta app faults since Feb 21. My event log goes back to 10/23/08 and there are no other app faults. Milkyway and Poem are the other 2 boinc apps besides rosetta.

Windows Xp, sp3
BM 6.2.18
Dual MP 2800

The particular WU you show suffers from the dreaded bug in the BOINC server code where a result is accepted after the deadline is reached but the task has already been reissued. There has been a BOINC trac item open to fix this for over a year.
http://boinc.berkeley.edu/trac/ticket/276

I am still of the opinion that this is not at all a bug to be dreaded. All parties involved still seem to be compensated with appropriate credits. Interested parties might like to have a look at the following wus (while they last):

2p64__BOINC_SYMM_FOLD_AND_DOCK_RELAX-2p64_-native_frag2__7622_8156

2 "Compute error", 1 subsequent success after "Too many error results Too many total results". Which somehow proves a point.


2p64__BOINC_SYMM_FOLD_AND_DOCK_RELAX-2p64_-native_frag2__7622_13799

1 "No reply", 1 "Compute error", after "Too many total results" 1 apparent success with no local error messages, but the result file shows the wu erroring out also with the third cruncher:
CPU time 11808.83
stderr out

<core_client_version>6.6.12</core_client_version> [[but computed with 6.6.11]]
<![CDATA[
<stderr_txt>
Rosetta@home Macintosh Stack Size checker.
Original size: 0.
Maximum size: 8388608.
RLIM_INFINITY 0
shell-init: could not get current directory: getcwd: cannot access parent directories: Permission denied [[normal error message in my situation]]
# cpu_run_time_pref: 21600
# random seed: 2821546
**********************************************************************
Rosetta score is stuck or going too long. Watchdog is ending the run!
Stuck at score -147.965 for 900 seconds
**********************************************************************
GZIP SILENT FILE: ./xx2p64.out

</stderr_txt>
]]>

Validate state Valid

Also now getting errors with rosetta_beta_5.98_windows_intelx86, but only after rebooting Windoze. Running BOINC on Server 2003 32bit. So far it crashed three times in a row and appears to have given up. Sent error reports to MS.
I looked at the reports, but the gibberish in there doesn't tell me a thing. Let me know if you need more specific info other than "it crashed and seems to be broken". :)

RamonS, if you could post a link to the task that failed, that would be great.

---

Rosetta Moderator: Mod.Sense