GeForce 387.92 WHQL Game ready Download & Discussion

How do you set the FPS cap with RTSS? I use it and it does not let you use decimals.

 

Did you under-clock/volt? I thought 139 | 405 MHz & 0.6500 V = TDP 4.x% = 39~43°c (My ambient is around 28~32°c)

 

https://www.blurbusters.com/howto-low-lag-vsync-on/

 

These drivers are much better than the previous three WDDM 2.3 drivers. The browser, DWM, video and fullscreen issues I kept running into appear to be fixed. And apparently my TV wasn't dying as the color is back to normal too.

 

Bunch of errors on 3DMark API Overhead test in the log, mostly myself killing it after hang, but including this one related to NV's driver:

Code:

Faulting application name: 3DMarkApiOverhead.exe, version: 1.4.0.0, time stamp: 0x59a3fb72
Faulting module name: nvwgf2umx.dll_unloaded, version: 23.21.13.8792, time stamp: 0x59d76a9a
Exception code: 0xc0000005
Fault offset: 0x000000000008c3d0
Faulting process id: 0x2bd4
Faulting application start time: 0x01d342bf8c720f4e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\3DMark\dlc\api-overhead-test\bin\x64\3DMarkApiOverhead.exe
Faulting module path: nvwgf2umx.dll
Report Id: 356c5506-257b-4d9d-b986-a461ea8a10d1
Faulting package full name:
Faulting package-relative application ID:

 

4 Black screens in a hour today. just about ready to throw the 1080ti out the window and jump on a Vega 64. It might not be as good but it just works at least.

 

Great drivers, no problems here at all. Clean installed with Windows 10 Creators fall update.

 

Same here but with upgrade to Fall update

 

Yep, same for me, after the directx 12 test.

And ShellExperienceHost crash too with fall creators update, can't open the start menu...

Code:

Nom d’événement du problème :    MoAppHang
Nom complet du module:    Microsoft.Windows.ShellExperienceHost_10.0.16299.15_neutral_neutral_cw5n1h2txyewy
Nom de l’application:    praid:App
Version de l’application:    10.0.16299.15
Horodatage de l’application:    59cda974
Signature de blocage:    ab9b
Type de blocage:    2097152
Version du système:    10.0.16299.2.0.0.256.48
Identificateur de paramètres régionaux:    1036
Signature de blocage supplém. 1:    ab9b89468e42e86e068aa614329a60d9
Signature de blocage supplém. 2:    96db
Signature de blocage supplém. 3:    96dbcac16f8f0eb4dcc89de9c23c6b44
Signature de blocage supplém. 4:    ab9b
Signature de blocage supplém. 5:    ab9b89468e42e86e068aa614329a60d9
Signature de blocage supplém. 6:    96db
Signature de blocage supplém. 7:    96dbcac16f8f0eb4dcc89de9c23c6b44

 

You can send this card my way and get your vega64...lol

 

I ran the overhead test and it froze after the second DX12 test. I got an error for 3DMark, but no driver error.

 

It is freezing at the start of Vulkan part so this is most likely a Vulkan driver/app error. Vulkan samples I have are all working fine, btw.

 

I have Doom installed, and while I have zero stability issues, I have noticed some wild framerate swings in Vulkan. But it's possible it might be level related, and that they have always been there. The Argent Tower is the most CPU intensive area in the game by far, and it's not well optimized in a few parts (especially during the beginning section), even with Vulkan. Although the framerates that Vulkan puts out are far superior to OpenGL to be sure.

 

Not for me, Vulkan in Doom is almost universally slower than OpenGL here, sometimes almost twice as slower.

 

Wow, that's surprising!

As I just posted in the Wolfenstein thread, Tiago Sousa stated on Twitter that an unspecified game (very likely to be Wolfenstein 2) has a 80% compute occupancy rate, which is very high! Doom had about a 40% compute occupancy rate if I recall, so it appears as though Wolfenstein has doubled it. I hope NVidia comes out with some really good Vulkan drivers before Wolfenstein 2 hits, or AMD will surge past them as the game will be hyper optimized for AMD, ie 16 bit floats, HBCC and intrinsic shaders.

Does Doom even support asynchronous compute on Pascal yet?

 

Not really, Doom Vulkan always ran slower than OpenGL in GPU limited conditions on NV.

This has nothing to do with drivers and everything to do with Vulkan renderer optimizations for specific h/w.

No, because id/Sousa hasn't implemented it because... reasons...

Tbf, I've beaten Doom for a second time this year using Vulkan renderer exclusively (just to check how it works on GF cards) and it was definitely absolutely playable and presented no issues whatsoever. Doom is not a very demanding game and it's capped at 200 fps which isn't a lot these days (we have displays with 240 fps refresh now ffs). In fact, it's so undemanding to CPU that I generally fail to see much benefit in porting it to Vulkan - aside from providing an AMD optimized renderer which helps to get around their awful OpenGL driver performance. Hopefully this reason is why they never bothered with proper optimization for NV cards.

 

These drivers appear to have been a bad revision for me. Video glitch not long after install then game crash the following day followed by system crash.

Gone back to the previous ones for now.

 

Speaking for myself, it seems that Doom isn't GPU bound at all. I play at 1440p max settings, and I'm practically always in triple digit framerates. Which is why it can be so jarring when I do experience a framerate drop into even the high 80s, although there is only one small area in the game where this happens.

I don't know man. I remember when Vulkan first became available last year, and running it on NVidia hardware at the time had very little performance increase, but much worse, had lots of stuttering and lag. This was later fixed in a driver update that brought about a massive increase in performance, and got rid of the stuttering entirely. So definitely, drivers can have a large impact even with low level renderers. Also the President of Khronos Group works for NVidia, so if Vulkan has no good NVidia specific optimizations, then NVidia can't blame anyone but themselves because they've doubtless had many opportunities to implement them.

Well the good news in all of this I suppose is that Wolfenstein 2 will support DX12 as well. So it should be VERY interesting to see what API runs faster on either GPU.

 

How does one disable async ?

 

If I'm right, you can't do it yourself, it's done driver side. Not sure if older AMD drivers (for your GPU) even have it enabled.