ATI and NVIDIA updates

Geforce 355.60 WHQL

http://www.geforce.com/drivers/results/89119

 

Don't Do It... It's a Twap!

 

Whats the latest version you guys using most stable?

-via Tapatalk (S4)

 

353.30 is what I'm on.

 

lool

 

Thanks...but help guys, using 353.30 now and I've been having 'driver stopped responding (freezes PC), and recovers after several seconds or so. Don't you guys encounter this? When I searched, it brought about a thread from geforce (https://forums.geforce.com/default/topic/833693/geforce-drivers/nvidia-driver-352-86-353-06-353-30-stops-responding-and-kernel-reloads/29/) w/ reports on the same problem, even with 355.60, so I'm not sure what would be a stable version. No wonder Chrome and some games started freezing randomly (though rarely, still annoying).

EDIT: Found this workaround: https://www.reddit.com/r/GlobalOffensive/comments/3do60l/if_you_get_the_error_nvidia_windows_kernel_mode/, anyone tried this fine?

 

Can't say I do but then again I do not run many titles.

Never have Chrome crash.

I been on W10 353.62 since release, too lazy to try to 355.60..... and don't want to hex it. p

 

Geforce 355.78 BETA

https://developer.nvidia.com/oculus-07-sdk-driver-support


* Support for VR developers using Oculus 0.7 SDK.
* Bug fix for an intermittent issue found in the publicly released 355.60 Game Ready driver as well as solving an issue with incorrect display timings.

 

Geforce 355.82 WHQL

http://www.geforce.com/drivers


* Windows 10 Fixed Issues

[Oculus Direct VR] Oculus screen stays blank when directmode.exe -present_test is run.
[GTX 980 SLI, 1×3 Surround] Wrong refresh rates are listed in the NVIDIA Control Panel.
[G-SYNC, SLI] Drastic tearing observed on 4K monitor when SLI enabled.
[SLI] Enable P2P on Intel Z170 platform.
[GTX 980 Ti, 1×2 Surround] Surround resolutions and their order are incorrect.



* Windows 8.1/Windows 8/Windows 7/Windows Vista Fixed Issues

[Oculus Direct VR] Oculus screen stays blank when directmode.exe -present_test is run.
[G-SYNC, SLI] Drastic tearing observed on 4K monitor when SLI enabled.
[SLI] Enable P2P on Intel Z170 platform.

 

I have this issue using 355.60, Windows 10, but I have only had it happen at Monte Carlo track, so far, of the several tracks I have tried with this machine, OS, and Build 998. And at Monte Carlo it happens repeatedly

 

I had off experience with W10, not as bad as freezing though.

Was just the overall performance and feel was like something was turned up.

I found my problem ( vsync method) but even then it still was not as snappy as W7 so I went back for now.

 

Geforce 355.98 WHQL

http://www.geforce.com/drivers

 

CPU-Z v1.73

http://www.cpuid.com/softwares/cpu-z.html

Extreme Overclock mode
CPU benchmark
Customized for Manufacturer
W10 edition

 

One thing gets lost, from time to time and that is, that every driver published does not get work with all computer setups. Sometimes you have to revert back to one that did work for you.

Safe to say that the last year, I have had more driver versions not work right on my setup. Such as momentary black screens with no error, etc.

Right now running 353.54 nVidia on win10.

 

Who ever said they did.


Try drivers AT your own PERIL !~

 

GeForce 356.04 Driver Available

The 356.04 developer's driver fixes an sli memory leak and provides very good performance in rF2, particularly in sli mode. W7, 8, 8.1, 10 x64 bit only.
Results so far indicate less stuttering and slight frame rate increase at high resolutions (7680x1440).

https://developer.nvidia.com/gameworks-vr-driver-support

 

My card is running at a higher temperature with this driver. 78deg compared to about 58deg and performance seems better. Cannot check the fps as I have them capped at 60. With the last driver I had some issues mid way through the race with the physics bar going crazy and lag from hell.

 

I don't know what ATI driver update it was recently, but earlier in the year I couldn't overclock beyond 1050 (core) without the driver crashing. Gave it another go yesterday and viola...1100 straight off the bat with no problems, this is all in Crossfire BTW. I may push the envelope a bit more to see where the tipping point is!

 

Are most of you installing the entire package...(i.e driver, PhysX, HD audio, GF Experience, 3D controller, etc...)?
I usually only install the driver itself plus PhysX and HD audio.
I've had zero freezes or instability with 355.98 or any other driver on W10-64 with GTX970.
Is it possible the other components are causing issues?

 

Had crashes with Singapore for FSR, many have had screen freezes. I think it's something to do with the light-filled buildings which keep changing colors, because it was fixed by changing some settings - not sure which one did it, but it might have been HDR, special effects or crowd/wind.

Same thing happened at Singapore(GPVWC in rFactor 1), and that was fixed by running in DX8 mode.

I only install the driver and PhysX. The above shows it's clearly something to do with tracks, and not drivers.