Hello Dev-Team,

since your server was down I get following exception.. Boinc starts exits starts again and exits again and thats it...

I tried the 3.18 and 3.19... same problem
I have still WUs for the Beta, but jet not received any WUs for the Seti@Home

Maybe you should change the errorlog. Written will be only the last error.. and thats not enough

Thanks for info
cu Thomas



***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00401D98 write attempt to address 0x69736142
1: 06/27/04 10:40:15
***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00401D68 write attempt to address 0x69736142
1: 06/27/04 10:37:18

2004-06-28 06:25:30 [---] Starting BOINC client version 3.18 for windows_intelx86
2004-06-28 06:25:30 [SETI@home] Project prefs: using your defaults
2004-06-28 06:25:30 [BOINC Beta Test] Project prefs: using your defaults
2004-06-28 06:25:30 [SETI@home] Host ID is 13972
2004-06-28 06:25:30 [BOINC Beta Test] Host ID is 125183
2004-06-28 06:25:30 [---] General prefs: from SETI@home (last modified 2004-06-25 17:23:16)
2004-06-28 06:25:30 [---] General prefs: using your defaults
2004-06-28 06:25:30 [BOINC Beta Test] Restarting computation for result 01ja04aa.16193.1552.253418.186_1 using setiathome version 3.08
2004-06-28 06:25:36 [BOINC Beta Test] Started upload of 01ja04aa.16193.1218.486090.74_2_0

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00401D98 write attempt to address 0x69736142
1: 06/28/04 06:25:38

2004-06-29 17:50:18 [---] Starting BOINC client version 3.19 for windows_intelx86
2004-06-29 17:50:18 [SETI@home] Project prefs: using your defaults
2004-06-29 17:50:18 [BOINC Beta Test] Project prefs: using your defaults
2004-06-29 17:50:18 [SETI@home] Host ID is 13972
2004-06-29 17:50:18 [BOINC Beta Test] Host ID is 125183
2004-06-29 17:50:18 [---] General prefs: from SETI@home (last modified 2004-06-25 17:23:16)
2004-06-29 17:50:18 [---] General prefs: using your defaults
2004-06-29 17:50:18 [BOINC Beta Test] Restarting computation for result 01ja04aa.16193.1552.253418.186_1 using setiathome version 3.08
2004-06-29 17:50:19 [BOINC Beta Test] Started upload of 01ja04aa.16193.1218.486090.74_2_0


***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00401D68 write attempt to address 0x69736142
1: 06/29/04 17:50:20

Hi.. a short notice

well after I did not have the possebility to update the projects or making other changes to the soft (exception to fast... and Boinc shutting down) I decided to rename the boinc-software-folder and reinstall the latest Boinc again.

oki, at this time I dont get any exceptions..:) but I am awaiting WU's from the seti@home ;)

cu Thomas

Hello Dev-tream,

well, I think the problem is the uploading of WU's.. I am using "proxy" without problems _down_loading WU's..

as soon as I have finished a WU and Boinc tries to __up__load, Boinc crashes..
Guess this is a bug.

Dev-Team..
any HELP in sight ?
cu Thomas


2004-07-05 17:08:35 [---] Starting BOINC client version 3.19 for windows_intelx86
2004-07-05 17:08:36 [SETI@home] Project prefs: no separate prefs for home; using your defaults
2004-07-05 17:08:36 [SETI@home] Host ID is 35946
2004-07-05 17:08:36 [---] General prefs: from SETI@home (last modified 2004-06-25 17:23:16)
2004-07-05 17:08:36 [---] General prefs: no separate prefs for home; using your defaults
2004-07-05 17:08:36 [SETI@home] Restarting computation for result 21se03ab.25795.6514.361092.56_0 using setiathome version 3.08
2004-07-05 17:08:39 [SETI@home] Started upload of 21se03ab.19747.4064.615894.176_2_0
2004-07-05 17:08:39 [SETI@home] Started upload of 11ja04aa.1511.10928.65906.168_1_0

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00401D68 write attempt to address 0x73614220

1: 07/05/04 17:08:59

I also have the same problem ( http://setiweb.ssl.berkeley.edu/forum_thread.php?id=688 ). BOINC seems to be a really neat concept, but someone should address the outstanding bugs in the application.

Question: would the Proxomitron possibly help?

I used the Proxomitron for the classical S@H to communicae through the proxy server, but I have uninstalled it when installing BOINC. I think I'll give it a try if I can find some spare time...

I tried the Proxomitron -- it works!!!

For those who have the same problem, here is what I did:
1) downloaded the Proxomitron from http://www.proxomitron.info/;
2) installed, launched, and configured it (proxy server, port, userid, password);
3) manually edited file client_state.xml in the BOINC directory (clear , , , change to 'localhost' and to '8080') - make sure that BOINC is not running when updating this XML file!;
4) run BOINC application;

The completed WU has successfully uploaded, and BOINC is now running without crashing.

Just for info..
I downgraded to boinc 3.07beta.. last uploads no probs with proxy.. :) download.. well ;) "no work..." ;) but I guess we all know these circumstances
I will monitor and wait for new versions, before I try to upgrade again.

cu Thomas

attention: after downgrading we will not get any work...!! "core client too old"

The original thread about this EXCEPTION is:
http://setiweb.ssl.berkeley.edu/forum_thread.php?id=154&sort=timestamp