Discussion in 'Videocards - NVIDIA GeForce Drivers Section' started by flimbo, Aug 13, 2015.
what mean TDR problem?
still icc profile changes when i run bf4 or hitman. ManuelG please check this issue
ok so I figured out why I keep getting low fps in GTA V with sli
for some reason one gpu usage will drop really low and clock speed drops for that card.
sometimes it will fix it self and go back to normal.
OK. thank you for correcting me then. The issue does not exist anymore so I am happy with that (though what is to say a future driver won't get blacklisted again?).
DX12 API overhead test has increase by well over a million calls per second with this driver, from:
http://www.3dmark.com/aot/46084 (16,087 K calls/sec)
http://www.3dmark.com/3dm/8173627 (17,452 K calls/sec)
DX11 ones have dropped somewhat though, in particular the multi-threaded one. This may not be a consistent benchmark though.
The test does seem fairly consistent. A second run gave me 17,600,000 calls/sec on the DX12 test. Unfortunately, the DX11 multi-threaded test is half the one from an earlier driver (1.1 million vs. 2.2 million) and not much higher than the single-threaded one.
Not sure what implications that has for games? Are multi-threaded DX11 games going to run worst with this driver than the 353.62 ones? :3eyes:
Actually the devs have confirmed there is a fix for FF40 in this driver.
Well, that's not quite true as the DX12 bug with MFAA enabled globally has been fixed (unless that was something that Microsoft fixed in a recent Windows Update?).
That would kind of make sense because the previous driver was blacklisted so something must have been changed/fixed in this driver so it also is not blacklisted. Whatever, it is fixed and I am happy with that as Firefox 40.0 seems really nice so far after using Chrome for the last 6-9 months or so.
The Quadro 353.82 works really well for me, no TDR´s or other problems what so ever, so i think im gonna stick to them and skip this release as i dont plan to play "Ashes of the Singularity" any how
As these are a new branch, do these include the Kepler fix?
Same FPS on The Witcher 3 as on 353.62 for me. No stuttering etc.
After 10 minutes of playing no TDR's so that's something ;D
PDF release notes, besides a few profile updates and the list of current known issues there's nothing much here that you couldn't already see in the driver download page's summary of what 355.60 brings.
GTA V does seem to do better with nvidia power mode set to performance.
but figured out if I stay below the max memory usage in GTA V graphic's settings. then the game wont have the memory leak.
if I go past it, system memory usage will go higher and higher resulting in low fps.
but if I lower the games setting, the memory usage starts dropping and fps jumps back up.
I just noticed that memory mhz is not being reported in anything.
gpuz/nvidia/msi afterburner both show 0mhz.
and this is after a reboot. so programs should be reading it.
and now gpu caps stops responding after running any test.
Custom res fixed?
this bug exists in 355.58 dev driver too
No, same FPS in the Witcher 3 as previous Windows 10 drivers.
Nvidia will never restore the performance tweaks of the 353.06. At this point, I'm thinking they did it just to shut up people, and it worked.
Oh well, lesson learned, if I had gone AMD I would have better performance in newer games and a full DX12 GPU.
Who cares? There are thousands of software for Windows. I'm not saying a graphics driver update cant be blamed for breaking FF, but it MUST do something very non-standard to even have a chance for this kind of issue in the first place.
Not true. There are fixes in this driver. I am not part of the docs team so not sure what happened but there are fixes in this driver.
Ehm, the ones who have their Windows 10 crashing into BSOD because of this might care I think.