Hi,

I'm having a Nvidia GTX 690 graphics card an wanted to use it within Boinc. However all packages that I get from Seti@Home which are calculated by my GPU fail after a few seconds.

So it seems to me that my GPU is beeing recognized but Boinc isn't able to use it for some reason.

Does someone have any experience with the GTX 690 inc combination with Boinc?

Best ask at the project that you have the trouble with. BOINC doesn't do any calculations, it's a managing program. It's the project's science application(s) that do their work, and thus the making of the errors. They or their volunteers have got eyes on what is erroneous or not at this time.

---

The answer has been posted in several SETI@home threads, but the shortest and simplest is probably Nvidia GT640.

The problem is generic to all GTX 6xx 'Kepler' cards, so the same answer applies for this questioner too.

Jord, could you perhaps edit the typo in the thread title to remove the reference to a non-existent card, and maybe substitute that generic "GTX 6xx 'Kepler'" formulation? That might save us a FAQ...

(We could probably use a sticky at SETI to cover this - I'll talk to the mods there)

Instructions for working round this problem have been consolidated into NVidia driver problems which cause computation errors

I'm running GTX460 and been getting intermittent comp errors on GPU work.
OK at the moment though.
I'm using 301.42 driver, though not the latest,as problems occur when I update driver to newer. The constant reminders about this are a bit irritating, tbh.
I see the fix for later drivers and applied it to see if it affected performance.
Will this Env.Var. fix be counterproductive- if I leave it in place on this earlier card version?

This thread was about an older SETI application called 'setiathome_enhanced' - specifically, version 6.10

This application was replaced in the spring of 2013 with 'setiathome_v7', v7.00

Both these applications are fully compatible with your GTX 460 card without any special configuration - the environment variable fix doesn't apply to you.

I suggest you visit us at the SETI@home Message Boards, where people will be able to see your results and the type of errors you are getting: the advice you can expect there will be much more specific than it can be here.

@ Jord: I suggest this thread has outlived its usefulness and can be de-stickied once trev has read this reply and moved to the other forum.

Thanks for clarifying, Richard.
The problem has disappeared for now, but was quite repetitive for
a few days.
I've noticed before that uploads & work getting comp. errors sometimes run oddly but, once they resolve, easily get forgotten.
It's a lot of work chasing faults up- as you know on here.
This was on both SETI and MilkyWay work at the same time,[GPU only]- so I thought it may be a config issue and tried your tip.
It's not affected work when being left in, anyway.
I've been doing F@H for Stanford for about 5 years and now doing some for others, as a change.
Feel free to close thread now, as suggested.