AMD, Intel and Nvidia driver issues and last recommended version

[Jeff R 1]

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!
The Magenta bug us gone for the JVC 2019 projector modesl, so I'm assuming that a firmware update for my 2018 model will fix that, or is it a physical problem that can't be fixed with a firmware update ?
And yes, I find that if I use any of the NVIDIA drivers where the meta date is correct, I get no HDR pass-through, I have to use one of the borked drivers so I can use the "slider" control in the Gamma settings.
Any other driver that isn't borked and the setting is gone, it's not even "greyed" out.

Why is that, do the drivers have to be defective to enable HDR pass-through to work properly and have the projector switch automatically between SDR and HDR ?

[Klaus1189]

Did you try fullscreen exclusive (madVR settings) for HDR passthrough on your Nvidia?

[Manni]

The Magenta bug us gone for the JVC 2019 projector modesl, so I'm assuming that a firmware update for my 2018 model will fix that, or is it a physical problem that can't be fixed with a firmware update ?
And yes, I find that if I use any of the NVIDIA drivers where the meta date is correct, I get no HDR pass-through, I have to use one of the borked drivers so I can use the "slider" control in the Gamma settings.
Any other driver that isn't borked and the setting is gone, it's not even "greyed" out.

Why is that, do the drivers have to be defective to enable HDR pass-through to work properly and have the projector switch automatically between SDR and HDR ?

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models (and earlier ones). They have never done that in the past (fixing things on an older model once new models are released). Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.

[Jeff R 1]

Did you try fullscreen exclusive (madVR settings) for HDR passthrough on your Nvidia?
Not in that case where the other drivers don't work with the HDR switching.
I don't care for fullscreen exlusive mode though, but I will see, just to satisfy my curiosity.

All the chapters in the movie are gone and I like to see how many frames per second, etc...

[Jeff R 1]

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models. They have never done that in the past (fixing things on an older model once new models are released. Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.
I have a GTX 1080ti, so I will try again with 385.28, I had to get NVIDIA to give me a link as it did not show up in the list of old drivers.
I restored the HTPC back to a restore point and it messed things up a bit, the NVIDIA control panel could not be accessed afterwards.

When you say the 2019 models, are we talking about late of 2019 or the new NX/RS series that have just been released ?

EDIT:
That was 398.11 that wouldn't work with HDR switching, I'll have to contact them again to get 385.28

EDIT:
I Googled it and it came up. :-)

[Jeff R 1]

385.28 works fine if you have a GTX. You get HDR passthrough and the slider works. If you have an RTX, you need 430.64.

I highly doubt that JVC will release a f/w fix for the magenta bug on the 2018 models. They have never done that in the past (fixing things on an older model once new models are released. Given the issues they have with the new models, the chances that they would spend any development time on an older model to fix such a bug (supposing it's not a hardware issue) is close to zero. Of course, I hope for you that I'm wrong.
Hmmm.
With driver 385.28 installed, the mapping level slider for the auto tone mapping is not there, at this point it only appears when I install an NVIDIA driver with the bogus metadata, does the slider appear.
I have only what is boxed in, in green when I install driver 385.28, and nothing else.
The red box only shows when I install a driver with bogus metadata, but I do have the option of switching what is in the green box.

When I use my Panasonic UB900 (not UB9000), the option in the red box is also gone.
Not sure what's going on.

Is it because the Panasonic player and the driver with the correct metadata is sending the right metadata, is the reason I don't have the option in the red box ?
I suppose in the end it doesn't really matter, but sometimes it would be nice to use the "auto tone mapping slider.

Maybe I need to upgrade the firmware on the projector for things to work properly.
I guess that's the next step.

https://forum.doom9.org/attachment.php?attachmentid=16848&d=1558249471

[Manni]

2019 models = new 4K native models
2018 models (and previous) = older eshift models (not native 4K).

Which model do you have?

With a 2019 RS2000, I don't have any of the issues you are mentioning and we have the same GPU. That's with the latest publicly available f/w (2.01), and Windows 10 Pro x64 1809.

It sounds like you are not sending passthrough, so the JVC isn't detecting HDR10. Make sure that you have enable the automatic HDR10 detection in the JVC and that the user mode selected has a PQ gamma selected..

All of this works fine with 385.28 (with 3D) or the latest 430.64 (no 3D).

Be careful when you install 385.28, windows will replace it at the next update with a slightly more recent driver. You have to roll that driver back, and then 385.28 will stay.

[Jeff R 1]

I need to update my firmware, and maybe that will solve the problem; I have a RS1000 _ should have mentioned that earlier. :o

I'm pretty sure it's switching to HDR, when I play a 4K UHD movie with MPC-HC and MadVR, the screen goes black for a moment and I can hear the projector adjusting things (I'm assuming the iris).
Plus when MPC-HC is not in full screen mode, the desk top is totally blown out and over saturated with colour indicating that the projector is in HDR mode.
At any rate I will make sure that the auto HDR detection mode on the JVC is turned on.

I'm running W10 Home edition x64 1809.

And about the Windows auto driver update.
Type in "Control Panel" in search and look for "System" in the old control panel.
Go to "Advanced System Settings" in the left pain.
In that window, click on "Hardware" and then "Device Installation Settings"
Click on "NO" in that box to keep Windows from updating any drivers.

Thanks !
I will report back.

[Manni]

And about the Windows auto driver update.
Type in "Control Panel" in search and look for "System" in the old control panel.
Go to "Advanced System Settings" in the left pain.
In that window, click on "Hardware" and then "Device Installation Settings"
Click on "NO" in that box to keep Windows from updating any drivers.


That doesn't work here.

Even asking CRU not to update the driver doesn't work here.

But after asking the roll-back, it stays at 385.28.

I'm testing 430.64 at the moment to see if I can live with it.

[SamuriHL]

I've got 430.64 stable on my 2070 so far. It seems like nVidia hasn't broken anything since they released the useful fixes in the first 430.xx driver for us. I'm using windowed mode and it's working quite well for me.

[Manni]

I've got 430.64 stable on my 2070 so far. It seems like nVidia hasn't broken anything since they released the useful fixes in the first 430.xx driver for us. I'm using windowed mode and it's working quite well for me.

Yeah, if they hadn't axed 3D mvc support it would be close to perfect. I guess with an RTX you don't have much of a choice, especially if you want HDR passthough. We have more options with GTX GPUs.

[Jeff R 1]

Updated the firmware on the JVC to 2.01 and that didn't solve the colour space problem when everything is pink and green, I'm not even sure if that update was supposed to fix that ?

Still have the problem with the HDR slider not appearing, not sure what to do, maybe contact JVC.
You can see in the screen shots that it is in HDR mode, but in the Gamma window the Max CLL/Max Fall is blank ???

In this case I'm using my Panasonic UB900.
Resetting the Panasonic and the JVC back to factory specs, doesn't solve the problem.

[SamuriHL]

Yeah, if they hadn't axed 3D mvc support it would be close to perfect. I guess with an RTX you don't have much of a choice, especially if you want HDR passthough. We have more options with GTX GPUs.

I plan on rebuilding my 3770k with the 1060 (with far less ram given the mobo issue) to watch 3D on my old plasma screen. With that one obviously I'm going to have the same kinds of issues you're facing and have to use an old driver. I'll get there.

[Manni]

Updated the firmware on the JVC to 2.01 and that didn't solve the colour space problem when everything is pink and green, I'm not even sure if that update was supposed to fix that ?

Still have the problem with the HDR slider not appearing, not sure what to do, maybe contact JVC.
You can see in the screen shots that it is in HDR mode, but in the Gamma window the Max CLL/Max Fall is blank ???

In this case I'm using my Panasonic UB900.
Resetting the Panasonic and the JVC back to factory specs, doesn't solve the problem.

You're clearly not sending HDR (unless you're using a disk without metadata to test, the slider only appears when the title contains valid metadata, many of them don't). Also you can't post pictures here, it takes ages for approval.

You need to set colorspace to auto in the JVC, or not use 12bits output in the source (due to a forced YCC 422 colorspace bug in the JVCs when using YCC 444 or RGB 12bits).

This is getting off topic here if you have the issue even with a UB900, you should ask in a JVC owner's thread. Click on the rs2000 link in my sig (calibration thread for 2019 models) and we'll sort it out there.

[Jeff R 1]

You're clearly not sending HDR (unless you're using a disk without metadata to test, the slider only appears when the title contains valid metadata, many of them don't). Also you can't post pictures here, it takes ages for approval.

You need to set colorspace to auto in the JVC, or not use 12bits output in the source (due to a forced YCC 422 colorspace bug in the JVCs when using YCC 444 or RGB 12bits).

This is getting off topic here if you have the issue even with a UB900, you should ask in a JVC owner's thread. Click on the rs2000 link in my sig (calibration thread for 2019 models) and we'll sort it out there.
So what is a disc that has meta data, I know the ones from Disney don't, do you know of any that have for sure, eg "Life Of Pi" maybe ?

I have my colour space in the NVIDIA control panel set to 12bit and the JVC is set to auto colour space.
I also have RGB and 0-255 range in the NVIDIA control panel as well.

I can see my own photos, but others can't _ that's silly.

In one of the photos it shows that the JVC has indeed switched to HDR.

It lists under Info.
Colour Space YUV
Colourimetry BT.2020
HDR HDR10 (ST.2084)

When I exit MPC-HC it lists HDR as SDR _ it switches back as it's supposed too.

I'll try some different discs.

Thanks !

[Manni]

So what is a disc that has meta data, I know the ones from Disney don't, do you know of any that have for sure, eg "Life Of Pi" maybe ?

I have my colour space in the NVIDIA control panel set to 12bit and the JVC is set to auto colour space.
I also have RGB and 0-255 range in the NVIDIA control panel as well.

I can see my own photos, but others can't _ that's silly.

In one of the photos it shows that the JVC has indeed switched to HDR.

It lists under Info.
Colour Space YUV
Colourimetry BT.2020
HDR HDR10 (ST.2084)

When I exit MPC-HC it lists HDR as SDR _ it switches back as it's supposed too.

I'll try some different discs.

Thanks !

As I said, it's off topic here given that you have this issue with a UB900 standalone player. It's only confusing to keep posting here. Post in one of the JVC owners' thread (as it's not HTPC related), or if you want me to help you, in the calibration thread linked in my sig where you can post pictures, and we'll take it from there. Life of Pi has no metadata in the US/UK (but some in Germany). Use any Sony title to be sure (Lucy, The Shallows...).

[Jeff R 1]

As I said, it's off topic here given that you have this issue with a UB900 standalone player. It's only confusing to keep posting here. Post in one of the JVC owners' thread (as it's not HTPC related), or if you want me to help you, in the calibration thread linked in my sig where you can post pictures, and we'll take it from there. Life of Pi has no metadata in the US/UK (but some in Germany). Use any Sony title to be sure (Lucy, The Shallows...).
It's not off topic, I mentioned the UB900 in one post all the rest are to do with my 1080i video card, my HTPC and why the slider only appears when I use a borked NVIDIA driver _ that was the original issue.

Please answer this question, if a disc has no meta data to send to the HTPC, then where is the borked NVIDIA driver getting it from ?
Or I suppose that is the problem with those drivers, they're creating meta data out of thin air...

I will play Lucy and see.

Here's a link to the photo's.
https://discuss.avscience.com/index.php?topic=1850.msg12603#msg12603

The first two photos show no meta data when using a driver when the correct meta data is present, this assumes it's normal since many discs don't have the meta data ?

The last photo shows what it looks like when I use one of the borked drivers, and this also pertains to the question above.

[Manni]

It's not off topic, I mentioned the UB900 in one post all the rest are to do with my 1080i video card, my HTPC and why the slider only appears when I use a borked NVIDIA driver _ that was the original issue.

Please answer this question, if a disc has no meta data to send to the HTPC, then where is the borked NVIDIA driver getting it from ?
Or I suppose that is the problem with those drivers, they're creating meta data out of thin air...

I will play Lucy and see.

Here's a link to the photo's.
https://discuss.avscience.com/index.php?topic=1850.msg12603#msg12603

The first two photos show no meta data when using a driver when the correct meta data is present, this assumes it's normal since many discs don't have the meta data ?

The last photo shows what it looks like when I use one of the borked drivers, and this also pertains to the question above.

Yes the borked drivers invent this metadata when not present, or replace the valid one when present. It's the same for all the disks, whether they have metadata or not. That's why and how they are borked. If you don't have this issue with the UB900, then you have no issue. Please don't post in two different thread about the same issue, that's even more confusing.

[Jeff R 1]

Yes the borked drivers invent this metadata when not present, or replace the valid one when present. It's the same for all the disks, whether they have metadata or not. That's why and how they are borked. If you don't have this issue with the UB900, then you have no issue. Please don't post in two different thread about the same issue, that's even more confusing.
See this thread where I posted some more photos with Lucy.

https://www.avsforum.com/forum/46-post-testing-area/3068564-jeff-s-photo-thread.html#post58074788

The problem was me not understanding what was specifically going on with the borked NVIDIA drivers.

And to answer you question in the other forum, the other movies that don't have any meta date are: "Life Of Pi" (Canadian Version), "Thor Ragnarok" (Canadian version) and "The Kid Who Would Be King" (US Version)

The last photo where the "slider" appears was just a simple screen shot from the manual to show a point of reference, it does not represent any disc. It was simply to show that the slider was missing from the other two photos

For anyone else that has just come here and seen this post, here is the link to the other forum where my photos are posted.

https://discuss.avscience.com/index.php?topic=1850.msg12603#msg12603

Thanks for you patience Manni !

[SoySauceWDF]

Anyone still experiencing stuttering after applying the NVInspector fix on RTX cards? A/V Sync issues as well? RTX 2080 ti, most recent driver (430.64), madvr, MPC-HC.

[videoh]

What is the "NVInspector fix"? Thank you.

[huhn]

it helps some turing user that have problem with madVR and stuttering where the madVR OSD doesn't notice anything at all.

it pretty much enables/forces vsync for mpc-hc(which doesn't make any sense but it works so...) changes the power saving setting to adaptive and a setting for optimus system so the nvidia card is used instead of the igpu. at least that's what i remember from it.

AFAIK clsid is behind that profile.

[videoh]

Where does one get this "fix"?

[clsid]

Here: nvidia profile for mpc (https://forum.doom9.org/showthread.php?p=1871970#post1871970)

[videoh]

Thank you!

[SamuriHL]

I made the same changes to my main profile manually and it seems to work for me on my 2070. I'm using windowed mode in madvr.

[Klaus1189]

Nvidia released 430.86.

[SamuriHL]

Oh god let's see what they broke now...er, I mean, oh yey! :D

[Jeff R 1]

According to this, still no 3D and no more 32bit OS support.
If one isn't gaming, why bother with any of these new drivers ?
I suppose it's part of the hobby bordering on the verge of obsetion and curiosity.

https://us.download.nvidia.com/Windows/430.86/430.86-win10-win8-win7-release-notes.pdf

[nevcairiel]

32-bit support was canceled a long time ago already. And 3D is not going to come back, they have said as much.

[Asmodian]

The new 430.86 drivers work well for me with my 2080 Ti. Still only 8 bit for custom resolutions but HDR works properly with both 8 and 10 bit. Also madVR's custom resolution tool works.

[ryrynz]

Am wondering if anyone can get these or any other 400 series drivers working with madVR custom res on the 10 series cards.

[SamuriHL]

I'm actually wondering what nVidia's long game is with these drivers. They're releasing both the game and studio drivers. So far they're identical but clearly they plan on diverging them. It'll be interesting to see which series of driver ends up being best for us in the HTPC world.

[nevcairiel]

I'm actually wondering what nVidia's long game is with these drivers. They're releasing both the game and studio drivers. So far they're identical but clearly they plan on diverging them. It'll be interesting to see which series of driver ends up being best for us in the HTPC world.

I don't think they plan on diverging them. Its just a marketing thing. Studio drivers come out less frequently and focus on stability and fixes for creator tools, while Game Ready drivers come out more frequently for game improvements - but when they do come out, they just contain the same stuff.

[chros]

I just tried out a quadro driver (385.69 (https://www.nvidia.com/download/driverResults.aspx/123914/en-us) that is close to 385.28) during the weekend hoping for 10 bit output, since somebody mentioned this:
- still no luck with the LG B8, there's only 8 or 12 bits selection.

So I wonder, maybe the display reports 8/10/12 bits and nvidia driver automatically offers the 10 bit. Who knows ... :)

[clsid]

You don't need quadro driver for high bitdepth output.

Using 10bit has no advantage over 12bit output, and is also not possible.

[SamuriHL]

I don't think they plan on diverging them. Its just a marketing thing. Studio drivers come out less frequently and focus on stability and fixes for creator tools, while Game Ready drivers come out more frequently for game improvements - but when they do come out, they just contain the same stuff.That would be disappointing. I was hoping that the studio drivers would focus on the things that are important for video and not break those things like the game drivers tend to do. But maybe that's far too optimistic. Sigh.

Sent from my Pixel 3a using Tapatalk

[chros]

Using 10bit has no advantage over 12bit output, and is also not possible.
Thanks, and do you know why it is impossible with nvidia drivers?
I wanted to experiment with banding on my display.

[Warner306]

It isn't impossible. Nvidia simply reverts to the highest supported bit depth reported by the display.

[chros]

It isn't impossible. Nvidia simply reverts to the highest supported bit depth reported by the display.
Thanks, that's what I think as well. Has anyone tried to modify this EDID entry with CRU? If so, how?
(Once again, I'm just curious whether there's a difference between 10 vs 12 bits output using the given setup.)

[oldpainlesskodi]

Thanks, that's what I think as well. Has anyone tried to modify this EDID entry with CRU? If so, how?
(Once again, I'm just curious whether there's a difference between 10 vs 12 bits output using the given setup.)

I could only get 10bit by using a displayport to HDMI adapter, so I would be curious to see if someone can get it working over hdmi - I'm not aware it has been done though.

[chros]

I could only get 10bit by using a displayport to HDMI adapter
Quadro or normal driver? Did you notice any improvement?

[oldpainlesskodi]

Quadro or normal driver? Did you notice any improvement?

Tried both, and none that I could see over 12 bit. Also, on my 1080, I cant seem to use any of the WDDM 2.6 drivers without getting insane banding, regardless of my settings, so I am on driver 425.31 until I/someone gets to the bottom of the issue.

[clsid]

Does 8bit output give you banding?
The native bitdepth of the screen is usually lower than what it accepts as input. If it does crappy conversion without dithering it can result in banding. madVR has an option to specify the native bitdepth.

[oldpainlesskodi]

It's happens with any WDDM 2.6 driver with the latest version on windows for me. It was fine before the Win update, now if I use wddm 2.6 I get banding with any bit depth.

On wddm 2.5, it's fine. My panel is a true 10bit panel, so I dont get banding (that I have seen) sending either 8bit dithered, or 12bit.

As an example, Spears_Munsil_Quantazation_Test_2160p.mp4 is a rainbow mess of banding using wddm 2.6, but on wddm 2.5, it looks as it should, with the 8bit (left hand side) window showing more banding steps.

[chros]

I could only get 10bit by using a displayport to HDMI adapter, so I would be curious to see if someone can get it working over hdmi - I'm not aware it has been done though.
Hmm... Maybe this way (https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU?pid=8763#pid8763)? :) (I haven't tried it yet.)

Does 8bit output give you banding?
Yes, using PC mode on LG B8, even in SDR mode, but HDR mode is truly something :)

The native bitdepth of the screen is usually lower than what it accepts as input.
You are right, it suppose to have 10 bit native, but it supports 12 bit (also madvr reports it based on the EDID info).
If it does crappy conversion without dithering it can result in banding.
Yes, that's the case: almost all the image processing is disabled in the chip of the TV. That's why I'm curious what we can do about it (still using PC mode to get chroma 4:4:4).
madVR has an option to specify the native bitdepth.
Yes, I've set it to "10 bit or more", nvidia display driver only allows 12 bit.
That's where the idea came from, maybe ...

Or maybe enabling dithering in nvidia driver (https://hub.displaycal.net/forums/topic/how-to-enable-dithering-on-nvidia-geforce-with-windows-os/)? :)

[huhn]

if the bit input is higher then the output bit deep nvidia is dithering by default. and everything else doesn't really apply to madVR.

this is super easy to test and it clearly works with full range too...
there are other situation where this reg edit may help but i can't see one for madVR.

the bit 12 situation is a dumb limitation on nvidia but if you get banding at 8 bit then 10 bit is very very very unlikely to help at all specially if 12 bit doesn't help. if the end device has a bad conversations(as they usually have) only 8 bit should help because it is a lot harder to add banding to a 8 bit dithered image compared to a 10 or 12 bit dithered image.

[oldpainlesskodi]

Hmm... Maybe this way (https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU?pid=8763#pid8763)? :) (I haven't tried it yet.)

Never seen it work myself, so look forward to your method :)

Or maybe enabling dithering in nvidia driver (https://hub.displaycal.net/forums/topic/how-to-enable-dithering-on-nvidia-geforce-with-windows-os/)? :)

Yep, if you go onto the nvidia forum, you'll notice people basically saying in the latest version of windows with a wddm 2.6 driver its busted and no longer works.

See here: https://forums.geforce.com/default/topic/1082681/geforce-drivers/is-it-possible-to-quot-port-quot-dithering-from-nvidia-x-server-to-geforce-driver-/23/

And, there is an easier way to add dithering, try this app :

https://jmp.sh/NGf7DJj

the settings I use are 1 (enable) 2 (10bit) 4 (temporal). Then use task manger to kill, and vola...done

You can check by opening up regedit and going to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\State\DisplayDatabase/your driver (in my case 07e0_ed) and its all done (the app has added DitherRegistryKey).

Still seems its borked with wddm 2.6 and the latest win10 version though.

Update:

one other observation. In device manager, using wddm 2.5 it picks up my display as generic pnp monitor. Using wddm 2.6, it actually detects my Samsung 8 Series, so something is clearly wrong, maybe with the way it reads the Edid under 2.6 perhaps.

[janos666]

It's happens with any WDDM 2.6 driver with the latest version on windows for me. It was fine before the Win update, now if I use wddm 2.6 I get banding with any bit depth.

Ah! I guess this is what I uncovered today. I suspected it will turn out to be a Win10 1903 / nVidia 430.x driver issue. (Although I guess we should check this with and AMD card as well, could still be Microsoft's fault.)
400.39 is already WDDM 2.6 and that's the first in the 400 series to fix the metadata bug. I don't see myself downgrading to 398.11 now because I also play some games on this PC (both new and old, randomly).

[chros]

I don't see myself downgrading to 398.11 now because I also play some games on this PC
398.11 wouldn't be enough: it blocks the usage of custom resolutions, even using CRU. So, you'd need go back to 385.28.

@Klaus1189, can you remove this line from the nvidia summary section, until someone definitely confirms it?
"If you want to use newer driver versions, you need CRU for custom refresh rates."


And, there is an easier way to add dithering, try this app : https://jmp.sh/NGf7DJj
the settings I use are 1 (enable) 2 (10bit) 4 (temporal). Then use task manger to kill, and vola...done

You can check by opening up regedit and going to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvlddmkm\State\DisplayDatabase/your driver (in my case 07e0_ed) and its all done (the app has added DitherRegistryKey).
Nice, although it doesn't work on my system (see my signature) :) There's no "State" in the mentioned registry path.

I applied the hack manually but I didn't notice anything different at all.

I could only get 10bit by using a displayport to HDMI adapter, so I would be curious to see if someone can get it working over hdmi - I'm not aware it has been done though.

I gave it a try but no luck so far (https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU?pid=8850#pid8850).

Maybe I'll try the quadro driver one more time with the CRU EDID hack.

Otherwise @clsid will be right :)

if you get banding at 8 bit then 10 bit is very very very unlikely to help at all ... if the end device has a bad conversations ...
It does in PC mode, since almost all the image processing are disabled.
You're right in theory, but we can only be certain if we manage to test it, but until I won't get 10bit option ... :)