AMD, Intel and Nvidia driver issues and last recommended version [Archive] - Page 54

KrazyLurt

5th October 2021, 13:32

[emoji23] It is RTM after all so you'd expect that. And yes all good here too.

I've been testing it. Works fine.

Me too, been testing different builds leading up to the release.
One issue for me is that madVR is reporting 8-bit even when 10 or 12-bit is selected in nvidia controlpanel. How is it for you?

Using RTX 3080.

aquanash

6th October 2021, 01:30

Me too, been testing different builds leading up to the release.
One issue for me is that madVR is reporting 8-bit even when 10 or 12-bit is selected in nvidia controlpanel. How is it for you?

Using RTX 3080.

Please see my findings in the main madVR thread: https://forum.doom9.org/showthread.php?p=1954008#post1954008

In my case pressing alt-tab in Windows 11 breaks 10bit until I reboot. I posted a registry workaround to disable the new task switcher UI that seems to be the culprit. I wonder if you may be running into the same issue. Please test by rebooting then starting playback before even pressing alt-tab a single time. If 10bit is now working, press alt-tab to switch to another window, then press it again to switch back and check if it went back to 8bit.

KrazyLurt

6th October 2021, 19:20

Please see my findings in the main madVR thread: https://forum.doom9.org/showthread.php?p=1954008#post1954008

In my case pressing alt-tab in Windows 11 breaks 10bit until I reboot. I posted a registry workaround to disable the new task switcher UI that seems to be the culprit. I wonder if you may be running into the same issue. Please test by rebooting then starting playback before even pressing alt-tab a single time. If 10bit is now working, press alt-tab to switch to another window, then press it again to switch back and check if it went back to 8bit.
I got it working, and I think I know why. Like a poster in the MadVR thread I removed a display device in MadVR settings. That was my main 8bit monitor that I don’t use when using MadVR.

So know I have only my Oled and my reciever as devices in MadVR.

maxkolonko123

11th October 2021, 15:16

So what drivers are recommended to use with madvr? I'm still 1060gpu though

ryrynz

11th October 2021, 19:03

So what drivers are recommended to use with madvr? I'm still 1060gpu thoughMost just use the latest unless you have specific use case that isn't working for example custom refresh rates. I'm not aware of any broken functionality with madVR with the latest drivers and that's really what we care about most.

SamuriHL

12th October 2021, 16:35

Good luck all :)

ashlar42

13th October 2021, 13:26

No more Standard driver release, only DCH release is available.
What does this mean?

SamuriHL

13th October 2021, 13:54

It's just how they package the drivers. They've been moving away from the standard packaging for a while so this is not a surprising move.

huhn

13th October 2021, 13:57

the DCH drtiver isn't shipped with the control panel and the windows store version is needed with that driver which creates very odd issues like a very laggy control panel and such.

ashlar42

13th October 2021, 15:33

the DCH drtiver isn't shipped with the control panel and the windows store version is needed with that driver which creates very odd issues like a very laggy control panel and such.
Oh, wow. And to think that the current control panel was such a speedy beast... they clearly had margins to slow it down.

NOT

SamuriHL

13th October 2021, 15:50

LOL yea. It's a good time. These changes are something MS has been pushing for not nVidia.

el Filou

13th October 2021, 18:26

One thing I find curious is on my old Radeon, after I did a clean install of the last ever driver for it (21.5.2 "Legacy"), both the Radeon software and GPU-Z say the driver is now DCH, but I did not have to open the Store to install the control panel, and it doesn't appear in the installed Store apps either.
Has AMD found a 'loophole' that allows to sideload their control panel with DCH drivers?

claw

13th October 2021, 20:35

https://www.nvidia.com/en-us/geforce/news/back-4-blood-game-ready-driver/
https://www.nvidia.com/download/driverResults.aspx/181095/en-us

Nvidia GeForce 496.13 WHQL driver released, new R495 driver branch, no longer supports Nvidia Kepler GPUs. No more Standard driver release, only DCH release is available.

From the EVGA user forum, not confirmed...

An important fact about this driver is that Windows 8.1/8/7 are no longer supported with this driver. If you have those old operating systems this driver will not work for you.

--------------------------------------------------------------------------------------------------------------

Updated Win11, RTSS, and the nVidia driver, rebooted, and FFXIV capped out at 24 FPS.

Turns out, the power limit had been set to the minimum. Dragging the slider back in Precision X1 and applying fixed it. Weirdly, the temp limit seems a bit lower than it used to be while linked to the power slider at 105% but I'm not sure if that means anything.

huhn

13th October 2021, 20:50

LOL yea. It's a good time. These changes are something MS has been pushing for not nVidia.

nvidia followed they didn't had to.
amd doesn't do it even if they use an DCH driver you don't have to seperate the control panel. on one hand the AMD driver is more like geforce experience and you can bet nvidia nor AMD is not going to remove that from the driver on the other hand it can't even change the refreshrate on AMD side.

removing kepler support is a bad move right now with the shortage but it's not even remotely as bad as removing GCN 1-2 support by amd month ago before fidelityFX "super becubic".

SamuriHL

13th October 2021, 20:52

https://nvidia.custhelp.com/app/answers/detail/a_id/4777/~/nvidia-dch%2Fstandard-display-drivers-for-windows-10-faq

Just for anyone interested in nVidia's official stance on this nonsense.

SamuriHL

13th October 2021, 20:57

nvidia followed they didn't had to.

No I know. I'm simply saying MS has been "encouraging" GPU driver mfg's down this path. nVidia could have flipped them the one finger salute but they've chosen to push this path at MS' behest. God only knows why. I'm sure there's some kind of monetary incentive. I've been using the DCH drivers on my laptop since I got it with no real ill impact. I know others have had performance issues with the control panel. Maybe it's all fixed now. :D LMAO

nevcairiel

13th October 2021, 21:29

removing kepler support is a bad move right now with the shortage

Kepler is so old, new drivers don't really benefit it anymore anyway. Its not like old hardware instantly stops working now, even if the internet wants you to believe that.
You barely hear of anyone even running a 600 or 700 card anymore these days.

huhn

13th October 2021, 21:57

statistics say soemthing else:
https://store.steampowered.com/hwsurvey
the immortal 750 TI.

i wouldn't even blink about that if there wouldn't be a new OS right now and a stortage.

in general the driver support time is outstanding.

nevcairiel

13th October 2021, 22:02

statistics say soemthing else:
https://store.steampowered.com/hwsurvey
the immortal 750 TI.

750 and 750 Ti is Maxwell. So lets just skip that one, since its still supported.

You really need to go to the bottom of the list to find anything actually Kepler, even if you add them all up you probably won't even break 2%.

huhn

13th October 2021, 22:18

the 750 TI is are both. GM206, GM107 and GK106. but it is still listed so it doesn't matter as you said.

2-3 % is a lot.

this WHQL driver for win 11 would have been nice plus a couple more upcomming fixes just for win 11.

Asmodian

13th October 2021, 22:43

Kepler is over 9 years old now... that is a pretty good run for driver support. :p

huhn

13th October 2021, 22:48

nevcairiel

13th October 2021, 22:49

You also need UEFI without CSM and Secure Boot, did NVIDIA even add UEFI support to those old cards? :D

huhn

13th October 2021, 23:01

ryrynz

14th October 2021, 00:24

as said outstanding

700 series kepler refresh is 8 years which is still great.

and my win 11 argument killed itself by forcing TPM 2.0 i was under the impression they where backing of of that. you really don't need driver for an OS you mostlikely can't install anyway even on some new machines.

You can run it with TPM 1.2. I do think any system running older hardware has limited benefit by installing W11 through. Overall I think everything is fine in terms of support from major manufacturers here. I was expecting Kepler removal from a new driver about a year ago, so yes very good support.

huhn

14th October 2021, 00:35

they double down on it they state TPM 2.0 not 1.2 anymore while it is still possible to install win 11 even on system without TPM that's now the official requirement.

SamuriHL

14th October 2021, 00:57

yes "they" did. https://www.hardwareluxx.de/community/threads/how-to-uefi-gop-bei-kepler-gpus-nachr%C3%BCsten.1044351/

does microsoft really think the AVG user can enable secure boot, TPM or worse update the bios...

No. They think they can push sales of new machines. They are mistaken, of course. I upgraded my Alienware laptop to W11 but I have a 2080 in it. Maybe look on the bright side...with nVidia only having to focus on "modern" GPU's now, their drivers will TOTALLY improve and become rock hard stable. :rolleyes: :D

nevcairiel

14th October 2021, 07:23

they double down on it they state TPM 2.0 not 1.2 anymore while it is still possible to install win 11 even on system without TPM that's now the official requirement.

Any system with a supported CPU should have fTPM support (thats just Ryzen 2000+ and Intel 8th Series and up), unless your mainboard is totally stupid. Older CPUs then that are not on the compatibility list anyway, so TPM is the least of your problem.

huhn

14th October 2021, 07:35

they are totally stupid.
https://www.dell.com/support/kbdoc/de-de/000132583/dell-systems-die-von-tpm-version-1-2-auf-2-0-aktualisiert-werden-koennen

and well the new bios version are adding windows 11 support if that's just TPM on by default or something more is somehting i can't judge but creating a new bios with "adds windows 11 support" is not something they should add for fun.

the TPM 1.2 thing is an issue because of that people where getting add cards/chips for somewhat older machines like zen 1 and now they are worthless.

ryrynz

14th October 2021, 09:49

become rock hard stable. :rolleyes: :D

Wow.:p

Asmodian

14th October 2021, 10:14

and well the new bios version are adding windows 11 support if that's just TPM on by default or something more is somehting i can't judge but creating a new bios with "adds windows 11 support" is not something they should add for fun.

I think this is just the defaults for CSM, Secure Boot, and TPM. I have a new X570 board and Asus did an update for Win11 that changed all those default settings. They used to all be wrong for Win11. The changelog even says:
1. Support Windows 11 by default, no settings changes required in the UEFI BIOS.

But of course they might have changed something else too.

ashlar42

14th October 2021, 13:05

the TPM 1.2 thing is an issue because of that people where getting add cards/chips for somewhat older machines like zen 1 and now they are worthless.

To be honest, people were doing that before Windows 11 had been released. While specifications were still up in the air. Why were they doing this? Because they were afraid of a shortage of components, maybe? So they wanted to be "smarter" than the average consumer?

All this to abandon an OS that has guaranteed support for a minimum of another 4 years (and I wouldn't be surprised if that gets extended).

I am not overly concerned about that behavior. That's basically on them if they have bought something that is worthless. If you want to be the earliest of early adopters... well, risk is on you, in my opinion.

clsid

14th October 2021, 14:12

The TPM/CPU requirement can easily be bypassed (for now). I have Win11 running inside VirtualBox on a 2nd gen i7. Even Windows updates are coming in.

But it is understandable that MS only offers official "support" for modern hardware. It is usually old hardware/driver that is giving troubles.

By the time Win10 goes EOL, the currently supported hardware is already 5-8 years old already.

el Filou

14th October 2021, 16:51

Does this new 495 branch support new Windows 11 features (WDDM) that the last 472.12 did not? Because that one already officially supported Windows 11 and also still supported Kepler.

oldpainlesskodi

14th October 2021, 17:55

Think I'll be staying on Win10 with AMD for a bit then, or buy a dedicated Media Player with DV support etc.

Balling

17th October 2021, 14:12

Nobody needs no TPM for windows 11. That is BS. This script workarounds the tempertrantum from Micro. https://gist.github.com/AveYo/c74dc774a8fb81a332b5d65613187b15

As for Secure Boot, it is a must have feature, if you are signing the kernel and its modules yourself. Also UEFI means no grub is needed, kernel can load natively in 4K resolution (grub also supports 4K now, but on some destributives it is commented out). For microsoft it also means GPT, since Microsoft thought that they do not need to follow the UEFI spec that allows MBR too. At least NTFS works usually.

distobj

20th October 2021, 21:34

Most just use the latest unless you have specific use case that isn't working for example custom refresh rates. I'm not aware of any broken functionality with madVR with the latest drivers and that's really what we care about most.

I've been using 442.74 since it came out. Any recent driver update, including the latest, displays washed out colours despite properly switching to HDR on my LG OLED. I'm even running Win10 21H1.

Suggestions?

ryrynz

20th October 2021, 22:15

I've been using 442.74 since it came out. Any recent driver update, including the latest, displays washed out colours despite properly switching to HDR on my LG OLED. I'm even running Win10 21H1.

Suggestions?Aside from looking to see whether there's extra devices that have been loaded in MadVR that might be affecting this and changing output bitrate in the graphics settings and trying an earlier driver nothing else springs to mind. Anyone else have these issues?

Chouonsoku

20th October 2021, 22:27

Just to verify, is everyone else seeing only 8 bpc as an option for NVIDIA GPUs under Windows 11? Using driver 496.13 on Windows 11 build 22000.258 with a GTX 1070 Ti. Had options for both 10 bpc and 12 bpc in Windows 10.

brazen1

21st October 2021, 00:38

12bit using W11 here. Did you set it for resolutions 30Hz and under?

Chouonsoku

21st October 2021, 05:54

12bit using W11 here. Did you set it for resolutions 30Hz and under?

I set the TV to 23 Hz and only 8 bpc was offered, it's the same for other frequencies. I tried creating a custom resolution but nothing gives me 10 or 12 bpc.

https://i.imgur.com/270YR95.png

What GPU are you using? Wonder if it's a weird query bug or something because I'm on an HDMI 2.0 device.

Asmodian

21st October 2021, 07:17

What GPU are you using? Wonder if it's a weird query bug or something because I'm on an HDMI 2.0 device.

That does seem possible, but weird. Have you tried deleting all your displays, and letting it be re-detected, using CRU?

Custom resolutions do not offer >8 bit modes. :(

https://hosting.photobucket.com/images/dd496/asmodian3/Nvidia_10-bit.png?width=960&height=720&fit=bounds

Chouonsoku

21st October 2021, 15:28

That does seem possible, but weird. Have you tried deleting all your displays, and letting it be re-detected, using CRU?

Is that as easy as opening CRU, hitting delete next to each display in the drop down, saving and then running restart64.exe? If so, no dice. :( Might try a clean install of the drivers next.

Edit: Clean installed the latest studio driver with DDU, no change.

nsnhd

22nd October 2021, 03:59

Something has changed in windows 10, FSW mode is creating ghosting and artifacts in 3D frame packing and FSE has to be used with mpc-hc/madVR.

Balling

22nd October 2021, 20:26

You need to set YCbCr obviously.

Chouonsoku

22nd October 2021, 22:40

You need to set YCbCr obviously.

That actually does work in Windows 11 (thank you!) but that doesn't exactly fix the problem I'm seeing. HDMI 2.0 has more than enough bandwidth for 3840x2160p @ 12-bit RGB @ 24 Hz. Forcing chroma subsampling to get 10/12 bpc should not be necessary.

https://images.idgesg.net/images/article/2017/12/formatdataratetable-100743742-large.jpg

Again, doing this works fine in Windows 10.

Edit: Hah, I fixed it. Deep color wasn't enabled on the HDMI input, swapping that on enabled 12 bpc RGB. ��