nV Drivers thread.

[Mangler]

These drivers are a bit faster in TW 3 on a 780.

[Meteor_of_War]

These drivers are a bit faster in TW 3 on a 780.

I'm hoping for me as well on 670. Haven't had a chance to try it out yet though.

[Nunz]

Just got on the new drivers. Will report how it runs.

W3 went from 48fps-52 (mostly right around 50) to 58-62..

niceeeee.

[Rummy]

Gonna test these as well, thanks.

[jimjobob]

played for a few hours last night after installing these no problems but now today I can't play for more then 20 minutes w/o a display driver has stopped responding.

EDIT: read several pages on the driver forums and it seems that these drivers are great for people with 6 and 7xx cards but 970's and 980's are crashing even more.

[Dave]

People on overclock.net are reporting crashing too.

I think it's something with Google Chrome. I use Internet Explorer and I haven't crashed yet with these drivers.

[Mangler]

I can play for hours as long as chrome is not running in the background.

With chrome running however, I get some sporadic display driver has crashed messages.

[Meteor_of_War]

I never use Chrome. I got one BSOD with Firefox running in the background with the previous drivers.

So far with these new ones everything's been fine. Played Alien Isolation for about 2 hours last night with FF open.

[Arrowhead]

I had two crashes in 2 days while using just internet explorer with the previous drivers. No crashes since rolling back. I know for a fact it's not a Chrome issue but a GPU acceleration issue which is enabled on my internet explorer. I didn't do any heavy gaming to find out about games too however.

[Rummy]

Another game crash with even the newer drivers, back to 350.12, again.

[Nascar24]

So far no crashing with these new drivers.

[bill dennison]

People on overclock.net are reporting crashing too.

I think it's something with Google Chrome. I use Internet Explorer and I haven't crashed yet with these drivers.

I'm up to 5 with 352.86 and Internet Explorer so don't think it's Chrome

I have not tried 353.06 but it looks like same crap to

back to 350.12 and my win 7 boot drive

[Megaman]

.

This is a GeForce Hot Fix driver, version 353.12 that addresses the following issues:

· G-Sync Windowed mode issue

http://nvidia.custhelp.com/app/answers/detail/a_id/3676

[Nunz]

I haven't had any issues with the 353 driver. Been smooth sailing.

[Dave]

I haven't had any issues with the 353 driver. Been smooth sailing.

Same here.

[Nunz]

I had issues with the 352.86 though. Blue screens, CTDs, DDSRs.

¯\_(ツ)_/¯

[Meteor_of_War]

Damn, I got another BSOD this morning just browsing on Firefox.

So with these 353.06 and the previous drivers, I have got a combined 4 BSOD.

[demo]

Still haven't bothered to update from 350.12 due to so many reports of issues with the last few driver sets.. Must admit, the last 6 months haven't been Nv's greatest when it comes to drivers. In fact, the worst I've experienced with them.

350.12 is solid as a rock, but useless to most of you I suppose because I guess the main reason you updated is for W3.. (un)Fortunately, I don't have it on PC. PS4 drivers working flawlessly

[Meteor_of_War]

Yeah, I updated for W3 and would hate to roll back as the performance with this latest one with the kepler fix has been a noticeable improvement. Didn't do extensive testing but I'd say just feels smoother all around.

Funny thing is though, the BSOD are happening just when browsing the web. Never happened when in game. Although W3 has crashed to the desktop without error message a bunch. Happy times to be an Nvidia user I guess.

[Mangler]

Don't know if it is a combination of the latest driver+1.05 patch or not, but I've noticed that TW3 will randomly crash to desktop if the afterburner OSD is active.

[Meteor_of_War]

I have been getting CTD's in W3 even without the afterburner OSD active.

[bill dennison]

still waiting to start W3 till they fix this POS .

could play on 290x cfx but they are not on water, I may have to wait for fury to play it at this rate

[Meteor_of_War]

So what are the chances the TDR and BSOD crashing with the last couple Nvidia drivers will be fixed in the upcoming game ready driver for Batman?

Getting mighty tired of this bullshit. I am averaging about one sudden BSOD a day at this point. Strangely enough it never happens during gaming though, which leads me to believe it might indeed be the hardware acceleration of Firefox, which I keep forgetting to disable.

[Dave]

I haven't had a BSOD or TDR on these new drivers, but then again I am using internet explorer.

[Hapatingjaky]

I haven't had any issues and I use Chrome

[Megaman]

Same

[Meteor_of_War]

Well its not just me. Plenty of people reporting with the same problems at the Geforce forums.

This is what some people are claiming is the problem:

Just thought I'd add my 5c on this TDR thing. Something that nobody has mentioned (weirdly) is Microsoft.

Every time MS make a change to the kernel (HAL) graphic cards start to have timing issues. Anyone that has been around since the release of the protected mode access with Vista will remember it took nearly a year for NV to get a stable driver together (AMD had the same issues). Same happened with win 7 to a lesser extent since that was simply Vista fixed. Win 8 started the problems again and before they have been nailed down fully MS announce Win 10 and we start again.

You might think that you are safe using an older OS but M$ update the HAL for compatibility and upgrade ease. This is one of M$ attempts to fix this problem: https://msdn.microsoft.com/en-us/lib...=vs.85%29.aspx Rep to Sora for this link. All this does is stop a lot of blue screens and you get the 'driver stopped responding' message, or even a silent reset where there is no error message at all. Partial reset, really? Your game is still going to crash or hang.

Because it's a windows timing error all sorts of things might fix it for you but of course the only fix is for NV and M$ to sort this out between them. MS want developers to only use published API calls. Video OEM's want to use whatever call they can find to get through the HAL as quickly as possible. A rock solid driver is easily achievable but it would be so slow as to be unacceptable to us users.

You won't see NV saying that win 10 is the problem since they are a development partner and specifically forbidden to say anything that might be construed as negative, especially this close to a major free upgrade. NV did hint at this problem when they stated that the behavior of G-Sync had to be changed for win 10 and this caused the permanently 'on' indicator. They tried to skim over the problem saying it was only cosmetic but the users forced NV to go back and see if they can fix the behavior.

I'm sure NV are as keen as we are to bottom out this problem before win 10 goes live.

Just to comply with feedback, on my Sli X8 this driver is better than the last three and only crashes out (TDR) when oveclocked - no big issue for me.

Many of you might be better to find an older driver (without any win 10 code inside) and stick with that until win 10 is 'fixed'? Use GFE to keep the game and Sli profiles up-to-date without updating the driver...

https://forums.geforce.com/default/topic/836914/geforce-drivers/official-nvidia-353-06-whql-game-ready-display-driver-feedback-thread-released-5-31-15-/post/4574535/#4574535

[Hapatingjaky]

No doubt you are having problems Meteor but like I said in an earlier post, uninstall the driver through programs and features, restart in safemode and run DDU+CCleaner, restart, install new driver. But everyone refuses to do it.

Give it a try and see what happens.

[Meteor_of_War]

No doubt you are having problems Meteor but like I said in an earlier post, uninstall the driver through programs and features, restart in safemode and run DDU+CCleaner, restart, install new driver. But everyone refuses to do it.

Give it a try and see what happens.

I did that actually, and I thought I was good for a few days until I got another BSOD. I think the only solution is to roll back a few driver versions, but I need the performance optimizations of the latest driver for Witcher 3.

I did finally remember to disable hardware acceleration in FF though, so we'll see how that goes.

My situation is especially frustrating because I am not getting the TDRs like most other people, I am just getting BSOD. I think maybe the TDRs are mainly happening with Maxwell cards, while I am using Kepler.

Right now the plan to is wait it out and ride the storm until the next driver when Batman releases, and hopefully that one fixes this.

[BababooeyHTJ]

That sucks, reminds me of the headaches that I went through with the 680 vsync issues.

[GanjaStar]

My situation is especially frustrating because I am not getting the TDRs like most other people, I am just getting BSOD.

really strange that there's such huge difference between a gtx660 and gtx670.

Must be some sort of component that is different between mid range and high end cards in a series, as everything else is pretty much just cut down specs.

Maybe a different brand voltage regulator or something.

[Meteor_of_War]

really strange that there's such huge difference between a gtx660 and gtx670.

Must be some sort of component that is different between mid range and high end cards in a series, as everything else is pretty much just cut down specs.

Maybe a different brand voltage regulator or something.

Do you always receive all Windows updates automatically?

[GanjaStar]

Do you always receive all Windows updates automatically?

no, but just 2 days ago I went ahead and fired up windows update and caught up with everything.

not being offered any new updates for win7 64.

no issues with hardware acceleration in chromium browsers or any games.

[Meteor_of_War]

no, but just 2 days ago I went ahead and fired up windows update and caught up with everything.

not being offered any new updates for win7 64.

no issues with hardware acceleration in chromium browsers or any games.

OK well please report back if you suddenly get some crashes.

Some over on the Geforce forums seem to believe the instability is related to Windows 10 upgrade compatibility tests sent over through Windows updates not playing nice with Geforce drivers.

[Arrowhead]

Has NVidia even acknowledged the TDR issue with the browsers?

I'm hoping this is fixed for the Batman drivers and we can move on...

I'm still on the GTAV game ready drivers having put Witcher 3 on the back burner.

[MNB4800]

The drivers and these TDR issues are the only reason I am not moving to Ti from my 2x980s.

[Higgy10]

new game ready driver out for batman

http://forums.guru3d.com/showthread.php?t=400215&page=3

[SLI, Batman: Arkham Knights] With a 4K display, a TDR occurs after the in-game
resolution is toggled and the application is exited.

[SLI, Batman: Arkham Knights] Heavy flickering occurs in game after Alt+Tab if SLI is
enabled.
[SLI, Batman: Arkham Knights] Severe stuttering seen, especially in indoor scenes,
when the game is running at 4K resolution and NVIDIA Gameworks settings are
turned on.
[SLI, Batman: Arkham Knights] Random flickering occurs in the game if SLI is
enabled.

[GM206, SLI, Batman: Arkham Knights] Stuttering occurs and performance drops
after shadow quality settings are toggled.
[GK180, SLI, Batman: Arkham Knights] When SLI is enabled, a crash points to
ntdll.dll shortly after the game is exited. [200116717]

looks solid...

[Mangler]

Well, there is a reason why I'm thinking of going single gpu.

Seems like the stubborn people will not have to deal with those the batman issues, they only affect 8.1 users.

[logical]

Clearly there are never any problems with SLI Enjoy SLI users.

[Dave]

Clearly there are never any problems with SLI Enjoy SLI users.

lol.

This driver doesn't fix the TDR when using Chrome or FireFox apparently. Not that that affects me as I use IE.