Two questions.

First, while investigating errors I’ve been receiving from TRP Sieve on one of my machines I happened to notice that there are several copies of the TRP sieve input file in the PG folder:
TRP_20100604.sieveinput
TRP_20101125.sieveinput
TRP_20110128.sieveinput
TRP_20110626.sieveinput
These are a bit largish and I’m wondering if it’s safe to delete all but the newest one?

Second question: The errors I’m getting are only happening on one machine out of six I have running TRP Sieve so it seems fairly obvious they are machine specific, but I’d like to hear any thoughts people have concerning a possible cause. They only occur occasionally. This machine has been running LLR’s cleanly so it’s pretty stable otherwise. All temps are in a comfortable range. (68 C or less)

Thanks in advance!

Some WU’s on this VISTA 32-bit machine are erring out with something similar to the following:

Stderr output
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
BOINC sr2sieve wrapper 1.12
Using Geoffrey Reynolds' sr2sieve 1.8.10

Unrecognized XML in parse_init_data_file: hostid
Skipping: 167608
Skipping: /hostid
Unrecognized XML in parse_init_data_file: starting_elapsed_time
Skipping: 0.000000
Skipping: /starting_elapsed_time
Unrecognized XML in parse_init_data_file: computation_deadline
Skipping: 1318303289.136000
Skipping: /computation_deadline
Major OS version: 6; Minor OS version: 0
pid: 116, thr: 120

.002766
.005545

. . . (etc)

.689741
.692532
Factors file not found
called boinc_finish

</stderr_txt>
]]>

[Edit] BTW, the machine itself is a stock Dell computer and is not overclocked. I've tried rebooting to no avail. Also tried reseating the memory sticks.[/Edit]

Theory on your one machine having errors. What virus program is on it? Can you have it avoid scanning the BOINC work directory? This is a usual cause to some of this.

Other than that I would run a battery of tests (Memtest and Prime95 are two good ones).

@John,
Wow that was fast. My daily driver just reported and the deletes came with it. BTW, no biggie but TRP_20100604.sieveinput still remains, but at least we got rid of half of them. Thanks.

@ Pooh Bear,
Outstanding idea, should have thought of it myself. The data directory is now exempt from Norton, I'll keep an eye on that machine and will report back either way. Thanks to you too!

Well, FWIW that's about 48 hours with no further errors. Due to the intermittent nature of this machine's problems I probably should not say it's absolutely fixed, but let's call it a PRP (Probable Repaired Processor) ;-)
Tks again to Pooh Bear.
I'll now trust it to feed a few cores on 5oB.