Nvidia GeForce 340.52 WHQL drivers

[nvgpu]

Nvidia has released 340.52 WHQL drivers on their website.

http://www.geforce.com/whats-new/articl ... hql-driver

[bruce]

As near as I can tell, there's noting in 340.52 that's in any way related to FAH. It's probably a good upgrade if you're a serious gamer.
The only exception I can find is if you happen to plan to buy a Quadro. viewtopic.php?f=83&t=24249#p267669

Please reply if you discover otherwise.

[7im]

No new devices added in 340.52 WHQL from NV 340.43 beta, and GPUs.txt is updated with the device list from 340.43 beta, as noted in the GPUs.txt Greylist topic.

[katakaio]

I may have an issue related to this driver...after updating to 340.52, FAH misallocates work to the GPUs. I have two GPU slots (560 Ti and 750 Ti) and when FAH reports that it is folding on the 750, computations are actually occurring on the 560. As a result, I'm getting failures on both slots with "BAD_WORK_UNIT" in the log. I'm rolling back to 337.88 to see if this corrects the problem - I'll post more when I learn more!

[bruce]

There are several reports of FAHClient assigning the wrong values to the GPU index values. This can be corrected manually, but in many cases, it's easier to interchange the names mentally when the WUs being assigned are essentially interchangeable. The OpenCL WUs (using Core_17) are interchangeable. WUs for most older FahCores were not interchangeable so you'd have to correct the setting to make sure (for example) a CUDA WU doesn't get assigned to a GPU that doesn't support CUDA.

[Joe_H]

Updating or reloading drivers is known to change the indexes for GPU's, so downgrading may or may not fix the issue you are seeing. If not, there are posts on how to manually set the index values so the right GPU is identified for each slot in a multiple GPU system.

[katakaio]

Indeed - I manually set the index values via this thread:
viewtopic.php?f=96&t=26334&p=264289&hil ... ot#p264289
and got the work going to the right GPU now. However, my PPD on the 750 seems quite a bit lower than what I've seen on similar projects (7626 and 8018 so far). I'm also failing to pick up work on my 560, but the client isn't throwing any errors. I think a driver downgrade is still in my future as a next step.

[pithos]

How does this driver stack up to the older ones. Is opencl performance still taking a massive hit? (non GK 110 cards).

[Napoleon]

Hmh... I've had some problems after upgrading to the 340 driver. Nothing too serious, and too early to call the new driver the culprit. However, later on this week I'm reverting to older drivers and see if certain intermittent weird things shall disappear.

EDIT: I noticed some weird UI snags with older drivers as well, although they seem to be less frequent. Anyway, I haven't noticed any odd UI things until recently, so something else besides the drivers is working differently. Currently sticking to 327.23 WHQL, I don't have any compelling reason to upgrade at the moment.