nVIDIA GeForce Driver v365.19 Findings & Fixes

+135 is the max AB goes. I'm sure it could do more, but I don't know how to push it.

Correlation != causation. Not everyone is crashing. I'm not crashing in Forza, ever. Quantum Break is broken and crashing heavily on nVidia but not AMD. Killer Instinct doesn't crash. Gears doesn't appeal to me, but I haven't read anything anywhere about it crashing. BTW, I fixed your typo.

 

QB didn't crash once for me, and the last patch allowed me to run the game at 1440p with decent performance.

 

Because you're on a stock vBIOS. They'll never go above +135, and for maxwell that might as well be stock.

The large majority of users are crashing. And only in UWP titles is there a huge amount of crashes. Since Gears of War came out that was an issue. GoW crashed nVidia, AMD ran like crap. #DX12. Killer Instinct I admittedly heard nothing about. Quantum Broken crashes a lot, and I've seen many many users complaining about Forza crashing (and none of them on AMD either).

Who knows? It might be drivers, though since it's limited to mostly M$-released UWP titles (won't happen on say... Rise of the Tomb Raider), that's where it looks. Also, DX12 is all about the developers' optimizations and usage methods for the GPUs. Stability, performance, smoothness, etc is almost entirely on their end. DX11 and below require the driver to interpret how the game wants to do what it wants and use tricks and hacks and all sorts of stuff to get it working, quite often "mimicing" another title's tech that's either easier to render or more established a method, even if the end-result is the same.

And I didn't make a typo.

 

And I'm not going to risk destroying my laptop just for a few extra MHZ.

Prove it.

No, you're correct, that wasn't a typo - that was a childish bit of immaturity. And I fixed it, again.

 

Then you're not "overclocked to its limits". Fix your statements before trying to get me to fix mine about a company that has literally zero care for its consumers.

Go look up reviews and people playing it in general. Start a reddit thread asking for people who have had no problems whatsoever playing UWP games on nVidia cards. Check other forums. Do your own bloody research. YOU have no problem in Forza, great. Congrats. Lucky for you. Multiple reviewers with barebones test-bench type installs, and multiple end users do. And they don't in other non-UWP games for the most part, or non-MS-UWP titles. UWP isn't the issue. It's their games. Just like when Battlefield 4 would crash my GPU drivers sometimes when I alt tabbed, or when Dark Souls 3 launched and using any "lighting" setting above "low" on Kepler cards caused GPU driver crashes. It's the games doing something they should not. I wasn't even on DS3 ready drivers or anything. People on old old old drivers had issues too. The game did something.

You're not "fixing" anything. I typed what I want to type. You understood what I was saying. You're not "fixing" anything. You're editing what I said because of whatever reasons in your head that I won't even begin to predict. Yet I'm childish?

 

It actually IS at it's limits, because regardless if the limit is imposed by the actual hardware or it's software, it's still the limit. Are there ways around the limit? Yeah. Is it worth potentially destroying an $1100 laptop? No.

As for Microsoft - well, there isn't a single company on this planet that has more than zero care for it's customers, unless it's customers are shareholdes.

Point 1, Forza is a beta. It does have problems. But I don't see a massive amount of complaining in the Forza subreddit, or the PCMR subreddit, and of all the reviews I've read, I think one had an issue with crashing.

I'm not interested in Gears, but I read/watched Digital Foundry's videos and articles about it, and they didn't call it out for crashing like they did QB. Which they did, because it crashed, a lot, which I read about in other places. In fact, based on my own reading around the web, QB is the only Microsoft-released UWP game that I could find that does crash a lot.

It's a maturity perception issue. Often, in my experience, people who change words or letters in company or product names with the intent to bash them (ie: Crapple, M$, Microshaft, XBone, Gaystation), have the mentality of a 13 year old. You do seem to have a clear, coherent argument to put forth, but it is otherwise marred to the point of being disregarded entirely by calling Microsoft, "M$".

 

It's not a hardware limit. It's always been here for mobile GPUs, a +135MHz limit. And there is no "risk" of destroying hardware from flashing a video BIOS. There is a risk of soft bricking the card if the flash somehow fails, however there are ways to fix that even, and it won't destroy your laptop. It's up to you whether to take that choice or not (I did it for mine; mine wouldn't even work at stock at 120Hz I got artifacts like crazy so it was literally required)... but it's nowhere NEAR the limits of your chip.

There's companies that care... most of them aren't in the US. Or they're smaller companies.

I saw many people the day it launched and a couple days after. Since then, as per usual, it died down. Every game's early problems vanish shortly after launch because people move on and new things to talk about show up. There's even users here at stock who'd tell you they ran into issues. Is it a beta on Xbox 1? If it isn't, and it's fully launched on X1 and "beta" on PC, I won't even count that. Too many marketing teams use "beta" incorrectly too, to scapegoat things or get people to buy. I don't buy it. One of my close friends worked at AV and at Microsoft. I hear lots of things about what really goes on with dev teams and games and why a lot of things end up being what they are. I don't give them any quarter.

If you can't find people complaining about Gears anymore I'll accept it. I saw what I saw on twitter and reddit etc on launch and then it got quiet. For all I know it might be fixed now.

When a company gets so boldfaced with the way they do their things and shafting their customers while boldfacedly lying, I tend to stop calling them by their proper name in contempt when it isn't necessary to use their name properly. Ubisoft is one other company that deals with that because of how they treat the PC platform with their games in general, after consistently lying about it every single game. nVidia gets their own versions at times. If they want their name said properly they can actually put in some work and stop lying for it. Simple. If we get no respect from them, they need no respect from us.

 

If you guys want to debate UWP, make a thread for it please. As for these drivers, I just picked up the X/X2 HD Remaster (it was only 17.99 on GMG with a coupon) so I'll install it and put these drivers on tonight and see how it goes with my 780 Ti.

 

Working great for me. And Squeenix needs to outsource all of their ports because this one is fantastic. Full 1080p out of the box, 8x MSAA, 16x AF, SMAA Ultra, the works! Obviously the game isn't very demanding so I'm considering kicking the DSR up to 4K to see how that works but anyway these drivers seem to be working fine and Squeenix games tend to be the WORST when it comes to unstable drivers. I should try XIII with these.....

This is on my 780 Ti btw.

Edit: 4K DSR works flawlessly which is a first. Usually on my 780 Ti, every time I would use DSR any time I alt-tabbed the game would crash but I was able to alt-tab and adjust the font size for the game in RTSS to adjust the monitoring text and went back to the game with no issue. Also, it looks ridiculously amazing. The 4K downsampling makes this game look like it was released this year with how smooth all the textures are. DSR never quite worked right before. It obviously kicked the temps up but my card is boosting the whole time so 70s are expected.

 

Wait, wait, wait... What is UWP in the first place? I'm guessing it's only those games off the Windows Store...

 

Yes, Universal Windows Platform. The games running from Windows Store are running as apps which is limiting a bunch of the usual properties like vsync, full screen etc. Apparently they´re working on fixing it, someone else will have to fill in the blanks here.

 

Oh, right, thanks very much then. I'll probably update to this driver since it appears to work well (but then again, I've never really faced a driver issue on my W230SS). I just think I might need a better card soon, but not so soon. I want to see how the GTX 1060M pans out.

 

I would say that these are the most stable drivers in awhile... look at the game time...



I was playing that whole time without a hitch and quite a bit of that is with 4K DSR and all graphics options in the game maxed out. Granted the game doesn't have a heavy load even on ultra but DSR kept it boosting whenever it wasn't playing a cutscene (its Final Fantasy so enough said there).

 

FS 4K - http://www.3dmark.com/3dm/12068296?
FS Extreme - http://www.3dmark.com/3dm/12068329?
FS - http://www.3dmark.com/3dm/12068364?
Sky Diver - http://www.3dmark.com/3dm/12068409?
3DM11X - http://www.3dmark.com/3dm11/11257089
3DM11P - http://www.3dmark.com/3dm11/11257098
SteamVR:



Long story short, these seem to be the best drivers my 780 Ti has ever used. Not once did my cards drop out of boost when the load got too high which I've seen on older drivers (my 780 Ti is on EVGA stock vbios and I haven't raised the power limit). It seems like they fixed Kepler performance in this release.

Wow. Unreal Tournament @ 2880x1620 (DSR) still maintains almost 60FPS with all settings on Epic. 1440p is flawless 60. Drop it down from Epic to High and its a smooth 60 at 4K.

Maybe I don't need to upgrade just yet...

Another thing I noticed? My boost clock is 1076MHz but this driver is boosting up to 1150 at times. I checked with GPU-Z and the base is 1006 and boost is 1076. Nice free performance upgrade. Didn't bump my temps either. I'm actually used to seeing 80s at 1076 but it's not passing 75 at 1150 and that's with the ACX fans only at 55-60%. Considering my particular card won't do 1200 stable at stock voltage, I wonder if overclocked cards get a boost bump too. I need to go to bed but I'll test it later.

Either way these drivers are winners. Oh I tried TW3. Ultra w/o Hairworks is over 50FPS all the time and when I'm not zoomed in on Geralt or other characters, its usually over 55 and often times 60-65. That's patch 1.08 so I'm sure it's improved even more since I updated the game last.

I'll try the ultimate crash king, Watch Dogs, later today too. If it doesn't crash these drivers are flawless.

 

i am assuming you mean your GPU lol

 

Okay okay, this driver now works really good on W-Ten.

One issue.

I can't make any 3DMark benchmark run god damn it.

 

Same.

 

Are you running the latest 3DMark? They recently updated it. The whole thing got an overhaul.

 

Well.. now I'm considering upgrading to this thing. I really want that SLI support for Dark Souls 3. >___<

 

Get on it man. I got a nice boost from these drivers, both clock and stability-wise. And I'm on W10 no less.

 

I'm so lazy though.

Meh I'll do it tonight. Maybe it'll reduce CPU temps in games for me; I'm certain now that 362.00 increased my CPU temps like another user was saying over 359.00

 

Ok I stopped being lazy after lying down for approximately 40 minutes. So far no issues, I guess.

 

Alright it's time to go venture into the world of Watch Dogs. I'll be back when it crashes or in an hour, whichever comes first.

 

Ehhhh... that game is too boring... Anyway... No crash.



There was some degree of boost the whole time too and this was with a DSR resolution as well (2715x something I am too lazy to look). The game was actually playable on ultra. Not a smooth 60 but no more pop in and stutter like it has always had. So yeah, again, more praise for these drivers.

Temps are high because my ambient is higher today. Its like 25C today instead of 20C. Still though, considering that these drivers are overclocking my boost clock from 1076 to 1150, 82C is low for Watch Dogs.

 

365.19 vs 362.00 both same custom settings, testing now with games.

 

But but, his niece was killed... You have to kill everyone, because you know, dead niece.
Did I mention his niece was killed?

 

I got so sick of the crashing and the stuttering that I totally spaced out about the story. Not that there was much of one. I even have the season pass and bad blood (I think that's what it's called) expansions. Doesn't interest me in the least.

 

so we're all good with this driver version?

 

I've literally had zero issues. The free boost increase is nice too. I just reinstalled W10 (my old install was just messed up from all the anti-spyware tools) and just got done with another hourish session of gaming. Its nice to actually be able to use my gaming desktop for, you know, gaming.

 

cool. same here: no problems.

 

Bit the bullet as well. Drivers seem to be fine.

 

Yas.

Tried the ones on Steam I purchased back in the days.

Tried the demos on their websites.

No luck.

Oh well, I can live with this.

 

What is the failure mode you are seeing? Is the app putting up an error dialog, or failing to start, or crashing during execution?

Futuremark has a bug support page where you can tell them about the problem, and they can give you debugging help to get it running.

How to report a problem
https://www.futuremark.com/support

 

Lets see.

> Start up 3DMark Basic Edition, Fire Strike
> No settings touched
> 64 bit/32 bit - doesn't matter, both produce same error
> Start Benchmark
> Desktop starts blinking and my second monitor gets an epileptic attack, epilepsy at its finest on hardware
> Win-X says something along the lines "nVIDIA driver crashed and recovered"
> 3DMark gives me the following score: 0. I know, amazing it could figure all of that out by itself.

Spoiler: screenshot

 

That failure mode sounds more like an Nvidia driver problem with multiple monitors, but could be a Futuremark bug too.

Did you try disabling either the internal or external monitor, and running the benchmark with only 1 monitor active?

 

Yass.

Just got a bluescreen trying to run it on one monitor lol.

No issues running the benches on the previous drivers.

I am too lazy to combat and analyze further, especially because everything else works flawlessly.

 

I haven't tried 3DMark, however this seemed to have lowered my CPU temps a few degrees in Dark Souls 3 and I'm going to assume in general, since I was using SLI in DS3 and had higher overall framerates in the game too.

Seems 362.00 had raised my CPU temps and I didn't realize. That would explain why TSBench was under 80c in 1024M but I got 86c in overwatch locked to 120fps.

Oh well, seems this driver is basically fine for me (not that I ever had problems with any drivers I ever tried... ever. Even though I went 353.06 --> 355.60 --> 359.00 --> 362.00 so I went stable through stable mostly)

 

Hard to have driver problems when you wait for everyone else to try them first

 

What can I say? I'm a sly man.

 

I think it's safe to say that of you are benching with more than one display it will screw up but single displays are ok... Odd though.

Sent from my SM-N910G using Tapatalk

 

I've benched with my TV hooked up to my laptop but it was mirrored not extended. I don't have my laptop right now or I'd try it but benchmarks are working fine on my desktop.

 

How can GPU drivers change the CPU temp? I know Nvidias drivers can meddle where they shouldn´t but can they shift load from GPU to CPU?

 

No idea. All I know is I'm on average running about 3-5c less in Dark Souls 3, and I'm sure in other games as well.

 

If something is being done more efficiently and the cpu doesn't have to work as hard (dx12 + vulkan good examples) it very well could. Or perhaps offloading something from the cpu to GPU.

Sent from a 128th Legion Stormtrooper 6P

 

Please note: my CPU usage has not gone up nor down. It simply runs cooler.

There was another user claiming 362.00 had made his CPU hotter than 359.00, and after using 365.19, I've found that to be true.

 

Maybe the cpu load is shared better between all cores. Therefore no change in cpu usage. Better cpu optimizing in the newer drivers. Have you same physics score with newest driver?

 

Haven't run firestrike. I've looked at the loads in Throttlestop and they appear to be the same. It's just overally lower.

 

So is 3dmark crashing a driver bug or a 3dmark bug? The gpu didn't crash since the clocks were still applied. This was with driver 362.00.

Sent from my SM-N910G using Tapatalk

 

That is a question only the GPU-gods can answer.

Win-X has been nice to me, but sometimes I wonder if it's all a trick.

 

I have no 3dmark crash so it sounds like it may be a Maxwell bug. Try Catzilla and see if it crashes. Catzilla stresses the system more than 3dmark.