Geforce game ready driver 359.00 whql

I checked. It needs the internet to download some c++ redistributable if your setup does not have it already installed. That is why some can install without internet, others not.

 

from release notes:

Windows 10 Issues

Driver installation will fail if GeForce Experience is a selected component and the system is either in safe mode or without a network connection. [200151914]

 

It can also happend without Geforce Experience selected.

 

Still to fix the no MFAA with SLI and no DSR with SLI and Gsync monitors..

 

Driver has been running great (forgot to monitor my temps...) but other than that no issues so far when playing SOMA, Vanishing of Ethan Carter, Alien Isolation and Project Reality.

 

I'm not using Geforce Experience. 358.91 is working fine without internet connection and Visual C++ redistributable.

 

anyone getting green lines on screen sometimes with these then going away?

 

Not me. But those could very well be a sign of the video card memory being clocked to high/overheating/going bad. Doesn't have to be, though.

 

no overclock here. happens at random. im also using a 4k monitor with hdmi 2.0. happens at random. also changed my motherboard from z1z0-a asus to a sabertooth mark 1. didnt have it until now. also games play stable and perfect. so seems weird

 

and just another problem i just see when playing residente evil revolations 2 i guet on some áreas red lines green sometimes full i cant see shi......... First watching movies with pot player at 60fps.Now this,Alan awake slow abit since the last ones but they work fine on alien isolation,bf3,etc

 

does it happen across the whole screen sometimes? then goes away? the lines

 

this is the first driver that i got TDR in both starwars and starcraft, upped the voltage by 10mv, do they mess with the overclock?

 

they again didn't fix bf bad company 2 issue, it's now totally impossible to play...

sc**w you nvidia!

 

It's not caused by any one thing. This isn't the first time we've experienced a tdr issue. I've read that people are getting them by being on their desktop, not even doing anything.

 

Been replaying Fallout 3 (damn a extremely unstable game), and Fallout New Vegas, amazing how these games seem so much better than Fallout 4. Odd thing is all of a sudden with these drivers, both older Fallout games run both my Titan X's at 95-99%. Which seems extremely odd.

I also have a issue that if my computer goes into sleep mode and I wake it up, sli does not always seem to work ingame, some games will use sli while others wont. If I reboot then sli works in all games that support it. Running Windows 7 sp1 64bit, all updates installed, all latest drivers.

 

16-bit resolution DSR still broken
AA Stutter bug still exists. SMH Nvidia.

I'm surprised they aren't forcing GFE on us yet.

 

Not sure if the fault is with the driver or the game but with the game ready v359.00 driver I am seeing what look like very ugly white seams between wall textures in Assassin's Creed Syndicate when using TXAA or MSAA. These 'seams' are particularly noticeable indoors and seem to run vertically up the walls at intervals and are very distracting.

I seem to recall that AC Unity had a similar issue with TXAA and MSAA until it was eventually fixed. I am surprised to see them in this game however seeing as this game-ready driver lists the game as one of the supported titles!!! :3eyes:

 

Sometimes I'm too lazy and just don't check "Clean install", result is oddly enough a display driver reset, even a silent one. Like yesterday when I played WoW, the screen started to blink and the game got tabbed out then back in again...no error message though.

 

is it me..

or should nvidia worry about fixing current problems while releasing game ready drivers.


they shouldnt even use that word("game ready")


because they never are ""game ready""


I need a frankenbuild computer with nvidia sli and AMD crossfire.

 

AVP2010 is another game with bugged mouse cursor..

It gets oversized and Low Quality after 1620p DSR... Older drivers didn't have such bug.