View Full Version : AMD, Intel and Nvidia driver issues and last recommended version
hotripper
28th April 2019, 01:25
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.
Yep sounds exactly like what I was experiencing. My fix has worked for me. Sorry it didnt work for you. I cant go back to that driver, I game a lot and don't really wanna miss those updates as I actually play the ones they improved. And I have tried that driver and it only fixed it temporarily but after a couple of restarts over a few days it just came back. So might as well have latest driver, for me anyways. Seems like madvr might need a new update for the new cards but I believe he is busy with his project atm.
Havent noticed Nvidia container using high cpu, and I have been watching during trying to trubleshoot the stutter issue.
el Filou
28th April 2019, 10:23
I think the Display Container LS only happens if you use standby/sleep.
Klaus1189
28th April 2019, 10:55
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.
Well, ... there is nothing that needs to be added, except at least the devs should be paid great for their work if I consider the prices of the green cards.
@all:
What is exactly the problem some guys here have with AMD cards? I have several different ones here, I know these are not the fastest, but I am happy with them and these were not expensive.
DMU
28th April 2019, 13:02
@all:
What is exactly the problem some guys here have with AMD cards? I have several different ones here, I know these are not the fastest, but I am happy with them and these were not expensive.
My problem is described here (http://bugs.madshi.net/view.php?id=596).
Klaus1189
28th April 2019, 13:09
Thank you, what file were you playing? Does it occur on hdr demo videos as well, so I can test, too? Maybe you can provide a link to a HDR file. Are you using HDR passthrough or processed in madVR?
DMU
28th April 2019, 13:38
File here (https://4kmedia.org/samsung-wonderland-two-hdr-uhd-4k-demo/).
HDR passthrough.
Post about your results, please.
Klaus1189
28th April 2019, 13:59
Cannot download file, seems it has too many downloads.
I search for other sources. Do you have another source?
DMU
28th April 2019, 14:15
Lets try from here (https://drive.google.com/open?id=18kLHSAYc15AgDwQK3NOrdAHkXQp6ZXbI).
ashlar42
28th April 2019, 14:42
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.And what do you plan on using, if I may ask? I don't see much around supporting everything correctly.
One needs bitstreaming for all audio formats, proper HDR with metadata and autoswitching, proper refresh rates with autoswitching... is there something around that offers all that?
Klaus1189
28th April 2019, 17:06
It is not darker here. Only in FSE the composition rate is 60 which is wrong, but I don't know if it is an AMD issue or an Win 10 1809 issue, older versions of Win10 didn't had this issue. But it doesn't bother me, since I am fine in FSW, also the other issue is not relevant in FSW.
I tried to take screenshots directly but if you use passthrough the final pic is not displaying it right and in FSE I only got black picture, silly me, I knew that but forgot about it.
https://drive.google.com/drive/folders/1c0ZdBPOX6tsEHJ6FGdFPwzy-7JRHkXO4?usp=sharing
I do get wrong colors in FSE, see also this issue (https://forum.videohelp.com/threads/373216-MPC-BE-colors-wrong) on videohelp.com and also here (https://forum.videohelp.com/threads/329866-incorrect-collor-display-in-video-playback#post2045830) here, FSW are the right colors. It also happens on SDR videos, I have a sample video of natural green grass which shows it perfectly. If it is shown wrong it gets very unnatural green, see also the color pattern in one of the videohelp threads.
Side note: Please use matching refresh rates, on your pics you were using 60 Hz for 23 Hz content. Avoid 3:2 Pulldown. But maybe you are using motion interpolation in madVR? Some love it some hate it.
DMU
28th April 2019, 17:35
It is not darker here. I am fine in FSW.
I assume that you have Polaris, not Vega?
Side note: Please use matching refresh rates, on your pics you were using 60 Hz for 23 Hz content. Avoid 3:2 Pulldown. But maybe you are using motion interpolation in madVR? Some love it some hate it.
I understand this, but it does not cause me inconvenience.
I do not use Smooth motion.
Klaus1189
28th April 2019, 17:39
Yes, Polaris RX480. I have a Vega 64 also here, but can not test now.
Just take a look at 50p videofile displayed at 60 Hz, it looks awful, especially during pans. I can only recommend using matched refresh rates. In my opinion one of the most important things.
DMU
28th April 2019, 17:48
If possible, check this at Vega later. I think this is a problem of Vega.
Thank you for your recommendations. But I do not use content with a frequency of more than 30p.
Manni
28th April 2019, 20:14
And what do you plan on using, if I may ask? I don't see much around supporting everything correctly.
One needs bitstreaming for all audio formats, proper HDR with metadata and autoswitching, proper refresh rates with autoswitching... is there something around that offers all that?
Off topic, but yes, I have an Oppo 203 clone (no disc) that does all that perfectly, and I'm working with a software developer friend at the moment to get a better interface from an iPad with a popular front end, as the Oppo 203 wasn't supported.
All the other media players I've looked at have issues with video and/or audio. The Dune Pro 4K could have been a great option but it doesn't look like it will ever work properly with the current chipset.
We've managed to get DVD/BD/UHD BD Folders working with this Oppo 203 clone. Files (mkv, ISOs) are a no go for now, but I already have all my discs ripped as folders anyway. I'll simply have to convert my 300 3D BD ISO rips to BD folders if we don't find a solution to play files (this is a limitation on the Oppo app itself, so hard to overcome as we have no command to sniff on the network). This will cost storage for 3D (double the space vs ISOs), but as my 3D collection isn't really growing, not too much of an issue. That won't help you if all your collection is in mkv or ISOs and if you're not willing to convert it.
Of course this will only work when/if the Envy lands, there is no way I can use this without a 3D LUT and HDR dynamic tonemapping with pixel shaders. At least not with my JVC projector, as the tonemapping is ok but far from being as good as what madVR delivers.
So for now, my HTPC is still very much necessary, but hopefully not for long :).
EDIT: funnily enough, this is the post of the devil: my post count is 666 as of now :)
ashlar42
29th April 2019, 11:28
Off topic, but yes, I have an Oppo 203 clone (no disc) that does all that perfectly, and I'm working with a software developer friend at the moment to get a better interface from an iPad with a popular front end, as the Oppo 203 wasn't supported.Oppo 203 clone? Details in PM, if you can. Edit: don't worry I've found everything. After more than a decade of Kodi, I could not go back to a GUI like that but it's a very interesting development, for sure.funnily enough, this is the post of the devil: my post count is 666 as of now :)I lured you here, son. There's no escaping now. Surrender to the dark side. :devil:
:D
Manni
29th April 2019, 13:06
Oppo 203 clone? Details in PM, if you can. Edit: don't worry I've found everything. After more than a decade of Kodi, I could not go back to a GUI like that but it's a very interesting development, for sure.
:D
You must have missed the part where I mentioned the work I'm doing to get this supported with a very popular front end on any tablet, phone etc, so that you can select the title you want to watch on a modern, beautiful interface and get it to play on the clone.
Unfortunately this requires a PC/laptop as a bridge between the tablet/phone and the clone, but the result is great: pretty and fully-featured interface on iPad (search, categories, genres, etc), flawless playback for all content, zero driver/OS headaches :)
Again, not an option for me until Envy lands, but very much looking forward to testing this combo.
Sorry everyone for the OT, let's move on :)
Klaus1189
29th April 2019, 16:15
Manni, just one last time offtopic. What App are you using with your clone 203? Do you have any link for the app and the clone. I got it that there is work to do, but maybe I could need at least one thing of these in future for anything. I am open to see new things.
cremor
29th April 2019, 16:41
Important note about 430.39:
Many users (myself included) report about high CPU usage of the process NVDisplay.Container.exe. Nvidia acknowledged the bug here: https://forums.geforce.com/default/topic/1107325/geforce-drivers/official-430-39-game-ready-whql-display-driver-feedback-thread-released-4-23-19-/post/6036972/#6036972
Asmodian
29th April 2019, 19:18
Interesting, may be related to the stutter some users are also experiencing? I do not see any CPU usage by NVDisplay Container, all instances of it show 0% CPU usage, and I do not have stuttering.
hotripper
30th April 2019, 00:02
May be a sleep issue
I dont think it has anything to do with the stuttering issues, I have stuttering but do not see ANY apps or services utilizing cpu abnormally
Asmodian
30th April 2019, 00:21
Sleep works fine for me too. Hmm...
hotripper
30th April 2019, 00:44
They acknowledge the bug but dont say how theyre able to recreate the issue. lol. Could be anything.
hotripper
30th April 2019, 00:47
Customers = Beta testers!!! Apply at Nvidia. com
nevcairiel
30th April 2019, 00:51
Why would they tell you how to reproduce an issue? They are happy if you don't encounter it.
In any case, there is a Hotfix driver thats supposed to fix it:
https://nvidia.custhelp.com/app/answers/detail/a_id/4798
hotripper
30th April 2019, 01:06
It would be helpful knowing as to avoid reproducing the bug, in general, until a fix is released, which has been.
What does the CRD mean? 385.28 version seems unstable.The video images running on 385.28 version often go green while the playback.Furthermore,win10 18.09 and player often crash after changing screen refresh rate,for example,into 50hz(non-standard screen refresh rate)
The most point is that 385.28 version results in the wrong level of video images (images go grey)
Asmodian
2nd May 2019, 18:55
Odd, 1809 does have a new WDM version and 430.39 is the first driver that supports it. Have you tried 430.39 or 430.53?
CRD means Creator Ready Driver, less optimized for games and more for creative applications. Supposedly, there is apparently little difference at the moment.
To fix the levels simply go into the change resolution section of the Nvidia control panel and set it to "Use Nvidia color settings" and set the output dynamic range to full.
Hello,master asmodian.
If i go into the nvidia control panel
and 'set it to "Use Nvidia color settings" and set the output dynamic range to full',Seems MadVR doesn't work anymore.All depends on nvidia control panle i set up.If so, that kind of the change actually gets meaningless.Because all i want is based on madvr.The major purpose is to play 4k uhd hdr movies with madvr.if madvr doesn't work anymore,all really gets meaningless.
i did a simple test for 430.39 version running on MadVR.Sure the levels of 430.39 running on MadVR was right while the plackback of 4k uhd hdr movies.Unfortunatedly my cpu burden rate was heavy,it was up to 100%.So i gave up 430.39 version.
Asmodian
3rd May 2019, 08:33
430.53 is the hotfix driver (https://nvidia.custhelp.com/app/answers/detail/a_id/4798/~/geforce-hotfix-driver-version-430.53) for that issue.
and 'set it to "Use Nvidia color settings" and set the output dynamic range to full',Seems MadVR doesn't work anymore.All depends on nvidia control panle i set up.If so, that kind of the change actually gets meaningless.Because all i want is based on madvr.The major purpose is to play 4k uhd hdr movies with madvr.if madvr doesn't work anymore,all really gets meaningless.
This is not true. Setting those simply tells Nvidia what to do with the RGB data madVR gives it. Nvidia always does something with it and if you use the same setting as its defaults you get the same results.
Nothing madVR does controls how Nvidia's drivers set those settings, they simply default to some value for your display or you can manually set them. It is "use default" or "use as set", neither of those are "application controlled". If it defaults to limited for your display the drivers will compress whatever madVR sends. The drivers always assume the video they get (madVR's output) is full range, so if you set madVR to limited as well you get double range compression. With the drivers using limited range it is impossible to get madVR's full range output to the display as full range.
This applies to bit depth as well, whatever bitdepth is set is what is sent to the display, madVR cannot control what the driver does with the data it sends. If madVR sends 10 bit with the driver on 8 bit it will dither the 10 bit video to 8 bit before sending it to the display. If madVR is set to 8 bit but the driver is set to 12 bit it will convert madVR's output to 12 bit and send 12 bit to the display. If it defaults to use YCbCr 422 it will convert and mangle madVR's RGB output before sending it if you leave it on "Use default color settings".
I like setting those manually, that way you know what is happening to the video data. If you use full range RGB at the same bitdepth as madVR or higher nothing bad will happen to madVR's output.
@Asmodian
Thank you,master asmodian,for what you explain clearly.
I don't actually understand the relation between what MadVR does(MadVR outputs) and Nvidia control panel until you explain it above.So i will reset nvidia control panel to as you said or as you set.I will give up the default on nvidia control panel and set it to nvidia color control.Set desk color depth to 32bit,output color depth to 12 bpc,output color format to RGB,output dynamic range to full.If i do like that,whether I need to set MadVR to exclusive mode or not? Or i just need to set MadVR to windowed mode? if i set MadVR to windowed mode,nvidia will convert 8 bit color depth into 12 bit.If so,actual video effects or video images quality should be the same as you said above,doesn't it?
Asmodian
3rd May 2019, 18:41
Yes, either windowed or exclusive are fine with those settings, no quality loss. :)
Klaus1189, you might want to add to the first page the link to the 430.59 hotfix (https://nvidia.custhelp.com/app/answers/detail/a_id/4798) posted by Nevcairiel that resolves the high CPU usage in 430.39 (especially until there is an official driver resolving this), and document it for 430.39.
Klaus1189
5th May 2019, 12:49
Klaus1189, you might want to add to the first page the link to the 430.59 hotfix (https://nvidia.custhelp.com/app/answers/detail/a_id/4798) posted by Nevcairiel that resolves the high CPU usage in 430.39 (especially until there is an official driver resolving this), and document it for 430.39.
Done.
Manni, just one last time offtopic. What App are you using with your clone 203? Do you have any link for the app and the clone. I got it that there is work to do, but maybe I could need at least one thing of these in future for anything. I am open to see new things.
Need offtopic info ;)
semi70
6th May 2019, 12:58
so anyone found a fix for the stutter issues on rtx cards with the latest drivers? im stuck on old firmware because only way to avoid the stutters but missing out on this HDR update.
hajosattila
6th May 2019, 13:18
so anyone found a fix for the stutter issues on rtx cards with the latest drivers? im stuck on old firmware because only way to avoid the stutters but missing out on this HDR update.
Download this (https://forum.doom9.org/showpost.php?p=1871970&postcount=151)
Klaus1189
6th May 2019, 13:38
Also mentioned in first post. The second note in Nvidia section.
omgi0wn
8th May 2019, 20:34
I'm using 430.53 with my LG C8, but I don't seem to get the 10-bit or 12-bit options in the control panel anymore. Was looking to play movies with the 23Hz option in RGB Full @ 12 bpc in HDR.
I'm only getting the 8 bpc option, any ideas? In the past I thought I had the 12 bpc option.
Asmodian
8th May 2019, 21:15
I have a 12 bit option for 23Hz RGB using 430.53 on my C7. :confused:
kostik
8th May 2019, 22:36
I'm using 430.53 with my LG C8, but I don't seem to get the 10-bit or 12-bit options in the control panel anymore. Was looking to play movies with the 23Hz option in RGB Full @ 12 bpc in HDR.
I'm only getting the 8 bpc option, any ideas? In the past I thought I had the 12 bpc option.
Check if Deep Color is enabled on your C8 (Settings->Picture->Additional Settings->HDMI ULTRA HD Deep Color )
SamuriHL
8th May 2019, 23:37
Yea working fine for me on the C8 with my 1060 and 430.53.
omgi0wn
8th May 2019, 23:45
Check if Deep Color is enabled on your C8 (Settings->Picture->Additional Settings->HDMI ULTRA HD Deep Color )
Yea working fine for me on the C8 with my 1060 and 430.53.
Very strange. I do have Ultra Deep Color enabled, but still only getting the 8 bpc option. Do you get the option when only HDR is enabled or SDR too?
Also, are you getting it with 60 Hz or at lower framerates?
I'm wondering if the sound bar I'm plugged into is limited me to 8 bpc, although I can't imagine why it would since I thought I had seen 12 bpc in the past. I'll try checking a few more things again.
I guess one last question, is it displayed as your primary monitor or extended?
SamuriHL
9th May 2019, 00:49
You won't get it with 60 as that's not possible on HDMI 2.0. You'll only get the option for 12 bit when you've got 23Hz selected. HDR/SDR doesn't matter.
Asmodian
9th May 2019, 01:02
You need to be actually running 30 Hz or below to see the 12 bit option. You cannot just select the refresh rate, you have to apply it.
omgi0wn
9th May 2019, 16:27
You won't get it with 60 as that's not possible on HDMI 2.0. You'll only get the option for 12 bit when you've got 23Hz selected. HDR/SDR doesn't matter.
You need to be actually running 30 Hz or below to see the 12 bit option. You cannot just select the refresh rate, you have to apply it.
I do have 23 Hz selected, and applied, but I'm still not seeing the option.
Windows Advanced Display Properties shows that the screen is displaying at 23 Hz, as does mpc-be if I view the stats. Still not seeing the option in Nvidia Control Panel though.
I'll take some screenshots when I'm home, maybe I'm missing something.
SamuriHL
10th May 2019, 01:28
Really not sure what's happening in your case but at this point I'd use driver cleaner, nuke the thing, and install clean.
Manni
10th May 2019, 08:17
I do have 23 Hz selected, and applied, but I'm still not seeing the option.
Windows Advanced Display Properties shows that the screen is displaying at 23 Hz, as does mpc-be if I view the stats. Still not seeing the option in Nvidia Control Panel though.
I'll take some screenshots when I'm home, maybe I'm missing something.
That can be because you're using a recent driver with a custom resolution. You need to select a standard resolution to be able to select 12bits even at 23p in the nVidia control panel. 385.28 (if GTX) allows to select 12bits even with a custom res. I forgot when that got taken away. Otherwise DDU and driver reinstall as suggested might help.
el Filou
12th May 2019, 02:53
x7007 on the madVR thread saying NVIDIA driver 430.64 reverts the output dynamic range to Limited when TV is turned off/on: https://forum.doom9.org/showthread.php?p=1874202#post1874202Edit: works fine on my system tooNvidia GeForce 430.64 WHQL driver with the fix for the high CPU usage bug in 430.39.It also includes security fixes for those vulnerabilities:https://nvidia.custhelp.com/app/answers/detail/a_id/4797
x7007 on the madVR thread saying NVIDIA driver 430.64 reverts the output dynamic range to Limited when TV is turned off/on
Works fine here, as with previous driver.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.