Here's one, it went over 63 hours so I finally just had to kill it. Doubt I will get credit for it, :(

http://setiathome.berkeley.edu/workunit.php?wuid=76855572

See my post #305676 in this thread. Maybe the same problem?

---

I've had two Workunits which produced an "Validation Error"

http://setiathome.berkeley.edu/result.php?resultid=327266416
http://setiathome.berkeley.edu/result.php?resultid=325117484

---

This is what I am getting: Unrecoverable error for result 28fe99aa.4515.353.204836.3.88_2 ( - exit code -1 (0xffffffff)) I have already posted the same problem on the number crunching message board, sorry!

---

I was having trouble getting new work units, so I detached from the project and reattached and got some new WU's...but each one has got a computation error 2 seconds after starting

5/18/2006 7:20:53 PM|SETI@home|Starting task 23fe99aa.15852.4161.978394.3.3_1 using setiathome_enhanced version 512
5/18/2006 7:20:55 PM|SETI@home|Unrecoverable error for result 23fe99aa.15852.4161.978394.3.3_1 ( - exit code -1073741515 (0xc0000135))

---

Human Stupidity Is Infinite...

I was having trouble getting new work units, so I detached from the project and reattached and got some new WU's...but each one has got a computation error 2 seconds after starting

5/18/2006 7:20:53 PM|SETI@home|Starting task 23fe99aa.15852.4161.978394.3.3_1 using setiathome_enhanced version 512
5/18/2006 7:20:55 PM|SETI@home|Unrecoverable error for result 23fe99aa.15852.4161.978394.3.3_1 ( - exit code -1073741515 (0xc0000135))

There is a thread on the Einstein forum

http://einstein.phys.uwm.edu/forum_thread.php?id=893

that has some hints to fixing this problem.

Found it by using google. :-)

---

Thanks, before I tried that though, I deleted the SETI folder, detatched from the project and let it redownload the files and it seems to work...so go figure...

---

Human Stupidity Is Infinite...

Eric, we have someone with crashing graphics and a big error dump in stderr.txt over in this thread. If you could take a look?

---

I see some messages here about very long-running WUs without progress.
Well, I got one too, WU 30mr99aa.29736.12129.123590.3.0 in my case.
My result shows a computation error 0xc0000005 but that is only because I tried to display the graphics to see what was going on.
The real problem was that it had already accumulated more than 54.000 seconds of CPU time, about twice the time of the other Enhanced WUs, and that it seemed to be "stuck" at about 9%. The percentage wasn't increasing, but the CPU time was.
Can enhanced WUs get stuck in an unending loop?

I had the same yesterday with this result.

It was stuck and I aborted the WU.

Got my first 5.15 WU.. and it errored out. Dont recall having seen this error before.


Result is here

...odd...

Paul.

edit - have not seen any probs with 5.15 while crunching beta but it is 2 different hosts... /edit

19/05/2006 12:26:27|BBC Climate Change Experiment|Pausing task hadcm3ln_0crj_00355717_1 (left in memory)
19/05/2006 12:26:27|SETI@home|Resuming task 22mr99aa.14090.5346.117328.3.64_0 using setiathome_enhanced version 515
19/05/2006 12:37:59|SETI@home|setiathome_enhanced not responding to screensaver, exiting
19/05/2006 12:38:03|SETI@home|Unrecoverable error for result 22mr99aa.14090.5346.117328.3.64_0 ( - exit code -1 (0xffffffff))
19/05/2006 12:38:03|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
19/05/2006 12:38:03||Rescheduling CPU: application exited
19/05/2006 12:38:03|SETI@home|Computation for task 22mr99aa.14090.5346.117328.3.64_0 finished

---

Wanna visit BOINC Synergy? Click my stats!

Join BOINC Synergy Team

18/05/2006 8:05:48 PM|SETI@home|Task 23fe99aa.15852.4066.592332.3.139_1 exited with zero status but no 'finished' file

I just iticed this.

---

Just finished crunching my first 5.15 app and it crashed and burned.
Minor *burp* as in "nothing to worry about?"

---

I realized the dead-end roads I ended up taking weren't always my fault. Many thanks to all that have helped in this - and you know who you are.
TheBeatenPath

I have a problem with a work unit on my seti@home enhanced. In particular with work unit 15no99ab.21008.3233.123566.3.115_1 It has been working on this unit now for almost 20 hours and is making no progress. When I first noticed something unusual I noted that it put unit progress at 14.14% complete and time to completion at 119.00 hours left to completion. The Progress of 14.14% has not changed and the time left to completion keeps getting longer. The time left to completion now is 120:36:53 and getting longer. and the progress remains at 14.14%. Does anyone know anything about this or have any suggestions? PS I am not very computer literate. I was barely able to get seti started in the first place so suggestions would be best in great detail.

Thanks in advance for your help

Roy

---

I have a problem with a work unit on my seti@home enhanced. In particular with work unit 15no99ab.21008.3233.123566.3.115_1 It has been working on this unit now for almost 20 hours and is making no progress.

Some of those with a similar problem have reported that simply quitting and relaunching BOINC has nudged the stuck task out of its rut.

---

Just finished crunching my first 5.15 app and it crashed and burned.
Minor *burp* as in "nothing to worry about?"

I was crunching my first enhanced unit last night, took about 10 hours and the computer shut down at one point, not sure when. Could the enhanced unit make a computer run hot?

Thanks,

Nick

---

I have a problem with a work unit on my seti@home enhanced. In particular with work unit 15no99ab.21008.3233.123566.3.115_1 It has been working on this unit now for almost 20 hours and is making no progress.

Some of those with a similar problem have reported that simply quitting and relaunching BOINC has nudged the stuck task out of its rut.

Thanks!! I think that did it. Or perhaps someone else read my post and fixed my problem because I noticed in the message portion something about downloading/uploading and things about readme text/copyright/and copying....what ever....thank to whoever. It seems to be working great again.

---

[…] perhaps someone else read my post and fixed my problem because I noticed in the message portion something about downloading/uploading and things about readme text/copyright/and copying....what ever....thank to whoever. It seems to be working great again.

That was probably the newly released v5.15 app downloading, along with new work to replace the WU you finished.

---

Could the enhanced unit make a computer run hot?

No more than the previous versions.

---

Grant
Darwin NT

I've removed the Boinc screensaver and (fingers crossed) I've had three units in a row complete. If anyone else has the same probs it may be worth a try.

They're out there somewhere,
Happy searching
Marts

If you can unhide your computers, I could look at the detailed error messages. It's likely that this is the problem that happens in the JPEG library. If so, I'm working on a fix.

Eric

Hi All

Since moving to Seti enhanced v5.1.2 around 9 in 10 of my work units fail to complete with the following message. "12/05/2006 00:03:30|SETI@home|Unrecoverable error for result 01mr99aa.26277.30545.972158.3.131_0 ( - exit code -1073741819 (0xc0000005))" Obviously the date and WU ref change but the exit code is always the same. Does anyone know what this specific exit code means?

Any enlightenment would be much appreciated.

Thanks
Marts

XP with sp2
AMD Athlon XP 2800+
1024 MB RAM
Nvidia 6800 128MB
Running Windows firewall only

Thanks for the response Eric. I've replaced the seti512.jpg in C:\\Program Files\\BOINC\\projects\\setiathome.berkeley.edu with one downloaded from your servers unfortunately this did not solve the problem. I was processing the old style WU's with no probs but the 5.12 ones keep falling over on me with the error message above. I've unhidden my PC's now so if you get time to take a look any advice would be much appreciated.

Thanks
Martin

---

I have a problem with a work unit on my seti@home enhanced. In particular with work unit 15no99ab.21008.3233.123566.3.115_1 It has been working on this unit now for almost 20 hours and is making no progress.

Some of those with a similar problem have reported that simply quitting and relaunching BOINC has nudged the stuck task out of its rut.

Thanks!! I think that did it. Or perhaps someone else read my post and fixed my problem because I noticed in the message portion something about downloading/uploading and things about readme text/copyright/and copying....what ever....thank to whoever. It seems to be working great again.

I just had this happen to me too. Something definitely not right. I noticed that a WU took 15 hours to get just over halfway, so I suspended and resumed it to see if that would help, and it did. The client then promptly uploaded the result. (Reporting a result seems to be a separate thing altogether, as I often have to do that manually. Reporting a result should happen at the same time a result is uploaded!)

Here's the example,
http://setiathome.berkeley.edu/workunit.php?wuid=78846679 computer 1924541

stock app, setienhanced 5.12

Perhaps later versions fix this problem,

Andy.

I've also discovered some thread synchronization problems in the BOINC api that I will try to resolve at the same time that I fix this.

I noticed something about the Enhanced results that were reported as "running a long time, but percentage is stuck": it seems to occur on systems with more than one (virtual) CPU.

Look at these results that were reported earlier in this thread as "stuck":
Result 77297562
Result 76855572
Result 78282589
In the first two examples it is really clear: the error result is coming from a dual-CPU computer, the other results are OK and are done by single-CPU computers. The third example is less clear because there are other errors there, but still the "stuck" result (the first one) is a dual-CPU computer.
And my own stuck result (deleted in the meantime) was also on a computer with 2 virtual CPUs...

This could very well be something related to those "thread synchronization problems" mentioned by Eric. Eric, if you are still looking at those thread synchronization problems, I hope this gives you an idea where to look for it.

EDIT: guess what, the stuck result posted by Andy just before my post is also crunched by a computer with 2 CPUs

---