Support NeoGAF

[zma1013]

364.72 caused me an issue where it made my picture brighter, as in blacks suddenly became grey. I'm on a 970, Win 10.

 

[dgrdsv]

364.72 caused me an issue where it made my picture brighter, as in blacks suddenly became grey. I'm on a 970, Win 10.

You're on HDMI? In any case you should check what the driver says in CP / Display / Change Resolution / Output dynamic range and maybe try changing the option from Full to Limited and back to see if that will help.

 

[Glitchesarecool]

I've been scared to move beyond 362, 960 on Windows 10. Although this thread seems to indicate maybe the problem isn't as widespread or serious as I have been lead to believe.

 

[TheTrain]

I'm on the latest version since the release of it and i've not encountered any problem on two different config (Desktop and laptop)

 

[SappYoda]

I've been scared to move beyond 362, 960 on Windows 10. Although this thread seems to indicate maybe the problem isn't as widespread or serious as I have been lead to believe.

Me too. There was a driver that crashed rocket league after the first goal. I reverted that driver and haven't updated since.

I have an 960m graphics card.

 

[johntown]

I am on the latest version and I am not having any problems. However the driver released for The Division gave me problems playing back video.

I am on Win 10 with a GTX980.

 

[Iced]

My v-sync setting keeps changing in NCP from globally off to globally on. Not sure what's causing it. Seems to be random. Every now and again I'll check to see if it's been changed (for example, it did tonight after having not changed for over a week).

 

[Rewind]

My v-sync setting keeps changing in NCP from globally off to globally on. Not sure what's causing it. Seems to be random. Every now and again I'll check to see if it's been changed (for example, it did tonight after having not changed for over a week).

Do you have gsync?

 

[Iced]

Do you have gsync?

Yep. I don't want to use vsync with it though, because I just cap frame rates using RTSS.

I should mention I used Display Driver Uninstaller over the weekend and then did a clean install of the latest Nvidia driver, and the problem persists. I used to use Nvidia Inspector to force vsync globally, but I'm pretty sure those setting would be overrided by any changes I'd make in NCP, wouldn't they?

 

[Aurongel]

364.72 caused me an issue where it made my picture brighter, as in blacks suddenly became grey. I'm on a 970, Win 10.

Are you playing Dark Souls 3?

 

[Rewind]

Yep. I don't want to use vsync with it though, because I just cap frame rates using RTSS.

I should mention I used Display Driver Uninstaller over the weekend and then did a clean install of the latest Nvidia driver, and the problem persists. I used to use Nvidia Inspector to force vsync globally, but I'm pretty sure those setting would be overrided by any changes I'd make in NCP, wouldn't they?

It defaults to on because gsync works like adaptive sync. If you go over the monitor refresh rate then vsync will kick on. If you drop below then gsync is used. RTSS will not stop taring but will fix frame pace issues if used with vsync. I don't know why your set up keeps changing unless you are reinstalling the driver with a clean install. If you change the global vsync setting to off then it should stay off but having it on does not stop the gsync if that concerns you.

 

[lordfuzzybutt]

Yep. I don't want to use vsync with it though, because I just cap frame rates using RTSS.

I should mention I used Display Driver Uninstaller over the weekend and then did a clean install of the latest Nvidia driver, and the problem persists. I used to use Nvidia Inspector to force vsync globally, but I'm pretty sure those setting would be overrided by any changes I'd make in NCP, wouldn't they?

Why don't you want to use vsync?
When your gsync is on, vsync doesn't really do anything except for capping the fps at your monitor highest supported refresh rate.

You can still rtss to cap it at any rate you want but there is no point to disable vsync.

 

[Iced]

It's not so much that it bothers me when it's on, as I cap my FPS to 135 globally so I will (theoretically) never reach my monitor's max refresh of 144Hz anyway. It's more that I just want to know why it's doing it. If it's changing vsync randomly, is it going to be changing other settings randomly too?

Edit: To answer the question of why I don't want it on though: vsync introduces latency, even with gsync.

 

[Hero_of_the_Day]

Sli Titan Xs and Windows 10. Cannot install 364.72. Totally fucks my system. I managed to recover after a few resets, but I won't be trying again. I'll wait for the next "stable" release before updating.

 

[nkarafo]

364.72 caused me an issue where it made my picture brighter, as in blacks suddenly became grey. I'm on a 970, Win 10.

Are you using a TV?

In the resolution panel, does it give you the option to chose color depth in 'Full" or "Limited" RGB?

If yes, select "Full"

 

[Duckhuntdog]

I've been hearing cautionary reports, particularly from the Super Best Friendcast, about how Nvidia's recent drivers have caused all sorts of problems for Windows 10 users, some even reporting that their systems have been rendered unusable.

Well they did hire many engineers from AMD and we all know AMD's rep with regards to drivers.

 

[Finaika]

My v-sync setting keeps changing in NCP from globally off to globally on. Not sure what's causing it. Seems to be random. Every now and again I'll check to see if it's been changed (for example, it did tonight after having not changed for over a week).

I have this exact same problem too.

Its driving me nuts to access the very slow Nvidia control panel to change the setting everytime.

 

[Iced]

I have this exact same problem too.

Its driving me nuts to access the very slow Nvidia control panel to change the setting everytime.

Phew. Glad I'm not alone. Is it a recent thing for you? It's hard to say for me if it's recent because I had it on globally up until getting this g-sync monitor about 3 weeks ago.

 

[drotahorror]

Well they did hire many engineers from AMD and we all know AMD's rep with regards to drivers.

Not tryin to start shit but reading threads like this make me glad I never went with nvidia. Only issue I've had with AMD is HDMI audio drivers that I've sorted out one way or another.

I was waiting to build a new PC next month with talks of nvidia's cards coming out but now I'm leery of even going with them.

For what it's worth, I've never had to roll back AMD drivers and I've gone AMD since the 9500 non pro. I do want to switch to nvidia as they have better performance, frame pacing, etc. But threads like this always turn me away.

 

[Crimsonclaw111]

364.72

GTX 770 4GB and crashes all the fucking time, getting annoyed over it. "Nvidia display driver has stopped responding" sometimes, and sometimes crashes to solid colors (brown, gray, black, blue, yellow... whatever. No error and can only reset).

 

[Deaf Spacker]

I've had a few blue screens and hard crashes whilst playing GTA V and Need For Speed, I'm using a 980 TI.

 

[Finaika]

Phew. Glad I'm not alone. Is it a recent thing for you? It's hard to say for me if it's recent because I had it on globally up until getting this g-sync monitor about 3 weeks ago.

Yup its recent.

 

[Iced]

Yup its recent.

Installed the 364.96 hotfix thinking maybe it would solve the problem. Checked vsync settings before installing and they were off. Restarted system after installing the driver and vsync was set to on. Grrr.

Curious: have you used Nvidia Inspector in the past? I had used it to set vsync on globally (and half-refresh for games I couldn't achieve 60fps on). I wonder if there are some old ghosts kicking around.

Edit: Another setting that keeps randomly changing is the "enable G-sync" options. Keeps falling back to "enable g-sync for full screen mode" and I have to set it to "enable g-sync for windowed and full screen mode" where I want it.

 

[GavinUK86]

I had to upgrade to 364.72 for the Mirror's Edge Catalyst beta and I've had zero problems so far.

 

[nkarafo]

To people having problems with drivers:

Are you sure it's the driver itself and not the uninstallation/installation process?

I remember having some problems with a certain driver version (don't remember which) and i used Display Driver Uninstaller to repeat the whole update process and all the problems were fixed, even though i used the same driver. I'm using that for a few months now and never had any problems since.

 

[Psychoward]

I just downloaded it and got bad screen tearing in TWD but I'll try again later today and see if it was a fluke. Civ V is still giving me issues though which is awful.

 

[Branson]

I had blue screens and display driver crashes with .72 also. First time that I've seen a blue screen on Win 10.

980 here. Rolled back to 362.00 and everything has been fine.

 

[UpDownLeftRight]

I just downloaded it and got bad screen tearing in TWD but I'll try again later today and see if it was a fluke. Civ V is still giving me issues though which is awful.

It's not just you. I tried again and scrolling through the library on steam was causing major screen tearing issues yet again for me. It also wouldn't seem to enable vsync on mirrors edge 2 which is the whole reason I had to try installing them again. Back to 362.00 I go again.

 

[Iced]

To people having problems with drivers:

Are you sure it's the driver itself and not the uninstallation/installation process?

I remember having some problems with a certain driver version (don't remember which) and i used Display Driver Uninstaller to repeat the whole update process and all the problems were fixed, even though i used the same driver. I'm using that for a few months now and never had any problems since.

I used DDU last weekend and reinstalled the most recent driver. Getting the same results. About to roll back to a previous version.

 

[Psychoward]

It's not just you. I tried again and scrolling through the library on steam was causing major screen tearing issues yet again for me. It also wouldn't seem to enable vsync on mirrors edge 2 which is the whole reason I had to try installing them again. Back to 362.00 I go again.

Ah alright, I was only getting screen tearing in the walking dead so I thought it may have just been a game thing. Guess there's no harm in going back though. I just hope I figure out a fix for Civ soon.

 

[MUnited83]

a few "Nvidia display driver has stopped responding" every now and then here. On a 970. Also regularly have "computer is getting slow" messages. Tempted to get back to 362.00

 

[Pathfinder]

No issues at all with latest Nvidia driver. Windows 10 64-bit Insider Build 14328.

 

[jwhit28]

On 364.72 with a 970, Witcher 3 has artifacts even with my GPU set to stock clockspeeds (not even factory OC). They were annoying but now I get display driver crashes that kick me out of the game too. What a time to join the green team.

 

[dgrdsv]

On 364.72 with a 970, Witcher 3 has artifacts even with my GPU set to stock clockspeeds (not even factory OC). They were annoying but now I get display driver crashes that kick me out of the game too. What a time to join the green team.

Sounds like your GPU is dying.

 

[SOLDIER]

Don't think it's Nvidia related, but recently I've had a thing where turning on my PC from rest mode won't display on my monitor. I've had to CTRL+ALT+DEL to have the screen pop back up. It's pretty annoying, and I'm wondering if anyone here on Win 10 has had a similar issue.

 

[alexbull_uk]

I'm using the newest driver on Windows 10 Pro x64 w/ a 980 Ti and I've had no issues. 3 monitors and a Vive, all good.

 

[Gattsu25]

Sometimes I feel like some people just fuck around too much with their computers on a daily basis and that's why only a vocal minority gets these problems.

Windows 8.1 with the latest drivers here and no problems whatsoever with my GTX760. Scratch that, I don't recall ever having a driver problem before.

Yeah, like when I got a blue screen of death and hard crash after installing last month's drivers because I "fucked around"* with my computer...by having a second monitor connected. That was it. That was all it took to get a fucking blue screen of death and hard crash.

Or the very next patch that caused people who watched Amazon or Netflix videos to have their PCs freeze up.

Yep.

 

[Mad Season]

no issues here. geforce 980

 

[Lazybob]

Don't think it's Nvidia related, but recently I've had a thing where turning on my PC from rest mode won't display on my monitor. I've had to CTRL+ALT+DEL to have the screen pop back up. It's pretty annoying, and I'm wondering if anyone here on Win 10 has had a similar issue.

I had that problem for a little while. I Uninstalled my nvidia driver with ddu and reinstalled it. Seemed to fix the problem.

 

[Kaldaien]

I can confirm that certain parts of the low-level driver API are still broken in the latest release. Some games that use NvAPI will not even start, they just hang while initializing it. My own software can no longer read certain hardware sensors on the latest driver version.

For context, anything that uses SLI or stereo 3D rendering goes through NvAPI. It's common in AAA games. I'd really suggest keeping away from the 364.xx branch.

 

[Weevilone]

The recent drivers rendered my Win10 machine unusable. It turned out to be an issue with auto driver installs, a Creative Labs driver that supports a Soundblaster card, and the audio portion of the Nvidia drivers.

 

[Halabane]

win 10, i7, latest driver, 980 ti., g sync predator monitor 144hz...no issues what so ever,

 

[-Deimos]

I actually re-installed the latest driver yesterday for my 670. It's still fucked and I had to roll back again.

 

[dgrdsv]

I can confirm that certain parts of the low-level driver API are still broken in the latest release. Some games that use NvAPI will not even start, they just hang while initializing it. My own software can no longer read certain hardware sensors on the latest driver version.

For context, anything that uses SLI or stereo 3D rendering goes through NvAPI. It's common in AAA games. I'd really suggest keeping away from the 364.xx branch.

What games?

The recent drivers rendered my Win10 machine unusable. It turned out to be an issue with auto driver installs, a Creative Labs driver that supports a Soundblaster card, and the audio portion of the Nvidia drivers.

Could you provide more detail on what "unusable" mean there?

 

[AxeMan]

I rolled back as when my monitors went to sleep (Windows power settings to turn them off after 10 minutes) the computer would make the noise like you'd just plugged in/unplugged a USB device (my monitors aren't hooked up via USB, they are DP)
They be black and my PC just kept making the noise over and over again until I move my mouse or hit a key to wake them up.

I'm on version GeForce Game Ready 364.72 and staying that way for a while
GeForce Driver 353.82
Driver version in Device Manager is 10.18.13.5382

I get told there is an update but I'm not going back to it

Win 7 and EVGA 970. 2 x 24" Benq monitors

 

[dgrdsv]

I'm on version GeForce Game Ready 364.72 and staying that way for a while
GeForce Driver 353.82
Driver version in Device Manager is 10.18.13.5382

If you're seeing 10.18.13.5382 driver version in the device manager then you're on 353.82 version of the driver, not on 364.72.
What does the CPL say in System Information -> Components tab? All driver files but the CPL and NV Update ones must have the same version number there. If it's different then your driver installation is corrupted.

Driver installation can easily be corrupted on Win10 if you install the NV's driver while Windows is installing the driver from WU in the background. This way you may get what is described above. If you deinstall a current version of the driver do a reboot, wait for Windows to install the driver from WU, do another reboot and after that install the NV's driver on top of the one which Windows has installed from WU. Always do another reboot when in doubt basically.

 

[Killzig]

I've been hearing cautionary reports, particularly from the Super Best Friendcast, about how Nvidia's recent drivers have caused all sorts of problems for Windows 10 users, some even reporting that their systems have been rendered unusable.

The current version that's available to install on my machine is version 364.72. I was thinking of installing it to see if it gave Dark Souls 3 a boost in performance, but if this is the driver that is known to cause the above problems, I'll hold off.

the current driver crashes more often than i'd like when using dual displays, but it's otherwise 'fine'.

 

[Weevilone]

Could you provide more detail on what "unusable" mean there?

It hosed an Nvidia driver update, so I was stuck at 640x480 or whatever horribly low resolution is default.. on my 3440x1440 display until it could be fixed. The NV driver couldn't install, even with all the usual safe mode, DDU, etc troubleshooting. The install would fail with no useful information in terms of error messages, and no logs were written.

I was stuck like that for a couple weeks. I suppose I could have moved back to integrated graphics for a few day, but it's a gaming rig so it still wouldn't have been good for anything.

 

[DOT DASH DOT]

364.72 random driver crashes, only seen on DS3 and ROTTR, after the driver has recovered error, they will run at around 20fps until I restart the PC.

 

[dgrdsv]

It hosed an Nvidia driver update, so I was stuck at 640x480 or whatever horribly low resolution is default.. on my 3440x1440 display until it could be fixed. The NV driver couldn't install, even with all the usual safe mode, DDU, etc troubleshooting. The install would fail with no useful information in terms of error messages, and no logs were written.

I was stuck like that for a couple weeks. I suppose I could have moved back to integrated graphics for a few day, but it's a gaming rig so it still wouldn't have been good for anything.

Why didn't you just ran system restore?