Posts by Brian_Hedrick

1) Questions and Answers : Windows : BOINK Causes more problems than it solves. (Message 219451)
Posted 22 Dec 2005 by Profile Brian_Hedrick
Post:
Not sure why I got a 5.2.13 error before a 5.2.8 error. I am running 5.2.13. I initially installed .8 and upgraded to .13. Anyway, the memory error only happens with BOINC, and it does it often. If it were overheating or hardware problems I would see this with other software. Sorry, I think BOINC is a piece of junk and I will probably drop it. SETI@home should have stuck with what worked.

Brian

Your last error was:
<core_client_version>5.2.8</core_client_version>
<message>WU download error: couldn't get input files:
<file_xfer_error>
<file_name>13au01aa.6597.5489.148584.129</file_name>
<error_code>-119</error_code>
<error_message>MD5 check failed</error_message>


One before that was:
<core_client_version>5.2.13</core_client_version>
<message> - exit code -1073741819 (0xc0000005)
</message>


Why did you go back in BOINC versions?

Anyway, the above is an error from Seti. It's severely hampered at this moment. (read the front page news)
You getting the MD5 checksum failures means that not the whole file could be downloaded or that Seti was sending out wrong files at that moment.

The older errors though were due to another error, usually because of overheating hardware, severely overclocked hardware or bad device drivers.

If you get those referenced memory errors thrown at you by Windows, then it's about time to start testing your own system.

2) Questions and Answers : Windows : BOINK Causes more problems than it solves. (Message 203278)
Posted 5 Dec 2005 by Profile Brian_Hedrick
Post:
I took a leap of faith and switched to BOINK for SETI@ home. I was pleased with classic. Not only did I lose a lot of the credit I had, but now it errors out all the time. Many of my work units don't get processed and I don't get credit. Additionally, I frequently get the following error:

The instruction at "0x7c9122ba" referenced memory at "0xf05b3ff8". The memory could not be "read".

If this doesn't stop soon, you will have lost a loyal SETI supporter. I am happy to share spare CPU time, but not when it causes problems for my computer.

I am using BOINK 5.2.13 on a Dell Dimension 8300 with Windows XP Pro service pack 2.





 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.