Monitor Tests Forum

Full Version: Custom Resolution Utility (CRU)
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
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 dealing with .inf files.

Download: - Source: - -

A message from ToastyX:

Creating and maintaining software is a lot of work, and I have provided updates and support for free over the years. I would like to continue providing updates and work on new ideas, but I need your support. If you find my software useful, please consider supporting me through Patreon:

[Image: patreon.png]

Requirements: Before doing anything, familiarize yourself with getting into safe mode in case you can't see the screen. If you don't have a recovery drive, press and hold the power button to shut off the computer while Windows is booting. Doing this twice should give you recovery options that you can use to get into safe mode: Troubleshoot > Advanced options > Startup Settings > Restart

Getting started:
  1. Run CRU.exe.
  2. Choose a monitor from the drop-down list.
    • "(active)" means the monitor is connected and recognized by the graphics driver.
    • "*" means changes were made and an override was saved in the registry.
  3. Edit the configuration as desired. Please read the sections below for more information.
  4. Repeat steps 2-3 for other monitors if required.
    • The "Copy" and "Paste" buttons at the top can be used to copy the resolutions, extension blocks, and range limits if included. It will not copy the name or serial number, but it will copy the inclusion of these items using the monitor's own information. Import follows the same logic unless "Import complete EDID" is selected.
  5. Click "OK" to save the changes.
  6. Run restart.exe to restart the graphics driver.
    • If the display does not return after 15 seconds, press F8 for recovery mode. This will temporarily unload all the EDID overrides without deleting them. Restart the driver again to reload any changes.
  7. Set the resolution in the Windows display settings. To set the refresh rate:
    • Windows 10: right-click on the desktop > Display settings > Advanced display settings > Display adapter properties > Monitor tab
    • Windows Vista/7/8/8.1: right-click on the desktop > Screen resolution > Advanced settings > Monitor tab
To reset a display back to the default configuration, use the "Delete" button at the top to delete the override from the registry and reboot. To reset all displays, run reset-all.exe and reboot. This can be done in safe mode if necessary.

Detailed resolutions:
  • Detailed resolutions are the preferred way to add custom resolutions. More detailed resolutions can be added using extension blocks.
  • The first detailed resolution is considered the preferred or native resolution. All other resolutions can be removed if they are not needed. The graphics driver will automatically add some common lower resolutions as scaled resolutions.
  • Use the timing options to help fill in the values:
    • "Manual" allows the timing parameters to be set manually. The dialog will always open in this mode.
    • "Automatic - LCD standard" uses standard timing parameters commonly used with LCD monitors and HDTVs.
    • "Automatic - LCD native" uses standard timing parameters for the native refresh rate. This may help when trying higher refresh rates.
    • "Automatic - LCD reduced" adjusts the timing parameters for some resolutions to reduce the pixel clock. This may help when trying higher refresh rates.
    • "Automatic - CRT standard" uses timing parameters compatible with CRT monitors.
    • "Automatic - Old standard" uses the GTF standard.
  • Pay attention to pixel clock limits:
Standard resolutions:
  • Standard resolutions are mostly useful for CRT monitors and for adding lower resolutions with LCD monitors. Do not add the native resolution as a standard resolution.
  • AMD/ATI only supports the resolutions in the drop-down list. Other resolutions will be ignored by the driver. These will be listed in gray.
  • NVIDIA does not support more than 8 standard resolutions.
  • Standard resolutions are limited to 60-123 Hz. Use detailed resolutions to add other refresh rates.
Extension blocks:
  • CRU can now read extension blocks from connected monitors with AMD/ATI and NVIDIA. Workarounds are no longer required for NVIDIA. CRU will automatically add a blank extension block in the registry and .inf files if necessary to work around NVIDIA driver issues.
  • Extension block types:
    • Use CEA-861 unless you need more standard resolutions. Note: NVIDIA requires at least 2 bytes left for data blocks or the driver may crash or ignore the override.
    • Use VTB-EXT to add more standard resolutions. Note: AMD/ATI only supports one VTB-EXT block, and it must be the last block in the list.
    • Default extension blocks are provided for compatibility with existing overrides. Avoid using this option. To read extension blocks from connected monitors with AMD/ATI and NVIDIA, reset the display first. Extension blocks that can't be read will appear as default extension blocks.
  • To manually add HDMI support, add an HDMI support data block, or import one of these extension block files:
  • To manually add audio support, add an audio formats data block and add the LPCM audio format, or import one of these extension block files:
Editing FreeSync ranges:
  • For DisplayPort monitors, use the "Edit..." button at the top to edit the range limits, and make sure "Include if slot available" is checked.
  • For HDMI monitors, edit the FreeSync data block in the first extension block.
  • CRU 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.
  • The video card will not reduce clock speeds when idle if the vertical blanking/total is too low. Horizontal values can still be reduced if necessary.
    • Older AMD/ATI cards require the "LCD standard" vertical blanking/total to reduce the memory clock when idle.
    • NVIDIA and newer AMD/ATI cards can handle some lower values depending on the resolution and refresh rate.
  • Older AMD/ATI cards have a design limitation that causes video acceleration to scramble the screen if the vertical blanking/total is below standard with the video card's memory overclocked or with multiple monitors connected. Skype is known to trigger this problem. Either don't overclock the video card's memory, or use the "LCD standard" vertical blanking/total.
Changes in 1.4.1:
  • Speaker setup: added new speakers from CTA-861-G
  • HDMI support: fixed undefined latency data saving as 2 ms (since 1.3.99-p1)
  • HDMI 2.0 support: preserve additional fields for HDMI 2.1
  • FreeSync range: added support for editing FreeSync 2 ranges
  • Added support for HDR static metadata blocks
Changes in 1.4:
  • Added support for DisplayID extension blocks:
    • Added support for "Type I" detailed resolutions.
    • Added support for tiled display topology data blocks.
  • Display properties: added support for ID serial number in EDID header
  • Detailed resolutions: added "Automatic - Old standard" timing option for GTF
  • TV resolutions: added new resolutions from CTA-861-G (requires driver support)
  • Colorimetry: added DCI-P3 standard from CTA-861-G
Changes in 1.3.1:
  • Fixed .inf export for Windows 10 Creators Update
  • Detailed resolutions: use CEA-861 timing parameters for 3840x2160 @ 60 Hz with "LCD standard" (use "LCD reduced" for old values)
  • Detailed resolutions: allow 0 back porch
  • TV resolutions: disable "Native format" for resolutions that don't support this option
  • Do not add blank extension block if no extension blocks exist by default
  • Allow invalid but possible product IDs when editing display properties
  • Fixed '&' character in monitor name and serial number not displaying correctly in detailed resolutions list box
  • Improved row spacing between UI elements with higher DPI settings
Changes in 1.3:
  • Added support for reading extension blocks from connected monitors with AMD/ATI and NVIDIA
  • Automatically add blank extension block in registry and exported .inf files to work around NVIDIA driver issues
  • Added support for multiple extension blocks
  • Added support for importing other types of extension blocks
  • Added support for VTB-EXT extension blocks (detailed/standard resolutions only)
  • Changed default TMDS clock to 340 MHz for new HDMI data blocks
  • Added support for HDMI 2.0 data blocks
  • Added support for HDMI FreeSync data blocks
  • Added BT.2020 formats in colorimetry data blocks
  • Added text file export (outputs hex values)
  • Improved UI scaling with higher DPI settings
  • restart.exe/restart64.exe: fix Start menu, search box, and Radeon Settings not responding after restarting
Changes in 1.2.6:
  • Fixed a bug affecting non-PnP monitors since 1.2.3 (invalid EDID version with new overrides)
Changes in 1.2.5:
  • Include range limits by default if min/max horizontal values match and certain conditions are met (for FreeSync monitors)
  • restart.exe/restart64.exe: restart Radeon Settings (cnext.exe)
Changes in 1.2.4:
  • Made range limits compatible with FreeSync monitors
Changes in 1.2.3:
  • Added basic support for range limits and serial number descriptors (use the "Edit..." button at the top)
  • Show included descriptors in the detailed resolution list
  • Added "Import complete EDID" option
Changes in 1.2.2:
  • Detailed resolutions: added "LCD reduced" timing parameters for 2560x1440 @ 144 Hz and higher resolutions
  • Extension block: added support for colorimetry and video capability data blocks
  • Redesigned icon to scale better with Windows 10's broken taskbar scaling
  • Fixed how disabled buttons appear with Windows 10
Changes in 1.2.1:
  • Detailed resolutions: added "LCD native" option
  • TV resolutions: added support for 4:2:0 resolutions
  • HDMI support: added support for HDMI resolutions, latency information, and supported content types
  • Fixed access violation in comctl32.dll message with higher DPI settings
  • Fixed layout issues with higher DPI settings and enabled DPI awareness
  • restart.exe/restart64.exe: implemented a better recovery mode
Changes in 1.2:
  • Added custom extension block editing
  • Added support for more than 8 standard resolutions (AMD/ATI only)
  • Added support for other standard resolutions (NVIDIA only)
  • Updated reset-all.exe to reset Windows resolution settings
  • Include new version of restart.exe/restart64.exe
Changes in 1.1.2:
  • Fixed HDMI audio not working with older AMD/ATI GPUs
Changes in 1.1.1:
  • Fixed monitors with invalid signal type information not working with AMD/ATI GPUs
  • Added "LCD standard" timing parameters for 3840x2160 @ 30 Hz and 1366x768 @ 60 Hz (use "LCD reduced" for old values)
  • Automatically enable extension block when importing extension block files
  • Show number of slots left
Changes in 1.1:
  • Import extension block from files (editing coming later)
  • Automatically fill in likely native resolution when adding a detailed resolution
  • Disable controls when deleting a monitor
Changes in 1.0.1:
  • Fixed .inf export
  • Added support for non-PnP monitors
  • Changed monitor list sorting
Older versions:

Using older versions is not recommended. Newer versions fix problems and add features. Please report any issues with newer versions that did not exist with older versions. Make sure to run reset-all.exe when testing different versions.

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?
It should work. Others are using it with Windows 8. What video card and monitor are you using?
(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?
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.
(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!
I have an issue not with this tool but rather with my monitor. A better explanation is available here: but basically, even with the Include extension block portion unchecked, I still get invisible HDTV resolutions. Any ideas?
Try removing the custom resolution from the NVIDIA control panel, then add it using CRU instead.
I have no resolutions added from nvidia's control panel. Here's a screenshot:


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.

Happens when I do a .inf mod as well.
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.
Reference URL's