AMD, Intel and Nvidia driver issues and last recommended version

[Calvi]

Yes, was not consistent for me either, seems ok after a reboot.
Am staying in 525.25 for now though as lots of other bugs in newer drivers being reported and I have no issues with this driver on a 2070.

[Klaus1189]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

[Ejziponken]

After a few hours, playing games and browsing, the issue is back when I start a movie...

[Ejziponken]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

I had the issue since the last two nvidia updates and I might have skipped one between those (im not sure). But yes I did multiple restarts since the installs and the issue comes back.

[Klaus1189]

Already tried DDU? What card do you have? Perhaps an issue of a single generation like Ampere, Pascal, ...

But if it goes away and comes back, that is not good. I also played games before testing, but no issue here.

[Calvi]

Which bugs? Should I include them?

Did you both a restart right after driver installation? Or later which fixed it then?

526.47:
Desktop Window Manager (dwm.exe) service may report higher GPU usage on some RTX 30- series configurations [3830387]
Workaround: disable Hardware-accelerated GPU Scheduling from the Windows Settings

Lots of people/gamers in the reddit thread with the above and stability issues that go away when rolling back to 525.25

526.98
Is not detecting 3060Ti cards.

You can include these if you wish.

I always install after DDU in safe mode so always a restart as well.

I’ll wait for the next release that’s more stable, I have a 2070 anyway so unless there’s any improvement related to video or windows 11 etc, no point me upgrading for new cards and games.

[Klaus1189]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?
I ask because with madVR (latest stable 0.92.17) the image looks washed out despite the display showing HDR OSD info and madVR NV HDR in statistics.

When using MPC-VR the colors look OK, so is this a driver issue or a madVR issue? Or combination of both. Should I update to a newer madVR version to test? If yes, which one?

[Calvi]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?


In my case the display did not show it was receiving HDR metadata and it was not, as the colours were washed out. I can tell easily anyway as the OSD on zoomplayer goes funky colours when in HDR mode.
If I force HDR in windows then it works again , but it’s forced so does not work for SDR, so no good esp when it worked automatically and faultlessly before.

It switched many times and then stopped at some point while I was showing someone HDR vs SDR demo’s.
525.25 and all earlier drivers do not do this for me.

Of course it could be MadVR, but MadVR and nvidia drivers have worked seamlessly since version 456.38 so I would say highly unlikely.

[Ejziponken]

OK, thanks for feedback. I add this asap.

I did some more tests. So your issue is that the display does not show that it is receiving HDR metadata (no HDR notification on display OSD)?
I ask because with madVR (latest stable 0.92.17) the image looks washed out despite the display showing HDR OSD info and madVR NV HDR in statistics.

When using MPC-VR the colors look OK, so is this a driver issue or a madVR issue? Or combination of both. Should I update to a newer madVR version to test? If yes, which one?

In my case, Im pretty sure it did show the HDR logo on my TV but it didnt switch to HDR colors.

[Whiskeyomega]

just to say I have the same issue with HDR colours not appearing sometimes. I have to reboot. im on 526.98 on a 3090. It just so happens to be at the same time I got a new TV replacement in the Samsung QN700B and until I found this thread thought it was the TV. Been looking for the problem for ages.

[Ejziponken]

To anyone with issues with HDR switching in the latest drivers:


Can you please fill out the driver feedback form an so that we can look into this?

https://forms.gle/kJ9Bqcaicvjb82SdA

Can you also download MediaInfo and export the codec information from one file that shows this issue and email it to driverfeedback@nvidia.com in case it is specific to certain video formats?
https://mediaarea.net/en/MediaInfo

[EpsilonX]

Hi, is this setting available in latest AMD Driver..?
It's for HDMI content reporting to display, these are the available options though not all always available (depends on display)...

Auto Select (Recommended)
Desktop Programs
Photos
Movies
Games
Full Screen-Videos


https://i.imgur.com/AQiJ1iq.png


It's not available for the RX580...
Thank you...

[huhn]

as far as i know no.

these usually only change the device picture mode to the matching name.
i personally only ever saw this working on panasonic TV other had this option but it did nothing.

i'm kinda happy AMD doesn't have it. on less point of failure.

[EpsilonX]

as far as i know no.

these usually only change the device picture mode to the matching name.
i personally only ever saw this working on panasonic TV other had this option but it did nothing.

i'm kinda happy AMD doesn't have it. on less point of failure.

For my desktop monitor, I always set it to Desktop Programs...
It's working with my Sony TV...
If I set it to Auto Select, my TV switch to Graphics picture mode on Desktop, and change to Game picture mode when I start a game...
With my RX580, the TV is set to Graphics picture mode all the time with no option to change it, that's why I ask... :D

I have this setup with 2 presets, one with image processing for video playback, and one without to lower input lag for gaming...
So far no solution if I opted for AMD for my next GPU... :D

[Klaus1189]

527.37 fixes HDR passthrough on 526.98 GRD and perhaps older drivers, but not many. So 522.25 was fine as far as I remember and also 526.47.

-> The only one affected could be 526.86.

I personally use only GRD, because I use my machine primarily for gaming and a new driver is always welcome :)

[SamuriHL]

WHY they keep breaking passthrough is beyond me...

[Klaus1189]

I tested with original Kodi (not DS or anything special) and it was fine with 526.98 GRD. So the HDR passthrough issue which sometimes returns at some new versions seems to be limited to madVR. It is strange, but Nvidia fixes it and that is all I care.

[SamuriHL]

To be fair, part of that is the fact that madvr has not really been updated to handle HDR "properly". The nVidia fix is to keep putting in a fix specifically for madvr. But it's not like they don't know it's needed each time they release a driver.

[Ejziponken]

Same HDR switching issue with latest driver.

[Klaus1189]

Not for me, it is working with latest 527.37, but I tried various things and tested again and again ... and now I can confirm that something is not fully fine, because after I launched GTA V the HDR stopped working, a restart fixes this. And again the Display reports HDR info OSD but not actual the true colors. But as mentioned, a restart "fixes" this.

[Ejziponken]

Not for me, it is working with latest 527.37, but I tried various things and tested again and again ... and now I can confirm that something is not fully fine, because after I launched GTA V the HDR stopped working, a restart fixes this. And again the Display reports HDR info OSD but not actual the true colors. But as mentioned, a restart "fixes" this.

A PC reboot always fixed the issue for me, even in the other two drivers. Its still an issue because it comes back after a few hours.

[Klaus1189]

The other drivers never worked for me. Even after restart.

[Klaus1189]

I tested new 527.56 GRD and it loks like HDR passthrough is fixed completely for madVR. Kodi HDR switching worked fine also on "affected" drivers. I tested a few games (also GTA V like before), no changes what so ever on my system like ghames settings or anything else, just new driver and it works fine for me.

I can also test, if the issue comes back after many hours of pc running and test then, but not today, maybe tomorrow, how many hours should I test? -> @Ejziponken

I get more and more the idea that a dev at Nvidia is reading this thread ... :)

[huhn]

if you really think nvidia reads this let me try this:

can you please not move the chroma by half a subpixel in DXVA before chroma scaling but after while this is 4x faster it places the chroma in the wrong position. if it is done before chroma scaling it needs to be 0.25.

this bug is about a decade old maybe longer.

[Goeggel]

Are there any known issues with the Nvidia GameReady 516.94 driver?

I have been using 511.79 for the last couple of months in gaming and watching MKVs without any issues whatsoever (RTX 2070 Super, Win10).
After updating to 516.94, gaming is fine, but MKVs are stuttering randomly from time to time.

Update: I am now back to 511.79 with just installing them over the 516.94 drivers -> no more stuttering in MKVs.

I have made a new attempt at updating from 511.79 to 522.25 GDR (read somewhere in this thread that this was a version supposedly without any issues). But I now get the micro-stutters in MKVs again.
Maybe every couple of minutes, it's hardly noticeable, but they are defnitely there. Rewinding the affected scene, and they are gone. So it seems completely random.

Anyone having an idea where this issue could be coming from or how to tackle it?

[huhn]

power settings
none forced vsync i my first guesses.

[Klaus1189]

@huhn: could you post screenshots of sample video which shows the differences when using the wrong method and the right method? And of course the samplefile itself, so I and probably NVIDIA can test. Not a specialist in this topic. But I am interested, maybe we are lucky :)

[el Filou]

if you really think nvidia reads this let me try this:

can you please not move the chroma by half a subpixel in DXVA before chroma scaling but after while this is 4x faster it places the chroma in the wrong position. if it is done before chroma scaling it needs to be 0.25.

this bug is about a decade old maybe longer.I think they don't care about this because it only happens with DXVA2 and not D3D11 and Microsoft says apps are supposed to migrate to D3D11 at least or something like this.
Just like AMD and their DXVA2 deinterlacing/scaling.

[huhn]

happens with d3d11 too.
and AMD is deint is broken on d3d11 too.

i make images later.

[huhn]

mpcVR is used here:
image is take from here: https://forum.videohelp.com/threads/294144-Viewing-tests-and-sample-files

subsampled using lavfilter by forcing nv12 output.
catmull-rom: https://abload.de/img/catmull-romd7cu2.png
d3d11: https://abload.de/img/d3d11sbicq.png

i could now go and turn this png into a 420 still video but nope.

[senzaparole]

Hi guys. I have a problem. After allowing several updates I noticed that my TV no longer automatically switches to HDR mode.
I have a PC connected to LG TV. does anyone know how i can fix it?

Edit
I solved. It was an AMD driver update (Adrenalin 22.5.1). I unistalled them and now everything works fine. I installed AMD driver older... About a year ago.

[Goeggel]

I have made a new attempt at updating from 511.79 to 522.25 GDR (read somewhere in this thread that this was a version supposedly without any issues). But I now get the micro-stutters in MKVs again.
Maybe every couple of minutes, it's hardly noticeable, but they are defnitely there. Rewinding the affected scene, and they are gone. So it seems completely random.

Anyone having an idea where this issue could be coming from or how to tackle it?

I am still troubleshooting this issue. What settings are recommended for LAV Video (DXVA2 etc.) and MadVR (Rendering general settings) with Nvidia drivers?

Currently I am using these settings: https://imgur.com/a/P2Boj4f

[huhn]

the lav filter settings depend on what you want.
your current ones are just fine.
you could use d3d11 native which will break deint and blackbar detection but else could be faster while everything will work with DXVA2 copyback.

the difference between D3D11 copyback and DXVA2 copyback is trivial.
i'm not ware of a single real world test where this shows a difference.

your stutter issue should be part of madVR and nvidia setting try to force deint and use a presentation buffer between 1-3.
it should go away.

[EpsilonX]

the level issue is now a different beast. it's now full range all the time. even when set to limited range only tested in mpc-be. so still broken but in a far more acceptable state.


So, if all my monitors and TV (especially) are set to Full Range, I wont have any problem right..?

[huhn]

assuming your display is setup correctly yes.

or you use a video renderer that doesn't care about DXVA stuff like mpcVR or madVR.

there are allso issue with forced post processing with ruins levels and such but these heavily depends on the application.

for vivaldi is was unbeatable on mpc-be using EVR is was not present last time i checked but again just sue mpcVR or madVR.

[EpsilonX]

assuming your display is setup correctly yes.

or you use a video renderer that doesn't care about DXVA stuff like mpcVR or madVR.

there are allso issue with forced post processing with ruins levels and such but these heavily depends on the application.

for vivaldi is was unbeatable on mpc-be using EVR is was not present last time i checked but again just sue mpcVR or madVR.

Nice, I use mainly PotPlayer/MPC-BE with MPCVR/MadVR... :D
Currently testing PotPlayer+MPCVR+LAV...
Thank you for the very swift response... :D

[clsid]

MPCVR uses the DXVA2/D3D11 video processor by default.

[EpsilonX]

MPCVR uses the DXVA2/D3D11 video processor by default.

It won't matter if the GPU driver and TV are both set to Full Range, right..? :confused:
PotPlayer + MPCVR (Jinc2m) + LavFilters (D3D11)...
Getting a 6800XT, now this reply makes me confused as hell..

[huhn]

MPCVR uses the DXVA2/D3D11 video processor by default.

volt recommend to disable it. and it is for reasons unknown to me not affect by the GPU driver video settings.
the GPU driver video setting don't have a off function or a preset that doesn't do anything. typical AMD issues which are truely just dumb oversights...

disable video processing in mpcVR you are save from everything that the GPU driver does. my 5700 XT has only odd bugs but the video settings from the driver are ignored. also think about activating deint in lavfilter or something because without a hardware video processer you lose that option.

this is really confusing stuff that shouldn't exist in the first place. these issue where fixed for nvidia cards a decade ago where they final snap out of it and set video stuff to off by default.

don't remind me of jinc2 what have i done...

[EpsilonX]

volt recommend to disable it. and it is for reasons unknown to me not affect by the GPU driver video settings.
the GPU driver video setting don't have a off function or a preset that doesn't do anything. typical AMD issues which are truely just dumb oversights...

disable video processing in mpcVR you are save from everything that the GPU driver does. my 5700 XT has only odd bugs but the video settings from the driver are ignored. also think about activating deint in lavfilter or something because without a hardware video processer you lose that option.

this is really confusing stuff that shouldn't exist in the first place. these issue where fixed for nvidia cards a decade ago where they final snap out of it and set video stuff to off by default.

don't remind me of jinc2 what have i done...

MPCVR have only have 2 "primary" options right..?

"Use Direct3D11" checked = D3D11 VP
"Use Direct3D11" unchecked = DXVA2 VP

"use for resizing" checked = D3D11/DXVA2 scaling
"use for resizing" unchecked = Shaders scaling (Jinc2m,Lanczos,etc)

What do you mean by disable..?
In my case, I must enable "Use Direct3D11", or else it won't activate HDR...

[huhn]

you go to DXVA2 and D3D11 video processor and disable everything under "use for:"

[EpsilonX]

you go to DXVA2 and D3D11 video processor and disable everything under "use for:"

Only 1 "use for"... :confused:

https://i.imgur.com/HlcBjaA.png
https://imgur.com/HlcBjaA

This is my current settings, D3D11 with Shaders scaling

[huhn]

disable nv12 p010/p016 yuy2 other supported formats

[EpsilonX]

disable nv12 p010/p016 yuy2 other supported formats

What, never knew we can disable all of that and still play... :stupid:
Thank you for the new knowledge :D

[EpsilonX]

OK, what is the 100% fool proof combination to show the elevated black caused by 16-235..?
MPC-BE + EVR-CP + DXVA..?

[huhn]

but limited range output doesn't have to be elevated blacks.

setting the GPU to limited and the playback software should show a major difference between a normal image and the same image loaded in the player that is set to output limited.
http://www.lagom.nl/lcd-test/black.php

your you just get a meter.

[EpsilonX]

Brief testing using simple MPC-HC + EVR + DVXA, the output shown in my TV is correct (not washed out or too dark)... :D
This is with 6800XT driver "Pixel Format" setting matching the TV's setting, Full-Full or Limited-Limited, both 4:4:4...
And yeah, the deinterlacer is useless...

@huhn
Remember when you said you prefer AMD didn't have the HDMI content setting..?
Well now they have it, but Auto only... :rolleyes:
Everytime an app uses 3D textures fullscreen (e.g Games, Media Player), it AUTOMATICALLY engages ALLM mode with TV/AVR that supports it (HDMI 2.1), and automatically LOCKED the TV setting to GAME... :eek:
So if the TV have a poor Game mode color accuracy / dimming quality, then you can't change to other mode... :cool:

[huhn]

i have no word except did you expect better?
trust my there even was a developer that wrote the forced auto type and hit him self on the shoulder for this good work.

[aquanash]

Is anyone else still seeing HDR passthrough issues with nvidia driver 527.56? It stops working for me randomly every few days and I have to restart to get HDR working again. The previous driver it happened more often, but the newest driver doesn't seem to completely fix it and it still happens every so often. I'm seeing this on 2 different machines both running 527.56.

[Klaus1189]

No, not for me, but it could be a Game or program which could lead to this behavior. Check what game or program you started after it worked and before it didn't work anymore.