nVIDIA GeForce Driver v365.10 Findings & Fixes

I grab them from the "Additional Infromation" tab on this page usually:
http://www.nvidia.com/download/driverResults.aspx/102072/en-us

 

Thanks, Nvidia has the correct updated PDF there, another place to go for Additional Info

 

It might be bad timing for some people, but if more and more are finding issues with the r364 branch and using 362.00 is fine, then... it can't be just bad timing. I know 364.72 seems to have had confirmed bricks for a small percentage of users, and if installing a driver causes bricks for even a small number of people at that specific time (within 1-3 days) then I think it safe to blame the driver.

However, while I don't know about bricking cards being such a thing, I will say that the LARGE number of people that I've seen on 364.51, 364.72 and 364.96 that have listened to me and used DDU and went back to 362.00 who have reported back to me that problems went away that they didn't even consider was part of the driver? I can safely judge r364 as a broken branch. It's things like, desktop screens changing their resolution when fullscreening Dark Souls 3... Adobe Premiere Pro crashing often... random hitches in gameplay... exceedingly bad performance while livestreaming games (this one should have been totally unrelated... but it wasn't) etc etc. I can't just say "well it was a coincidence" for all of this.

Yes, it is possible they did that. There were 780Ms that held higher clocks depending on the vendor due to the memory used, though I can't remember the specifics right now. As for the memory clock bumps helping FPS, I don't know what games you're playing, but some games would show that. The 960M isn't a card so strong that this should show up often, but it does have rather low memory bandwidth. Some games might simply want or need higher amounts. If your +700MHz clock is 100% stable and you run it overclocked anyway, and it helps to have it OC'd that far, then go ahead and use it I suppose. Overclocking is overclocking; it reduces lifespans no matter what you do. Might as well get the most out of it.

With a +700MHz bump, since the card is 5000MHz normally, that should mean you managed 6400MHz on the memory clock. That's pretty good; better than I can manage on mine.

 

@D2 Ultima

I've had Windows Dialogue Boxes change their size on their own a few times on the past few drivers (excluded 365.10 so far.. touch wood). Also random 'display port not detected' errors.

I'm still on 365.10 (coz Forza tomorrow)

 

Whenever my display turns off (windows power setting, turn off display after x minutes) = every single window that isn't full screen will reset to a fixed size on the top left of the screen.

 

And does it go away if you go back to 362.00?

 

Here, look, ANOTHER r364 issue. I didn't even ASK for this one, I literally woke up to it.


Not making these things up.

 

I might need to downgrade to 362.00

Maybe the problems will go away

 

I think I might be one of the lucky ones, don't really ever have display driver issues, and I always update to the latest.

I just never see any real changes in driver performance, I've been tabulating 3DMark and game benchmark results for all drivers for the last few years - the only differences are when newer drivers are optimised for specific games & very rarely (like once or twice since I began measuring) when NVidia improve some kind of efficiencies within the driver in general (at which point they normally point to said 'accross the board' driver efficiencies in the release notes). I always use the latest driver, just for game compatibility reasons & perhaps compatibility with Windows (I don't know if compatibility with Windows is 'better' with latest drivers, it's just a thought - obviously not though for the people having issues!).

 

I'm in the same boat. Except for one release that was broken for EVERYONE I've never had a problem for years.

Sent from a 128th Legion Stormtrooper 6P

 

Yeah, it's true that if you cherry pick driver forum posts (like on geforce.com) you'll find lots of people with driver problems or at least they THINK it's because of the driver - it's mostly the people with either geniune or mistaken issues that post so it ends up looking like all drivers are rubbish when that is probably not the case. (But say if 3 or 4 longtime NBR users posted they had the same issue with a driver then I'd be inclined to believe there was a problem).

 

so is there a major problem or not? i can't even play forza motorsport 6 apex.


Looks like it can be bypassed simply by holding page up while clicking quit....WTF?

EDIT:
hmmm....looks like my laptop can't even do it on low. LOL upgrade time.

Though i wonder if that's due to not having a compatible driver or not. Also, the dynamic render quality also determines the fps: so if you set it to Low/Medium it caps the fps to 30 with high and ultra set to 60/uncapped.

even when i set it to high it can't hold 60fps.

 

Try setting the launcher to use nVidia graphics instead of the Intel IGP.

But anyway, I figure that the claims of drivers being bad to the point of causing physical damage are either overstated (such as trolls looking for attention and/or grinding the anti-nVidia axe) or false correlations (such as GPUs that were going to die anyway happening to die in proximity to a driver update). If there were systemic problems like this then there would be reports in the trade press, not just a few random forum posts.

 

did you look at my system specs? i guess not. 120hz = no IGPU.

 

Sorry, no, I don't keep up with Alienware mods.

 

Isn't a mod. AW17 R1 was sold with 120Hz.

Also, even normal AWs prior to AW17 R2 had the MUX switch, so everyone could use dGPU only.

 

Hi ! I have been looking around and decided to post and ask a question here. Did anyone encounter issues with mkv playback using hardware accel.(nvidia purevideo) in players such as splash 2 or vlc when using fullscreen ? I have updated to nvidia's 365.10 last night and when playing any movie in any app using the mentioned settings fullscreen stutters and presents diagonal tearing sometimes. This has not happened with 362.00.

ps: i have used ddu to install, nothing else changed in the system.

 

Okay, so, I don't keep up with Alienware in general, either.

 

I've seen someone on reddit complaining about the same issue. Just stick with 362.00

 

Here, want some more random internet proof?

Spoiler: Because it's a large pic

 

So no solution but driver rollback ? I guess i will stick with 362.00 a little longer. Thanks !

 

double post sorry

 

Correct. Just use 362.00 until r364 branch is gone. When nVidia puts out 367.xx or 368.xx or something, the driver branch may be different and the drivers might actually work better. I want them to hurry up because I want to use SLI with Dark Souls 3 and they have a driver-level update for the game so even importing the nVidia Inspector profile doesn't make it run correctly, so I want an update I can use without any issues. And I refuse to update to anything that looks like it's causing people problems, and r364 is ridiculously notorious.

 

Hoping for the same thing, that the next branch will be close to flawless or at least with less issues. Currently i am exchanging mails with nvidia support to help them investigate the fullscreen movie problem.

 

so long as the new doom works with 362.00 i am not gonna complain that much

 

Somehow I doubt that. I mean, Pascal will be releasing soon, so it's about tome nVidia begins their planned obsolescence.

 

Yeah. It's time now to start crippling every new drivers for old Maxwell.

 

Same reason The Division driver will probably be the last one for me

 

These maintain the trend of killing 8-9 fps in AC Syndicate. Well, back to trusty 353.06. Dark Souls 3 performs the same, anyway. I don't even know why I keep trying out newer drivers.

 

This driver crashes my GT 750M when playing Witcher 3, clean install back 362.00 and its working great.

 

Addiction to new drivers. based on joy you had getting performance and feature improvements in the past. Now it's just a shadow of that joy.
You can force yourself to stop doing that which is the cheapest method or... you get the best addiction-free method in the world one day (drivers fry your GPU and your rage makes you free of that addiction and immune... temporary).

 

Oh, I haven't bothered with those that got the most negative feedback right from the start.

 

Just thought I would drop in and tell everyone that this driver has been golden for me since it came out. I have played 7 Days to Die, Starcraft 2, Ashes of the Singularity, Battlefleet Gothic, Rocket League and a few other titles with buttery smooth goodness and no crashes what so ever in any game and no funky business in desktop activities. Looks like nVidia delivered on this one for me.

 

I wish Nvidia added names of those who driver was specifically built for in Release notes. Considering their latest struggles this Deliver to list shouldn't be too long anyways

Although I am happy for you.

 

One thing I have noticed is that youtube tears on chrome... anyone else getting this? First time I have had this issue.

 

This is usually because hardware decoding isn't happening, and this is because YouTube is serving VP9 in the HTML5 player. We get no hardware accelerated decoding for VP9. Try installing the x264ify add-on. It's supposed to force YouTube to serve h.264 video instead of VP9.

 

Working great here. Dragon Age: Inquistion, The Secret World, Rise of the Tomb Raider, and Wolf The Old Blood all running great.

Not sure if it's related to the drivers, but I can push an extra 60mhz on my GPU's ram - from +500 to +560 stable.

Forza Apex seems to have less stuttering, too, even at max settings at 1080p.

 

Will wait for the next driver depending on the severity of the TDRs.

Sent from my SM-N910G using Tapatalk