What do you think of the new Beta drivers from Nvidia ?
GPU Folding fix is supposed to be incorporated.

Several WUs error out with the latest beta drivers.

Several WUs error out with the latest beta drivers.

Got several WUs error out with the latest WHQL 295.73 too !

I just come back to 290.53 drivers.

---

Lubuntu 16.04.1 LTS x64

Several WUs error out with the latest beta drivers.

Got several WUs error out with the latest WHQL 295.73 too !

I just come back to 290.53 drivers.

Had several errors with the 295.51 beta drivers and now with the 295.73 WHQL drivers too.
Beta 290.53 and lower seem fine.

Here is my Windows Application Event log

Faulting application name: acemdlong_6.15_windows_intelx86__cuda31, version: 0.0.0.0, time stamp: 0x4e11af1b
Faulting module name: acemdlong_6.15_windows_intelx86__cuda31, version: 0.0.0.0, time stamp: 0x4e11af1b
Exception code: 0x40000015
Fault offset: 0x0003af9a
Faulting process id: 0x1368
Faulting application start time: 0x01ccf1ae8797b3c6
Faulting application path: C:\ProgramData\BOINC\projects\www.gpugrid.net\acemdlong_6.15_windows_intelx86__cuda31
Faulting module path: C:\ProgramData\BOINC\projects\www.gpugrid.net\acemdlong_6.15_windows_intelx86__cuda31
Report Id: c619037a-5da1-11e1-aa23-50e5493a576e

Here the 295.73 driver seems to work fine.

You should try a "clean" installation of the 295.73 drivers. You can choose it from the advanced setup options, at the beginning of the installation.

Yeah, nvidia drivers are really sensitive to installation problems.

first, you should delete the old nvidia drivers by using the uninstall feature.

The download something like 'driversweeper' and run that to completely clear out the old files.

re-boot

run a registry clean to get rid of all old references in the registry.

re-boot again

install new driver. best way is to do a custom installtion and install the driver only. don't install the nVidia audio drivers unless you need them (using HDMI cable) or the 3d drivers unless you need them also.

lengthy procedure, but should result in a proper 'clean' install of the new driver.

The SETI optimizer crew noted that the beta (and now WHQL) drivers will fail if a monitor is connected to the DVI port and goes to sleep/power save.

I am still running 280 drivers on my couple of GPUgrid machines. My monitor (actually a KVM switch) is connect via the VGA port anyway but I am not willing to try it if other people have already reported problems. As other have said the 290 series seem to work fine though.

---

BOINC blog

I created an FAQ on drivers, and may add to it again, when prompted.

http://www.gpugrid.net/forum_thread.php?id=2868

It sounds like this is specific to W7/Vista (possibly WDM related) and only occurs when using the DVI connector (probably the driver turning off the 5V power to the DVI connection, which it can't do on the 15pin VGA connection).

Anyone with this problem that hasn't already went back to earlier drivers could try 4 things:

Disable screensaver and switching monitor off (recommended setting for GPUGrid)
Set the Power option for PCIE to Full power (recommended setting for GPUGrid)
BIOS, make sure PCIE is first display device, and not some on-board thing (assuming you are not using an on-board display).
Select Prefer Maximum Performance in NVidia control panel (a well established recommended setting for GPUGrid)

---

FAQ's

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

Prime Grid is reporting lots of issues with 295.xx.

I've been on 295 beta for a month here at GPUgrid w/o many issues.

Nvidea doesn't like it when your remote into a PC, as it stopps teh GPU crunching until you reboot.
I am connected to TV monitor via VGA at the moment.

---

Finally have a CUDA capable video card.

Nvidea doesn't like it when your remote into a PC, as it stopps teh GPU crunching until you reboot.

It's not nVidia's fault, it is by design of the MS RDP.