Threaded Mode | Linear Mode

***ToastyX*** · Today, 06:55 PM

(Today 03:52 PM)yenic Wrote: Odd, it won't let me take screenshots in CRU or after making changes. Either way this is what it looks like after I change anything for any of my 3 monitors in CRU. I can't do any changes with CRU without this happening (not just changes to TV resolutions). The LG is on HDMI 2.1 (for no DSC at the panel's native 1440P 240Hz), and the Dells are on DP 1.1a I believe (enabling DP 1.2 in the monitor's settings disables HDCP support in NV drivers for some reason).
https://imgur.com/a/C59xLWj
and how it's supposed to look
https://imgur.com/a/t9rA6df

That shouldn't happen. You need to report that to NVIDIA. That's a bug in their driver.

(Today 03:52 PM)yenic Wrote: Here's the 4th mystery monitor that remains.
https://imgur.com/a/nMNJEF8

Running restart.exe would create an entry because the basic display driver is active while NVIDIA's driver is restarting, but I don't know why that would happen after rebooting. That would mean at some point in the boot process, that entry was active, then switched to a different entry for some reason. Do you hear a device connect sound during boot?

yenic · (Last edited: Today, 08:19 PM by yenic)

(Today 06:55 PM)ToastyX Wrote:
(Today 03:52 PM)yenic Wrote: Odd, it won't let me take screenshots in CRU or after making changes. Either way this is what it looks like after I change anything for any of my 3 monitors in CRU. I can't do any changes with CRU without this happening (not just changes to TV resolutions). The LG is on HDMI 2.1 (for no DSC at the panel's native 1440P 240Hz), and the Dells are on DP 1.1a I believe (enabling DP 1.2 in the monitor's settings disables HDCP support in NV drivers for some reason).
https://imgur.com/a/C59xLWj
and how it's supposed to look
https://imgur.com/a/t9rA6df
That shouldn't happen. You need to report that to NVIDIA. That's a bug in their driver.

(Today 03:52 PM)yenic Wrote: Here's the 4th mystery monitor that remains.
https://imgur.com/a/nMNJEF8
Running restart.exe would create an entry because the basic display driver is active while NVIDIA's driver is restarting, but I don't know why that would happen after rebooting. That would mean at some point in the boot process, that entry was active, then switched to a different entry for some reason. Do you hear a device connect sound during boot?

Maybe a newer NV driver would help with using CRU. I can't update it right now, been bad drivers lately.

I do hear a device connect on boot that I've been meaning to find out what it is. Perhaps I'll look at the event viewer and see what's going on finally.

Also on login, my screens sure blink a lot. About twice on startup. It's weird. I'm on the latest version of Windows11 but on a September 2024 NV driver so I guess that may be part of it. When I reinstalled this last-working NV driver, I used DDU and used its option to clear out hidden monitors. So I'm on a pretty clean slate I'd hope.