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

Klaus1189
26th February 2021, 18:39
So you got a 960 with 4GB VRam? This card should not be affected by the bug. I am testing latest 461.72 and so far it looks very promising :)
Never had any issue with that display with my heater RX480 then the RX5700XT had this drop outs (everybody had these) and also this new Nvidia RTX 30 card, probably not so new anymore, but 700 € more expensive now.
But the issue seems tobe gone in this new driver version. Look in one of my older posts, yesterday I installed without ddu or clean install in installer and got one flicker/dropout per Minute. :D
I was happy because that means they did something to the driver and I only must do a clean install or ddu it. Very happy now, but 23Hz refresh rate of AMD is so good out of the box...

brazen1
26th February 2021, 18:43
I should add, for many driver versions going way back, I still have the audio problem I had in the past beginning after 388.59. It's frustrating but fixable as usual. This is why I'm on-top-of every new driver release... for me personally using my setup. I don't think there's anything weird, strange or elaborate with my components or my setup. I've never received a reply from anyone if they experience the same thing though I've brought it up a few times here and elsewhere. I'll throw it out here again...

To duplicate:

Clean install a new driver. DDU or whatever.
Windows audio properties reports it's in stereo even though the AVR is turned on. So make the changes for 5.1, 7.1, etc. to match what you use.
Turn the AVR off. Windows Audio will switch back to stereo as it should. Leave the AVR off.
Now reboot. Windows audio will report 5.1, 7.1 or whatever you set it to earlier. Except the AVR is still off and a display, for example, should be using its internal speakers instead of the AVR's external speakers.
Now go to a desktop application like YouTube and play a video. There is no audio from the TV speakers.
Of course you turn on the AVR and use its external speakers but what if you don't want the AVR on and you prefer the TV speakers while surfing desktop apps?

Windows audio isn't auto switching dependent on the Off/On AVR state fed by the audio driver.

The fix is to replace the present nVidia HDAudio driver with the older one from back when it worked by editing the installer package. Then everything performs perfectly as it should. Now I know this doesn't apply to everyone since most folks use an AVR on for everything. I only want my AVR on when watching movies and such. Not so much when using the Windows desktop but I still need audio. Some say never to adjust Windows audio properties and just leave it at stereo so the AVR does the decoding. I don't even know what that means because my AVR is still decoding even if Windows Audio properties matches my audio format. Furthermore, 'some' audio formats such as AAC will not convert to multi channel if stereo is set. They simply output stereo because they haven't been told to output any differently.

brazen1
26th February 2021, 19:04
For me, nVidia 23Hz refresh rate and all other refresh rates are good out of the box too. Here's some screens with the madVR OSD showing I posted elsewhere the other day.

https://www.avsforum.com/threads/madvr-player-support-thread.2215490/post-60511664

Tbh, newer GPU's, and all the micro stutter, flutter, and other complaints of late, considering their prices too, the 960 remains the apple of my eye. But then, I don't need to madVR tone map thank goodness. That would be impossible.

Klaus1189
26th February 2021, 19:15
I get ~50 minutes in 23 Hz mode but that is nowhere near AMD :) Every other refresh rate is good imho. It was always the 23 Hz refresh rate (not 24 Hz or any other one) which was about 4 minutes out of the box.

But isn't that fixed? I added a note to Nvidia section:
Every Nvidia driver after 388.59 has a faulty updated HD Audio driver in the newer Windows driver installer packages. 456.71 fixes that issue.
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319
https://forum.doom9.org/showpost.php?p=1925217&postcount=1978

Klaus1189
26th February 2021, 19:24
Correction: ~53 minutes for my Nvidia.

Since I do not have a Intel CPU with Intel HD 630. How does this one do for a simple small HTPC. Any issues known?

brazen1
26th February 2021, 20:02
I get ~50 minutes in 23 Hz mode but that is nowhere near AMD :) Every other refresh rate is good imho. It was always the 23 Hz refresh rate (not 24 Hz or any other one) which was about 4 minutes out of the box.

But isn't that fixed? I added a note to Nvidia section:
Every Nvidia driver after 388.59 has a faulty updated HD Audio driver in the newer Windows driver installer packages. 456.71 fixes that issue.
https://forum.doom9.org/showpost.php?p=1913991&postcount=1319
https://forum.doom9.org/showpost.php?p=1925217&postcount=1978

That driver and my report was jumping the gun. I remember now. I always reboot after installing new drivers including that one to the best of my memory. I was so excited to see it remained working after the reboot (unlike other drivers) I reported here.

Unfortunately, after the next reboot, it failed. I spent time duplicating what I always do but never got it to work again. I chalked it up to I did something wrong in my 1st test that was off... possibly even not rebooting but thinking I did. Not sure? I definitely forgot to report back here to correct my post. Totally on me and my bad. Sorry. You can remove that 2nd 'fixed' update on the 1st page. The damn thing still doesn't work.

el Filou
26th February 2021, 20:49
Can anyone with a RX6000 card and an LG C9/CX OLED corroborate that it can do QMS, not blanking out for frame rate switches, like this user at AVS has experienced? https://www.avsforum.com/threads/2019-lg-c9%E2%80%93e9-dedicated-gaming-thread-consoles-and-pc.3123168/page-260#post-60426761QMS uses HDMI VRR internally, so this is strange. Do PC graphics cards support HDMI VRR?
It would need to at least be on for QMS to work.

Warlock
26th February 2021, 22:42
I've been using 461.72 for a couple days now. I've watched several mixed content videos and used many, many desktop applications. The only Manage 3D setting I've changed is Power Management Mode set to Adaptive. With and without madVR fwiw. The flickering and other complaints must be exclusive to elaborate conflicted setups, alpha/beta software, display type and/or choice of GPU. I constantly read complaints yet never experience any of them and the GPU driver is always to blame. Driver works fine here fwiw.

Has it just changed in the global settings tab?

VBB
26th February 2021, 23:35
'Adaptive' is the default now anyway, since they got rid of 'Optimal'. From an HTPC perspective, there is nothing to change in 'Manage 3D Settings'.

Asmodian
27th February 2021, 02:27
Now it is called 'Normal' not 'Adaptive'.

But it does work well for me, no benefit to 'Prefer maximum performance' for HTPC.

VBB
27th February 2021, 06:41
There you go. Shows how often I check those settings these days ;)

el Filou
27th February 2021, 17:08
I think it depends on the GPU. I still have Optimal, Adaptive, Max perf with a Pascal card even after DDU.

VBB
27th February 2021, 20:25
With the 46*.** drivers? I have a Maxwell card, and it shows only Normal and Max Perf.

Klaus1189
27th February 2021, 21:32
Only Normal and max Performance here too for an Ampere card

SamuriHL
27th February 2021, 22:33
On my 2070 it still shows adaptive. I just did a clean install of the driver.

Manni
28th February 2021, 02:04
Weird. Only normal and max perfect with my 3090.

Klaus1189
28th February 2021, 10:27
@VBB - "Maxwell":
• Normal
• Prefer maximum performance

@el Filou - "Pascal":
• Optimal power
• Adaptive
• Prefer maximum performance

@SamuriHL - "Turing"
• Optimal power
• Adaptive
• Prefer maximum performance

@Manni & @Klaus1189 - "Ampere":
• Normal
• Prefer maximum performance

I installed on my current Windows fresh install only:
1.) 461.40 from 2021-01-26, then
2.) 461.51 from 2021-02-05 and last
3.) 461.72 from 2021-02-25.

That is a really strange distribution between the architectures :confused:

Klaus1189
28th February 2021, 15:25
Is there is a Vega and/or Radeon VII user, who followes this thread?
If so, please test Hardware deinterlacer and color range - see details in first post of this thread. I do not know, but I think Vega and Radeon VII were both fine and the issues started in RX 5000 series. I still have my RX 5700 XT and can test myself.
I want to collect as much info as possible. Perhaps I can get AMD to recognize these video related bugs.

SamuriHL
28th February 2021, 16:12
To your question yes optimal is there and default for my 2070.

Sent from my SM-G998U1 using Tapatalk

brazen1
28th February 2021, 18:04
461.72 and all previous GRD versions I've always shown

• Optimal power
• Adaptive
• Prefer maximum performance

Maybe it's the difference between SD and GRD versions?

Klaus1189
28th February 2021, 18:42
@SamuriHL:
Thanks :)

@brazen1:
I have only installed 461.40 GRD, then 461.51 Hotfix and then 461.72 GRD on a complete fresh windows installation, I deleted all previous partitions during installation.

el Filou
28th February 2021, 18:45
With the 46*.** drivers? I have a Maxwell card, and it shows only Normal and Max Perf.Yes, 461.09. Maybe it depends on the Windows version? I'm still on 1909. (Edit: Game Ready Driver)

Manni
28th February 2021, 18:52
In case it makes a difference, I'm using studio drivers (461.72) and I'm on 20H2.

SamuriHL
28th February 2021, 19:26
I'm using GRD on whatever the hell version of windows is installed on that machine now. It's at least 20h2 but it might be something later than that at this point as I don't know what branch I have that machine set to at the moment.

huhn
28th February 2021, 19:34
just check the windows version number.

Klaus1189
28th February 2021, 19:57
search for "winver"

VBB
28th February 2021, 20:21
Perhaps there is a difference between Standard and DCH drivers?

"Standard" packages are those that do not require the DCH driver components.

"DCH" (Declarative, Componentized, Hardware Support Apps) refers to new packages preinstalled by OEMS implementing the Microsoft Universal Driver paradigm.

DCH drivers cannot be installed over a standard system, and Standard drivers cannot be installed over a DCH system.

To confirm the type of system you have, locate Driver Type under the System Information menu in the NVIDIA Control Panel.

I have always installed the standard version of every driver, including hotfixes. DCH installs the entire control panel via the Microsoft Store. I never liked that idea.

Klaus1189
28th February 2021, 20:27
I know that I have installed the Standard non DCH on my system.

SamuriHL
28th February 2021, 20:32
Yes guys I know how to find the version lol. I'm just not on that machine right now and won't be today. I always install the DCH version of the driver.

VBB
28th February 2021, 20:35
Aha! Looks like we're getting somewhere ;)

Manni
28th February 2021, 20:50
I always install DCH as well.

VBB
28th February 2021, 20:53
...and back to square one :P

oldpainlesskodi
28th February 2021, 21:06
@Klaus1189 - what colour issues are you referring too ? Full-Full-Full chain I see no issues at all.

Klaus1189
28th February 2021, 21:15
This issue can only be be observed in EVR (CP) and MPC VR in D3D9 mode, D3D11 is fine and also madVR is always fine. Setting doesn’t matter in madVR.

AMD states that Windows 10 App is fine and declare it is fine but it is NOT.

Yes guys I know how to find the version lol. I'm just not on that machine right now and won't be today. I always install the DCH version of the driver.

Haha :D :D

Calvi
28th February 2021, 22:42
461.72 Stutters for me unless I force v-sync on in Nvidia settings.
Rtx2070, dch, 20h2

I have always turned it on(so earlier drivers are probably all the same here), but tried with this version in response to the comments about not having to set anything.
Stutter is also prevented by reducing frames to 1 in mad-Vr but with v-sync on I can leave mad-vr at default settings.

VBB
28th February 2021, 22:55
That's the point, though. For the Nvidia 2-series and newer, set madVR frames presented in advance to 1. Then you can leave all Nvidia settings at defaults.

SamuriHL
28th February 2021, 23:13
My machine is 10.0.19042 for the record.

SamuriHL
28th February 2021, 23:16
As for the present frames in advance being set to 1, madshi somewhat alluded to the fact that the Envy is doing that, as well. Or something like it anyway.

VBB
28th February 2021, 23:18
I think he meant queue sizes in general are much smaller with Envy, but yeah, probably frames presented in advance as well.

SamuriHL
1st March 2021, 02:02
He may have but given that it's 2xxx based (and upgrading to 3xxx) I suspect the frames presented in advanced is very low.

oldpainlesskodi
1st March 2021, 11:32
@Klaus1189 - ok, understood.

Calvi
1st March 2021, 14:27
That's the point, though. For the Nvidia 2-series and newer, set madVR frames presented in advance to 1. Then you can leave all Nvidia settings at defaults.

Yes, agreed.

Comes down to which you prefer, driver at defaults or madvr at defaults (or more than 1 frame in advance).

I figure 3 frames in advance is more useful than v-sync off as i only watch video on the pc.

Would perhaps be good if there was a MadVR setting or it defaulted to request vsync on from the driver then it would make sense to leave the default leave up to application setting in driver.

I guess another option is to set an application profile if gaming on same pc and there is a desire for v-sync off for some applications.

Manni
1st March 2021, 20:10
Not sure if this is a known bug or not, so I thought I'd report it anyway. I let madshi know but he isn't aware of it and doesn't know the cause (driver and/or OS).

D3D11 rendering in fullscreen windowed doesn't work anymore for me (3090, 8bits full).

When tonemapping HDR to SDR, colors are completely wonky in full screen windowed (think Andy Warhol).

Until recently, I was able to deal with this by staying with 460.89.

Unfortunately, something changed (OS update? 20H2?) and I have this issue with any driver supporting 3090.

If you get out of fullscreen windowed (hover the mouse on the playbar, right click, move the player from full screen to window), colors are fine.

If you use D3D9 new path, colors are fine too even in full screen windowed.

Anyone else experiencing this? Do we know what broke it and when?

The only fix is to use D3D9, which isn't ideal.

I only have the issue with madVR as I think MPC-VR uses D3D9, so doesn't have the issue.

Klaus1189
1st March 2021, 20:23
I only have the issue with madVR as I think MPC-VR uses D3D9, so doesn't have the issue.

What happens if you enable D3D11 in MPC-VR settings?
Play video -> rightclick -> Filters -> MPC Video Renderer.

I'll take a look at it, but not now, I am so tired from work. Other users can check that issue also in the meantime.

VBB
1st March 2021, 20:42
Manni, you're not the first one to report this, but I haven't heard of a fix for those affected. Very strange issue indeed.

Manni
1st March 2021, 20:59
What happens if you enable D3D11 in MPC-VR settings?


Thanks, no issue with MPC-VR when using D3D11, so it's a madVR bug.

Manni, you're not the first one to report this, but I haven't heard of a fix for those affected. Very strange issue indeed.

Good to know it's not just me. Very weird indeed, and sorry it's the wrong thread as it's a madVR bug apparently, given that MPC-VR doesn't show the issue when using D3D11.

huhn
1st March 2021, 21:07
did you try the different FSE modes?

Manni
1st March 2021, 21:27
did you try the different FSE modes?

No difference, the only option that makes a difference is d3d11 vs d3d9.

Klaus1189
1st March 2021, 21:29
What different FSE modes?

huhn
1st March 2021, 21:31
you can get the old real FSE mode back with some compatibility changes.