OpenCL: NVIDIA GPU 0: GeForce GT 440 (driver version 304.79, device version OpenCL 1.1 CUDA, 2048MB, 2001MB available)

On Windows XP, don't know about Linux.

---

Attention.

I have received info today describing the timeline for a (Cuda 3.0 related) fix as not until Cuda 5 Production Release in August/September timeframe.

Given that stock 6.10 will not work on Kepler class cards with 304 series (Cuda 5.0 preview) drivers, I have forwarded the information to project staff, to see if some project end action is feasible.

Kepler GPU Owners (at least on Windows OS) should, as appropriate, either crunch with third party applications, or if stock 6.10 (Cuda 3.0) application is preferred for whatever reasons, revert to 302 series or earlier drivers.

Jason

---

"Living by the wisdom of computer science doesn't sound so bad after all. And unlike most advice, it's backed up by proofs." -- Algorithms to live by: The computer science of human decisions.

I have received info today describing the timeline for a (Cuda 3.0 related) fix as not until Cuda 5 Production Release in August/September timeframe.

Given that stock 6.10 will not work on Kepler class cards with 304 series (Cuda 5.0 preview) drivers, I have forwarded the information to project staff, to see if some project end action is feasible.

Kepler GPU Owners (at least on Windows OS) should, as appropriate, either crunch with third party applications, or if stock 6.10 (Cuda 3.0) application is preferred for whatever reasons, revert to 302 series or earlier drivers.

Problem might be bigger than just the 302+ drivers... I'm having an SLI GTX460 (1st chipset versions) here and running the older 295 drivers of nVidia, but still get a bit over 10% computation errors with the cuda_fermi 6.10 application.

I did re-install BOINC last week, and noticed that this time it's an x64 application, while in the past it used to be x32. And with the old x32 application I had only a few computation errors.

---

<--- Searching for this one ;-)

I did re-install BOINC last week, and noticed that this time it's an x64 application, while in the past it used to be x32.

Separate 32-bit and 64-bit versions of BOINC have been available since the beginning of development of the v5.10 line, over five years ago. The main download page for the recommended version should automatically offer you the one which best matches your operating system: if you download a development (test) version, it's up to you to select which version to download.

If you had cached work onboard at the time you transitioned from 32 to 64 bit clients, that might not be handled properly, and might error. But apart from that, I don't think the bitness of the boinc client is implicated in the driver and hardware issues being discussed in this thread.

I have received info today describing the timeline for a (Cuda 3.0 related) fix as not until Cuda 5 Production Release in August/September timeframe.

Given that stock 6.10 will not work on Kepler class cards with 304 series (Cuda 5.0 preview) drivers, I have forwarded the information to project staff, to see if some project end action is feasible.

Kepler GPU Owners (at least on Windows OS) should, as appropriate, either crunch with third party applications, or if stock 6.10 (Cuda 3.0) application is preferred for whatever reasons, revert to 302 series or earlier drivers.

Problem might be bigger than just the 302+ drivers... I'm having an SLI GTX460 (1st chipset versions) here and running the older 295 drivers of nVidia, but still get a bit over 10% computation errors with the cuda_fermi 6.10 application.

I did re-install BOINC last week, and noticed that this time it's an x64 application, while in the past it used to be x32. And with the old x32 application I had only a few computation errors.

Your errors are being caused by the CUDA sleep bug that was in the 295.xx and 296.xx drivers.

setiathome_CUDA: No CUDA devices found
setiathome_CUDA: Found 0 CUDA device(s):
setiathome_CUDA: CUDA Device 2 specified, checking...
Device cannot be used
SETI@home NOT using CUDA, falling back on host CPU processing

You would be better to upgrade to the newest release build that will eliminate that problem.

---

Problem might be bigger than just the 302+ drivers... I'm having an SLI GTX460 (1st chipset versions) here and running the older 295 drivers of nVidia, but still get a bit over 10% computation errors with the cuda_fermi 6.10 application.

You would be better to upgrade to the newest release build that will eliminate that problem.

Installed 301 drivers and all seems to work correctly again. TY for informing me about this sleeping bug ;)

---

<--- Searching for this one ;-)

Are the computation problems with the 304.79 beta drivers fixed? GuildWars2 tells me that the 301 drivers have known errors with the game, and I don't want my SETI@home calculations to be screwed when I update to the latest beta drivers...

---

<--- Searching for this one ;-)

Are the computation problems with the 304.79 beta drivers fixed? GuildWars2 tells me that the 301 drivers have known errors with the game, and I don't want my SETI@home calculations to be screwed when I update to the latest beta drivers...

Since you only seem to have GTX 460 cards, the warnings in this thread do not apply to you.

Are the computation problems with the 304.79 beta drivers fixed? GuildWars2 tells me that the 301 drivers have known errors with the game, and I don't want my SETI@home calculations to be screwed when I update to the latest beta drivers...

If you had a Keppler based GPU as I do, then the answer would be no. I didn't see this thread until someone pointed out, largely as this is a different driver version set then when this was first noticed; and I had 25 WUs all error out as such before I got back to BOINC to check it out....

As someone mentioned already though, this prob is on nVidia's newer arch, so unless you upgraded your video card this year or something, you shouldn't see the problem we have.... For me, it's a laptop I just bought in the last month...

---

Still having trouble with these and the Lunatics installer doesn't seem to work well on Windows 8 :(

---

Still having trouble with these and the Lunatics installer doesn't seem to work well on Windows 8 :(

Could you describe what works, and what doesn't work, please? By PM, if preferred. I maintain the installer code, but so far I don't have a copy of Windows 8 to test it on.