Milkyway@home 1.07 crashes

Author	Message
HTH Send message Joined: 8 Sep 07 Posts: 6 Credit: 712,027 RAC: 0	Message 382 - Posted: 11 Nov 2007, 8:46:18 UTC Milkyway@home 1.07 crashes: 1.png 2.png 3.png 6a37_appcompat.txt I am using 32-bit Windows XP. ID: 382 · Rating: 0 · rate: / Reply Quote

Helli_retiered Send message Joined: 9 Nov 07 Posts: 2 Credit: 18,380,242 RAC: 0	Message 383 - Posted: 11 Nov 2007, 9:09:36 UTC Same here. I stopped after crashing 21 Workuits. Windows XP x64 Helli ID: 383 · Rating: 0 · rate: / Reply Quote

rebirther Send message Joined: 28 Aug 07 Posts: 52 Credit: 8,353,747 RAC: 0	Message 384 - Posted: 11 Nov 2007, 10:20:32 UTC Its better to cancel all bad jobs by server, just babysitting boinc ^^ ID: 384 · Rating: 0 · rate: / Reply Quote

[B^S] BOINC-SG Send message Joined: 27 Aug 07 Posts: 16 Credit: 25,087 RAC: 0	Message 386 - Posted: 11 Nov 2007, 12:10:27 UTC A few WUs crashed here too - all after 20seconds. I tried detaching/reattaching, but no use. Got this Windows XP error message: szAppName : astronomy_1.07_windows_intelx86.exe szAppVer : 0.0.0.0 szModName : astronomy_1.07_windows_intelx86.exe szModVer : 0.0.0.0 offset : 0007f646 Now one wus seems to work... Will watch it and report here! Cheers, Steffen My NEW BOINC-Site Why people joined BOINC Synergy... Crunch fair! ID: 386 · Rating: 0 · rate: / Reply Quote

Philadelphia Send message Joined: 9 Nov 07 Posts: 131 Credit: 180,454 RAC: 0	Message 387 - Posted: 11 Nov 2007, 14:50:11 UTC - in response to Message 382. Milkyway@home 1.07 crashes: 1.png 2.png 3.png 6a37_appcompat.txt I am using 32-bit Windows XP. I had the same thing happen to me on Vista. My system crashed after I acknowledged that it should be aborted and wasn't very happy. I had to reboot and it too an exceptionally long time to reboot, I thought I had a major problem. Fortunately it now doesn't appear that way. CLICK TO HELP BUILD ID: 387 · Rating: 0 · rate: / Reply Quote

zombie67 [MM] Send message Joined: 29 Aug 07 Posts: 115 Credit: 502,661,158 RAC: 4,584	Message 389 - Posted: 11 Nov 2007, 16:35:26 UTC The real problem with these pop-up errors, is that core/thread is idle until someone manually dismisses the pop-up. That brings crunching for all projects to a halt, not just this one. ID: 389 · Rating: 0 · rate: / Reply Quote

Travis Volunteer moderator Project administrator Project developer Project tester Project scientist Send message Joined: 30 Aug 07 Posts: 2046 Credit: 26,480 RAC: 0	Message 391 - Posted: 11 Nov 2007, 16:57:00 UTC - in response to Message 389. The real problem with these pop-up errors, is that core/thread is idle until someone manually dismisses the pop-up. That brings crunching for all projects to a halt, not just this one. yeah, i'm not quite sure why the bad workunits are bringing up the windows dialog and stopping everything. no new bad workunits should be created so it's just a matter of getting through these unfortunately :( BOINC doesn't seem to have any tools to get rid of a bad work unit once it's out there (as far as i can tell). and really, thanks again for putting up with all this. we're new to BOINC and still trying to figure everything out. we're trying our best over here to get everything running as smoothly as possible as possible. ID: 391 · Rating: 0 · rate: / Reply Quote

[B^S] BOINC-SG Send message Joined: 27 Aug 07 Posts: 16 Credit: 25,087 RAC: 0	Message 402 - Posted: 11 Nov 2007, 19:12:41 UTC Last modified: 11 Nov 2007, 19:19:31 UTC It looks like the WUs that end with 3 and 4 are crashing, WUs ending with 0 are running fine. Couldnt check WUs ending with 1 or 2 so far. Edit: Ending with 2 crashes also... My NEW BOINC-Site Why people joined BOINC Synergy... Crunch fair! ID: 402 · Rating: 0 · rate: / Reply Quote

Labbie Send message Joined: 29 Aug 07 Posts: 327 Credit: 116,463,193 RAC: 0	Message 403 - Posted: 11 Nov 2007, 19:28:49 UTC - in response to Message 402. Last modified: 11 Nov 2007, 19:30:09 UTC It looks like the WUs that end with 3 and 4 are crashing, WUs ending with 0 are running fine. Couldnt check WUs ending with 1 or 2 so far. Edit: Ending with 2 crashes also... The ending number of 0, 1, 2, 3, 4, is merely the replication number, i.e., how many times it has been sent. Anything above 0 is likely to crash unless the first person that received it had a download error. After a WU gets sent out with a 4, it will not be sent again. I have had maybe 4 or 5 today that have crashed with a 0 as the ending number. Calm Chaos Forum...Join Calm Chaos Now ID: 403 · Rating: 0 · rate: / Reply Quote

[B^S] BOINC-SG Send message Joined: 27 Aug 07 Posts: 16 Credit: 25,087 RAC: 0	Message 404 - Posted: 11 Nov 2007, 19:54:15 UTC 5 crashes as well... As far as I can see, no 0 crashed here My NEW BOINC-Site Why people joined BOINC Synergy... Crunch fair! ID: 404 · Rating: 0 · rate: / Reply Quote

[B^S] BOINC-SG Send message Joined: 27 Aug 07 Posts: 16 Credit: 25,087 RAC: 0	Message 405 - Posted: 11 Nov 2007, 20:03:11 UTC - in response to Message 403. Last modified: 11 Nov 2007, 20:05:34 UTC The ending number of 0, 1, 2, 3, 4, is merely the replication number, i.e., how many times it has been sent. Anything above 0 is likely to crash unless the first person that received it had a download error. After a WU gets sent out with a 4, it will not be sent again. I have had maybe 4 or 5 today that have crashed with a 0 as the ending number. Edit: I think all wus should be canceled server side. Especially since the windows error message halts BOINC completely... My NEW BOINC-Site Why people joined BOINC Synergy... Crunch fair! ID: 405 · Rating: 0 · rate: / Reply Quote

Labbie Send message Joined: 29 Aug 07 Posts: 327 Credit: 116,463,193 RAC: 0	Message 406 - Posted: 11 Nov 2007, 20:07:12 UTC Yep, just got a 5 myself. That one had a missed deadline so it got reissued one more time than normal. I looked back and it was 4 "0"'s that crashed this morning, this one, this one, and this one have already been resent and returned successfully. The other one has been resent, but not returned yet. These were not the short ~20 second errors, these ran 8-10 minutes before erroring out. The machine they were run on has been having some other troubles lately (nothing to do with BOINC projects), so that may be the reason it had some errors. I just haven't had the time or desire to look into it too deeply yet. I've also gotten some shorty WUs again, they take anywhere from 2 - 6 minutes on my P4 3.2 HT. Calm Chaos Forum...Join Calm Chaos Now ID: 406 · Rating: 0 · rate: / Reply Quote

Viking69 Send message Joined: 12 Sep 07 Posts: 17 Credit: 7,374,736 RAC: 4,873	Message 410 - Posted: 12 Nov 2007, 1:10:30 UTC I was having similar issues. I deatatched and reatatched and the WU's downloaded and processed normally. I watched and if it passed about 39-42 seconds it went to completion. ID: 410 · Rating: 0 · rate: / Reply Quote

zombie67 [MM] Send message Joined: 29 Aug 07 Posts: 115 Credit: 502,661,158 RAC: 4,584	Message 420 - Posted: 12 Nov 2007, 17:59:59 UTC - in response to Message 391. BOINC doesn't seem to have any tools to get rid of a bad work unit once it's out there (as far as i can tell). You can do server side abortions using this: http://milkyway.cs.rpi.edu/milkyway_ops/cancel_wu_form.php I suggest you cancel the bad WUs even if they have already started crunching. ID: 420 · Rating: 0 · rate: / Reply Quote