Hello
Getting the following error:
11/8/2007 7:30:47 AM|Milkyway@home|Reason: Unrecoverable error for result gs_1_1194578582_33452_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))

This error also causes a windows error of a failed application which can/is reported to MS.

---

Hello
Getting the following error:
11/8/2007 7:30:47 AM|Milkyway@home|Reason: Unrecoverable error for result gs_1_1194578582_33452_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))

This error also causes a windows error of a failed application which can/is reported to MS.

thats weird, has this happened multiple times or just once?

thats weird, has this happened multiple times or just once?

This happened on two of my machines.
Result ID 41820 on Host 916 and the other Result ID 210 on Host 214
Interesting the second one is WUID 22 and 13 others failed as well along with a download error and finally one success.

Hope this helps.

---

Got the same error with a windows popup, last batch faulty?

Got the same error with a windows popup, last batch faulty?

I've gotten a few on each of two machines. But one of them has been resent and it completed successfully.

---

Calm Chaos Forum...Join Calm Chaos Now

Just got the same.
Windows error pop-up and then computational error: The faulty WU is http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=117364.

EDIT: It seems only "gs_5" WUs are broken on my lappy. :-D

---

Lovely greetings, Cori

All of mine are erroring out at 23 seconds in to the work.

Results


[EDIT] I'm getting the errors on both GS_5 and GS_4 WUs [/EDIT]

---

Calm Chaos Forum...Join Calm Chaos Now

Mine errored out at 33 to 36 seconds.

http://milkyway.cs.rpi.edu/milkyway/result.php?resultid=117329

---

I've gone to No New Tasks for now. Kinda silly for me to go continuously between 2 machines to click the MS error box.

---

Calm Chaos Forum...Join Calm Chaos Now

7 in a row ended with a windows popup error:

The exception Breakpoint
A breakpoint has been reached (0x80000003) occurred in the application at location 0x0047f646.

and the Boinc error:
10/11/2007 18:12:54|Milkyway@home|Reason: Unrecoverable error for result gs_4_1194764357_64_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))

All after 39 - 40 seconds

Huge stderr_out on all of them.

I'm not sure whats up with the invalid argument error yet -- but i think some work units are erroring because when i increased the work being done in each work unit it went over the alloted time specified. new work units should have a much longer report time so hopefully that problem will be fixed.

Only got one duff one in the last batch I got. I ran each until they got past the previous blockage and then suspended them so I could see if any would fail, and only one did.

[Edit]Only thing is, when they do fail, they lock up Boinc so that it can't do anything else until the windows error box is closed. I got another duff one after reporting a success, but I feel the pub beckoning (9pm local) and don't want to leave the machine vulnerable to locking up overnight. Could you purge the broken ones, Travis, so they don't get reissued? [/Edit]

All those from gs_4_11947810xx seem to be OK, at least for me. They're quite a bit longer as well as Travis predicted in another thread. 6 times as long for me as the previous wus before the bunch of failures.

My VISTA box seemed to have crunched OK, but it is stuck in the upload mode. WHen the system tries to report the unit anyway, i get this:

11/10/2007 1:05:44 PM|Milkyway@home|Scheduler RPC succeeded [server version 511]
11/10/2007 1:05:44 PM|Milkyway@home|Message from server: Result gs_1_1194561432_317_1 is no longer usable


but it is still stuck in my upload queue, and will not show in my list of computers that the VISTA box has even had a single WU.

Also, the age of the files in the computers list is only one day, the 10th of november. Is this normal for this project to not show a longer history of file processed?

Only got one duff one in the last batch I got. I ran each until they got past the previous blockage and then suspended them so I could see if any would fail, and only one did.

[Edit]Only thing is, when they do fail, they lock up Boinc so that it can't do anything else until the windows error box is closed. I got another duff one after reporting a success, but I feel the pub beckoning (9pm local) and don't want to leave the machine vulnerable to locking up overnight. Could you purge the broken ones, Travis, so they don't get reissued? [/Edit]

All those from gs_4_11947810xx seem to be OK, at least for me. They're quite a bit longer as well as Travis predicted in another thread. 6 times as long for me as the previous wus before the bunch of failures.

i'm pretty sure the broken ones are purged so they shouldn't be downloaded.

this also happens to me

10-11-2007 22:22:53|Milkyway@home|Reason: Unrecoverable error for result gs_4_1194786145_853_0 (Um ou mais argumentos são inválidos (0x80000003) - exit code -2147483645 (0x80000003))

portuguese client, so there it goes the translation

10-11-2007 22:22:53|Milkyway@home|Reason: Unrecoverable error for result gs_4_1194786145_853_0 (One or more arguments are invalid (0x80000003) - exit code -2147483645 (0x80000003))

is there some way to make this not to happen?

Only got one duff one in the last batch I got. I ran each until they got past the previous blockage and then suspended them so I could see if any would fail, and only one did.

[Edit]Only thing is, when they do fail, they lock up Boinc so that it can't do anything else until the windows error box is closed. I got another duff one after reporting a success, but I feel the pub beckoning (9pm local) and don't want to leave the machine vulnerable to locking up overnight. Could you purge the broken ones, Travis, so they don't get reissued? [/Edit]

All those from gs_4_11947810xx seem to be OK, at least for me. They're quite a bit longer as well as Travis predicted in another thread. 6 times as long for me as the previous wus before the bunch of failures.

i'm pretty sure the broken ones are purged so they shouldn't be downloaded.

Travis, are you saying that new WUs will not be created that cause errors or that you have purged everything that had a previous error?

If you mean the latter, you missed some. I just received a WU that was re-issued due to the errors.

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104950

[EDIT] And just got two more on the same machine [/EDIT]

---

Calm Chaos Forum...Join Calm Chaos Now

Only got one duff one in the last batch I got. I ran each until they got past the previous blockage and then suspended them so I could see if any would fail, and only one did.

[Edit]Only thing is, when they do fail, they lock up Boinc so that it can't do anything else until the windows error box is closed. I got another duff one after reporting a success, but I feel the pub beckoning (9pm local) and don't want to leave the machine vulnerable to locking up overnight. Could you purge the broken ones, Travis, so they don't get reissued? [/Edit]

All those from gs_4_11947810xx seem to be OK, at least for me. They're quite a bit longer as well as Travis predicted in another thread. 6 times as long for me as the previous wus before the bunch of failures.

i'm pretty sure the broken ones are purged so they shouldn't be downloaded.

Travis, are you saying that new WUs will not be created that cause errors or that you have purged everything that had a previous error?

If you mean the latter, you missed some. I just received a WU that was re-issued due to the errors.

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104950

[EDIT] And just got two more on the same machine [/EDIT]

i'm pretty sure i've purged the old ones which caused errors, and the new ones that are being generated wont cause errors. there might be a few generated work units out there that still will cause errors, but newly generated ones wont.

Only got one duff one in the last batch I got. I ran each until they got past the previous blockage and then suspended them so I could see if any would fail, and only one did.

[Edit]Only thing is, when they do fail, they lock up Boinc so that it can't do anything else until the windows error box is closed. I got another duff one after reporting a success, but I feel the pub beckoning (9pm local) and don't want to leave the machine vulnerable to locking up overnight. Could you purge the broken ones, Travis, so they don't get reissued? [/Edit]

All those from gs_4_11947810xx seem to be OK, at least for me. They're quite a bit longer as well as Travis predicted in another thread. 6 times as long for me as the previous wus before the bunch of failures.

i'm pretty sure the broken ones are purged so they shouldn't be downloaded.

Travis, are you saying that new WUs will not be created that cause errors or that you have purged everything that had a previous error?

If you mean the latter, you missed some. I just received a WU that was re-issued due to the errors.

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104950

[EDIT] And just got two more on the same machine [/EDIT]

if BOINC is re-issuing errored work units, then i'm going to have to look into a way to make it not re issue them.

http://milkyway.cs.rpi.edu/milkyway/workunit.php?wuid=104843

This one has been sent out twice (so far). Both errored out with Exit status -2147483645 (0xffffffff80000003). Mine triggered a Windows Error Message box asking if I wanted to send in the error report. (I sent it in.)

Hmmm....Instead of erroring out in the usual ~20 seconds, this one took 848 before it errored.

And this one took 725 seconds.

Neither WU was a re-issue of the earlier problems.

---

Calm Chaos Forum...Join Calm Chaos Now