Featured Custom Resolution Utility (CRU) (Monitor Overclock) 1.0.0

Custom Resolution Utility (CRU)


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.