Hi, I had to install the driver for Linux, Nvidia 346.16 Beta to accomplish tasks 8.46-Cuda 6.5.

Hi, So far I can not see performance improvement in short tasks when using v8.46 Cuda 6.5

The cuda 6.5app has not been updated yet...

---

FAQ's

HOW TO:
- Opt out of Beta Tests
- Ask for Help

Regarding the confusion about CUDA 6.5 in driver 340 / 341: are these the last drivers with legacy support for G80 etc.? This might explain why they might have gotten some bugfix after the release of the 343 branch.

MrS

---

Scanning for our furry friends since Jan 2002

From what I understand, the GPUs that recently were excluded from the latest GeForce driver sets... are still supported with R340 driver releases until April 2016.
http://nvidia.custhelp.com/app/answers/detail/a_id/3473

I even have an open NVIDIA Bug with them right now, where R340 (up to and including current 341.05 for my FX3800 M)... broke some of their OpenCL calculations that were working just fine in R337. They are supposedly working to fix it.
http://setiathome.berkeley.edu/forum_thread.php?id=75633&postid=1597385

Will Quadro driver v341.05 be enough with CUDA drivers?

Yes 341.05 will suffice. As stated by the webpage to which you link, the quadro 341.05 driver features CUDA 6.5. My Quadro K4000 is now getting tasks again after upgrading to 341.05.

Here v342.05 will only get CUDA 6.0 tasks due to application restrictions. You'll need v343.22 or above for CUDA 6.5 in Linux. For Windows v344.65 is the latest WHQL driver and it runs fine. Might as well use it.

I think you are mixing GeForce and Quadro drivers...they have different numbers! ;)

---

non-profit org. Play4Life in Zagreb, Croatia, EU

The drivers come from the same Release families (R337, R340, R343, etc.). And my point was, for the GPUs that have been deprecated from the R343 drivers.... The R340 drivers will have bugfix support for them until April 2016, for both Quadro and GeForce series of those R340 drivers.

341.05 is the latest R340 driver release for my Quadro FX3800 M, and as I said, I have an open bug with NVIDIA - they completely broke how the GPU calculates certain OpenCL functions, and they should hopefully have it fixed it in the upcoming R340 release. So far as I know, CUDA is calculating fine, but I have not personally tested it.

Regards,
Jacob

Many thanks.

I had trobule with the new driver. It locked the videos I tried to watch. I returned to the older drive and the problem ended, and this is because I still use an old driver.

I am not sure if will be able to use the newer driver. Has anyone had the same problem here? If so, how was it solved?

Many thanks,
Valter.

Many thanks.

I had trobule with the new driver. It locked the videos I tried to watch. I returned to the older drive and the problem ended, and this is because I still use an old driver.

I am not sure if will be able to use the newer driver. Has anyone had the same problem here? If so, how was it solved?

Many thanks,
Valter.

Hello: I see you have a very old GT 640 in Windows 7 and controller.

Unfortunately one GT 640 for GPUGRID is not appropriate, I do not accept assignments shortly. Greetings.

My computer with this graphics board used to get only CUDA 4.2 workunits.

12/5/2014 9:12:47 AM | | CUDA: NVIDIA GPU 0: GeForce GTX 560 (driver version 344.75, CUDA version 6.5, compute capability 2.1, 1024MB, 852MB available, 1116 GFLOPS peak)
12/5/2014 9:12:47 AM | | OpenCL: NVIDIA GPU 0: GeForce GTX 560 (driver version 344.75, device version OpenCL 1.1 CUDA, 1024MB, 852MB available, 1116 GFLOPS peak)

After 4.2 workunits were discontinued, it got one 6.0 workunit, which failed, and it now gets no GPU workunits from GPUGRID at all, only the CPU test workunits. What do I need to change in order the get GPU workunits again?

Hi Robert,

I tried to put together a comprehensive list of what is necessary to receive GPU workunits. You can either do step 1 and post back the results or take a look at your settings for steps 2-5 and see if anything needs to be changed.

- Happy crunching,
Steve

---------------------------------------------------------
1. Turn on the <work_fetch_debug> flag to see what BOINC
is doing during work fetch.
http://boinc.berkeley.edu/wiki/Client_configuration

-stop / restart boinc and post back with what the event
log says after it tries to get new work from GPUGrid.

- this will help identify if your issue is one of the
topics below or if we need to look deeper.
---------------------------------------------------------
2. Computing Preferences web
http://www.gpugrid.net/prefs.php?subset=global
Suspend GPU work while computer in use = no
- if yes then used in conjunction with ...
'In use' means mouse/keyboard activy in last "x" minutes
Suspend GPU work while computer in use = no
----------------------------------------------------------
3. Computing Preferences local (takes precendece over web)
Boinc Manager - Advanced View (ctrl+shift+a)
Tools menu --> Computing preferences
same as above but if you have set local preferences
then you will be always running local preferences and
nothing you chnage on the website for preferences will
matter until after you press the 'Clear' button. Keep in
mind this is "BOINC wide" setting so the last site you
chnaged this on across all of the projects you are
connected to takes precedence.
---------------------------------------------------------
4. Project preferences
http://www.gpugrid.net/prefs.php?subset=project
- Use NVIDIA GPU = on
- ACEMD short runs
----------------------------------------------------------
5. Activity Status
Boinc Manager - Advanced View (ctrl+shift+a)
Activity menu
- Suspend = off
- If 'Run based on preferences' = on then see Computing Preferences above
- Suspend GPU = off
- If 'Use GPU based on preferences' = on then see Computing Preferences above
---------------------------------------------------------

Valter wrote:

I had trobule with the new driver. It locked the videos I tried to watch. I returned to the older drive and the problem ended, and this is because I still use an old driver.

What do you mean by "locked the video"? The driver neither plays back videos, nor does it allow or forbid which ones to play. It does provide an interface for hardware acceleration of video playback, which other software can hook into. Maybe your video player (which one?) is too old for a modern nVidia driver? Update it or try VLC?

BTW: your GT640 is not powerful, but it can still rturn "long runs" within 2 days just fine, if you run 24/7. Otherwise it does can run "short runs" just fine. I would not recommend to buy one for GPU-Grid, but if you have you can still use it for some time :)

@Robert: I can not see any recent GPU task for your PC, only some very old errors and 2 CPU tasks.

MrS

---

Scanning for our furry friends since Jan 2002

I am running Nvidia driver 344.75 for my Titan Z, which is obviously not a 900 series gpu. I have noticed issues with WU's and it does not seem to be functioning as it was before with an older driver and my sli 780's. Any advice?

---

I am running Nvidia driver 344.75 for my Titan Z, which is obviously not a 900 series gpu. I have noticed issues with WU's and it does not seem to be functioning as it was before with an older driver and my sli 780's. Any advice?

I'd try turning off the CPU and test apps and then see if the GPU apps will run. Right now they don't seem to be starting and just time out.

I am running Nvidia driver 344.75 for my Titan Z, which is obviously not a 900 series gpu. I have noticed issues with WU's and it does not seem to be functioning as it was before with an older driver and my sli 780's. Any advice?

TWO TITAN Z.........

I tried uninstalling BOINC client and reinstalling, letting BOINC benchmark run, then running GPU Grid to no avail--I am getting about 70% through long-run WU's and then crash! Worst part is, I seem to be starting over on WU's when i reboot the system and not completing the WU's that were almost finished. This has to be a driver issue, because my sli 780's were running fine on 340.52 driver, and I did not update to driver 344.75 until I installed my Titan Z. I have not tried my Titan Z on 340.52 because I heard GPU Grid will not give me any WU's, but I know this new driver has to be the issue!

Will i get work units if I roll my 344.75 driver back to 340.52, the last known good working configuration I had? 340.52 driver is only 6-8 months old, but I cannot get 344.75 to run. As soon as i start boinc client, my driver crashes, restarts, then it will let me run wu's, but then the whole system crashes 3/4 of the way through long run wu's.

Are you doing any overclocking? Also, are you making sure to keep your GPU temps below 70*C? Does it error in Heaven 4.0 at maximum settings for 5 hours? Have you tried downclocking it until it stops erroring?

Will i get work units if I roll my 344.75 driver back to 340.52, the last known good working configuration I had? 340.52 driver is only 6-8 months old, but I cannot get 344.75 to run. As soon as i start boinc client, my driver crashes, restarts, then it will let me run wu's, but then the whole system crashes 3/4 of the way through long run wu's.

Well I see you have two PC's, but they are the same so could be the same one.
But if there are two then you can install an older driver on one PC and see what happens. If not working, update to the next driver and so on.

---

Greetings from TJ

I have tried downclocking, default clocks and overclocking, same results. Temps never go above 65c with aggressive fan profile, cpu is overclocked to 4.715 Ghz, fx8350, but thats the same overclock i have always used for gpu grid, and previously with my sli 780's

I have not ran haven benchmark for 5 hours, but have run full benchmarks with no issues, as well as normal gameplay with no issues. The system does not become unstable until I start up BOINC client, as far as I can tell anyway

You can try other 344 dirvers:
344.11
344.48
344.60
344.65
Did you checked all power connectors in your PC (including the 24 pin MB power connector) for burn marks, or loose connections?
Do you use any power connector converters, or extension wires inside your PC?

EDIT: you can try uninstalling the GPU driver, then use driver sweeper to remove any remaining driver files before installing different drivers.