Custom Resolution Utility (CRU)

[ToastyX]

Custom Resolution Utility (CRU) allows custom resolutions to be defined for both AMD/ATI and NVIDIA GPUs by creating EDID overrides directly in the registry without having to deal with inf files.

http://www.monitortests.com/cru-1.0.zip

If you find this software useful, donations are welcome (but not required).

Requirements:

• Windows Vista or later (Windows XP does not support EDID overrides)
• AMD/ATI or NVIDIA GPU (Intel's driver does not support EDID overrides)
• Display must report a working EDID
  

Quick start:

1. Choose a display from the drop-down list.
   • "(active)" means the display is connected and the configuration is active.
   • "*" means changes were saved and an override is in effect.
     
2. Edit the configuration as desired.
   • The first detailed resolution is considered the preferred or native resolution. To make games use a higher refresh rate, define it as the first detailed resolution.
   • At least one detailed resolution should be defined. All other resolutions can be removed if they are not needed.
   • NVIDIA users must uncheck "Include extension block" to get custom resolutions to show up.
     
3. Repeat steps 1-2 for other displays if required.
   • The "Copy" and "Paste" buttons can be used to copy all the resolutions from one display to another.
     
4. Click "OK" to save the changes.
5. Reboot.
   

To reset a display back to the default configuration, delete the display and reboot. To reset all displays, run reset-all.exe and reboot. This can be done in safe mode if necessary.

Notes:

• This program adds monitor resolutions, not scaled resolutions. Lower resolutions will be scaled up if GPU scaling is enabled, but higher resolutions won't be scaled down by the GPU. Higher resolutions will only work if the monitor can handle them.
  

• Timing modes for detailed resolutions:
  • "Manual" allows the timing parameters to be set manually. The dialog will always open in this mode.
  • "Automatic - LCD standard" (formerly "Automatic - Best for LCD") uses timing parameters commonly used with LCD monitors and HDTVs.
  • "Automatic - LCD reduced" adjusts the timing parameters for certain resolutions to reduce the pixel clock. This may help when trying higher refresh rates.
  • "Automatic - CRT standard" uses timing parameters compatible with CRT monitors.
    

• Single-link DVI and HDMI are limited to 165 MHz pixel clock unless the video driver is patched:
  • AMD/ATI Pixel Clock Patcher
  • NVIDIA Pixel Clock Patcher
    

[Valdez]

Hi!

Thank you for making this application, it is very handful!

I used it in win7 without problems, but i just upgraded to win8, and your application doesn't work there. I can add custom resolutions and everything, but in windows 8 they doesn't appear.
What do you suggest?

[ToastyX]

It should work. Others are using it with Windows 8. What video card and monitor are you using?

[Valdez]

(12-13-2012 04:07 AM)ToastyX Wrote:  It should work. Others are using it with Windows 8. What video card and monitor are you using?

MSI R6870 Hawk and Asus PA246Q with displayport. It worked fine on windows 7.
In the list, where i have to choose the monitor, there my monitor appears three times. Is it possible, i choosed the wrong one?

[ToastyX]

It's possible you're editing the wrong one. Each connection creates a separate entry, and there may be outdated entries that aren't being used anymore. CRU should pick the first active entry it finds, but if you're not sure which is which, delete all of them and reboot. Then the list should only have entries that are currently active.

With AMD/ATI, sometimes the highest refresh rate has to be listed as the first detailed resolution or the video driver will ignore it. You can also try unchecking "Include extension block" if that's checked.

[Valdez]

(12-14-2012 02:02 AM)ToastyX Wrote:  It's possible you're editing the wrong one. Each connection creates a separate entry, and there may be outdated entries that aren't being used anymore. CRU should pick the first active entry it finds, but if you're not sure which is which, delete all of them and reboot. Then the list should only have entries that are currently active.

With AMD/ATI, sometimes the highest refresh rate has to be listed as the first detailed resolution or the video driver will ignore it. You can also try unchecking "Include extension block" if that's checked.

Thanks, i copied the custom resolutions to all three entries, and now works fine. Thanks!

[Mangix]

I have an issue not with this tool but rather with my monitor. A better explanation is available here: http://forum.doom9.org/showthread.php?p=...ost1607421 but basically, even with the Include extension block portion unchecked, I still get invisible HDTV resolutions. Any ideas?

[ToastyX]

Try removing the custom resolution from the NVIDIA control panel, then add it using CRU instead.

[Mangix]

I have no resolutions added from nvidia's control panel. Here's a screenshot: https://dl.dropbox.com/u/102011983/high%...01080p.png

and

https://dl.dropbox.com/u/102011983/high%...nvidia.png

edit: for some reason, the checkbox in the second screenshot never seems to get properly applied. The first resolution under PC is always checked and always matches the current refresh rate. I'm not sure if this is intentional or an oddity. When I used to manually modify the EDID with a .inf file, I always increased the maximum supported resolution as well as set the signal type to HDMI-A(default is set to DVI-D even though the connection is made through HDMI).

edit2: this is also an oddity.

https://dl.dropbox.com/u/102011983/high%...nitor1.png

https://dl.dropbox.com/u/102011983/high%...nitor2.png

Happens when I do a .inf mod as well.

[ToastyX]

I just checked with a 1080p monitor. It's a quirk with the NVIDIA driver. This happens when the refresh rate is set to 59 Hz when only 60 Hz is defined. The HD listing disappears when set to 60 Hz. This stops happening if I change the 60 Hz resolution to something like 59.94 Hz.

The monitor information is correct. Real-time is just the EDID directly from the monitor. The EDID override still takes precedence.