nVIDIA GeForce Drivers v372.54 Findings & Fixes

I game in borderless window, but haven't adopted the driver yet... Sorry. Let me know how this works!!!

Sent from my SM-G900P using Tapatalk

 

Well, whenever I do update, I'll come back and post my findings. So far my 365.19 has an issue where I often get high CPU usage from multimedia task scheduler in windows (every time on boot for 15-30 minutes, and randomly but very rarely for a few seconds to a few minutes during normal operation), and it was not there from any previous driver, and the only thing I'd changed was installing 365.19, so... yeah. I'd like if this new driver did NOT have that too. =D.

 

Yet another update from Futuremark, only a day after the previous. Damn mess 3DMark v2.1.2973
http://www.futuremark.com/support/update/3dmark


Download from here http://www.futuremark.com/downloads/3DMark.exe This link will always have the latest version!!

 

I'm downloading them now. For what its worth, the 372.54 drivers have the Miracast driver in the folder, it just doesn't appear in the install options so I dunno if its installed or not.

 

I never did custom runs so I was never affected apparently.

@Phoenix Those drivers won't install, my 780 Ti isn't supported.

 

Gave up, installed 372.54.

Launched 7 Days to Die, which I was playing with friends right before I updated.

I *LITERALLY* could not believe how smooth it was. I expected no difference, but it was about as good as fullscreen is... or even better. SMOOTH like butter all over. Feels like I was using a 100Hz screen before and just fully unlocked 120Hz. It's so far the only game I tested so I'll try more later... I haven't slept. Again. Because... insomnia is not nice.

I. SAW. AN. ANOMALY.

7 Days to Die is a single GPU game. And for just a split second, JUST ONE, I saw my GPU hit 100% utilization. Literally 100% utilization. I have never, in the past six years of staring at my utilization using playclaws 2 through 5, across my 280M and dual 780Ms, EVER, seen even a HINT of a spike to 100% GPU utilization. EVER. But today.... today it happened. And HWMonitor recorded it too.

I didn't even know it was possible. But it happened. I'm amazed. I'm legitimately amazed. I sat staring at the screen for 3 minutes just in amazement at seeing 100% GPU utilization. even in firestrike I only ever would see 99%.

It didn't fix my windows being stupid and using up my CPU power when idle.

 

haha i saw the same during firestrike runs with this driver! also first time for me to see 100% gpu utilization spikes

another anomaly ive found: i usually set a batch file to start with windows to underclock my gpu to lowest stable values to keep it nice and cool for everyday work. derived the contents from nvidia inspector shortcuts. what i saw now: instant BSODS! whenever i tried to change anything whatsoever in the P8 performance profile level. so im just ignoring that now and only adjust P5, P1 and P0 levels. also, when underclocking, im not able to adjust memory clocks anymore, they are somehow tied now to the core clocks and "automatically" downclock once the core reaches a certain threshhold. i can control the core, albeit more restricted than before, i get erratic jumps in mhz downwards once i apply more than 10 mhz difference. thus, when i try to go down 5 mhz nothing changes, but when i apply -10 mhz the core suddenly shows like 4 or 6 mhz less. quite random! but at least it works and in the end im reaching the same underclocks as before, so all good
when it comes to overclocks and overvolting, nothings changed, functionality is still given

Sent from my Huawei Mate 8 NXT-AL10

 

Pretty decent :

http://www.3dmark.com/3dm/14279225

That has been an issue for a while now. The last 3 drivers haven't let me restore P - States without a BSOD.

 

I've already moved from 365.19 to the one in my Sig, It's a fine driver, released for Pascal Titan X. Was having an Exam week with immediate travelling 24Hr flight btw, couldn't keep up with the Pascal flood and this and adding Jetlag to the mix = disastah

TL;DR is this driver any worth trying ?

 

Add support. It's a pretty simple mod to add your device id and string into the right file using notepad...

Sent from my SM-G900P using Tapatalk

 

interesting about the underclocking. Mine just sits at a low clocked state when not in use so I don't really care.

Preliminary tests say CPU temps are a little higher than 365.19. Managed to spike to nearly 80c in Overwatch in the early morning. I'll check in the daytime. I was getting 87c CPU spikes and sitting around 85c in the daytime in 362.00 with overwatch, and 365.19 dropped that to "I don't remember ever cracking 80c on any core with Overwatch since". So if this sends me over that limit in the evenings when I usually would play it, I don't know what I'll do. I don't wanna be sitting here watching more 85c CPU in that game. And it'll affect my other titles too.

 

It's only got one INF file, nvci, and I'm not patient enough to go through the process of modding it when I'm just going to end up back on 372.54 anyway. These drivers have no issues for me and the smoothest performance I've seen since the 34x branch. Part of me is tempted to throw Watch Dogs on to see it the playability has increased.

But then the other part of me wants to be lazy.

 

Fair enough. Later next week when I'm done with my deadline, I'll mod the file for you and try to strip out your hardware id from the desktop default .inf files, then send you the lot. I got used to stripping mine out of the nvci files, and putting them into the desktop one, I'm sure I can try to reverse it (just can't guarantee it will work, but enjoy the college try)!

Sent from my SM-G900P using Tapatalk

 

Just use the @j95 modded drivers from over at TI.

 

This driver has screwed up G-sync on my Clevo P651RE (GTX 970M) ... again. This time, unlike the last time this issue appeared, I have all the G-sync options visible in the Nvidia control panel, but no matter what I do, can't get any G-sync. Back to 362 driver - and voila; G-sync - and everythng else, works. This is not funny anymore.

 

Oh, I should come back and report. The extra CPU load at boot was caused by Windows Update. I just set it to never check for updates (as I can manually do that) and voila, no more CPU usage spikes.

Had nothing to do with these drivers.