"Sebastian Schildt" <fhnon-usenet@frozenlight.de> wrote in message
news:newscache$zcze1i$sj$1@at.fhnon.de...

I had this problem before (also posted to this group). I completely
deleted BOINC and Seti from my computer and reinstalled it.

From a later reply to this post, you sounded pretty cpu savy,
so I'm assuming you meant "remove", rather than delete. If by some
chance you "deleted" the BOINC s/w, rather than "removed" it
via the Control Panel, this could easily have caused your probs. I hope
I haven't insulted your intelligence w/this suggestion. I'm just trying to
touch on all bases.

I got one WU after a few days of waiting :), which is finished now.
Everytime BOINC launches, it tries to transfer the result and crashes.
This happens with either the GUI or the CLI client.


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

Seeing as the WU never started, and you're getting sys mem access
violations, I agree you're likely having a s/w conflict, and not a cpu
load related issue. But, I've also seen h/w issues cause the same error msg.

Since the issue appears to be occuring during comm attempts, have you
ascertained the integrity of you networking h/w & drivers? IOW, your NIC
is fine, you haven't moved it around or messed w/the drivers, or done any
reconfig'ing (intentionally, or inadvertently) to your networking
parameters? Are other local apps able to comm, as usual, to the outside
world?

It's a reach, but have you considered  running Prime95 Torture for an hour,
or two, just to eliminate other possibilities? Again, I'm just tossing out
ideas.

This machine is x86/WindowsXP Home based. It has no problems whatsoever
with any  other software, so I'm quite sure that there's nothing "wrong"
with my machine, only BOINC doesn't seem to lke it.

Any ideas?

Did you set a sys restore point before the BOINC d/l, that you can return
to, or, if not, is there a restore point prior to the BOINC d/l that will
work for your current sys config? Sys restore has save my arse a few times,
particuliarly when I was running the dreaded WinMe.

FWIW, I've run the GUI 3.19 & 3.20, 24/7, since the getgo of each, on three
~25% OC'd P4C machines, running another DC client concurrently w/SAH2
BOINC. My OS is XPro. The client's have been solid as a rock, and I've yet
to occur a BOINC client s/w error. Lack of work, or a dysfuntional website,
yes, but never a BOINC client issue.

Quite frankly, it smells to me like you're having comm probs; Either s/w or
h/w, but where, I just don't know, and I'm not leaving out the possibility
of a bad client d/l or install.

Good Luck
-- 
Strat