All my machines were getting Computation Errors.

Here is the specifics on one:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x007480C0 read attempt to address 0x9800503B

Engaging BOINC Windows Runtime Debugger...

I pulled everything off of Rosetta.

---

My computer has stopped DLing any new work from the rosetta project since
27 Oct 2009 3:20:11 UTC. I double-checked all my settings. Nothing has changed,
I'm just not receiving any new work. So what's happened now, any ideas?

---

My computer has stopped DLing any new work from the rosetta project since
27 Oct 2009 3:20:11 UTC. I double-checked all my settings. Nothing has changed,
I'm just not receiving any new work. So what's happened now, any ideas?

Whatcha getting for messages?

---

Rosetta Moderator: Mod.Sense

My computer has stopped DLing any new work from the rosetta project since
27 Oct 2009 3:20:11 UTC. I double-checked all my settings. Nothing has changed,
I'm just not receiving any new work. So what's happened now, any ideas?

I see you're getting tasks through from Einstein ok. Could it be something to do with debt on one project compared to another? Or the split of work between the two? Or just Boinc messing up scheduling again.

Additional info on what Boinc is reporting under the messages tab would help to pin the reason down.

---

Mike has figured out where the bugs are and is currently working on them.
there seems to be a conflict between the symmetry code and disulphide, which is why a lot of symm runs are failing.
also, there is an api bug for zip, which causes some of the i/o problems.

hopefully we'll be able to update at the beginning of next week.

My computer has stopped DLing any new work from the rosetta project since
27 Oct 2009 3:20:11 UTC. I double-checked all my settings. Nothing has changed,
I'm just not receiving any new work. So what's happened now, any ideas?

I see you're getting tasks through from Einstein ok. Could it be something to do with debt on one project compared to another? Or the split of work between the two? Or just Boinc messing up scheduling again.

Additional info on what Boinc is reporting under the messages tab would help to pin the reason down.

Problem solved, I notice. And in a big way.

New problem - too many WUs! ;)

---

Error on this WU after a couple of wasted hours of crunching, as follows:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00436BD8 read attempt to address 0x016AE000

I was using this machine, running XP SP3 and usinb BOINC version 6.6.41

Will suspend work fetch and await developments...

---

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

Segfault...

Let's leave the sticky on this thread until the existing 1.98 WUs have had 10 days to reach their expiration.

---

Rosetta Moderator: Mod.Sense

This may be ancient history with the release of 2.0 but I had several tasks with names like threading_bongs_pipeline_hb* hang under Windows System 7 at random percentage completion values. Bringing up the graphics window simply resulted in a blank window: I had to abort the tasks.

Example: task 293254584

---

This may be ancient history with the release of 2.0 but I had several tasks with names like threading_bongs_pipeline_hb* hang under Windows System 7 at random percentage completion values. Bringing up the graphics window simply resulted in a blank window: I had to abort the tasks.

Example: task 293254584

---

svincent, did you get a look at the task manager? Was the processing task getting CPU? It is possible that the graphic had a problem but the processing was continuing.

---

Rosetta Moderator: Mod.Sense

svincent, did you get a look at the task manager? Was the processing task getting CPU? It is possible that the graphic had a problem but the processing was continuing.

Graphics worked OK for other workunits. I didn't take a look at the task manager (will do next time) but was going on the combination of the Progress and Elapsed Time fields in the Boinc Manager: the former was stuck and the latter kept going. I had one such task that went on over 25 hours before I aborted it: unfortunately my results page doesn't go back far enough to find it. On the other hand I did have some workunits named threading_bongs_* complete successfully.

Sorry about the previous double post.

---

Two final 1.98 errors to report over the last week. The first on my main Vista desktop and one on my spiffy new W7 laptop.

threading_oct09_hb_t302__IGNORE_THE_REST_15390_247_1
{Edit: I was the wingman on this job after it failed for similar reasons on its first try}

Outcome Client error
Client state Compute error
Exit status -1073741819 (0xc0000005)
CPU time 15.8497

stderr out <core_client_version>6.6.41</core_client_version>
...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x005C28F0 read attempt to address 0x00000000

lr5_dun08_it02_B_rlbd_1eyv_SAVE_ALL_OUT_IGNORE_THE_REST_DECOY_15457_979_0
{Edit: the wingman failed on this job too, as a Mini 2.00 job}

Outcome Client error
Client state Compute error
Exit status 1 (0x1)
CPU time 10215.96

stderr out <core_client_version>6.10.17</core_client_version>
...
ERROR: Option file open failed for: relax_options_lr5_dun08_it02_B_yfsong

No errors at all on either machine on Beta 5.98 or MiniRosetta 2.00 WUs.

---