Im crunching nm_s82_r10 wu's at the moment got no errors like your getting, in fact its running quite stable so far... cross my fingers...:)

---

Funny enough most of my WUs run just fine - but why the heck are there ~5% (rough estimate) which do have errors?? *scratches head*

---

Lovely greetings, Cori

Who knows what the story is?? Bloody fickle these computors.. up until a few hrs ago I was running the stock app and ive changed to an opp app ssse3 and all is good taking avg 17min each wu

Glenn

---

Funny enough most of my WUs run just fine - but why the heck are there ~5% (rough estimate) which do have errors?? *scratches head*

It seems to go in spits and spurts but my quads-XP Home- are right now running 50/50 with errors... strange that there were no such problems prior to yesterday and I have changed nothing on my machines...

edit >> it looks like nearly all are completing just fine in BOINC Manager but when I look in the online account details I see 50/50 computation errors and that is odd...

ya its funny it seems to be happening more on the quads then the others...

as of 2 days ago everything was smooth,, i wouldnt have even checked

if i hadnt of noticed my daily output droped by almost half lol...

but yesterday and today are horrible..... NNW till its fixed :)

time to spread some love around :) :)

---

Well this is an r9, and other like it are there:

Task ID 1700236
Name nm_s82_r9_551302_1234449169_1
Workunit 1612303
Created 12 Feb 2009 15:57:10 UTC
Sent 12 Feb 2009 15:58:33 UTC
Received 12 Feb 2009 16:16:15 UTC
Server state Over
Outcome Client error
Client state Compute error
Exit status -1073741819 (0xffffffffc0000005)
Computer ID 1500
Report deadline 15 Feb 2009 15:58:33 UTC
CPU time 0
stderr out <core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>


Unhandled Exception Detected...

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

Engaging BOINC Windows Runtime Debugger...

---

Doesn't expecting the unexpected make the unexpected the expected?
If it makes sense, DON'T do it.

Task ID 1626452
Name nm_s82_r10_465192_1234432008_1
Workunit 1526193
Created 12 Feb 2009 12:14:52 UTC
Sent 12 Feb 2009 12:16:04 UTC
Received 12 Feb 2009 15:51:16 UTC
Server state Over
Outcome Success
Client state Done
Exit status 0 (0x0)
Computer ID 21898
Report deadline 15 Feb 2009 12:16:04 UTC
CPU time 1027.688
stderr out <core_client_version>6.4.5</core_client_version>
<![CDATA[
<stderr_txt>

</stderr_txt>
]]>

Validate state Valid
Claimed credit 2.75358423458219
Granted credit 30.60666
application version 0.16

Just looked and found this on my task list...
Glenn

---

Errm... now what will happen with all these different errors?
Do we have to put up with them? Or will there be a solution?

Here you can see the tasks on my lappy, still getting all kinds of errors. ;-(
And yes, I've re-downloaded several star files by resetting MW and even manual deletion from the project folder. And there were errors with long stderr out entries which didn't look too nice...

Although the most errors do happen immediately (while downloading or at the start of a new task) there are some which happen more at the end of processing.
A bit annoying I have to admit.

Any help would be appreciated.

---

Lovely greetings, Cori

Now gone through all the recommended proceedures -

1. reset project - done, and still a boat load of cumputer errors (no time take as reported)

2. detached and reattached to MW project- done, and still a boatload or errors.

This is only happening on my healthy quad.

Just making sure of something -- you guys getting the errors are using our stock app and not some optimized app right?

---

I'm using the v0.16 windows optimized app (the one you said was OK), but I think I finally got it straightened out.

Took me a while and I trashed some WUs, but all seems OK now.

---

Calm Chaos Forum...Join Calm Chaos Now

John and Cori, are you guys using an optimized app?

---

Gday Travis I am using an opp app ssse3ver 016 got from Ice's Link http://zslip.com/

Been using it now for nearly 24hrs have not had any computation errors like what has been seen the project has been granting me credit for the wu's since firing it up check out this thread if you havent already http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=627&nowrap=true#10417

So far so good for me anyways..
Glenn

---

John and Cori, are you guys using an optimized app?

Yes I am, the same as Labie.

The _s79_rX also seem to be affected, as you can see here. This shows 34, mainly _s79 WUs, have errored, and it seems to be getting worse.

I wonder why?

My other 2 slower rigs are not getting any errors, just the quad.

John and Cori, are you guys using an optimized app?

Yes I am, the same as Labie.

The _s79_rX also seem to be affected, as you can see here. Thios shows 34, mainly _s79 WUs, have errored, and it seems to be getting worse.

I wonder why?

My other 2 slower rigs are not getting any errors, just the quad.

If it's not a stock app, you might be asking the wrong people here. Have you tried deleting the binary and trying a new one or the stock app?

---

John and Cori, are you guys using an optimized app?

I'm also using the 'approved' 0.16 opti app - had never errors before with that one.
Also not every WU has errors.
I didn't change anything on my configuration when these errors started to happen, so I have been wondering if you changed something with the newer WUs?
The opti app hasn't been changed since the end of January.

---

Lovely greetings, Cori

John and Cori, are you guys using an optimized app?

I'm also using the 'approved' 0.16 opti app - had never errors before with that one.
Also not every WU has errors.
I didn't change anything on my configuration when these errors started to happen, so I have been wondering if you changed something with the newer WUs?
The opti app hasn't been changed since the end of January.

there's nothing new with the WU generation. could you try using the stock app for a bit and see if the problem still happens? i can't particularly debug an app that isn't ours :P

---

I was using a different opti application (0.14) a few days ago before I swapped to V0.16. Shortly after we got hit with these Error out issues, but not consistent.

I have just reported a load of work OK, as seen here from WU ID 1953986, and this includes the stripes I was erroring out big time on earlier.

I would have suspected it was perhaps some of my memory intermittently going bad. But, so many are reporting this problem over so many countries I am inclined to return to the client and WU combination.

It only seems to have happened since the release of the new stripes?

could you try using the stock app for a bit and see if the problem still happens? i can't particularly debug an app that isn't ours :P

I'll swap over now and see how things go for the next few hours.

The swap over will be easy, and to the 0.16 stock application. I will let the opti client complete the 4 _s79_r6_ WUs currently being crunched, first.

there's nothing new with the WU generation. could you try using the stock app for a bit and see if the problem still happens? i can't particularly debug an app that isn't ours :P

Ok, I will have a try - on my lappy now.

But I think there must be some aliens living in my puters. *LOLOL*

---

Lovely greetings, Cori