AMD, Intel and Nvidia driver issues and last recommended version

[VBB]

Same here. Didn't notice any change. Everything works just like before.

[chros]

So what benefits does 398.18 get over 385.28 at all? Does 3D still work well incase you're using it ?
I don't use 3d, I guess it was removed before :)
And there's only 1 benefit: madvr b113 was broken with the older driver, due to FastBlur implementation, and that is working with this newer one.

[nsnhd]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

[Klaus1189]

So what benefits does 398.18 get over 385.28 at all? Does 3D still work well incase you're using it ?
Thanks
I guess it was removed before :)

430.39 from 2019-04-23 drops 3D support according to my info ;)

[brazen1]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

I doubt Kodi is going to fix anything to accommodate 2 - 3 yr old drivers. Are you using Windows 10 20H2? Also did you install JAVA for Kodi 1:1 rips? If you use them and you didn't, that might lead to green screens. I understand you need to use older drivers for 3D but honestly and sadly everyone else has moved on.

[nsnhd]

No, I'm not using JAVA and haven't installed them. But I'm also not using Windows 10 20H2 because newest version might break some things according to posters here, maybe I should upgrade to it if Kodi not fixing the issue, v19 just released and they may need some time.
Thanks

[chros]

But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

It was this green and black acreen with b113 when you used d3d11-native, it didn't happen with dxva-copyback (as far as remember). Try this out in mpchc and lavfilters.

[brazen1]

Matrix is really nothing new except the official release of it recently. I was using Kodi v19 for over a year with and without JAVA. Now I'm using v20 with. I'm also using Windows 20H2 and all the previous O/S's. If you're on W7 or something, upgrading might help. If you're one or two Windows builds behind, that won't make any difference because myself and others used them with no problems either. I've no idea what 20H2 broke for other users here? Didn't break anything for me or others here afaik. I have to assume your green screen problem is something else upstream. More details and specifics in user signatures would help. I'm just curious why 18.9 works for you and 19 doesn't given both work perfectly for me and others. In other words, there is nothing for Kodi devs to fix imo.

[nsnhd]

It was this green and black acreen with b113 when you used d3d11-native, it didn't happen with dxva-copyback (as far as remember). Try this out in mpchc and lavfilters.
The issue happens only on Kodi19, the rest including Kodi 18.9 is fine.

If you're one or two Windows builds behind, that won't make any difference because myself and others used them with no problems either. I've no idea what 20H2 broke for other users here? Didn't break anything for me or others here afaik. I have to assume your green screen problem is something else upstream. More details and specifics in user signatures would help. I'm just curious why 18.9 works for you and 19 doesn't given both work perfectly for me and others. In other words, there is nothing for Kodi devs to fix imo.
I'm using WinPro 1909, so maybe not much different from 20H2.
Lots of complains here are about breaking switching frame rates, HDR, 8-bit/10-bit...etc. when mixing drivers updates with windows updates.
As I read in Kodi forum, there is a huge change from Kodi 18.9 to Kodi 19, so maybe that affects my usage. Even devs there suggest to install Kodi 19 in Portable Mode and wait for stability.

[VBB]

GeForce Hotfix Driver Version 462.07 (https://nvidia.custhelp.com/app/answers/detail/a_id/5174)

GeForce Hotfix display driver version 462.07 is based on our latest Game Ready Driver 461.92.

The hotfix addresses the following issues:
[Vulkan][X4: Foundations 4.00/X4: Cradle of Humanity] The game may crash on GeForce RTX 30 Series

Nothing to see here. Move along...

[the_jaguar]

3D MVC is working well with 385.28 by MPC-HC/madVR b113 and GTX 1060.
What's broken with b113, maybe I'm using tone mapping to my SDR displays hence don't notice that ?
But now I have issues with Kodi19 hardware decoding, it shows green screens (Kodi 18.9 doesn't), disable HW decoding solves it, maybe I have to wait for a Kodi fix.

430.39 from 2019-04-23 drops 3D support according to my info ;)

Yes, 425.31 is the last official version with 3D MVC support. That being said, by using the 3D fix tool available on another forum, I was able to get 3D MVC to work on 452.06 (I am sure it will work on later versions too). One thing to note is that beta 113 of madVR will not work (due to a bug), so you will have to use beta 114. This will introduce the time limitation constraint of madVR, which I have overcome using a windows tool that changes date just for madVR.

In my case, Windows forced an OS version upgrade, which forced a Nvidia driver upgrade, so had to go through this process to get 3D MVC to work again :)

[Klaus1189]

by using the 3D fix tool available on another forum, I was able to get 3D MVC to work on 452.06 (I am sure it will work on later versions too).

Do you mean the "3D Fix Manager", that is mentioned in Notes of Nvidia section? Or is it another tool?

[the_jaguar]

Do you mean the "3D Fix Manager", that is mentioned in Notes of Nvidia section? Or is it another tool?

Yes, that works too, but there is also another script that's written by Losti that automates the entire process (https://www.mtbs3d.com/phpbb/viewtopic.php?f=105&t=25361)

[SamuriHL]

Oh no. I mean, hurray! LOL

[el Filou]

PCI Express Resizable BAR is now supported on RTX 3000 with the new driver. I'm curious if this could improve performance of copyback DXVA decoding with 10-bit UHD.
Could anyone who has hardware that has official support for that feature (apparently there are multiple requirements https://www.nvidia.com/en-us/geforce/news/geforce-rtx-30-series-resizable-bar-support/) do before/after benchmark with DXVA Checker?

Edit: apparently from what I understand support has to be enbled by NVIDIA on a game by game basis? :(

[SamuriHL]

I wouldn't stress too much about it.


NVIDIA CUVID and Intel QuickSync are deprecated, not recommended for usage, and will be removed in a future version.

However, there is some light at the end of the tunnel. A replacement for the old CUVID implementation, which had serious deficiencies, will hopefully be available at the same time, based on FFmpegs NVDEC hardware acceleration support, which solves many of the shortcomings (like missing HDR metadata, among other things), while still providing deinterlacing out of the box. And maybe even with D3D11 interop, which means that it could devlier d3d11 native frames to the renderer, and avoid the copy-back overhead.


Help is coming at some point in the future. That's LAV Filters in case it wasn't obvious.

[huhn]

resizable bar shouldn't matter for decoding.

if a new frame is done decoding it is uploaded frame by frame so it is always much smaller than the current size limitation and is by design sending "small" data.

i have a 5600x, b550, 5700 XT combo so i could test it in theory.

[Klaus1189]

How can I note this in the first post? :confused:
Same version number, ... How can user know to have the new package?

[Ejziponken]

There is a Windows update (KB5000842).

Highlights:
Updates an issue that makes high dynamic range (HDR) screens appear much darker than expected.

I wonder if this has any effect playing up video with madvr?

[ryrynz]

Not many have their desktop set up in HDR mode anyway.

[jkauff]

Not many have their desktop set up in HDR mode anyway.
The Win10 release coming next quarter, with its considerable UI changes, will encourage you to do it if you have a 4K HDR-capable monitor.

[el Filou]

What UI changes are considerable?
I only read the Insider Blog to follow what they change and it seems like it's mostly cosmetic changes like new icons and even more white space.

[huhn]

you may should add this line in 21.3.1 and newer:
Radeon RX 400 and 500 series graphics products may experience a TDR during extended periods of video playback.
this is an official known bug and user should know about this in term of video playback and nearly for sure not new.

TDR is a special term for a driver crash.

BTW. there are also pro driver for AMD: https://www.amd.com/en/support/kb/release-notes/rn-pro-win-21-q1-1

[jkauff]

What UI changes are considerable?
I only read the Insider Blog to follow what they change and it seems like it's mostly cosmetic changes like new icons and even more white space.
As I understand it, new UI elements (like the icons) will take advantage of the increased color space in HDR if it's turned on. Of course, they'll still work fine without HDR.

I believe this was the reason for adding HDR to Win10. I doubt if many people watch HDR movies and home video using just the Windows player.

[brazen1]

@Klaus1189

I've installed NVidia 465.89. The lingering HDAudio driver problem present all these years is no longer an issue. I have toggled the AVR on/off several times and Windows Audio Properties now cooperates. I have tested results that were working fine and then rebooted no less than 6 times between checks. I have played a few SDR and HDR titles briefly. I have checked YouTube audio with the AVR on/off. I've compared driver versions and some functions using notepad ++. I don't want to appear to jump the gun so if I don't report back here within the next few days, it means they're still working. Someone else should confirm if they too have been struggling and modding the install with an older HDAudio driver. (Windows Audio Properties - Stereo vs Multi-Channel dependent on AVR on/off state) I should note, I didn't use DDU. I usually save that for when this audio test fails but it hasn't this time. Now I'm afraid to DDU but in the next few days I will :eek:

*EDIT*

Well, this is ridiculous. Today I turn on my PC and the audio doesn't work properly. This after repeatedly turning my PC off/on yesterday. It's like the bug is on a 12hr timer. I regress back to HDAudio driver 388.59 which is about 4 yrs old but still works as intended.

[el Filou]

When you said you rebooted your PC and turned your AVR On/Off the first time when you thought it had been fixed, did you also turn off your TV at some point? Maybe that's what triggered the issue.

Did you notice if it behaved differently when the AVR and TV were on when you turned the PC on Vs only the TV on, or even both TV and AVR off and then turn them on after the PC?

[brazen1]

Thanks for your interest @el Filou.

I don't think this is an EDID handshake issue? I use a Harmony remote (they just announced they are discontinuing making Harmony remotes anymore btw). From a single button press all my equipment turns on and adjusts. It doesn't deviate. So, when I start my PC activity environment, or quit it, all the devices and adjustments for them react accordingly. Same with any other activity like HTPC activity.

The difference between my PC activity and my HTPC activity are very different. One I have setup to use my panel speakers instead of my AVR and it's speakers. The AVR is off. I don't want to use my AVR all the time. The other activity uses the AVR and it's speakers and the panel speakers are off (auto turned down to zero).

I know all my equipment turns OFF completely because all of it is right in front of me. Same with ON depending the activity I've selected. Of course I can manually turn things off/on too. I've been doing exactly all of this for years.

So, during test day, I turned off all my equipment for a few minutes and turned back on using different activities exactly as I always do it - multiple times, testing many different scenarios like YouTube with AVR on. YouTube with AVR off. SDR/HDR movie playback with AVR on/off. Front end GUI sounds. I challenged the driver many different ways repeatedly rebooting and turning off/on all the equipment between test and retests to make sure registry entries would stick.

It all worked fantastic and I was convinced NVidia had finally addressed this niche issue. Why it's niched, I don't know? I must be the only user that sometimes wants to use the stereo panel speakers only and other times full blown multichannel surround sound. Anyway, I turned off all my equipment as usual and called it a night. The next day when I turned my system on, nothing worked anymore. I didn't do anything differently I'd done previously the day before. The only variable was the longer time the equipment was turned off.

Here's the rub though... everything works perfectly using the old HDAudio driver so I don't see how user error or equipment error (including EDID) is responsible and can be circumvented or worked around. With the AVR on, Windows audio properties should report multichannel output. With the AVR off, it should report stereo. If Windows doesn't report the correct state of output, things don't work correctly or even at all. YouTube will have zero audio. Video will have no audio. These are challenges when using an HTPC as a desktop workstation and/or a video player depending the activity that mostly the AVR dictates. A user should simply be able to toggle an AVR off or on. Windows audio should oblige and set the output to stereo or multichannel automatically. New drivers don't. Old drivers do.

Let's assume your AVR is on right now. Right click your audio icon in the tray. Speaker setup will say the multichannel you have going. Now turn the AVR and check again. It will still say multichannel. It should say stereo. Now go to YouTube and play any video. There will be no sound coming from your panel speakers. The video might not even play and you'll get a YouTube error window in the video area.

Now turn the AVR back on. All is well. This is what new HDAudio drivers do. Older ones don't. Reboot when you think everything is ok. Better yet, turn everything off and leave it that way overnight like I did. Surprise!

[el Filou]

Here's something you may want to try.

Recently I noticed a problem in the NVIDIA driver where if I played 2 channel and then 5.1 material in succession with exclusive mode, the audio driver would fail to map the audio channels correctly with 5.1 (my speaker config is set to stsreo in Windows for Web stuff, and I rely on the media player to switch config for surround). It's like the driver was 'stuck' in sending stereo even though the audio renderer was sending multichannel (I wouldn't hear the center channel and the surrounds at all).

Now, normally each time I update the audio driver I immediately disable the energy saving timeouts in the registry because it's getting on my nerves cutting off the audio after 4 seconds, and that time I had forgot to do that because the audio driver version hadn't changed and I assumed this meant the installer didn't change anything, but in reality it reinstalled the same version and reset the settings, so I had to redo the registry changes but I didn't notice at first.

Try to change this: in regedit, open HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e96c-e325-11ce-bfc1-08002be10318}\<***put your NVIDIA High Definition audio driver entry here***>\PowerSettings and change the PerformanceIdleTime value to 00 00 00 00 then reboot (if for some reason you are using the "power savings" energy plan, change the ConservationIdleTime value instead).
This will disable the graphics card turning off the audio connection to save power.

I can't give any guarantee that this will fix anything, but in my case it fixed the issue I was having.
Note that this will prevent the AVR from turning off the amp to the speakers when there's no audio being played, which isn't a problem if you're not leaving it on without using it but something to keep in mind.

[brazen1]

Interesting. Thank you for that. Currently I'm using the old HDAudio driver from 388.59 which I replaced using 465.89 in the installer package fwiw. My PerformancIdleTime value is already 00 00 00 00. I guess because I'm using the older driver? I'm using high perf energy plan already too so my ConservationIdleTime value is 1e 00 00 00. I will compare once I install 465.89 with the current HDAudio driver and make the registry changes. Should I use the same values I reported here especially the 1e 00 00 00 since that value is working and I'm not using a power savings adjustment afaik? I'm a little concerned about your last sentence but I'll see if it affects my usage. I'll need to system image and get done with some other tests I'm doing elsewhere so this will take a bit. Thank you for this suggestion.

[el Filou]

I don't think there's a need for a whole system backup or anything like that just for this tweak, as just reinstalling another version of the audio driver resets the values or at best you can save a .reg of that key and re-import it.

My default value with 1.38.40 is 04 00 00 00 and the audio switches off after 4 seconds, so I think with your version it should switch off after 30 seconds in power saving mode, and never in high performance/balanced, but I think there was a mistake in NVIDIA inf files in old driver versions because they added those values but using a wrong type so they didn't work in practice. They fixed it at one point and that's when I nearly became crazy because the audio connection was turning off even when I was pausing playback for 4 seconds like in the bad old days of ATI's "silent stream" issue.

Here's what's in the .inf for 1.38.40:[NVHDA_D3cold.AddReg]
...
HKR,PowerSettings,ConservationIdleTime,1,04,00,00,0 ; 4 seconds for idle power management when on battery - enabled
HKR,PowerSettings,PerformanceIdleTime,1,04,00,00,00 ; 4 seconds for idle power management when on AC power - enabled
HKR,PowerSettings,IdlePowerState,1,03,00,00,00 ; go to D3 for idle power management
I don't think you need to be concerned about my last warning, as it's clear that in your current config and driver the power saving is already inactive, so it wouldn't change much. This feature has the same effect as manually muting an HDMI audio output in Windows, except it does it automatically and then brings it back up when an app plays audio again but you miss the first few samples while the HDMI connection re-establishes the stream.

[Mordred]

Long story short, I was on some version of the nVidia driver (I believe from January-ish) and when I updated both Windows and nVidia at the same time my HDR broke. I was able to get HDR, but could not solve another problem I had in DSPlayer Kodi when exiting HDR (https://www.youtube.com/watch?v=Ss0DcYJ6U2s&t=86s). I rolled back to 445.87 and everything is fine... except now I've got a new and harder to reproduce problem that seems similar to what Brazen is experiencing.

Occasionally when I turn on the receiver and TV, my audio device (listed as DENON-AVRHD) is "partially" invalidated. In a true device invalidation, like after installing a driver, I have to manually reselect the device in all my programs I want to enable audio playback as the old device settings have been automatically cleared since the device ID no longer exists. In my case, the device is still listed... it's just somehow not really valid? Foobar reports the device was invalidated, but it's still shown (and selected) and reselecting it does nothing. It does not show up in the Windows Volume Mixer, but if I right click on the Audio icon and go to "Sounds" to bring up the old Windows 7 style Sound dialog, I can switch to the playback tab and there's my DENON-AVRHD still listed as default device. I then have to right click on it, select "Test Speakers" and after about a second, the chimes start coming through my speakers. At that point I can close the dialog, and now Kodi, Foobar and anything else all work correctly again without needing any changes. A reboot also fixes it, but that's a pain in the ass.

The HTPC is on 24/7. The issue only seems to occur when the Denon (maybe the TV too?) have been turned off for at least half an hour, but that might be random variance. It happens every morning when I turn the TV on. It happens when I come back from lunch sometimes. If I turn everything off, wait 5-10 minutes and turn it back on I've never had problems. Anybody seen anything like this before?

[VBB]

Fixed Issues in this Release

 Some displays may show incorrect color levels after booting into Windows. [3285148/3287063]

Some people over at AVS had experienced this bug.

[brazen1]

@el Filou

Fwiw, I installed 466.11 today. Windows audio properties wasn't in sync with AVR off/on 100% of the time (reboots, cold starts, panel/AVR states, etc.)

I went ahead and changed PerformanceIdleTime from 04 00 00 00 to 00 00 00 00. It's still not in sync 100% of the time but I (think) things have improved. When it isn't in sync I'm now able to turn panel/AVR off/on and then it syncs. There are a lot of different variables - Turning panel/AVR on prior to booting PC, turning on after booting, toggling on/off while booted into Windows, state of panel/AVR on/off when shutdown awaiting next PC cold start, etc. None of that matters using the old HDAudio driver fwiw.

I'm going to continue trying your edit until either I gather more ammo to help isolate or I can't live with it anymore. As has happened a couple times in the past testing newer drivers, once this all parks shutdown overnight it could reveal a whole new behavior. I just wanted you to know I appreciate your efforts and sharing while I give this a go.

[el Filou]

It's always so difficult to diagnose HDMI audio as it's also linked to the GPU itself and Windows architecture.
For example since Windows 1803 I have a big popping sound every time I switch refresh rate. I never had this before so it's not the AVR, and now even if I install a really old (like from 2017) HDMI audio driver it still happens. HDMI has provisions to automatically mute the audio stream when initializing/resetting the connection to specifically avoid this kind of thing, but who knows what part of the chain fails to instruct it to do that now... and everyone says it's normal to have pops in that situation so I just gave up trying to report it.

[aron7awol]

The HTPC is on 24/7. The issue only seems to occur when the Denon (maybe the TV too?) have been turned off for at least half an hour, but that might be random variance. It happens every morning when I turn the TV on. It happens when I come back from lunch sometimes. If I turn everything off, wait 5-10 minutes and turn it back on I've never had problems. Anybody seen anything like this before?
Every so often I have an issue where my audio device stops working and shows a red x in my system tray volume icon. Rather than rebooting, I've found the quickest fix is to go into Device Manager and disable then enable NVIDIA High Definition Audio device. Not sure if this helps you, but figured I'd mention it.

[clsid]

Restarting the Windows Audio service might solve that as well.

.bat file:

@echo off
net stop audiosrv
pause
net stop AudioEndpointBuilder
pause
net start AudioEndpointBuilder
pause
net start audiosrv
pause
Right-click and run as admin.

[Calvi]

I use the windows audio driver: “High Definition Audio Device” (instead of nvidia) as I find it works 100% for my receiver through hdmi and maintains atmos correctly, switches to 3 channel etc.

Just right click “NVIDIA High Definition Audio Device” in device manager and uninstall driver. Then rescan and it will add the windows one.

I make nvcleaninstall drivers with the hdmi audio driver removed so as to avoid the nvidia included audio driver.

Every now and then I try a new version but always end up reverting.

[alleway]

I use the windows audio driver: “High Definition Audio Device” (instead of nvidia) as I find it works 100% for my receiver through hdmi and maintains atmos correctly, switches to 3 channel etc.

Just right click “NVIDIA High Definition Audio Device” in device manager and uninstall driver. Then rescan and it will add the windows one.

I make nvcleaninstall drivers with the hdmi audio driver removed so as to avoid the nvidia included audio driver.

Every now and then I try a new version but always end up reverting.


i am using hdmi audio via earc but when i try to use your method there is no sound from the windows driver.

[Calvi]

I don’t use e-arc so can’t comment on that.
Not sure why it would be any different though.

[darksen]

Hey, guys, you can disregard my previous comments as it seems the audio crackling and desync were happening because a bogus LightBulb release (See #198 (https://github.com/Tyrrrz/LightBulb/issues/198)). For some reason all the problems didn't happen with 457.51.

[VBB]

These include an updated HD Audio Driver - 1.3.38.60

[SamuriHL]

I'll install the driver later. I've been on the windows update for a while now already.

[Andy o]

Is anyone still getting the washed out colors on HDR when taking it out of full screen with NV and madVR? It's not happening here anymore, I'm on madVR 0.92.17 and MPC-HC 1.9.11 by CLSID, NV drivers above 466.47 game ready. I also recently updated to Windows 21H1 so not sure what fixed it.

Edit: never mind I just realized this is when RGB output is set to 8 bit, when I set it to 10 or 12 bit, it still washes out the image, not that it's a huge issue.

[VBB]

GeForce Hotfix Driver Version 466.55

The hotfix addresses the following issues:
[RTX 20 series][GTX 16/10 series][HDMI] 4K @ 120Hz display mode is not available from display settings [3312401]
If GPU is connected to a 4K UHD TV, system may freeze when launching a VR game [3313315]

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

[huhn]

the deint issue is nearly for sure a driver issue the same happened with the release of the first crimson driver for all cards.

i reported over 1.5 years ago.

[kasper93]

AMD Radeon

Known limitations of Radeon RX 5000 and 6000 GPUs (older generations are fine, like my good old "heater" RX 480 :D):
If you are a Vega or Radeon VII user, please let me know, you could test 2 things for me. It will only take 2 minutes.

• Hardware deinterlacing is broken in every driver version -> It is poor quality when applied to interlaced video and it is not adaptive anymore, which is a NO-GO for HTPC usage.
You can check this issue yourself: Download this short MBAFF sample file (https://drive.google.com/file/d/12wO8NJbIrfa2MD4yVaA38RrBBdziCda8/view)
The Hardware Deinterlacer should be aware that the characters above "WWW.D88.COM" are progressive and should not be deinterlaced, otherwise you will see flickering like in this picture:
https://upload.wikimedia.org/wikipedia/commons/f/f0/Indian_Head_interlace.gif
See here (https://forum.doom9.org/showpost.php?p=1928654&postcount=2155) for more details
• 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.

Did someone contact AMD for clarification about those issues? Deinterlacer issue is probably harder to fix if they messed up it on hardware level, who knows.

But the color levels is more interesting. In driver settings there are video presets and "cinema classic" has proper levels, ever other have wrong levels. This cannot be intentional, but at least there is workaround to select one preset that works... or well use madVR like sane person. EDIT: nvm, levels are still wrong, it is just way closer to proper image.

[Klaus1189]

https://youtu.be/1Kio8Hn8f3U

[el Filou]

Do you know if there's something interesting for video playback/processing in that one hour long presentation? :) (they could at least have added chapters... :rolleyes:)

[Klaus1189]

Sadly no, we are „smol“ niche ;)

[Klaus1189]

And also new Studio driver 462.65
Both new drivers with support for the new 3080 Ti or "Tie" just like the Rasperry Pi or: https://www.youtube.com/watch?v=bvlK_Wc_aYo :D