Since the latest version of S@H hit the streets, my 8800 GT has been unable to successfully complete any work units. For example -

http://setiathome.berkeley.edu/result.php?resultid=3044437557

Was this planned or is it an unintended consequence?

Thanks.

PS - I should mention that my other two hosts, one a GTX 460 and the other a GTX 580 have had no problems since the update. However, the last good one I returned on the 8800 GT was on May 11, 2013.

---

Since the latest version of S@H hit the streets, my 8800 GT has been unable to successfully complete any work units. For example -

http://setiathome.berkeley.edu/result.php?resultid=3044437557

Was this planned or is it an unintended consequence?

Thanks.

PS - I should mention that my other two hosts, one a GTX 460 and the other a GTX 580 have had no problems since the update. However, the last good one I returned on the 8800 GT was on May 11, 2013.

Made the link active.

Check out this thread .

---

Donald
Infernal Optimist / Submariner, retired

The reason for the error is not the GPU 'version'

If you want to read about the reason:
"v7 cuda23 WUs getting ERR_TOO_MANY_EXITS"
http://setiathome.berkeley.edu/forum_thread.php?id=71953

Some posts in the same thread:
http://setiathome.berkeley.edu/forum_thread.php?id=71953&postid=1379544#1379544
http://setiathome.berkeley.edu/forum_thread.php?id=71953&postid=1383240#1383240

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

As noted by the two previous replies, this ongoing problem is discussed in:

http://setiathome.berkeley.edu/forum_thread.php?id=71953

The short version of all that is that you can temporarily get around the problem by manually deleting the cudart.dll and cufft.dll files from the S@H project directory. However, unless you're running 24/7, you'll have to delete them again every time you reboot, since each time BOINC restarts, it notices that the files are missing and quickly downloads them again!

As noted by the two previous replies, this ongoing problem is discussed in:

http://setiathome.berkeley.edu/forum_thread.php?id=71953

The short version of all that is that you can temporarily get around the problem by manually deleting the cudart.dll and cufft.dll files from the S@H project directory. However, unless you're running 24/7, you'll have to delete them again every time you reboot, since each time BOINC restarts, it notices that the files are missing and quickly downloads them again!

Eh? Did you disable V6 in prefs?

Mine appears to be working fine (so far). Maybe I never restarted my notebook... I'll do that now just to make sure.

As noted by the two previous replies, this ongoing problem is discussed in:

http://setiathome.berkeley.edu/forum_thread.php?id=71953

The short version of all that is that you can temporarily get around the problem by manually deleting the cudart.dll and cufft.dll files from the S@H project directory. However, unless you're running 24/7, you'll have to delete them again every time you reboot, since each time BOINC restarts, it notices that the files are missing and quickly downloads them again!

Eh? Did you disable V6 in prefs?

Of cause, if you disable MB v6 (SETI@home Enhanced) in the preferences you then can't get the 6.11 and now 6.12 (cuda)/(cuda22)/(cuda23) apps Eric is sending to try and get around the dll problem.

Setiathome applications

Claggy

Not sure if I'm understanding you Claggy...

Do you want me to re-enable V6 for troubleshooting?

Not sure if I'm understanding you Claggy...

Do you want me to re-enable V6 for troubleshooting?

If you have never received tasks for 6.08 or
If you have since then reseted the project

You don't need to do anything else, your system doesn't have the problem causing DLLs anymore.

For those who have received tasks for 6.08 and have not reseted the project the best course of action is to set No new tasks, complete, upload & report any work on-board, reset project and Allow new tasks.

The server isn't sending the problem DLLs anymore so in your case (you reseted the project, right?) enabling or disabling v6 doesn't make any difference.

However, if you are running stock apps and have NVIDIA GPU you might want to not select v6 work. Both v6.11 and v6.12 are trashing work. v6.11 came with wrong app_version block in scheduler reply which caused BOINC to reject the tasks immediately. v6.12 comes with good app_version block. But v6.12 is really 6.03 CPU app in disguise (v6.11 was too), and for GPU apps BOINC adds --device N parameter to apps command line to select used GPU, and being a CPU app v6.03 doesn't know what that parameter means so it exits with error.

Thanks for the replies, all.

I've got an E@H Persus Arm Survey WU that has about 3-hours to go on that GPU right now, so I hit "reset project" on S@H since that sounds like part of the answer to the problem.

OK - so changing preference to exclued V6 work no longer seems to be an option as the only options that are available for me are the following:

SETI@home Enhanced
SETI@home v7
AstroPulse v6

Just in case SETI@home Enhanced is the "V6" app, I shut that off.

I'll post the results either way.

---

Thanks for the replies, all.

I've got an E@H Persus Arm Survey WU that has about 3-hours to go on that GPU right now, so I hit "reset project" on S@H since that sounds like part of the answer to the problem.

OK - so changing preference to exclued V6 work no longer seems to be an option as the only options that are available for me are the following:

SETI@home Enhanced
SETI@home v7
AstroPulse v6

Just in case SETI@home Enhanced is the "V6" app, I shut that off.

I'll post the results either way.

SETI@home Enhanced contains the 6.xx app version. So that was the correct one.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thanks for the help, all.

My 8800 GT has successfully returned 4 WUs now. Back in business. :)

---