Latest NVIDIA GeForce Graphics Drivers for Windows 10

http://www.nvidia.com/download/drive...px/97037/en-uk

GEFORCE GAME READY DRIVER 361.43 WHQL

NVIDIA continues to work closely with VR headset and game developers to deliver amazing VR games and applications. This Game Ready driver includes the latest GameWorks VR tweaks, bug fixes, and optimizations to ensure you have the ultimate VR gaming experience.

Gaming Technology
Support added for GameWorks VR 1.1 including VR SLI support for OpenGL applications and support for the latest Oculus SDK

venla said:

http://www.nvidia.com/download/drive...px/97037/en-uk

GEFORCE GAME READY DRIVER 361.43 WHQL


NVIDIA continues to work closely with VR headset and game developers to deliver amazing VR games and applications. This Game Ready driver includes the latest GameWorks VR tweaks, bug fixes, and optimizations to ensure you have the ultimate VR gaming experience.

Gaming Technology
Support added for GameWorks VR 1.1 including VR SLI support for OpenGL applications and support for the latest Oculus SDK

Thanks for the heads up on this venla

Here are your fixes

Changes and Fixed Issues in Version 361.43
The following sections list the important changes and the most common issues resolved
in this version. This list is only a subset of the total number
of changes made in this driver version. The NVIDIA bug number is provided for reference.

Windows 10 Fixed Issues

Cleaned up flip timing and event notification bugs. [200151547]

Fixed a driver bug where if the output is
active, hot unplugging
a device will cause
any following hot plug device to be ignored. [1707505]

Cleaned up unexpected behavior related
to the multi-HMD (helmet-mounted device)
use case. [200152110]

Return
NVAPI_NO_CONNECTOR_FOUND
from the
NVAPI_GPU_GetAllDisplayIds()
when headless GPUs are detected to allow
for identification of the unsupported use
case. [200155835]

[GM20x] Clock speeds remain above idle at 144 Hz on desktop. [1631144]

Lag in Star Wars Battlefront with SLI en
abled after updating to driver 359.06.

Hi,

I've just installed the 361.43 driver on both my Win 10 Pro installations. One is my main OS and it is the 10586.36 build - tweaked and modified according to my preferences - and the other is Windows 10 Insider Preview Build 11082, which I use as an Insider and I keep completely unmodified.

What I have observed is that this latest nVidia driver has resolved that issue with openCL.dll on the Insider Preview build! On that build I have run sfc /scannow after clean installing the driver and it has not found any integrity violations! On my main OS, on the other hand, it still finds errors and "corrects" them. This means replacing openCL.dll (it does this in SysWOW64). I then clean installed the driver again. By clean installation of the driver I mean through the nVidia installer. By the way, I always install just the driver and PhysX software. Nothing else.

Thank you.

Joanne said:

Hi,

I've just installed the 361.43 driver on both my Win 10 Pro installations. One is my main OS and it is the 10586.36 build - tweaked and modified according to my preferences - and the other is Windows 10 Insider Preview Build 11082, which I use as an Insider and I keep completely unmodified.

What I have observed is that this latest nVidia driver has resolved that issue with openCL.dll on the Insider Preview build! On that build I have run sfc /scannow after clean installing the driver and it has not found any integrity violations! On my main OS, on the other hand, it still finds errors and "corrects" them. This means replacing openCL.dll (it does this in SysWOW64). I then clean installed the driver again. By clean installation of the driver I mean through the nVidia installer. By the way, I always install just the driver and PhysX software. Nothing else.

Thank you.

Thanks for telling us about Opencl.dll problem being fixed on Windows Preview build 11082!!!! That IS great news to hear, I just hope MS doesn't mess it up in later builds. So I guess that means we only have to wait a few more months for this to be fixed and show up in a update. For those who don't run insider builds. Which is fine with me, I can wait. Also Joanne I only install the same 2 drivers as you. Just glad MS did address this problem finally!!!! Thanks again Joanne for this information!!

OldMike65 said:

Thanks for telling us about Opencl.dll problem being fixed on Windows Preview build 11082!!!! That IS great news to hear, I just hope MS doesn't mess it up in later builds. So I guess that means we only have to wait a few more months for this to be fixed and show up in a update. For those who don't run insider builds. Which is fine with me, I can wait. Also Joanne I only install the same 2 drivers as you. Just glad MS did address this problem finally!!!! Thanks again Joanne for this information!!

You are welcome, I was glad to see this resolved, as well, and I sincerely hope it will remain so! :)

I'd also like to leave the following screenshot here:



Thank you.

Joanne said:

You are welcome, I was glad to see this resolved, as well, and I sincerely hope it will remain so! :)

I'd also like to leave the following screenshot here:



Thank you.

LOVE those screen shots Joanne!!!! We been waiting a LONG time for MS to address this problem, nice to see they finally woke up.

Migrated to Win10 5 weeks ago.

Have dual BenQ 24" Monitors (primary via DP, secondary via HDMI)

Now all of a sudden, when monitors turn off 30 minutes after locking, the primary (DP) is not detected when waking the monitors (tapping keyboard or moving mouse) and logging into the computer. I have to reboot to have it detect and come back on again.

Tried by using driver removal tool for clean install of nvidia drivers again, but same issue comes up again.

Have also tried a different DP Cable, and also tried another DVI Cable, with same results.

(This same hardware setup, worked just fine with Win 8.1 Pro for the previous 14 months)