Errors on R9 280X

It has been happening for a while and hasn't yet been commented on or fixed by the Devs.  If you know how to use a plain text editor like notepad, it's pretty easy to fix for yourself.  It's a 'once off' fix for a single machine.

As Richie notes, the problem is to do with the JPLEPH.405 file which should be in your einstein project folder.  Initially, the problem was that the file itself was quite correct but the reference to it in the state file (client_state.xml in the BOINC data folder) contained a bad MD5 checksum.  Someone pointed out that the checksum was actually correct for a completely empty file.  In the light of what you are now seeing, this is quite important in explaining why waiting for a fix from the project may not immediately fix things for you.

On the latest failed tasks the error is not about the MD5 checksum.  This implies that your current JPLEPH.405 file is actually passing the MD5 check.  In other words, it must be an empty file or the process wouldn't get as far as trying to read from it - which is now the current error.

To fix the problem, all you need to do is stop BOINC on the 'bad' machine and do two things.

1. Take a copy of the JPLEPH.405 file from your 'good' machine (say on a USB stick) and use it to overwrite the file on your 'bad' machine.
2. Open the client_state.xml file in your BOINC data folder on the 'bad' machine and search for the string JPLEPH.405 in a <file>...</file> block and you should find something like this

   <file>
       <name>JPLEPH.405</name>
       <nbytes>0.000000</nbytes>
       <max_nbytes>0.000000</max_nbytes>
       <md5_cksum>d41d8cd98f00b204e9800998ecf8427e</md5_cksum>
       <status>1</status>
       <sticky/>
       <download_url>http://einstein8.aei.uni-hannover.de/EinsteinAtHome/download/29/JPLEPH.405</download_url>
   </file>

   It's the 32 char string between the <md5_cksum> tags that needs replacing.  Just replace it with d6ce12bacd2a81a56423f5f238ba84eb  (just confirm you are replacing 32 chars with 32 exactly).

Save the edited state file making sure it is still called client_state.xml without any .txt extension.  Once you restart BOINC on that machine, you should be able to request tasks and when you receive them they should crunch without any error.