• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

372.70 WHQL Driver Released

God damn it. BF1 has resolutions scale slider and it's bugged.
Defaults to 42% which is actually native res

Ive been playing with 100% which is basically 2x and wondering why the fuck it runs like shit.

game is really good graphically, but actual gameplay feels meh to me

also DX12 spreads load more evenly across CPU threads and I have lower core temp spikes on CPU compared to DX11
 
Have installed this driver six times today on four cards without issue on virgin installs.
 
  • Like
Reactions: Nenu
like this
You don't. To have access today, you needed to have been a battlefield insider. For everyone else, it starts tomorrow.


God damn it, guess were waiting. Hopefully it unlocks around midnight or some shit. Gonna try it out on my pc and xb1
 
Flickering is still here on Gsync with Dell 2716DG. Grrrrrr.....


Back to 368.95.
 
That is what happened to me with 372.54.

I was hoping 372.70 would fix it.

Well, I DDU'd my 369.05 drivers in safe mode, rebooted and installed 372.70, and they actually installed! (Yay, thus far MUCH better than 372.54 :p )

Now for some stability testing!
 
Well, I DDU'd my 369.05 drivers in safe mode, rebooted and installed 372.70, and they actually installed! (Yay, thus far MUCH better than 372.54 :p )

Now for some stability testing!

So much promise, but alas another fail.

With 372.70 Fallout New Vegas instantly crashes on load, with no overclock.

Time for another roll back to 369.05 :(
 
So much promise, but alas another fail.

With 372.70 Fallout New Vegas instantly crashes on load, with no overclock.

Time for another roll back to 369.05 :(

Yep, back on 369.05, and everything works again.

It's a crying shame. Solid drivers have been one of the biggest reasons to buy Nvidia for over a decade.

Makes you wonder what happened. Thus far they dropped the ball big time with both 372.54 and 372.70.
 
Did an inline install on top of 372.54 with GeForce Experience and no issues thus far. Overclocking is better with this release than prior. No longer getting DPC latency issues in F1 2016. Video card is now consistently clocks down to idle speed when my display is at 144 Hz. Seems like a good release at this point.

Found out my Windows 8.1 install got borked somehow. I'm going to have to do a wipe and clean install at some point...
 
Installed and working well here, so far. I'll probably test with some BF1 tomorrow. Hopefully it fixed the DPC issues that I was encountering.
 
Overclocking is back to normal again.


It is funny that these drivers bring back the low gpu usage issue in Ryse Son of Rome yet again that impacts Maxwell and Pascal cards.

BTW to those that have no idea what I am talking about, you have to run something in the background such as Origin to make the gpu usage work properly in Ryse.

I found the most bizarre fix for low gpu usage on Maxwell cards :: Ryse: Son of Rome General Discussions



a long time you had to run windows media center to achieve the same thing in certain games lol
 
Side note, is anyone else's Origin running like complete dog shit? Like nothings loading in the store properly and what not? I'm guessing traffic for the beta download coming up??
 
Side note, is anyone else's Origin running like complete dog shit? Like nothings loading in the store properly and what not? I'm guessing traffic for the beta download coming up??
Well, I have noticed my rig just freezing out of ordinary with no clues in the winlogs that only started after the new version that came out I guess a few weeks ago. Other than Origin beta cant contact some server. I also upgraded to the latest NVidia driver that came out right before this one here we are talking about at the same time that Origin patch came out. Not sure which caused the issue.. Now both of those are upgraded, so I will wait and see how it goes...No lock up yet.
 
So much promise, but alas another fail.

With 372.70 Fallout New Vegas instantly crashes on load, with no overclock.

Time for another roll back to 369.05 :(

I kept the 372.70. But yes. still no fun in running Fallout3/NV. And I guess Oblivion(HDR only?) too due to incorrect ability detections. Aka SM2.0, no HDR etc.

Still wondering if its the drivers or WDDM 2.1 to blame for that.
 
uhh getting < 50 fps in GTA V lush areas (grass, primarily) @ 1600P with a Titan Pascal on these drivers. Everything at highest settings (graphics + advanced graphics), 4x MSAA, Grass at "very-high", shadows at softest - is this to be expected? I know 4x MSAA is and grass are frame rate killers but I expected more...
 
uhh getting < 50 fps in GTA V lush areas (grass, primarily) @ 1600P with a Titan Pascal on these drivers. Everything at highest settings (graphics + advanced graphics), 4x MSAA, Grass at "very-high", shadows at softest - is this to be expected? I know 4x MSAA is and grass are frame rate killers but I expected more...

What did you have with earlier drivers?
 
Overclocking is back to normal again.


It is funny that these drivers bring back the low gpu usage issue in Ryse Son of Rome yet again that impacts Maxwell and Pascal cards.

BTW to those that have no idea what I am talking about, you have to run something in the background such as Origin to make the gpu usage work properly in Ryse.

I found the most bizarre fix for low gpu usage on Maxwell cards :: Ryse: Son of Rome General Discussions




Interesting. It doesn't help if you just set the 3d settings in the Nvidia driver settings to "prefer maximum performance"?
 
372.54 was the same, don't have anything to compare to prior to that.
wi
Ok, I thought you were comparing to, say 369.05, and noticed downgrade in performance. I however saw a small performance increase in RotTR with these drivers as in the benchmark my minimum fps in forest area increased in a few fps.
 
Artifacts display on character toons in Star Wars the Old Republic Knight of the Fallen Empire. This occurs with driver versions 372.54 & 372.70. Revert to 368.81 to resolve.
 
I had flickering and artifacts with the 372.54 drivers. I have not tried these, yet. I'll give them a go this weekend. I went back to the 369 drivers.
 
Interesting. It doesn't help if you just set the 3d settings in the Nvidia driver settings to "prefer maximum performance"?
No because the issue is with GPU usage not the clock speed of the card. What makes me mad is that the devs flat-out ignore me everytime I ask them about why this fixes the GPU usage for their game.
 
No because the issue is with GPU usage not the clock speed of the card. What makes me mad is that the devs flat-out ignore me everytime I ask them about why this fixes the GPU usage for their game.

i had this problem after updating with geforce experience, just ddu and installed same driver manually and it was fixed
 
Played some Overwatch on these last night and everything seems fine to me. Card overclocks to 2088MHz, totally stable, no issues compared to earlier releases.
 
These drivers also supposedly fix the issue where maxwell and pascal GPUs won't clock up after being idle for a couple hours. Huge problem, if you hit that bug-- I left MSI afterburner open on my desktop since getting my 1080 because I had to reapply my profile every couple days to fix it.
 
These drivers also supposedly fix the issue where maxwell and pascal GPUs won't clock up after being idle for a couple hours. Huge problem, if you hit that bug-- I left MSI afterburner open on my desktop since getting my 1080 because I had to reapply my profile every couple days to fix it.

Interesting.

I never noticed this, but that is likely because I dual boot for games. I only ever boot into windows immediately before launching a game, and when I quit the game, I also reboot out of windows again :p
 
Weirdly enough I had again this glitching/artifacting in Attila and it was on the campaign map now. I don't have any artifacts in other games like F4, witcher 3, GTA V and RotTR, but this is the second time I see this in this particular game with first 372.54 and now 372.70. I still blame drivers, as I don't remember anything like this happening with attila on older ones, but I still don't like it. Will have to be cautious. Though I also had OSD turned on in afterburner and I guees it could conflict with the game too.
 
I'm getting some artifacting in Photoshop using Camera Raw filter with these drivers. Everything else seems to be working good.
 
I'm getting some artifacting in Photoshop using Camera Raw filter with these drivers. Everything else seems to be working good.

I'm getting this black/coloured pixelated artifacts. Really hopes it's just the driver and particular game issue.
 
I'm getting this black/coloured pixelated artifacts. Really hopes it's just the driver and particular game issue.

How does it look like for you? I basicaly get this balck/coloured pixelated areas in Attila.
 
My 1080 is back to not downclocking at idle with these even if I set my main monitor to 120Hz. Sadly I need to keep them installed since I'm playing BF1 beta.
 
Finally had some time to download driver, tested Doom in Vulkan and was very impressed! The time delay to respawn is gone and is rather quick. Frame rate went up significantly from the high 50's to mid 70's on Nightmare settings (everything maxed) at 3440x1440p. Looking great.
 
Back
Top