NVIDIA GeForce 511.23 WHQL driver download & Discussion

FH5 has had such a rough launch that PG had to quickly do a PR by *basically* saying: "this time, it is not our fault for these issues, seriously!"

 

Odd, I don't have a problem at all. The game has been running fine for me since early access, no crashes even with this driver. Except one glitch at a certain danger sign with a light blue metallic Shelby Cobra where a big blue square would appear underneath the car in the air (which also happened on Xbox Series X), the game has been smooth driving on both my PC and the Series X so far. I guess the crash bug with this driver must be limited to certain hardware configurations.

 

It happened to me with the Jesko (color change) and some other cars, but not with all.

 

Can you share an example/screenshot? In which game/app?

 

Some 1440p monitors advertise support for 4K 60Hz and the driver is detecting this as the native resolution. The driver is scaling based on this resolution. We are working on a fix but I don't have an ETA.

 

This will be fixed in our next driver update.

 

I do not believe that as normal seems like it is trying to be way more efficient in games than adaptive ever was. Adaptive would always find the proper clockspeed needed in games but normal just craps itself sometimes letting the gpu go to 99% at some silly low clockspeed instead of properly ramping up when needed. For instance it may drop to 1200 mhz or even 900 mhz and then go to 99% and then stutter as it did not keep the 60 fps with vsync on before it could ramp up the clockspeeds. Hell some games I can just flick the mouse around fast and drop fps below 60 as normal power cant always properly adjust the clockspeeds on the fly. I have several games now where I have had to go in change to maximum so the game will run properly the whole time. I wish they would just bring adaptive back as that worked great on the previous cards.

 

Which Call of Duty game?

 

GPU monitoring utilities should always be closed when updating display drivers.

 

Can you give me steps to reproduce?

 

so all i need to do is edit this with a 0 over regedit using the latest driver?

 

Hmn, I seem to get random weird lines/artifacts on the horizon/water in Far Cry 6 with Windows 10 21H2.
Also in Mass Effect Legendary Edition. Without any OC.

 

Can you email me screenshots of your in game graphics settings used in Mass Effect Legendary Edition so we can look into this? We already have an open bug for Far Cry 6 in the open issues list of the release notes.

 

Windows 11 22000.438 (x64) , nVidia 511.23 , madVR 0.92.17 (x64), MPC-HC 1.9.18 (x64)
Gigabyte RTX 3080 (10Gb) WaterForce WB (RBar BIOS) + LG 55C9 (05.20.07) on HDMI 2.1 port + Denon AVR 2809 (with a DVI monitor hooked to it's HDMI 1.3 output via passive adapter) on an HDMI 2.0 VGA port
Display output mode set to 12 bit RGB (Full range) in NVCP for the LG C9, left at default (8bit Full RGB) for the AVR+monitor.
The Windows desktop is normally in 2160p120 SDR with G-Sync (full+windowed) but madVR auto-switches to 2160p24 for movie playback (where G-Sync disengages because 24 is outside of the 40-120 range).
When maVR goes into fullscreen mode (actually borderless windowed because exclusive fullscreen is not enabled for madVR since it's no longer available in modern Window) the diagnostic OSD (CTRL+J) queries the display mode as 2160p24 12 bit Full RGB (and also NVAPI HDR mode where applicable) but it's output mode remains 8 bit (both for SDR and HDR10).
The expected behavior is madVR's output being 10 bit (both for 8 and 10 bit videos) and a stutter-free playback.
With the last few previous drivers (and one Win11 patch before the current), 511.xx the output was correctly 10 bit but the playback stuttered. This stuttering stopped when I brought on the seek-bar and thus madVR dropped out of fullscreen mode and switched back to 8 bit output mode (stuttering returned when the seek-bar disappeared and madVR switched back to 10 bit mode).
With even older drivers (and also some Win10 patches before the current one), pre-49x.xx everything was fine (correctly 10 bit output without any stuttering).
This also affects 2160p25 (UK content), not just 2160p24 (US content), both H264 SDR FHD and H265 UHD HDR10 formats.
I didn't try to downgrade to significantly older (pre-49x.xx) drivers and didn't try to uninstall Win11 updates. But everything was fine a few months ago and I had no hardware changes (not even UEFI Setup or VGA card OC changes).
The video decoder is set to DXVA11 (native). Audio is decoded on the CPU and sent out as LPCM 7.1 24/96 (no Atmos) to the HDMI 1.3 AVR.

Edit: A screenshot of the madVR diagnostic OSD:

 

Getting crashes to desktop running 2042 with patch 3.2. No errors are shown but game randomly and fairly frequently freezes and closes itself. It's probably the 2042 patch and not these 511.23 drivers.

 

Haven't posted here for a long time,

Gigabyte RTX3070
Updated to 511.23 from 497.29. Clean install

No noticeable problems on 497.29 , now experiencing random hard freeze lockup then reboot when watching videos or browsing in Firefox 96.0.1 and 96.0.2.

Not sure if other applications affected yet.


Here is the analyses of the Crash Memory Dump

EXCEPTION_RECORD: fffffe069a50eb68 -- (.exr 0xfffffe069a50eb68)
ExceptionAddress: fffff8057416c78e (nvlddmkm+0x0000000000b1c78e)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: 0000000000000138
Attempt to read from address 0000000000000138

CONTEXT: fffffe069a50e3a0 -- (.cxr 0xfffffe069a50e3a0)
rax=0000000000000000 rbx=ffff8a8a745af500 rcx=ffff8a8a7d590730
rdx=0000000000000001 rsi=0000000000000000 rdi=ffff8a8a745aebf8
rip=fffff8057416c78e rsp=fffffe069a50eda0 rbp=fffffe069a50eea0
r8=0000000000000000 r9=0000000000000000 r10=ffff8a8a745aed18
r11=ffff8a8a745aebf8 r12=ffff8a8a745a9000 r13=ffff8a8a745aec00
r14=0000000000000008 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050286
nvlddmkm+0xb1c78e:
fffff805`7416c78e ff9038010000 call qword ptr [rax+138h] ds:002b:00000000`00000138=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME: System

READ_ADDRESS: 0000000000000138

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: 0000000000000138

EXCEPTION_STR: 0xc0000005

STACK_TEXT:
fffffe06`9a50eda0 fffff805`742688be : ffff8a8a`745af500 fffffe06`9a50ef40 ffff8a8a`745a9000 ffff8a8a`71b64000 : nvlddmkm+0xb1c78e
fffffe06`9a50ef10 fffff805`7416a9b3 : ffff8a8a`42c80000 00000000`00006100 ffff8a8a`00000000 ffff8a8a`745a9000 : nvlddmkm+0xc188be
fffffe06`9a50ef80 fffff805`7416a8a0 : ffff8a8a`745a9000 ffff8a8a`00006100 ffff8a8a`74587000 fffffe06`9a50f030 : nvlddmkm+0xb1a9b3
fffffe06`9a50eff0 fffff805`743a58e4 : ffff8a8a`74587000 fffffe06`9a50f159 ffff8a8a`74587000 fffffe06`9a50f159 : nvlddmkm+0xb1a8a0
fffffe06`9a50f0e0 fffff805`6ec58a7a : fffffe06`9a50f2a0 00000000`00000000 fffff805`743a5861 fffff805`6ec34772 : nvlddmkm+0xd558e4
fffffe06`9a50f1c0 fffff805`6ec59040 : 00000000`00000000 01000000`00100000 3fbcb2f0`3c800018 00000000`00000000 : dxgkrnl!DpiDxgkDdiSetTargetAdjustedColorimetry2+0xae
fffffe06`9a50f270 fffff805`6eded58a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!DpiSetTargetAdjustedColorimetry2+0x70
fffffe06`9a50f2f0 fffff805`6ed88cf1 : ffff8a8a`725dba60 ffff8a8a`00000267 ffffae06`33ad3b00 00000000`0000009a : dxgkrnl!DXGMONITOR::_SendAdjustedHDRParamsToDriver+0x84bb6
fffffe06`9a50f3a0 fffff805`6ed86ec0 : ffff8a8a`00000000 fffffe06`9a50f958 00000000`00000002 ffff8a8a`725dba60 : dxgkrnl!DXGMONITOR::_UpdateEDIDBaseBlock+0x17d
fffffe06`9a50f420 fffff805`6ed8b609 : ffff8a8a`725dba60 ffff8a8a`743aa9a0 ffff8a8a`725dba60 00000000`00000005 : dxgkrnl!DXGMONITOR::_InitializeMonitor+0xf4
fffffe06`9a50f4b0 fffff805`6ed8b374 : 00000000`00000000 fffffe06`9a50f568 00000000`00000000 ffff8a8a`7462b000 : dxgkrnl!MONITOR_MGR::_CreatePhysicalMonitor+0x10d
fffffe06`9a50f520 fffff805`6ed8b1a8 : 00000000`00000000 ffffae06`2dcd8740 ffff8a8a`78c909e0 00000000`00000000 : dxgkrnl!MONITOR_MGR::_HandleCreatePhysicalMonitor+0xf8
fffffe06`9a50f5b0 fffff805`6ed757cb : ffff8a8a`73f44db0 00000000`00000001 00000000`00000001 00000000`00000000 : dxgkrnl!MonitorCreatePhysicalMonitor+0xb8
fffffe06`9a50f640 fffff805`6ed7529b : ffff8a8a`74420030 00000000`00000001 ffffae06`2dcd8740 ffff8a8a`74420180 : dxgkrnl!DpiPdoAddPdo+0x4af
fffffe06`9a50f6e0 fffff805`6ec2072d : ffff8a8a`73f44db0 ffff8a8a`74420180 fffffe06`9a50f9c0 ffff8a8a`74420180 : dxgkrnl!DpiPdoHandleChildConnectionChange+0xf3
fffffe06`9a50f8c0 fffff805`6eec6056 : ffff8a8a`74420030 ffff8a8a`74420e68 ffff8a8a`74420180 ffff8a8a`74420e68 : dxgkrnl!DxgkQueryConnectionChanges+0x67d
fffffe06`9a50fa80 fffff805`61474783 : ffff8a8a`7c19b7f0 ffff8a8a`74420030 ffff8a8a`7e332040 fffff805`6eec5ed0 : dxgkrnl!DpiIndicateConnectorChangeWorkItem+0x186
fffffe06`9a50fac0 fffff805`614b8655 : ffff8a8a`7e45d040 ffff8a8a`7e45d040 fffff805`614746f0 00000000`00000000 : nt!IopProcessWorkItem+0x93
fffffe06`9a50fb30 fffff805`61555995 : ffff8a8a`7e45d040 00000000`00000080 ffff8a8a`6a29d040 00000000`00000001 : nt!ExpWorkerThread+0x105
fffffe06`9a50fbd0 fffff805`615fe938 : ffffdb01`5f103180 ffff8a8a`7e45d040 fffff805`61555940 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe06`9a50fc20 00000000`00000000 : fffffe06`9a510000 fffffe06`9a509000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME: nvlddmkm+b1c78e

MODULE_NAME: nvlddmkm

IMAGE_NAME: nvlddmkm.sys

STACK_COMMAND: .cxr 0xfffffe069a50e3a0 ; kb

BUCKET_ID_FUNC_OFFSET: b1c78e

FAILURE_BUCKET_ID: AV_nvlddmkm!unknown_function

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {7eea5677-f68d-2154-717e-887e07e55cd3}

Followup: MachineOwner

 

@ManuelG - this driver update included "day 1 support for Hitman III Year 2."

What exactly does that mean? Nothing has changed in the game visually in the Year 2 update. No new graphical features like ray tracing or DLSS have been added.

 

They could still have tweaked the engine (rewrote some shaders or made changes to the rendering pipeline, etc). I think it's nice if the driver keeps up with game updates (however small the changes are).

 

It's possible, but nothing about it was mentioned in the patch notes.

I thought maybe IOI would have added DLSS in this update at least.

 

Anyone playing the latest GOD of WAR game on pc...

holy god damn i cant seems to stop this game from stuttering like crazy when entering new area`s or just running about randomly ....

latest drivers
5950x
x570 meggodlike
32gb tuned memory
3090 24gb

whats the problem lol and the game is installed to a SSD.