Log in

View Full Version : AMD, Intel and Nvidia driver issues and last recommended version


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 [45] 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69

kostik
7th December 2020, 19:56
Are you saying the C9 has 119 as an option? That's great then, and even more of a head-scratcher as to why the CX doesn't.

What is this 119 option you talk about? 119Hz?

CX has 119.880Hz option but you can select it on the Advanced Graphics options in Windows Settings on the Dev build (MS added refresh rate selection in display settings few builds ago )

119.880/23.976= 5 (exactly 5)

For movies I guess it is better to select 119.880 over 120Hz

https://imgur.com/BSbO8ES.png

VBB
7th December 2020, 20:21
If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

kostik
7th December 2020, 20:26
If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

Too bad this option is not present in NVIDIA control panel .

VBB
7th December 2020, 20:39
But it's usable regardless, no? Does madVR switch to it?

kostik
7th December 2020, 20:52
But it's usable regardless, no? Does madVR switch to it?

Yes. 119Hz is listed in madVR with Native resolutions only is ticked.

When 120Hz selected, madVR OSD shows Display : 119.99999HZ and decomposition: 120HZ

When 119.880Hz selected madVR OSD shows Display: ~119.8794 and decomposition : 119.758

chros
8th December 2020, 00:32
Nice, thanks, what's the interval for frame drops that madvr reports on the OSD after about 2 minutes?

Asmodian
8th December 2020, 01:52
If you go back a page, Asmodian told us that he doesn't have 119Hz as an option for refresh rate, and that he has to use smooth motion at 120Hz because of this. 119Hz is what you want for proper 23.976 fps playback, yes. Thanks for your screenshot. That's great news then.

Too bad this option is not present in NVIDIA control panel .

Wow, the option is present in Advanced display settings on my CX as well. I wonder why it doesn't show up in the Nvidia control panel. :(

edit;
At 119 I see 119.87880 Hz in madVR, settling down to a estimate of 1 frame repeat every ~2 hours.

huhn
8th December 2020, 02:09
check under SD, HD, UHD.
1080p120 and such are usually placed under PC because they are not broadcast standard TV use. with HDMI 2.1 that's different and the EDID could be different for this too placing them into the default TV timings.

Asmodian
8th December 2020, 02:12
There are only two sections for resolutions in the Nvidia control panel and nothing above 1920x1080 under Ultra HD, HD, SD goes above 60 Hz. It seems like that section is limited to 2.0b resolutions, except it allows 10 bit too so that isn't it.

Just weird I guess. :p

huhn
8th December 2020, 02:39
that's a driver bug then.

i don't have a 2.1 card yet to test it my self sorry.
you could check the EDID and where it is listed to know where it should be listed but that will not tell us why it is not listed in the driver so i don't see much worth in that.

SweetLow
8th December 2020, 08:26
Are you saying the C9 has 119 as an option? That's great then, and even more of a head-scratcher as to why the CX doesn't.
I think CX has too.
P.S. It would be nice if anybody post dumps of CX EDIDs (and I suppose it has options for EDID with and without HDMI 2.1 on).

Asmodian
8th December 2020, 09:47
Yes, the CX has it too. I was fooled by only looking in the Nvidia control panel.

SweetLow
8th December 2020, 10:49
Can you dump CX EDIDs (moninfo or madvr raw edid data)? For my curiosity - i will compare with C9. And I can post decoded info (if someone interested in).

Asmodian
8th December 2020, 11:00
Sure, LG_CX_EDID.bin (http://www.mediafire.com/file/04htbyg096e2jut/LG_CX_EDID.bin/file)

SweetLow
8th December 2020, 19:58
Thanks, but the second part of EDID (high 128 bytes) zeroed :(

kostik
8th December 2020, 20:14
Can you dump CX EDIDs (moninfo or madvr raw edid data)? For my curiosity - i will compare with C9. And I can post decoded info (if someone interested in). @SweetLow


Here is mine:
http://www.mediafire.com/file/0rvwhwdgiof8tuo/OLED65CX.bin/file

This is the EDID of my CX. I just copied from madVR window =\


00 FF FF FF FF FF FF 00 1E 6D C8 C0 01 01 01 01
01 1E 01 03 80 A0 5A 78 0A EE 91 A3 54 4C 99 26
0F 50 54 A1 08 00 31 40 45 40 61 40 71 40 81 80
D1 C0 01 01 01 01 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 40 84 63 00 00 1E 66 21 50 B0 51 00 1B 30
40 70 36 00 40 84 63 00 00 1E 00 00 00 FD 00 18
78 1E FF 77 00 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 47 20 54 56 20 53 53 43 52 0A 20 20 01 AA

02 03 64 F1 5E 61 60 76 75 66 65 DB DA 10 1F 04
13 05 14 03 02 12 20 21 22 15 01 5D 5E 5F 62 63
64 3F 40 2C 09 57 07 15 07 50 57 07 01 67 04 03
6E 03 0C 00 10 00 B8 3C 24 00 80 01 02 03 04 6A
D8 5D C4 01 78 80 53 22 28 78 E2 00 CF E3 05 C0
00 E3 06 0D 01 E2 0F FF EB 01 46 D0 00 2A 1A 03
51 8B 67 73 6F C2 00 A0 A0 A0 55 50 30 20 35 00
40 84 63 00 00 1E 00 00 00 00 00 00 00 00 00 40

Asmodian
8th December 2020, 23:59
Here is my CX from madVR, my second block is pretty different.
00 FF FF FF FF FF FF 00 1E 6D C8 C0 01 01 01 01
01 1E 01 03 80 A0 5A 78 0A EE 91 A3 54 4C 99 26
0F 50 54 A1 08 00 31 40 45 40 61 40 71 40 81 80
D1 C0 01 01 01 01 08 E8 00 30 F2 70 5A 80 B0 58
8A 00 40 84 63 00 00 1E 66 21 50 B0 51 00 1B 30
40 70 36 00 40 84 63 00 00 1E 00 00 00 FD 00 18
78 1E FF 77 00 0A 20 20 20 20 20 20 00 00 00 FC
00 4C 47 20 54 56 20 53 53 43 52 0A 20 20 01 AA

02 03 5B F1 5E 61 60 76 75 66 65 DB DA 10 1F 04
13 05 14 03 02 12 20 21 22 15 01 5D 5E 5F 62 63
64 3F 40 23 09 57 07 6E 03 0C 00 40 00 B8 3C 24
00 80 01 02 03 04 6A D8 5D C4 01 78 80 53 22 28
78 E2 00 CF E3 05 C0 00 E3 06 0D 01 E2 0F FF EB
01 46 D0 00 2A 1A 03 51 8B 67 73 6F C2 00 A0 A0
A0 55 50 30 20 35 00 40 84 63 00 00 1E 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5B

Edit:
I also re-exported from Moninfo and updated the file I linked above, not sure why the second part was zeroed.

SweetLow
9th December 2020, 13:53
Here is mine:

Thanks.
This is decoded info (in parts where moninfo does not decode correctly):


Extension ID: 2 (CE)
Version: 3
Capabilities: F1h

Tag: 2 (Video Data Block)
*See "Supported CE Standard Video Modes"
Hex Dump: 616076756665DBDA101F0413051403021220212215015D5E5F6263643F40

Tag: 1 (Audio Data Block)
Hex Dump: 095707150750570701670403

Tag: 3 (Vendor-Specific Data Block)
Vendor OUI: 000C03 (HDMI 1.x / HDMI LICENSING, LLC)
Hex Dump: 1000B83C24008001020304

Tag: 3 (Vendor-Specific Data Block)
Vendor OUI: C45DD8 (HDMI 2.x / HDMI Forum)
Version: 1
Maximum TMDS Character Rate: 600 MHz
3D OSD Disparity Indication: No
3D Dual View signaling: No
3D Independent View signaling: No
Less than or equal to 340 Mcsc scrambling support: No
Color content bits per component indication: No
Initiating an SCDC Read Request: No
SCDC functionality: Yes
10-bits/component Deep Color 4:2:0 Pixel Encoding: Yes
12-bits/component Deep Color 4:2:0 Pixel Encoding: Yes
16-bits/component Deep Color 4:2:0 Pixel Encoding: No
Max Fixed Rate Link (FRL): 5 (3 and 6 Gbps per lane on 3 lanes, 6, 8 and 10 Gbps on 4 lanes)
FAPA in blanking after first active video line: No
Auto Low-Latency Mode (ALLM): Yes
Fast as Possible V-active (FVA): No
Negative Mvrr values: No
Media rates below VRRmin (CinemaVRR): No
Mdelta: Yes
VRRmin: 40
VRRmax: 120
Hex Dump: 01788053222878

Tag: 7 (Use Extended Tag)
Extended Tag: 00h (Video Capability Data Block)
Hex Dump: CF

Tag: 7 (Use Extended Tag)
Extended Tag: 05h (Colorimetry Data Block)
xvYCC601: No
xvYCC709: No
sYCC601: No
opYCC601(Adobe): No
opRGB(Adobe): No
BT2020cYCC: No
BT2020YCC: Yes
BT2020RGB: Yes
DCI-P3: No
Metadata Profile: 0
Hex Dump: C000

Tag: 7 (Use Extended Tag)
Extended Tag: 06h (HDR Static Metadata Data Block)
Traditional gamma - SDR Luminance Range: Yes
Traditional gamma - HDR Luminance Range: No
SMPTE ST 2084: Yes
Hybrid Log-Gamma (HLG): Yes
Static Metadata Type 1: Yes
Hex Dump: 0D01

Tag: 7 (Use Extended Tag)
Extended Tag: 0Fh (YCbCr 4:2:0 Capability Map Data Block)
*See "Supported CE Standard Video Modes"
Hex Dump: FF

Tag: 7 (Use Extended Tag)
Extended Tag: 01h (Vendor-Specific Video Data Block)
Vendor OUI: 00D046 (DOLBY LABORATORIES, INC.)
Hex Dump: 2A1A03518B6773

Supported CE Standard Video Modes:
61h: 3840x2160p; 59.94Hz/60Hz; 16:9; *YCbCr 4:2:0 Supported
60h: 3840x2160p; 50Hz; 16:9; *YCbCr 4:2:0 Supported
76h: 3840x2160p; 119.88/120Hz; 16:9; *YCbCr 4:2:0 Supported
75h: 3840x2160p; 100Hz; 16:9; *YCbCr 4:2:0 Supported
66h: 4096x2160p; 59.94Hz/60Hz; 256:135; *YCbCr 4:2:0 Supported
65h: 4096x2160p; 50Hz; 256:135; *YCbCr 4:2:0 Supported
DBh: 4096x2160p; 119.88/120Hz; 256:135; *YCbCr 4:2:0 Supported
DAh: 4096x2160p; 100Hz; 256:135; *YCbCr 4:2:0 Supported
10h: 1920x1080p; 59.94Hz/60Hz; 16:9
1Fh: 1920x1080p; 50Hz; 16:9
04h: 1280x720p; 59.94Hz/60Hz; 16:9
13h: 1280x720p; 50Hz; 16:9
05h: 1920x1080i; 59.94Hz/60Hz; 16:9
14h: 1920x1080i; 50Hz; 16:9
03h: 720x480p; 59.94Hz/60Hz; 16:9
02h: 720x480p; 59.94Hz/60Hz; 4:3
12h: 720x576p; 50Hz; 16:9
20h: 1920x1080p; 23.98Hz/24Hz; 16:9
21h: 1920x1080p; 25Hz; 16:9
22h: 1920x1080p; 29.97Hz/30Hz; 16:9
15h: 720(1440)x576i; 50Hz; 4:3
01h: 640x480p; 59.94Hz/60Hz; 4:3
5Dh: 3840x2160p; 23.98Hz/24Hz; 16:9
5Eh: 3840x2160p; 25Hz; 16:9
5Fh: 3840x2160p; 29.97Hz/30Hz; 16:9
62h: 4096x2160p; 23.98Hz/24Hz; 256:135
63h: 4096x2160p; 25Hz; 256:135
64h: 4096x2160p; 29.97Hz/30Hz; 256:135
3Fh: 1920x1080p; 119.88/120Hz; 16:9
40h: 1920x1080p; 100Hz; 16:9


Max Fixed Rate Link (FRL): 5 (40Gbit/s) (48Gbit/s in C9), no DSC, all HDMI 2.1 modes present. Nothing new, i can say :)

my second block is pretty different.

Thanks. Your and kostik's EDIDs are different in audio blocks only. Video parts are equal.

mikahawkins1
9th December 2020, 16:30
I am surprised that I haven't encountered any driver problems so far.

el Filou
9th December 2020, 16:45
Added Background Application Max Frame Rate controlThis is nice, may install this one just to try this.

kostik
9th December 2020, 18:23
This is nice, may install this one just to try this.

The more interesting feature is Color Accuracy Mode:

https://imgur.com/Ou8mAMB.png

VBB
9th December 2020, 19:30
This has been fixed: When setting the refresh rate higher than 100Hz, the color format switches from RGB to
ycbcr422

This as well (wasn't awere of it): [MPC-HC]: The video player crashes when playing 1088 pixel-width videos

Seems to me like the new Color Accuracy Mode is best left at the default Reference.

chros
9th December 2020, 22:01
What about the SDR video is stuck in HDR issue?

VBB
9th December 2020, 22:24
Just close the damn player! ;)

All kidding aside, I doubt this will get fixed, but at least there is a workaround.

chros
9th December 2020, 22:32
And through out the baby with the bath water... :D

VBB
10th December 2020, 09:48
Seems to me like the new Color Accuracy Mode is best left at the default Reference.

Quoting myself here, because Reference is actually not the default. Accuracy is, so I guess we'll have to wait and see what's best here. I forced Reference anyway.

JaylumX
11th December 2020, 05:43
Only just realised that with the 460.79 drivers Nvidia fixed the annoying switching when playing HDR content. Now it is seamless.

VBB
11th December 2020, 08:21
Care to give some more detail? You mean this issue?

What about the SDR video is stuck in HDR issue?

chros
11th December 2020, 09:40
Care to give some more detail? You mean this issue?
So for the 4th time (https://forum.doom9.org/showthread.php?p=1928383#post1928383) :D

VBB
11th December 2020, 19:18
So for the 4th time (https://forum.doom9.org/showthread.php?p=1928383#post1928383) :D

Oh, this wasn't directed at you, sorry. I know the issue, but it wasn't clear what the poster above me (JaylumX) meant.

chros
11th December 2020, 23:44
That's why I was confused since you quoted me :)

JaylumX
12th December 2020, 01:42
Oh, this wasn't directed at you, sorry. I know the issue, but it wasn't clear what the poster above me (JaylumX) meant.

What I meant was that when I used MPC-BE to play HDR content, there would be a display change (1 second black screen) to activate HDR mode, again to go into full screen, then if I change an option in MadVR another 1 second black screen, when I exit fullscreen and finally when I exit the video. This only occurs with NV HDR and not OS HDR (As a temporary fix to limit the amount of 1 second black screen I set MPC-BE to open videos in fullscreen).

It never used to happen with NV HDR until Nvidia posted a fix for MadVR's HDR activation that it broke with a previous driver update.

Now with 460.79 the display changes once and that is it till I exit the video with no 1 second black screen just like it was before Nvidia's driver changes affected MadVR.....nice and simple.

SamuriHL
12th December 2020, 02:04
Latest driver looks good to me. Metadata's correct. No changed behavior from the last couple.

IngramAU
12th December 2020, 04:58
Just close the damn player! ;)

All kidding aside, I doubt this will get fixed, but at least there is a workaround.

Just tried this with Media Portal playing HDR tv show. While playing I hit alt+f4 shut it down back to desktop and... TV still reports HDR is on. So I guess this isn't a fix.

Back to using MPC-HC.

I don't understand this issue, a few weeks ago I never had this problem until I updated Windows to H20 whatever it is and also updated Media Portal.

After alt+f4 to desktop if I open up display settings my screen gets washed out, a quick toggle of HDR on/off puts things back to normal.

Andy o
14th December 2020, 03:15
Anyone with Nvidia getting audio dropouts? I recently just upgraded to a 3070, and both with this new and previous driver, I'm getting dropouts bitstreaming audio, most prominently with TrueHD Dolby Atmos, on CLSID's MPC-HC 64-bit 1.9.8 with both internal LAV 0.74.1.75 and external nightly 0.74.1.92. Rest of my hardware is in my sig. LAV external tried at default settings, except ticking the bitstreaming checkboxes, and switching to DXVA2 (to avoid presentation glitches, but dropouts don't improve when switching video decoders anyway).

A bit more info, I was using a GTX 1650 Super previously, without issues. eARC into the LX503. Also I'm running 119.88 Hz 12-bit into the C9, but I also tried switching to 8-bit, like it was with the 1650 and there's still dropouts. I've tried the CableMatters 48Gbps (not certified) and now I'm using the Zeskit 3m 48Gbps certified cable, with the same results.

Edit: Intel i7-4770, Gigabyte GA-Z87MX-D3H, RTX 3070, Win 10 64

SamuriHL
14th December 2020, 03:21
Is this in MKV's? Or directly playing discs? Because MKV ATMOS issues are well documented and is a ripping problem.

VBB
14th December 2020, 04:01
@Andy o - Can't say I've ever had audio dropouts. Not with MKVs, not with Atmos or any other format. Is the audio renderer set to internal? Do you have exclusive/bitstream ticked?

One weird issue I've now encountered twice very recently is that out of the blue channels will get reassigned. Voices will suddenly come out of the rear speakers, for example. At first, I thought it was mixed like that. I was watching an episode of Westworld at the time. Then last night it happened with The Desolation of Smaug. Pausing and resuming made the channels go back to normal.

Andy o
14th December 2020, 06:01
I'm also seeing it in the m2ts of the same content, and in other content as well. I was getting very subtle pops in DD+ content also. I do have the renderer set to internal, and to bitstream/exclusive. You just reminded me about it so I also just tested with not using the internal renderer, only directly to the Nvidia device, with the same results. It's been a bit of a hassle to test though, a couple of times I think I had it solved (like at first for some reason it was giving me dropouts almost in sync with the presentation glitches and switching to DXVA2 seemed to get rid of both, but the dropouts came back later).

Now I've disconnected the HTC Vive Cosmos from the DisplayPort and it seems OK, but it doesn't make sense that it would be it cause IIRC I was getting dropouts before I even installed it as well.

But in any case I'm glad to hear it's not widespread and I'm in the process of upgrading the whole rig anyway, just waitin for those damn 5900x to be in stock again.

clsid
14th December 2020, 16:27
Change the Power management mode to "Adaptive" in NVIDIA settings.

That helps solve video rendering glitches, but sometimes also issues with audio dropouts.

Andy o
15th December 2020, 00:02
I don't have "adaptive" as an option, just "normal" and "prefer maximum performance", it was already set to "normal".

clsid
15th December 2020, 00:26
Does anyone know is which driver version they replaced Optimal/Adaptive choices with Normal choice?

Manni
15th December 2020, 00:50
Does anyone know is which driver version they replaced Optimal/Adaptive choices with Normal choice?

It might be more complex than that. I still have optimal as a choice with the latest in a 3090.

Asmodian
15th December 2020, 00:53
Weird. I have only Normal/Prefer maximum performance with a 3090 and 460.79. I think it was the previous version that changed it.

VBB
15th December 2020, 00:57
I haven't even noticed that change in the latest driver, because it's been fine to leave it at the default for a while now. That default used to be "optimal", and I guess it's now "normal".

Manni
15th December 2020, 00:58
Weird. I have only Normal/Prefer maximum performance with a 3090 and 460.79. I think it was the previous version that changed it.

My apologies, I didn’t test that one if it’s such a recent change. Looks like I’m a couple versions behind, or didn’t check that option recently enough.

SamuriHL
15th December 2020, 01:21
I'm with VBB, since the past I don't know 5 or so drivers I've not changed that setting, either. I didn't even go look. Leaving it set to what is it now, "normal"?, should be fine. In theory.

Asmodian
15th December 2020, 01:29
I hope that is the case. I certainly wouldn't want to use prefer maximum performance all the time. Normal does seem to be working well for me.

Andy o
15th December 2020, 01:58
I'm experimenting with this setting, but it's still super annoying to test. I forced "normal" in mpc-hc.exe and it seemed to work... for a while. I also tried with max performance and it also seemed to work, but it was consuming around 20W extra at the wall which I'd like to avoid if possible.

This whole thing reminds me a long long time ago in the HTPC infancy some ATI drivers were causing popups and it was because of the clocks jumping up and down. When DXVA was engaged it was supposed to fix the clocks to a low-ish setting, but it wasn't doing it, so it had to be done manually by editing some obscure text file.

VBB
15th December 2020, 19:51
Thanks GTPVHD. This time around they listed this as an open issue:

[HDR]: With HDR enabled, black levels are incorrect. [200682795]

A lot of people, mostly gamers, have been reporting this, although I have not encountered it myself. I think this only applies to those who use the Windows HDR switch.

VBB
19th December 2020, 02:41
GeForce Hotfix Driver Version 460.97

https://nvidia.custhelp.com/app/answers/detail/a_id/5145

Fixed: With HDR enabled, black levels are incorrect. [200682795]