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

IngramAU
25th January 2022, 01:13
I give up on fixing my bitstreaming audio issues. I'm getting drops in audio less frequently now but it's happening on DD+ Stereo files not just Atmos files. PCM from here on out.

mclingo
25th January 2022, 23:55
i found audio drops using copy back d3d11 with mpcbe, you tried a different decoder?

EpsilonX
27th January 2022, 07:40
Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the
standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm
whites.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video
bugs .These are there since RX 5000 series launch.

Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

mclingo
27th January 2022, 19:44
Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

doubt it still broken on 5700 series

Klaus1189
28th January 2022, 11:35
Color levels (full 0-255 vs. limited 16-235) are broken. That means limited 16-235 which is the
standard range for videos are interpreted as 0-255 and this leads to elevated blacks and dimm
whites.
This issue can be best seen on displays which want full range 0-255, like TVs in PC Mode (PC
mode for full 4:4:4/RGB support, so you do not use color subsampling like 4:2:2 or 4:2:0)
Also overriding the range for test purposes in MPC-BE (video tab -> Output range) does not
take effect.
Dear AMD, if any of your driver programmers read this: Please fix this fundamental video
bugs .These are there since RX 5000 series launch.

Have AMD fix this in the latest driver for the 6000 series card..?
Thank you

doubt it still broken on 5700 series

Can users who have a RX 5000 / RX 6000 card please test this?
I sold my RX 5700 XT, so I can't test anymore.

mclingo
28th January 2022, 11:58
I guess a sample of 1 (me) is not representative of everyone but its highly unlikely anyone's is fixed if mine isnt, AMD are useless at fixing movie playback bugs, it is also only present in some renderers, I dont see it in MADVR, only MPC HC / BE using EVR, but i'm not using PC mode on my TV as use TRUMOTION which is disabled in PC mode on my LG OLED.

EpsilonX
28th January 2022, 12:23
IIRC. Nvidia used to have this kinda problem with color range with HDMI right..?
Though it can be 'fixed' by the user through registry.
For me personally, I can live with the deinterlacing problem...
But my PC is always connected to my TV (PC Mode RGB of course), to watch movies (MPC-HC + MadVR), YT from bed when I'm lazy... :D
So this 'simple' bug is very annoying.

QBhd
28th January 2022, 13:45
I have no idea what this "problem" is. I have had flawless playback on my 5700XT for well over a year.

QB

mclingo
28th January 2022, 16:07
if you play an SDR movie in MPC-BE or HC using the !!! EVR renderer !!! the wrong colour space it output so you have to add a filter to switch it between 16/235 / 0-255 - no issues on HDR.

If you dont use this renderer you'll never see the issue, I only use it for previewing videos, I do all my playback using MADVR and KODI-DS

QBhd
28th January 2022, 16:39
So why do you think it is an AMD driver issue? Sounds like an MPC to me.

QB

huhn
28th January 2022, 18:53
because normal EVR is part of windows and the problem is also present with windows media player.

AMD also has a problem that there presets are forced on all the time there is no off option. you can move a small piece in fort of it liek a windows explorer as long as you didn't release the left mouse button it uses no image corrupting stuff.

https://abload.de/img/amdcijpo.png
these are all options.

hdr has wrong ranges since the release of windows 11 (it was fine in the beta) even even computer games using AGS are totally messed up.

Snowknight26
29th January 2022, 02:31
Can users who have a RX 5000 / RX 6000 card please test this?
I sold my RX 5700 XT, so I can't test anymore.

Seems to be fixed with an RX 6800 XT running 22.1.2.

Tested with a limited-range H.264 video, MPC-HC using EVR-CP. Forcing the output range to 0-255 (right click video -> Renderer Settings -> Output Range -> 0-255) results in washed out colors, while setting forcing the output range to 16-235 results in correct colors (matching madVR).

If you consider forcing the output range to be a fix, then yes it's fixed.

clsid
29th January 2022, 02:53
Does your monitor/tv expect limited range input?
Have you configured madvr to also output limited range?

huhn
29th January 2022, 11:09
i did a test on win 11 so don't take these findings seriously there are massive issues with win 11 and AMD.

D3D11 processing is using correct ranges (i didn't test P010).
you can make it use bob deint if d3d11 processing is active else it'S not doing it. scaling with deint at the same time is NN.

DXVA processing is still using wrong ranges.
Deint is now even more broken it's simply not done at all.
also i got this the first time in my life: https://abload.de/img/wowifk06.png
don't worry that error crashed and got stuck there.

clsid
29th January 2022, 13:11
What do you mean with the error got stuck? Were you unable to click on the message box buttons?

Can you also test with a HDR video? So people are having driver crash issues with D3D11 rendering + HDR with the AMD 21.12.x/22.1.1 drivers. I am not sure if it also requires HDR passthrough to trigger.

huhn
29th January 2022, 14:02
no sorry i can't test HDR anymore with the new AMD driver.
it was buggy but still working with the last driver but with this one it doesn't enter HDR at all and games are so messed up there are no word for it.

HDR to sdr with mpcVR works here.

it got completely endless loading mouse icon nothing was clickable.
this is not the newest mpc-hc version (i still have desktop for subtitle resolution) and i'm on the dev build for win 11 which stops shutting down because it can't close the taskmgmt.

after killing it in the taskmgmt it was running's a windows error report without asking me. i would not be shocked that this was the reason it got stuck in the first place.
so don't think to much about it. on the last dev build i got like a 100 TPM errors... it's just not a stable system.

Snowknight26
29th January 2022, 16:49
Does your monitor/tv expect limited range input?
Have you configured madvr to also output limited range?

It's a monitor so 0-255 naturally. madVR was configured so that the monitor was set to expect 0-255. Changing the monitor to expect 16-235 resulted in washed out colors.

clsid
29th January 2022, 17:18
Then setting 16-235 for EVR is wrong, and there obviously is a bug in the driver.

Klaus1189
1st February 2022, 20:41
511.65 has new new HD Audio Driver (https://drive.google.com/file/d/1RCwl6XTxhcsbxv18IX89ejZJilo28IH4/view?usp=sharing)

kostik
1st February 2022, 21:37
511.65 has new new HD Audio Driver (https://drive.google.com/file/d/1RCwl6XTxhcsbxv18IX89ejZJilo28IH4/view?usp=sharing)

but still has this issue:

[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos. [3345965]

v0lt
10th February 2022, 04:42
The driver for Intel UHD 770 (30.0.101.1191) has different behavior depending on the name of the executable file. (https://sourceforge.net/p/mpcbe/tickets/912/)

Aleksoid1978
10th February 2022, 06:08
The driver for Intel UHD 770 (30.0.101.1191) has different behavior depending on the name of the executable file. (https://sourceforge.net/p/mpcbe/tickets/912/)

Intel 30.0.101.1340 - the same issue, Intel UHD 730.

huhn
10th February 2022, 15:52
maybe you should ask the user with the problem if 1340 fixes the issue.
this is the biggest "bug" i have seen in a while...

v0lt
10th February 2022, 18:25
maybe you should ask the user with the problem if 1340 fixes the issue.
this is the biggest "bug" i have seen in a while...
30.0.101.1340 does not solve the problem.

DinaMoe
16th February 2022, 20:43
Very late to the party. Just getting up to speed with regard to Nvidia drivers not passing through HDR correctly.

Has that been fixed with any of the 500.00 WHQL drivers?

SamuriHL
16th February 2022, 21:26
What's the issue with pass through on HDR? I just today finished my new HTPC build with a 3080 and I've got a VRROOM so I can validate anything you want. I'm using the very latest drivers.

DinaMoe
16th February 2022, 22:04
@SamuriHL: Maybe there isn't a problem anymore. You would know better than I.

SamuriHL
16th February 2022, 22:51
Seems to work just fine for me. Not really sure. It doesn't work for me on my laptop with my 2080 but who knows why that is.

nevcairiel
17th February 2022, 09:23
I use HDR pass-through every day, and its fine. I also verified metadata with HDFury Arcana. Granted though, I don't use madVR for it.

DMU
17th February 2022, 11:02
Granted though, I don't use madVR for it.
What renderer are you using for this?

SamuriHL
17th February 2022, 13:08
He's using his own. Lol jrvr. I've tested both jrvr and madvr with the vrroom and everything is working as expected on the latest drivers.

Sent from my SM-G998U1 using Tapatalk

Polopretress
2nd March 2022, 15:14
Hello.

I see some user of 6800XT.
On my side, already 2 people using this GPU have seen their rendering time increased a lot compared to their previous GPU.
One has previoulsly a Vega64 and the other had a GTX1080.

Normally, rendering time should be highly below the previous boards and we cannot find a solution so far to explain the issue and i suppose that most of users have no issue.
So, i post to ask if there is a known tip about that to fix this problem before to send back the GPU. (some settings inside the driver configuration ?)

Than you very much.
For information, i have provided some specific settings.bin of madvr and video to test and compare the rendering time and we confirm the problem.
GPU Benchmark test are OK (no problem highlighted) - scan with GPU-Z are correct.
Their driver software are updated.
The PCHCs use standard software such as Lav filters 0.76, MPC-BE, MadVR 0.92.17 with and without the beta 157. One is in 32 bits configuration, the other is full 64 bits (same result)

I am really at the end of investigation to understand/identify the issue...

Klaus1189
2nd March 2022, 17:34
@Polopretress:
Welcome in my thread :)
Can you test something for me? I am interested in hardware capabilities of Vega64 and RX6800XT.
So please just do the following:
Make sure you have a TV in pc mode which wants 0-255 and play a video in MPC-BE or also MPC-HC and check the black levels. Are the blacks elevated or black as it should be. In MPC-BE, probably also in MPC-HC there is an option in "Video" Tab in options which lets you override the output range. Does this setting make a difference if you choose 0-255 and then 16-235?

For the deinterlacer test you need to download:
https://drive.google.com/file/d/1Zs2T4-Nlu-16H0aCBWWxLn5pTVK4ftwV/view?usp=sharing
Play it and check the charakters above "www.D88.com" for flickering:
https://drive.google.com/file/d/1Sq5aspz8ikCTZdBKcUV4h27kLzgufgoN/view?usp=sharing
Flickering like here:
https://de.wikipedia.org/wiki/Datei:Indian_Head_interlace.gif
If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.
Disable Software deinterlacing in LAV Filters, if it is enabled.

Since you know someone who has a Vega64, would you mind to ask him/her to test this with the Vega64, too.

That would help me a lot ;)

If a Radeon VII user is reading this, please test this also for me and let me know the results.

Polopretress
2nd March 2022, 18:11
I will ask since it is 2 contact of me (on my side i have still a GTX1080) and i think one of the both has already returned RX6800XT for a RTX2080TI...

i have another contact who has still a Vega64 and i am sure at nearly 100% that he is connected to the VP (Epson EH-LS10500) in RGB 0-255 and it works fine for him.(in SDR FullHD or UHD HDR with DTM output in SDR)
I will confirm with him as well. Is it necessary to have a TV instead of a VP ? because sure , he will not be possible for him to test with a TV since he has no TV in its HC room.
For deinterlaced video, i think he use lav filters software such as Yadiff.

Polopretress
3rd March 2022, 00:40
@Klaus1189

Find below the answer of my contact who has a Vega64

I am playing MPC-BE + LAV 0.76.0 + madVR 0.92.17 .
My HTPC is connected to Denon AVR-X4300 then to Epson EH-LS10500.

1/ My video stream is in RGB 4:4:4 10bit 0-255.
I have perfect blacks and whites.
If I switch madVR from 0-255 to 16-235 (Devices/Properties), then it does what is supposed to happen : Blacks are lifted, and whites dimmed.
In the "video tab" of Options in MPC-BE, Output Range is greyed using madVR (only available for VMR-9 and EVR-CP).

2/ I did the deinterlacer test :
I normaly do not use hardware acceleration in my process.
I use software YADIF deinterlacement of LAV decoder. No flicker.
If I select "no software deinterlacing", there is a strong comb effect, but still no flicker at all on the chinese sponsor (camera does not move).
I cannot use HW/GPU deinterlacing whatever is selected in HW acceleration. It's always greyed, and seems to work only for "(CUVID/QS only)".

Hope that can help.

Klaus1189
3rd March 2022, 18:06
@Klaus1189

Find below the answer of my contact who has a Vega64
I am playing MPC-BE + LAV 0.76.0 + madVR 0.92.17 .
My HTPC is connected to Denon AVR-X4300 then to Epson EH-LS10500.

1/ My video stream is in RGB 4:4:4 10bit 0-255.
I have perfect blacks and whites.
If I switch madVR from 0-255 to 16-235 (Devices/Properties), then it does what is supposed to happen : Blacks are lifted, and whites dimmed.
In the "video tab" of Options in MPC-BE, Output Range is greyed using madVR (only available for VMR-9 and EVR-CP).

2/ I did the deinterlacer test :
I normaly do not use hardware acceleration in my process.
I use software YADIF deinterlacement of LAV decoder. No flicker.
If I select "no software deinterlacing", there is a strong comb effect, but still no flicker at all on the chinese sponsor (camera does not move).
I cannot use HW/GPU deinterlacing whatever is selected in HW acceleration. It's always greyed, and seems to work only for "(CUVID/QS only)".

Hope that can help.



1. That is good to know
2. That is impossible. If for this special MBAFF file YADIF is truely active, it will flicker, because YADIF is not frame adaptive. That is the hole point of this test.
Only the Hardware deinterlacer is frame adaptive, at least should be, not on RX 5000 series, but it possible AMD has changed something, but I sold my crap 5700XT for good money :) and got a 3090 before high prices (still much lower price than as of this week) and can't test it anymore.
Could you please tell him/her to set LAV Filters Software deinterlacer to none and as I already pointed out:
@Polopretress:
If you use LAV Filters use DXVA2 copyback, but not D3D11 for deinterlaing test.
Disable Software deinterlacing in LAV Filters, if it is enabled.
This is important for this test!

He/She should also test with Hardware acceleration enabled and disabled. I doubt is will make a difference, but we test here, so I need input :)

Please also add both testes with the RX 6800XT. I really need that info. ;)

ryrynz
4th March 2022, 05:26
Please also add both testes with the RX 6800XT. I really need that info. ;)

[emoji6]

Snowknight26
5th March 2022, 07:00
Results haven't changed since early 2021 (https://forum.doom9.org/showthread.php?p=1936390#post1936390).

Klaus1189
5th March 2022, 08:25
I was expecting a change after a year.

Klaus1189
5th March 2022, 09:08
I was hoping for fix, because it is not so long to the next generation of AMD cards, not the RX 6000 refresh but the next generation. What if they are ignoring basic video stuff again, for the third time?

RX 5000 is not fixed either, right? That would be a miracle.

mclingo
8th March 2022, 18:02
amd users could so with spamming the AMD forums with both faults, i'm going to log it myself today just to see what they come back with, i havent logged anything for ages on there as nothing every happens, plus I dont notice either problem as I dont have any interlaced videos and I dont use PC mode on my TV as I use all motion processing if I do.

CZ Eddie
11th March 2022, 07:35
I'm replacing my 2060 Super with a 3080 tomorrow.
Looks like they both use the same driver download from Nvidia.
Do you guys think it's necessary to do a clean uninstall and reinstall of the driver after the swap?

Also, has Nvidia really gone three months without a driver update?
This is the most recent I'm finding:

Version: 472.84 Studio Driver
Release Date: 2021.12.13

huhn
11th March 2022, 09:10
no. you are clearly no trying hard enough.
https://www.nvidia.com/Download/driverResults.aspx/187098/en-us

it's never necessary to do a clean install but always recommended.

btw pretty much all nvidia GPU use the same driver.

ryrynz
11th March 2022, 11:18
Sometimes necessary, would do it for a major driver update or changing cards. Lots of issues can be fixed by a proper clean install
which involves usually removing the driver using ddu first. Even nVidia recommended this to my brother and it fixed his gaming issues.

clsid
11th March 2022, 14:14
Yes, always use Display Driver Uninstaller (DDU) when swapping GPUs.

CZ Eddie
11th March 2022, 15:00
Thanks, guys. I'll use the DDU just in case.
no. you are clearly no trying hard enough.
hahahah

Wow, okay the Nvidia "advanced driver search" page sucks.
https://i.ibb.co/pdTydJx/Untitled.jpg

Klaus1189
11th March 2022, 16:40
Please upload your picture to google drive or similar, otherwise it will take some days till we can watch it.

CZ Eddie
12th March 2022, 04:01
Hah, and now it's too big.

Klaus1189
12th March 2022, 06:36
Only post the link here of google drive and we can open it in a new tab.

SamuriHL
23rd March 2022, 00:56
People might want to look at the issues list on this one. Specifically this:

[NVIDIA Ampere GPU]: With the GPU connected to an HDMI 2.1 audio/video receiver, audio may drop out when playing back Dolby Atmos. [3345965]

That seems, you know, bad.