Threaded Mode | Linear Mode

***ToastyX*** · 03-14-2025, 06:55 PM

(03-14-2025 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.

(03-14-2025 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: 03-14-2025, 08:19 PM by yenic)

(03-14-2025 06:55 PM)ToastyX Wrote:
(03-14-2025 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.

(03-14-2025 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.

FreeMyQ7HDR · (Last edited: Yesterday, 02:50 PM by FreeMyQ7HDR)

Hoping that someone here has experience with the issue I'm having with my TCL Q7 2023 version and my recently built windows 11 gaming pc. This tv has been, for the price, fantastic for viewing hdr,hdr10+ and dolby vision content on streaming services, youtube , plex and others with fire tv stick 4k and using the google tv included with tv. also series x outputs hdr 10 and dolby vision with no issues in games that support it. it's not the cable or input since I've tried them on series x and fire tv with no problems. so the hdr certification is "not found" under advanced display and display information. I'm assuming this is what's causing all the problems. the use hdr toggle shows up and when I turn it on it switches to hdr probably in windows 11 but the tv doesn't change anything. so it's like hdr is on in windows 11 but tv is still in sdr mode. it even shows peak brightness of 749 nits under display information while hdr toggle is on. it should be 592 according to a review I read but at least it recognizes it. unfortunately this q7 has no way of manually switching on hdr. it has to detect it and then will change automatically to hdr. I downloaded the CRU app and used some ai recommendation to change the 3 luminance numbers but that did nothing but change the peak brightness nits and didn't get my tv to recognize that hdr is on and change to hdr. I changed the luminance to its original numbers and I haven't touched anything else in the app. is there anything that can be done in the app that can it make my tv recognize that hdr is being turned on or really anything else that can help solve this problem?

yenic · Yesterday, 07:14 PM

(03-14-2025 06:55 PM)ToastyX Wrote:
(03-14-2025 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?

I ran CRU, deleted the nonexistent 4th monitor, and then did not run restart.exe and just restarted the machine instead. No more undetect and redetect of a device. Also reopened CRU and the 4th monitor remained gone. Running restart seems to bring back the phantom monitor though.

Nothing good could have come out of having a mystery monitor like that. I can see why people have success using DDU with the 'remove present and non-present monitors' option, which I always use when I have to use DDU.

***ToastyX*** · Yesterday, 10:18 PM

(Yesterday 07:14 PM)yenic Wrote: I ran CRU, deleted the nonexistent 4th monitor, and then did not run restart.exe and just restarted the machine instead. No more undetect and redetect of a device. Also reopened CRU and the 4th monitor remained gone. Running restart seems to bring back the phantom monitor though.

Nothing good could have come out of having a mystery monitor like that. I can see why people have success using DDU with the 'remove present and non-present monitors' option, which I always use when I have to use DDU.

What you're describing is completely normal and not an issue. CRU doesn't really delete inactive monitors. It only deletes the last read EDID from the registry so it doesn't appear in the list. You would have to use Device Manager with "Show hidden devices" enabled to see the inactive monitors, but normally you can ignore them. Even if you use DDU, you will be left with an inactive monitor created by the basic display driver being active before NVIDIA's driver is installed. That shouldn't cause any issues.

Running restart.exe switches to the basic display driver briefly while NVIDIA's driver is restarting, so the inactive monitor becomes active briefly and the last read EDID is put back in the registry. The same thing happens if you disable and enable NVIDIA's driver using Device Manager. That is normal. What isn't normal is if you're getting the device connect sound during boot. That's a completely separate issue, and I don't see how deleting the cached EDID for an inactive monitor would have any effect. That's likely something NVIDIA's driver is doing, perhaps in response to something the TV is doing, like if the TV is disconnecting while HDR or VRR is being enabled, or the driver is crashing because of a bug and restarts, which would cause the basic display driver to be active briefly.

***ToastyX*** · Yesterday, 10:18 PM

(Yesterday 02:33 PM)FreeMyQ7HDR Wrote: Hoping that someone here has experience with the issue I'm having with my TCL Q7 2023 version and my recently built windows 11 gaming pc. This tv has been, for the price, fantastic for viewing hdr,hdr10+ and dolby vision content on streaming services, youtube , plex and others with fire tv stick 4k and using the google tv included with tv. also series x outputs hdr 10 and dolby vision with no issues in games that support it. it's not the cable or input since I've tried them on series x and fire tv with no problems. so the hdr certification is "not found" under advanced display and display information. I'm assuming this is what's causing all the problems. the use hdr toggle shows up and when I turn it on it switches to hdr probably in windows 11 but the tv doesn't change anything. so it's like hdr is on in windows 11 but tv is still in sdr mode. it even shows peak brightness of 749 nits under display information while hdr toggle is on. it should be 592 according to a review I read but at least it recognizes it. unfortunately this q7 has no way of manually switching on hdr. it has to detect it and then will change automatically to hdr. I downloaded the CRU app and used some ai recommendation to change the 3 luminance numbers but that did nothing but change the peak brightness nits and didn't get my tv to recognize that hdr is on and change to hdr. I changed the luminance to its original numbers and I haven't touched anything else in the app. is there anything that can be done in the app that can it make my tv recognize that hdr is being turned on or really anything else that can help solve this problem?

You shouldn't have to do anything. HDR certification is not required for HDR to function. The graphics driver is responsible for enabling HDR. What GPU do you have? How do you know HDR is not being enabled? Does the TV report if HDR is active?

Case · Yesterday, 11:02 PM

(Yesterday 02:33 PM)FreeMyQ7HDR Wrote: the use hdr toggle shows up and when I turn it on it switches to hdr probably in windows 11 but the tv doesn't change anything

Probably? Does the switch show as enabled? Have you run the HDR calibration app to check that HDR is working? What happens if you try to view actual HDR content? Remember that Windows UI is just SDR, so you might not see any difference just by enabling the HDR switch in Windows, depending on what your SDR brightness on your TV is and the setting of your SDR brightness slider in Windows.

(I use SDR mode at the more or less standard 120 nits, so the default SDR brightness setting when enabling HDR is way too bright and I have to set it down to like 10 to match my SDR brightness, but many people unfortunately crank SDR mode brightness on their monitors/TVs very high, so even the relatively high default might not look much different on their setups.)