I don't really know, whether it's an issue with boinc or the seti-client,
but i've seen the following several times now:

0. Boinc(Windows) is running, doesn't matter which version (gui, cli; 3.20, 3.19)

1. The boinc task gets killed due to a hard reset or a bluescreen (not caused by boinc).

2. When i restart the pc and boinc starts, the following happens (copied from eventlog):
2004-07-26 23:14:02 [---] Starting BOINC client version 3.20 for windows_intelx86
2004-07-26 23:14:03 [SETI@home] Project prefs: using your defaults
2004-07-26 23:14:03 [---] State file has different major version (0.00); resetting projects
2004-07-26 23:14:03 [SETI@home] Resetting project
2004-07-26 23:14:05 [SETI@home] Host ID is 86465
2004-07-26 23:14:05 [---] General prefs: from SETI@home (last modified 2004-07-11 22:58:25)
2004-07-26 23:14:05 [---] General prefs: using your defaults
2004-07-26 23:14:12 [---] Fewer active results than CPUs; requesting more work
2004-07-26 23:14:12 [SETI@home] Requesting 852822 seconds of work
2004-07-26 23:14:14 [SETI@home] Sending request to scheduler: http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi
2004-07-26 23:14:58 [SETI@home] Scheduler RPC to http://setiboincdata.ssl.berkeley.edu/sah_cgi/cgi succeeded
BOINC error: 0; 2004-07-26 23:14:58 [SETI@home] Message from server: No work available

3. Afterwards the following files have been deleted by boinc/seti
- all queued workunits (29 this time, 40 last week,...)
- all not yet sent results, except the last one
- the seti-client itself

I saved the content of the boinc directory: http://kannix.net/download/BOINC.zip
Ehm - except the one result file that has not been deleted. It was uploaded to the server, just before i was able to stop boinc...

Well, a bluescreen _should_ not appear very often, but neither should boinc delete all project data then, right?

my team: http://setiweb.ssl.berkeley.edu/team_display.php?teamid=31442
my account: http://setiweb.ssl.berkeley.edu/show_user.php?userid=13841
the computer: http://setiweb.ssl.berkeley.edu/show_host_detail.php?hostid=86465
ps: Yes, i've changed the account-id in all files;)

--
KANNIX

This is most likley caused by the client_state.xml file getting corrupted in the crash. There is a task to use a 2 file rotation that should fix this issue.

John Keck
BOINCing since 2002/12/08