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

Charky

18th April 2019, 12:21

385.28 GRD 2017-08-14 HDR passthrough OK
Win10 1809: Use this version if you want to use custom resolutions in 8bit and 12bit. If you want to use newer driver versions, you need CRU for custom refresh rates
I was able to test this more precisely once again yesterday...

385.28 perfectly switches from 60Hz/8bits to madvr-created custom 23Hz/12bits without a hitch. Atmos passthrough works (that may sound silly but I encountered HDMI sound issues with newer drivers as well...), HDR works, 12 bits works like a charm, it's the perfect driver for me. I need a default 60 Hz since I also use my HTPC for internet browsing, YouTube watching, gaming via streaming...

I would have used CRU with newer drivers but, somehow, the "front porch" value found by madvr for each and every optimized timings (1276) was too high and CRU wouldn't let me use it (red-colored text, "ok" button blanked).

If I may add, even with newer drivers, I never could switch from stock 60Hz/8bits to a CRU-created custom 23Hz/12 bits.

60Hz/8 bits could only be switched to custom 23Hz/8 bits. 12 bits had to be activated before the switch (as already evidenced and documented by many).

Bottom line : as much as it pains me to use an almost 2 years-old driver (I'm a mad updater :D), 385.28 saves my ass one more time, as it already had by allowing me to create a custom res for my Sony HW40ES, something other drivers wouldn't let me...

NM20

18th April 2019, 14:18

Go back to an earlier driver (385.28 recommended) or upgrade the projector. :)

The magenta bug is gone on the new (2019) 4K models, it doesn't happen in 8bits or 12bits, at any frame rate, which makes using 8bits an option again.

With older models, 385.28 only has the magenta bug at 4K60 8bits. There is no magenta bug at 12bits (though colorspace is forced to YCC 422 internally when using RGB or YCC444, irrespective of the frame rate, which hopefully will be solved on the new models, it won't be on the old ones).

Every driver post 385.28 breaks something. The only advantage to using a more recent driver with a GTX card is 3D. Otherwise stick to 385.28.

I think 391.24 is the last driver where the magenta bug is not with 12bits as well as 8bits, at all frame rates. However the video levels are borked in 12bits if using video levels, and you can't select 12bits in a custom res. Of course 3D only improved with 391.35, so it's one or the other. Then after 398.11 you lose HDR passthrough as well.

Again, 385.28 is the driver to use with GTX (not an option with RTX), unless you really have to use a more recent driver for whatever reason, or a frame drop in 3D every 13min instead of every 3 minutes is good enough motivation to deal with all the other issues.

Hopefully the next major driver branch coming up this month should allow at least some of us to upgrade, especially if HDR passthrough is supported again.

Klaus1189, if you think it's useful, please could you link to this post in the first post, as a "note to JVC projector owners with nVidia GPU"? Thanks!

That is a huge help and plenty of detail, thank you. It was a 3d film that it wasn’t working for and causing the bug, I don’t watch many 3d films and it looks like it will even fewer going forward!

I thought at first it may be some MADVR setting, such as report BT2020 that was causing it.

What I can’t understand is how it worked recently and I have upgraded the driver every iteration because I also use the PC for gaming. However, now it has gone bonkers again.

I am amazed no one has created some sort of software solution to the issues. Thanks again for the help.

Aemstel

18th April 2019, 16:38

AFAIA CLSID's Nvidia inspector profile resolves it in every case but it also seems it either has been fixed or is a rare occurrence when upgrading. Perhaps keeping track of which versions caused it isn't worthwhile at all. Does anyone still have this issue?

I agree with you. It's hard to pinpoint what's going on. I had the stuttering with 425.31 driver and rolled back to 418.91 and all was smooth again. However, I tried 425.31 again after reading about clsid's (thank you!) Nvidia settings. I tried those settings and all is smooth now. I can't be sure if the settings actually fixed it or something else caused the stuttering before. In any case, those settings are worth trying out for anyone experiencing stuttering issues.

NM20

19th April 2019, 18:29

I am on the latest Nvidia drivers and all of a sudden when playing a frame packed 24p film via MPC with Mad VR it has the magenta display no matter whether I pick 8 bit or 12 bit on the Nvidia CP.

I am using a JVC projector, but on an earlier driver this didn't happen and 3d films were fine. What can I do?

I have sorted the issue.

I had ticked ‘Report BT.2020’ under my calibration settings in Mad VR for BT.709. Once I unticked this, the magenta issue was gone.

Klaus1189

20th April 2019, 11:27

NM20

20th April 2019, 14:28

@GTPVHD thank you, do you have more info about Intel? I think it's time to add info for Intel users.

@NM20 and Manni should I remove the Nvidia Note about magenta bug and JVC projectors in the first post?

@all if you have any info about Intel or you think that something is missing and should be added, please let me know.

Thank you :)

I think it was useful information. My solution may help some people too, so whatever you think is best.

Manni

20th April 2019, 21:54

@GTPVHD thank you, do you have more info about Intel? I think it's time to add info for Intel users.

@NM20 and Manni should I remove the Nvidia Note about magenta bug and JVC projectors in the first post?

@all if you have any info about Intel or you think that something is missing and should be added, please let me know.

Thank you :)

NM20 made a mistake, there is no reason for checking “report BT2020” with a rec-709 calibration. The magenta bug is still an issue for many JVCs, so I would leave the link as it might be useful for others.

kostik

23rd April 2019, 14:45

https://www.nvidia.com/en-us/geforce/news/mortal-kombat-11-game-ready-driver/

Nvidia GeForce 430.39 WHQL driver, should be the WDDM 2.6 driver but Win10 May 2019 update still not yet officially released.

New branch... [r430_34-5] WDDM 2.6. Finally it switches to HDR mode immediately and they fixed the 'bug' where seek bar unhidden was causing the screen to change to SDR mode and once hidden again to HDR. I hope metadata is also fixed, waiting for the experts test :)

j82k

23rd April 2019, 15:39

It's even in the release notes of 430.39:

Fixed Issues in this Release[madVR][HDR]: MadVR is not rendering videos in HDR mode using MPC player. [200505657]

grendelrt

23rd April 2019, 15:47

New branch... [r430_34-5] WDDM 2.6. Finally it switches to HDR mode immediately and they fixed the 'bug' where seek bar unhidden was causing the screen to change to SDR mode and once hidden again to HDR. I hope metadata is also fixed, waiting for the experts test :)

Is HDR metadata being passed correctly (not 1000/20 for everything)?

j82k

23rd April 2019, 16:21

4000 nit metadata is passed correctly. HDR triggering when madVR is set to 8-bit works too. So far so good.... :)

Klaus1189

23rd April 2019, 16:30

Do custom refresh rates work on Win10 1809 without CRU (https://forum.doom9.org/showthread.php?p=1868928#post1868928) in 430.39?

nevcairiel

23rd April 2019, 16:34

Do custom refresh rates work on Win10 1809 without CRU (https://forum.doom9.org/showthread.php?p=1868928#post1868928) in 430.39?

You should always prefer to use CRU in any case, it gives you far better control.

SamuriHL

23rd April 2019, 18:39

Manni

23rd April 2019, 18:50

I like this driver very much. It looks to me like they fixed the metadata but I have no real way to confirm. HDR triggers perfectly. I'm very pleased. I think we have a new baseline driver. Of course, others will need to chime in here.

Only checked briefly with my LG 4K monitor, the HDR metadata passthrough is fixed and it looks like it was able to switch to HDR in 8bits.

I'll report back if I see any issues with the JVC later tonight.

Looks like a good one though :)

brazen1

23rd April 2019, 19:16

I've installed the new nVidia driver 430.39. It is now once again allowing madVR to switch HDR mode. It has also rectified the long lingering audio problem - Multi channel vs stereo auto switch dependent on AVR state on and off.

As expected, nVidia no longer supports 3D. It has been completely removed from the driver install. So far I have installed 3D vision from an older driver. I get a notice that 3D vision does not match the new graphics driver after installing it. I also ran the 3D .reg file in madVR. The 3D option no longer shows up in Windows display properties or NCP. I did attempt to play a 3DMVC.iso in PowerDVD. 3D mode does not engage. I also tried MPC-BE. It displays some strange SBS and then does engage 3D mode. This is a frame packed MVC iso. It shouldn't go into SBS mode imo.

I don't want to spend anymore time fussing with this new driver and I will be reverting back to 416.81 video drivers. Instead of editing those drivers and applying the 388.59 audio driver (bug free) as I've been doing in the past, I will be attempting to use the newer 430.39 audio driver which at this time appears to also be bug free. This combo will update me to the newest working audio and video drivers that meet my demands.

*edit*
The audio bug still exists using the 430.39 driver. It doesn't survive a reboot. I will be using 388.59 audio driver with 416.81 video driver as usual.

SamuriHL

23rd April 2019, 19:19

Yea I've been watching Infinity War since I installed it and it's flawless. I'm also running 1903 so having a driver that truly supports it and works for everything else is great. And hopefully the RTX owners can chime in on how it works for them, as well. I landed a new job so I started a rebuild of my HTPC. At some point I'll likely get a 2070 for the new 9900k I'm building. Would love to know we have a new baseline driver that works for everyone.

NoTechi

23rd April 2019, 20:42

As expected, nVidia no longer supports 3D.

This is crazy ... in other words no more driver updates from now on .... :(
Time to start to look for AMD

NoTechi

hotripper

24th April 2019, 01:24

*edit*
The audio bug still exists using the 430.39 driver. It doesn't survive a reboot. I will be using 388.59 audio driver with 416.81 video driver as usual.

Audio bug??? What is the issue? Just curious

ryrynz

24th April 2019, 01:54

One page back...

No auto switch from stereo to multiple speaker setup in Windows Audio considering if AVR state is On or Off.

grendelrt

24th April 2019, 02:03

I launched a couple HDR games in Windows on the new 430.39 driver and they both reported 1000/400 metadata. Looks like it still doesn't update per game, but its no longer 1000 /20 :/

NoTechi

24th April 2019, 10:20

What would be the best way to use an older audio driver? Not sure if it is the audio bug but from time to time windows audio is on stereo. Just a reboot fixes this.
Another problem is that I can't select Atmos anymore even though it was working for some time. Maximum I can select is 7.1. My guess is that this is also caused by communicating wrong EDIT information between AVR and Windows thats why I would like to try an older audio driver.

NoTechi

clsid

24th April 2019, 13:06

Has 430.39 fixed the stuttering problems that some were having with previous drivers?

Manni

24th April 2019, 17:24

I launched a couple HDR games in Windows on the new 430.39 driver and they both reported 1000/400 metadata. Looks like it still doesn't update per game, but its no longer 1000 /20 :/

I don’t think the OS has ever reported dynamic HDR metadata. It’s always been fixed. Not sure if the games ask for various values or not.

I can only confirm that with film content, HDR passthrough works fine and reports the actual metadata sent by madVR.

It doesn’t solve any of the outstanding issues on the JVCs (mainly the forced YCC422 in 12bits in RGB or YCC444), but it doesn’t seem to make anything worse.

Apart from the zapping of 3D, it looks like a pretty good driver, and the only one that users of RTX cards can use if they want HDR passthrough to work with madVR.

SirMaster

24th April 2019, 17:37

This is NVIDIA Profle Inspector tool with an optimized profile for MPC-HC/BE.

Download (https://www.sendspace.com/file/ohoudl)

Most important settings it uses:
Power management mode = Adaptive
VSync = on
GSync = off
SLI = off
Prefer NVIDIA on Optimus systems

Is there a way to check if this actually worked?

I tried running this on my system with RTX 2060 on 430.39 driver, but how do I know it actually did something?

I thought I would see something like vsync ON in my nvidia control panel settings, but even after running the .bat file it still says "use application setting" for vsync in my control panel for example.

grendelrt

24th April 2019, 18:28

I don’t think the OS has ever reported dynamic HDR metadata. It’s always been fixed. Not sure if the games ask for various values or not.

I can only confirm that with film content, HDR passthrough works fine and reports the actual metadata sent by madVR.

It doesn’t solve any of the outstanding issues on the JVCs (mainly the forced YCC422 in 12bits in RGB or YCC444), but it doesn’t seem to make anything worse.

Apart from the zapping of 3D, it looks like a pretty good driver, and the only one that users of RTX cards can use if they want HDR passthrough to work with madVR.Yeah I have no frame of reference since it has never worked correctly since I have had my hdr projector. I was hoping the metadata for each game would at least have the peak brightness output, such as 4000,1000,10k nits etc.

Nicog

24th April 2019, 21:48

Has 430.39 fixed the stuttering problems that some were having with previous drivers?

Yes, at least better than previous driver (I didn't tried w/o vsunc ON).

Klaus1189

25th April 2019, 12:44

I updated some stuff in the first page, if something is missing or probably wrong, let me know

clsid

25th April 2019, 15:20

Is there a way to check if this actually worked?

I tried running this on my system with RTX 2060 on 430.39 driver, but how do I know it actually did something?

I thought I would see something like vsync ON in my nvidia control panel settings, but even after running the .bat file it still says "use application setting" for vsync in my control panel for example.You can use the NvidiaProfileInspector tool to view all application profiles on your system. The .bat file adjusts the settings of the "Media Player Classic" profile. It doesn't change your global defaults.

Nicog

25th April 2019, 20:18

Yes, at least better than previous driver (I didn't tried w/o vsunc ON).

Yesterday when I installed it it worked (no stuttering). Today it's dead (like previous drivers in fact, and also on non HDR content).

I'm back to 418.91, and now it's works fine...

I'm the only guy who has this issue?

hotripper

25th April 2019, 23:17

Yesterday when I installed it it worked (no stuttering). Today it's dead (like previous drivers in fact, and also on non HDR content).

I'm back to 418.91, and now it's works fine...

I'm the only guy who has this issue?

What issue stutter? I have it stutter issues too. I found a workaround for now though.

sat4all

26th April 2019, 09:34

Guys,

Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start.

Nicog

26th April 2019, 09:35

Massive stutter (different of what I had without FSE ou without sync ON on HDR).

Maybe an issue with my config...

What workaround are you speaking about Hotripper?

SirMaster

26th April 2019, 14:19

You can use the NvidiaProfileInspector tool to view all application profiles on your system. The .bat file adjusts the settings of the "Media Player Classic" profile. It doesn't change your global defaults.

Oh yeah that makes sense, thanks.

I'll just have to apply them manually then I think as I use MPC-BE rather than MPC-HC.

For some reason with madVR in MPC-HC I get crashing all the time (like when going fullscreen or resizing the window), but I do not ever with MPC-BE. I suspect it's some conflict with LAV filters being used by default in MPC-HC compared to internal filters included with MPC-BE, but the errors are beyond my debugging capabilities.

I also get some massive posturization when switching to full-screen often with MPC-HC, but never with MPC-BE.

Sorry doesn't belong in this thread anyways.

clsid

26th April 2019, 14:49

The profile works for MPC-BE as well.

The crash dialog should usually indicate where the crash happened. Post screenshots.

I doubt it is because of LAV Filters. Most likely a driver issue.

SirMaster

26th April 2019, 14:55

The profile works for MPC-BE as well.

The crash dialog should usually indicate where the crash happened. Post screenshots.

I doubt it is because of LAV Filters. Most likely a driver issue.

I can if it's something you think you or someone else would want to troubleshoot.

Though driver wasn't my first guess because it only happens in HC and not BE, but you know way more about this stuff than I do. Happens with both the 417 and 430 driver I had on that system. I know it's some madVR .ax file that it says is the "cause", but again, madVR is running exactly the same in BE heh.

I shall post it in the MPC-HC thread? I won't be able to until Sunday night anyways.

hotripper

26th April 2019, 19:00

Massive stutter (different of what I had without FSE ou without sync ON on HDR).

Maybe an issue with my config...

What workaround are you speaking about Hotripper?

Here: https://forum.doom9.org/showpost.php?p=1872824&postcount=55968

So far this makes 3 of us with 2070s and stutter

cremor

27th April 2019, 08:52

clsid

27th April 2019, 13:30

Yes, that should be fine too.

Manni

27th April 2019, 13:47

I'm back to 385.28 for now as I needed 3D to calibrate my PJ :)

Until a new version of windows forces me to upgrade, I don't see why I should lose such an important functionality for no benefit (I have a 1080ti).

Hopefully nVidia with put HDMI 3D support back (I did request it), but I'm not holding my breath.

It might be more realistic to prevent an OS upgrade from 1809. Unfortunately MS doesn't make that easy, even when editing group policies. You can delay it, but you can't stop it.

chros

27th April 2019, 15:13

Yes you can, use LTSB. (see my signature)

Manni

27th April 2019, 15:40

Yes you can, use LTSB. (see my signature)

I thought LTSB only delayed updates for 2-3 years? It's better than six months, but you still can't stop the upgrades, unless it has changed since I last looked at it.

Anyway I don't really want to do a full re-install, my HTPC has Pro x64, I don't have an Enterprise license.

huhn

27th April 2019, 18:49

do you really want to run a 2-3 year old OS?

if intel 3D playback works i have a theoretical workaround in my head.
and there is still navi.

Manni

27th April 2019, 20:20

do you really want to run a 2-3 year old OS?

if intel 3D playback works i have a theoretical workaround in my head.
and there is still navi.

All the security updates are applied. And yes, frankly I would be happy with 1809 in three years for a HTPC. What's wrong with that? The only need to update is to try to fix what they have broken over time.

If 385.28 had the better 3D that later drivers have, it would really be perfect.

Anyway I'm in the process of moving away from the HTPC altogether for film playback, provided that Envy delivers what we expect. Too much hassle really between OS, drivers and other issues.

Klaus1189

27th April 2019, 20:30

huhn

27th April 2019, 20:31

so you don't want to replace hardware ever?

el Filou

27th April 2019, 22:39

Carefull with the new driver it cause high cpu usage, nvidia Container LS alone take about 30% from my cpu, had to stop it and disable auto start.I can confirm. Here it takes up 100% of one CPU core.
I prefer to restart the service. Anyone knows what disabling that service does exactly?
I know the Telemetry isn't necessary, but I thought the Display Container was needed.
Edit: answering myself: NVIDIA Control Panel won't open if this service is not running. Display mode change via other means, reading GPU sensors, and NvAPI still seem to work fine. I guess you can still manually restart the service if you need to access NVIDIA Control Panel.

Manni

27th April 2019, 22:53

I understand fully your point, but all that is needed, is a graphics chip manufacturer that supplies drivers with 3D support and all other features working which is updated to run on actual and future OS versions. Sounds easy in theory ...

And when did that last happen? :)

What makes you think it will be any different in the future? :)

This thread really show the poor state of drivers/OS incompatibilities.

Frankly, they could have released a driver with everything working (HDR passthrough and HDR API in 8bits) before axing 3D... but they didn't.

semi70

27th April 2019, 23:10

Here: https://forum.doom9.org/showpost.php?p=1872824&postcount=55968

So far this makes 3 of us with 2070s and stutter

I have a 2080 and I have the stutter issue too. I have no problems at all when im on the 418.91 driver. everything after that version I have the stutter issue. madvr is not reporting any problems and I tried every proposed fix posted here with no improvements.
when im in windowed mode there is no stutter too. it seems to be a full screen exclusive mode issue.
its a shame Im stuck on this driver now that they have released a HDR fix on the latest too.