Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by peppercute, May 30, 2019.
Does this driver whql or beta via DXdiag ?
When WU pushed out the first WDDM 2.6 driver, it was Standard only. Perhaps the trend continues. I'm on DCH now so it's not worth it for me to DDU, block auto-install and hope I get this one pushed as Standard.
Threaded Optimization was merged to this option as well. In case nobody noticed.
EDIT: Does anyone know what this flag does? I'm suspecting it's a copy of the "Threaded Optimization" setting
It's set to 0 on Best Performance and 2 on Lowest Latency.
Also, Lowest Latency sets the Pre-Rendered Frames to 1 and the Threaded Optimization setting to Off.
EDIT2: Beware, I think Windows isn't liking this driver very well. Opening the Start Menu is making the entire DWM freeze.
This setting stores only the value for the control panel.
0x0005F543 - NVCPLAPI_SETTING_LATENCY
Best Performance - 0x00000000
Low Latency - 0x00000001
Lowest Latency - 0x00000002
installed this driver on 1903 build , i lost 3k points in gpu score in 3dmark timespy
So far all my benchmarks work fine, and games as well , no crashes at all.
435.27 from WU, / Windows 10 pro insider preview/ build 18908
7 986 in Time Spy 435.27
7 787 in Time Spy 419.35
Why does the folder contain gforce experence setup but setup only installs the display driver and audio driver?
I definitely don't recommend installing this on 18362. I just rolled back because of a TDR when opening the Start Menu. It's fine now.
On best performance, what is Threaded Optimization set to?
Im on Windows 10 insider fast ring, 1903 - 18908.1000 and tonight (Swedish time ~18.00) Windows update, "updated" my nvidia drivers back to 430.86 away from these 435.27
Did this happen to you guys who are on the insider build too ?
I decided to manually install this driver to try it out and Windows Update downgraded it back to 430.86 the first time I checked it.
Guess they had second thoughts about releasing into the wild. I've decided to call it the case of the mysterious missing beta driver.
go go monkeysoft lol
Well, I guess I will be 'patient zero'. Updated to 18908.1000 yesterday and manually installed 435.27. Here we go...Windows update check in 3...2...1 and...
for me, nothing happened. It said I was 'Up to date'.
working fine on may update
like a normal driver
Just to try and prove to myself that I am not crazy, I ran DDU and installed the 435's again.
And wouldn't you know it, When I ran Windows Update it didn't change them back this time.
So....crazy I am I guess lol
Strange things happen. When I first updated to the driver, I had no Control Panel in the context menu. I don't know if it would have worked otherwise. I almost decided to roll back then said...oh...should do a reboot first. And viola', everything is fine.
works fine for me on 1903.
Haha I did the same, used DDU to uninstall 430.86 that Windows had "updated" me to from 435.27 earlier today.
Then I installed 435.27 this time from the file in this thread instead of Windows update. And after a reboot Windows update tells me that "you´re up to date".
For those of you saying the latency setting is simply renaming the previous prerendered frames setting, that's not quite right.
1 used to be the lowest setting, that's the new "low" setting, there is now an even lower setting called "lowest", I guess this is the new 0. Pretty interesting.