Hi folks. I switched from classic to Boinc early in December. On December 9th, I successfully completed a work unit. However, every work unit since then has errored out. All the other BOINC clients (e.g. Predictor, Einstein, rosetta, LHC) appear to be doing fine - it's just Seti that won't work. Any suggestions?

Thanx, Ric

---

At Seti you have errors
exit code -1073741819 (0xc0000005)
like on this WU

At Einstein, you have the same error
exit code -1073741819 (0xc0000005)
like on this WU

According to the Boinc Wiki, the "common causes of these errors can be:
• Over stressed hardware, usually by heat.
• Flaky, or bad device drivers.
• An actual problem (Bug) in the BOINC Client Software, Science Application, or Operating System.
• A bad Work Unit (usually a rare occurrence)."
See here

Is your PC overclocked? Do you know at what temperature the CPU is running? Are your RAM in a good shape?

---

Read the News at the homepage
Have a look at the Technical News
Look if your question is not answered at the Boinc Wiki

Best greetings, Thierry

Hi Thierry,

FWIW, the hardware seems fine and not overheated. No other activity on my system appears to be having problem, and as mentioned other BOINC clients do seem to be completing. I ran a RAM test on memory which found no errors.

Meanwhile, I did get another error (this time for both Seti and Einstein):

"The instruction at '0x7c919f9b' referenced memory at '0x000009a88.' The memory could not be 'read'. Press OK to terminate program"

which occured when exiting the BOINC manager. Do you know if the manager does not shut down work cleanly when exiting? Perhaps the various clients need to be suspended first before exiting the program. I don't think this is the root cause, because the errors occur even when BOINC is left up, but I thought I'd eliminate the specific symptom this time as well.

Any advice appreciated,
Thanx, Ric

---

Hi folks,

It turns out that this was being caused by setting preferences to keep Seti in memory even when paused. When BOINC is terminated it apparently doesn't do memory cleanup properly. By changing preferences to remove a preempted calculation from memory, the problem goes away (from Seti and all other clients).

Thanx, Ric