Custom Resolution Utility (CRU)

[ToastyX]

(10-27-2019 07:21 AM)Shakko81 Wrote:  I found a solution: I had to delete the freesync block, then adding a new one with desired range will fix it. It will appear enabled on amd radeon panel and ofc will work.

Can you run reset-all.exe and restart, and then export the default configuration to a file and post it here so I can see what's different about the default FreeSync data block?

[EeK]

@ToastyX, I'm having a weird issue after using CRU, while on the latest Nvidia driver (441.08).

Prior to installing 441.08, I'd been using the 440.52 beta driver, as that was the only one with support for G-Sync on the LG C9 series of TVs.

Everything ran smoothly, and I was able to add a custom resolution of 3840x2160 with a refresh rate of 66Hz to my display, via CRU, selecting LCD standard as the timing. If I were to use NVCP, the only color format and depth available would be RGB and 8bpc, for some reason. With CRU, I could select YCbCr444/8bpc and YCbCr422/10 or 12bpc - the latter being my preferred choice.

As always, I used DDU before installing the new driver. The installation was successful, and I then used to CRU to add the same detailed resolution as before. However, after running restart64.exe to restart the graphic driver, my whole system rebooted and got caught in an infinite reboot loop.

I was only able to do something when Windows automatically prompted to boot into safe mode, after a few failed login attempts. I the uninstalled the driver, again using DDU, downloaded it once more and clean installed it a second time. Also for the second time, running CRU would result in the same issue.

This, time, I simply ran reset-all.exe while on safe mode and that stopped the infinite rebooting. However, I'm still unable to add a custom resolution at the desired refresh rate.

Do you have any idea what's causing this? It's the first time ever experiencing this issue, after literally years of using CRU. Aside from the display driver, nothing changed between 440.52 and 441.08. I'm still running the same (updated) version of Windows, the same TV (on the same firmware), etc.

[ToastyX]

(10-30-2019 02:48 AM)EeK Wrote:  Do you have any idea what's causing this? It's the first time ever experiencing this issue, after literally years of using CRU. Aside from the display driver, nothing changed between 440.52 and 441.08. I'm still running the same (updated) version of Windows, the same TV (on the same firmware), etc.

That can only be a driver bug. CRU only writes EDID overrides and doesn't do any driver modifications, so if you can get the driver to crash with CRU, then that's a driver bug. Even if CRU wrote garbage instead of a correct EDID, that shouldn't cause the driver to crash. Does the driver crash if you try to add the same resolution with the NVIDIA control panel?

[Pegasus78]

Hi Guys

I have a surface pro 3 with windows 10. I want to put the screen size the same as a Mobile like an iPhone but with max resolution possible.

Can I do this with CRU ? And how?
Thanks!

[ToastyX]

(10-30-2019 04:45 PM)Pegasus78 Wrote:  I have a surface pro 3 with windows 10. I want to put the screen size the same as a Mobile like an iPhone but with max resolution possible.

Can I do this with CRU ? And how?

If you mean centering a smaller resolution, CRU doesn't deal with scaling or positioning, but you can use CRU to create a custom resolution and then use Intel's control panel to set the scaling to center the image. I don't know if Intel's control panel offers that option with the Surface display like it does with external displays.

[EeK]

(10-30-2019 01:04 PM)ToastyX Wrote:  That can only be a driver bug. CRU only writes EDID overrides and doesn't do any driver modifications, so if you can get the driver to crash with CRU, then that's a driver bug. Even if CRU wrote garbage instead of a correct EDID, that shouldn't cause the driver to crash. Does the driver crash if you try to add the same resolution with the NVIDIA control panel?

With NVCP, any resolution of 3840x2160 with a refresh rate higher than 60Hz didn't get past the tests, so it couldn't be applied. That behavior only started after the latest driver (411.08). Before that, with either 440.52 or 440.97, I successfully added 4K resolutions of up to 66Hz, using NVCP (albeit with RGB as the only available color format, for some reason).

I tried again with CRU, and instead of using restart64.exe, I restarted Windows and rebooted the entire system. It worked! 3840x2160 at 66Hz successfully added, without the infinite reboot loop.

Still don't understand why I wasn't able to simply restart the graphics driver without rebooting the system, as I'd always done before, though. Very odd.

[ToastyX]

(10-30-2019 09:31 PM)EeK Wrote:  I tried again with CRU, and instead of using restart64.exe, I restarted Windows and rebooted the entire system. It worked! 3840x2160 at 66Hz successfully added, without the infinite reboot loop.

Still don't understand why I wasn't able to simply restart the graphics driver without rebooting the system, as I'd always done before, though. Very odd.

Even if the driver crashed while running restart64.exe, it shouldn't have caused a reboot loop. If you're willing to experiement, what happens if you disable and enable the GPU in Device Manager? If it crashes when disabling and causes a boot loop, it might actually be a bug in Microsoft's Basic Display Adapter driver, although that shouldn't listen to EDID overrides. If it crashes when enabling, it's definitely an NVIDIA driver bug. Then again, now that it's working, it might not crash at all.

[EeK]

(10-30-2019 09:49 PM)ToastyX Wrote:  Even if the driver crashed while running restart64.exe, it shouldn't have caused a reboot loop. If you're willing to experiement, what happens if you disable and enable the GPU in Device Manager? If it crashes when disabling and causes a boot loop, it might actually be a bug in Microsoft's Basic Display Adapter driver, although that shouldn't listen to EDID overrides. If it crashes when enabling, it's definitely an NVIDIA driver bug. Then again, now that it's working, it might not crash at all.

At this point, I'm honestly scared of trying anything else and messing up all of my settings again.

But another person on a different forum mentioned having the same issue as me, when trying to add a custom resolution via CRU. It's most certainly an Nvidia driver bug, as none of that was happening on previous versions, and the new driver won't even allow the same resolution/refresh rates as before.

[h72david]

(10-30-2019 09:31 PM)EeK Wrote:  

(10-30-2019 01:04 PM)ToastyX Wrote:  That can only be a driver bug. CRU only writes EDID overrides and doesn't do any driver modifications, so if you can get the driver to crash with CRU, then that's a driver bug. Even if CRU wrote garbage instead of a correct EDID, that shouldn't cause the driver to crash. Does the driver crash if you try to add the same resolution with the NVIDIA control panel?

With NVCP, any resolution of 3840x2160 with a refresh rate higher than 60Hz didn't get past the tests, so it couldn't be applied. That behavior only started after the latest driver (411.08). Before that, with either 440.52 or 440.97, I successfully added 4K resolutions of up to 66Hz, using NVCP (albeit with RGB as the only available color format, for some reason).

I tried again with CRU, and instead of using restart64.exe, I restarted Windows and rebooted the entire system. It worked! 3840x2160 at 66Hz successfully added, without the infinite reboot loop.

Still don't understand why I wasn't able to simply restart the graphics driver without rebooting the system, as I'd always done before, though. Very odd.

I have the same issue, it happens with these Nvidia drivers: 441.08 and 440.97, if it's a bug from Nvidia drivers hopefully it wil get fixed. I'll stick to the old drivers for now

[urkqsrk]

Hello, I have overclocked my monitor Philips 240V5QDSB (1920x1080 60hz stock) and reach 77hz with just add custom resolution in nvidia control panel (gtx 1060, HDMI cable) , now I trying to overclock with CRU, but even with 600x400 resolution I can't reach 78hz. My monitor just refuse to go over 77hz, do you have any idea what can cause this problem and is it possible my monitor to be locked up to 77hz?