Custom Resolution Utility (CRU)

[Squall Leonhart]

on nVidia drivers, Restart64 causes a race condition inside the desktops Explorer.exe process which results in a resource leak , this condition is not triggered through toggling the driver state manually in device manager.

under this condition, both video memory commit and working set grow in the following events

* Opening the start menu rapidly
* Turning a display on and off (with displays that are treated as disconnected when turned off, like tv's)
* changing the windows advanced performance settings

The first is only a few hundred MB's at a time, the second 2 can be gigabytes of memory each time you perform the action.

I suspect the cycle is too fast for the UMD state to complete unloading, else its crapping up the shell animations / dpi change automation.

after using Restart64, i can power cycle my tv until the kernel runs out of memory and display driver fails to recover from a TDR,

I caught this most recently when i noticed 14GB's memory and 5GB's of vram consumed by Explorer.exe, after Ryujinx's Vulkan failed to start correctly (Nvidia drivers don't handle vulkan overcommit at all)

[ToastyX]

(08-20-2022 07:01 PM)Squall Leonhart Wrote:  on nVidia drivers, Restart64 causes a race condition inside the desktops Explorer.exe process which results in a resource leak , this condition is not triggered through toggling the driver state manually in device manager.

under this condition, both video memory commit and working set grow in the following events

* Opening the start menu rapidly
* Turning a display on and off (with displays that are treated as disconnected when turned off, like tv's)
* changing the windows advanced performance settings

The first is only a few hundred MB's at a time, the second 2 can be gigabytes of memory each time you perform the action.

I'm not seeing increased memory usage with those actions. I do see increased memory usage from restarting the driver, but that happens for me even when using Device Manager, so your issue seems to be different. Does the problem happen with the restart64.exe that comes with CRU 1.4.1? https://www.monitortests.com/download/cr...-1.4.1.zip

The older version has a delay between stopping and starting the driver, so if it still happens with the older restart64.exe, then it's not a race condition. Does restarting explorer.exe work around the problem?

[Squall Leonhart]

Restart 1.3 can trigger it, if either or both of the driver unloaded dpi and loaded dpi are above 100% (native is 150% on my TV), i use 125% or 100% depending on if the tv is on or off respectively.

Restart 1.5 doesn't seem to have that condition and introduces the issue either way

It may be exploding an until now unknown bug in Explorer.exe regarding glyph or icon rendering, i did notice at 150% that during the restart process with 1.3, some icons do not finish redrawing on the task bar before the driver is started again.

[ToastyX]

(08-21-2022 08:29 AM)Squall Leonhart Wrote:  Restart 1.3 can trigger it, if either or both of the driver unloaded dpi and loaded dpi are above 100% (native is 150% on my TV), i use 125% or 100% depending on if the tv is on or off respectively.

Restart 1.5 doesn't seem to have that condition and introduces the issue either way

It may be exploding an until now unknown bug in Explorer.exe regarding glyph or icon rendering, i did notice at 150% that during the restart process with 1.3, some icons do not finish redrawing on the task bar before the driver is started again.

Is this with Windows 10 or 11? I'm not seeing the problem with Windows 10 regardless of the DPI. I don't think the redrawing has anything to do with the problem. That shouldn't affect actions after the redrawing is complete.

[sunurnuts]

can u make a setting to show and change the DPMS settings (power saving settings on the monitor EDID) https://en.wikipedia.org/wiki/Extended_D...ata_format Byte 24, Bits 7, 6, 5.

i changed this manually and it seems to make the monitor more responsive.
do you have any information on how the DPMS works (active-off) mode?

[JasonMT]

Is there a way to enable HDMI Forum VRR (not FreeSync) on AMD RX6000 GPU for TVs that don't support FreeSync?

[ToastyX]

(08-25-2022 03:28 PM)JasonMT Wrote:  Is there a way to enable HDMI Forum VRR (not FreeSync) on AMD RX6000 GPU for TVs that don't support FreeSync?

Does AMD support HDMI VRR? If the TV supports VRR, it should already be enabled unless the GPU or driver doesn't support it. The range is defined in the HDMI 2.x data block.

[ToastyX]

(08-25-2022 01:47 AM)sunurnuts Wrote:  can u make a setting to show and change the DPMS settings (power saving settings on the monitor EDID) https://en.wikipedia.org/wiki/Extended_D...ata_format Byte 24, Bits 7, 6, 5.

i changed this manually and it seems to make the monitor more responsive.
do you have any information on how the DPMS works (active-off) mode?

More responsive how? DPMS isn't used anymore. Windows and modern displays only support on and off. Active off was the lowest power mode and equivalent to what off is now.

[Squall Leonhart]

(08-21-2022 06:18 PM)ToastyX Wrote:  

(08-21-2022 08:29 AM)Squall Leonhart Wrote:  Restart 1.3 can trigger it, if either or both of the driver unloaded dpi and loaded dpi are above 100% (native is 150% on my TV), i use 125% or 100% depending on if the tv is on or off respectively.

Restart 1.5 doesn't seem to have that condition and introduces the issue either way

It may be exploding an until now unknown bug in Explorer.exe regarding glyph or icon rendering, i did notice at 150% that during the restart process with 1.3, some icons do not finish redrawing on the task bar before the driver is started again.

Is this with Windows 10 or 11? I'm not seeing the problem with Windows 10 regardless of the DPI. I don't think the redrawing has anything to do with the problem. That shouldn't affect actions after the redrawing is complete.

10, 19045.1889

[JasonMT]

(08-25-2022 06:46 PM)ToastyX Wrote:  

(08-25-2022 03:28 PM)JasonMT Wrote:  Is there a way to enable HDMI Forum VRR (not FreeSync) on AMD RX6000 GPU for TVs that don't support FreeSync?

Does AMD support HDMI VRR? If the TV supports VRR, it should already be enabled unless the GPU or driver doesn't support it. The range is defined in the HDMI 2.x data block.

Some users have found that AMD RX6000 series supports HDMI Forum VRR only when TMDS is being used (like at 4k60). But once the card goes into FRL mode, only FreeSync over HDMI becomes available and it won't support HDMI Forum VRR anymore. I was hoping there would be some way to trick the card into still using HDMI Forum VRR.