• 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.54 driver out

Yeah, they really took a shit with this one. This and the Anniversary Update for Win10 just make me sad to use my computer right now.
 
I used DDU and the flickering went away after a reinstall it appears. I don't think this driver is a good driver to write over the existing.

I also used DDU as well but it never changed anything. The only way I could get it to stop flickering was to change my refresh rate from 144 to 120 and then back to 144 each time the PC was rebooted.
 
I also used DDU as well but it never changed anything. The only way I could get it to stop flickering was to change my refresh rate from 144 to 120 and then back to 144 each time the PC was rebooted.
Are you using Shadowplay's desktop capture or something?
 
I also used DDU as well but it never changed anything. The only way I could get it to stop flickering was to change my refresh rate from 144 to 120 and then back to 144 each time the PC was rebooted.
Mine very well could flicker but I reverted to 368.95 so I really didn't test further.
 
Are you using Shadowplay's desktop capture or something?

Nope not using any capturing software. It would intermittently flicker it seems at every time the card boosted. Opening folders, browsing and scrolling in chrome/IE/Firefox, any action really. I reverted back to the previous drivers.
 
Ill check these drivers out now. That DPC latency issue has been killing me in games. I honestly do not understand why people are not talking about it. I bought this 1080 like a month or so ago and its still an issue in games like Dying Light. These Nvidia drivers have honestly felt just as bad as people say AMD drivers are.

Update.

Still getting DPC latency issues in Dying Light causing sound to lag and making all dialogue in the game an absolute pain in the ass.
 
Last edited:
Just had an hour or two of fun with Dying Light, audio sounded fine to me (372.54)?
 
Just had an hour or two of fun with Dying Light, audio sounded fine to me (372.54)?
I'm glad it works well for you but on my end i get audio lag. I can prove it if you don't believe it. Like all driver issues different configurations will lead to different issues.
 
Ill check these drivers out now. That DPC latency issue has been killing me in games. I honestly do not understand why people are not talking about it. I bought this 1080 like a month or so ago and its still an issue in games like Dying Light. These Nvidia drivers have honestly felt just as bad as people say AMD drivers are.

Update.

Still getting DPC latency issues in Dying Light causing sound to lag and making all dialogue in the game an absolute pain in the ass.

Not everyone has the DPC issues. It's likely a combination of factors and not just using one brand of GPU.
 
The drivers work fine on my Windows 7 machine, it's Windows 10 that I have a whole slew of problems that I didn't in 369.09.

Too bad, since I wanted Global Vsync off.
 
Not everyone has the DPC issues. It's likely a combination of factors and not just using one brand of GPU.

Yeah but this has been going on for ages, and I haven't even seen a definitive cause for the issue. Yeah, not everyone has it, but enough people have it be a major issue
 
@Fidel How are you getting audio anyways? Are you using an HDMI cable to your screen, or the onboard audio out to some speakers (analog or digital)?

Also is it just Dying Light or are there other games?
 
I've decided to try geforce experience driver update... I'm on 369.09 will update to 372.54. If you don't hear from me within a day please, tell my family i loved them.

Update: it's alive
 
Last edited:
I'm glad it works well for you but on my end i get audio lag. I can prove it if you don't believe it. Like all driver issues different configurations will lead to different issues.

Might be unique to your setup. I've owned a 1080 and now Titan X (P) and neither has dpc latency problems.
 
Yeah but this has been going on for ages, and I haven't even seen a definitive cause for the issue. Yeah, not everyone has it, but enough people have it be a major issue

Once upon a time I had a dpc latency issue. Turned out it was that my computer's power scheme had been set to balanced at some point. Setting it to max performance took care of it, no more sound skipping or interruptions.
 
Once upon a time I had a dpc latency issue. Turned out it was that my computer's power scheme had been set to balanced at some point. Setting it to max performance took care of it, no more sound skipping or interruptions.

Yeah i get what you're saying and it's often a stupid thing like that causing it, but there's some strong correlation between pascal cards and dpc latency, so there's obviously some kind of issue that appears under certain conditions, exclusive to pascal.
 
Yeah i get what you're saying and it's often a stupid thing like that causing it, but there's some strong correlation between pascal cards and dpc latency, so there's obviously some kind of issue that appears under certain conditions, exclusive to pascal.

True, but it's unlikely to be exclusively the 10x0 card's fault because there are plenty of us around that don't have that problem. So therefore it's likely that there are multiple conditions that have to be met. Sometimes it's possible to locate and fix the other contributors and take care of the problem without needing to worry about something like nVidia addressing it.
 
True, but it's unlikely to be exclusively the 10x0 card's fault because there are plenty of us around that don't have that problem. So therefore it's likely that there are multiple conditions that have to be met. Sometimes it's possible to locate and fix the other contributors and take care of the problem without needing to worry about something like nVidia addressing it.

I've never had the issue with any other card. My Maxwell Titan X is fine and the old 390x was fine. My 1080 rig is set to high performance and I still deal with the issue. It's set to 70% min cpu freq and high performance on the gpu side too.
 
I have to DDU and reinstall the drivers... getting low gpu utilization in obduction and it's pissing me off, was fine on 369.09 >_> will give 372.54 a shot then back to 369.09 if its still weird

DDU and reinstalled 372.54, now it runs fine everything is normal.

Ieldra's verdict:

GFE sucks balls
 
Last edited:
I've never had the issue with any other card. My Maxwell Titan X is fine and the old 390x was fine. My 1080 rig is set to high performance and I still deal with the issue. It's set to 70% min cpu freq and high performance on the gpu side too.

He's saying the card isn't the root cause of the issue, not that it's unrelated. There's clearly some unfortunate mix of factors that lead to this dpc issue specifically with Pascal cards
 
  • Like
Reactions: sover
like this
I think it's simply an "early adopter" issue that should be resolved shortly.

Like how the 300 series cards were downclocking when they first came out because of all the wacky power-states etc
 
Have artifacts in Attila with this driver. Reverted back and no problems there. Yeah, 372 seems to be of a lesser quality than 368.81.
 
I am pretty sure its an issue with either the 1080 or pascal in general and the NVIDIA drivers. My previous 780 Ti's had no issue and I did a clean install on Win 10 when I upgrade to my 1080 and still experienced DPC latency issues. The 372.54 driver update fixed those issues. Also I believe the issue still has not been fixed for SLI, so if you have SLI and still have DPC latency issuses that is why.
 
adaptive vsync isn't working for me the way it used to. 58 fps and im still stuttering and tearing. 60 fps and im smooth, but tear occasionally. wat :(
 
Fallout 3, NV, Oblivion, and Potentially Skyrim are not working with this driver on Windows 10 Anniversary Update.
 
Having DPC latency issues with F1 2016 and my Pitan X. Oddly doesn't happen in any other game I've played. Also doesn't happen in Windows 8.1...
 
I too lost a lot of overclocking capacity with this and a 1080 and a G-SYNC monitor and the Win10 anniversary update. Lots of random driver crashing if I leave it where I had it.

Does the previous driver work with the anniversary update? Or do I need to wait until they fix this one?
 
I too lost a lot of overclocking capacity with this and a 1080 and a G-SYNC monitor and the Win10 anniversary update. Lots of random driver crashing if I leave it where I had it.

Does the previous driver work with the anniversary update? Or do I need to wait until they fix this one?
The AU shipped with a WDDM 2.1 driver that you could roll back to. It's version 369.09.
 
369.09 worked flawlessly for me. 372.54 appears fine but I've only tested obduction. I'll try paragon later tonight
 
For a single 1070 (hopefully I will get it this week) what driver should install on my win10? I want to make sure the card is fine and do some o/c with it.

Thanks.
 
Is anyone else noticing that when they do a remote desktop or any other full screen overlay the task bar won't disappear/hide?
 
Fallout 3, NV, Oblivion, and Potentially Skyrim are not working with this driver on Windows 10 Anniversary Update.

Interesting, seems to be a Windows 10 AU issue with DX9 and Games for Windows.

The issue seems to be based around this: (Taken from Geforce forums with Fallout3/NV)
  1. Renderer Device Information:
  2. NVIDIA TITAN X (Pascal)
  3. C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_b07608b795ac4102\nvd3dum.dll
  4. RenderPath : BSSM_SV_2_0
  5. PSversion : 300
  6. VSversion : 300
  7. VStarget : vs_2_0
  8. PStarget : ps_2_0
  9. PS2xtarget : ps_2_0
  10. maxPS20inst : 512
  11. 3.0 Shaders : no
  12. Image space effects : yes
  13. Nonpowerof2textures : yes
  14. FP16ARGB blending : yes
  15. FP16ARGB filtering : yes
  16. High dynamic range : no
  17. Bloom lighting : yes
  18. Refraction : yes
  19. 2.0 hair : yes
  20. SLI mode : no
  21. Water shader : yes
  22. Water reflections : no
  23. Water displacement : no
  24. Water high res : no
  25. Multisample Type : 0
  26. Shader Package : 2
In short, that's messed up.

I wonder if its actually a WDDM2.1 issue with these. But I hope its a driver issue. Else its not going to be solved anytime soon if it has to come from MS.
 
Last edited:
Love Windows 10 Anniversary!!! Have nothing but these type of errors whether its a Blizzard game or EA/Origin(Battlefront): Application has been blocked from accessing graphics hardware. Application Diablo.III .exe has been blocked from accessing graphics hardware. Replace Diablo III with Deus EX on steam, Battlefront.exe. wow.exe, overwatch.exe, etc..
This is happening since Windows 10 Anniversary update on 2 different drivers. I had a log one night last week for WoW that had 18 times it had this error as it kept repeating the error after error till I forced a restart. Thanks M$!! :banghead: Had no problems like this the last few years. that I can remember!
 
Back
Top