GUIDE: How to remove 4096x2160

Some 4K UHD TVs define 4096x2160 even though their native resolution is 3840x2160. This can cause scaling problems when games automatically choose the highest resolution or when using NVIDIA's Dynamic Super Resolution (DSR). This guide will show you how to disable 4096x2160 using Custom Resolution Utility (CRU).

4096x2160 can exist in these CTA-861 data blocks:

  • TV resolutions
  • HDMI support
  • 4:2:0 resolutions

Edit the CTA-861 extension block:

Edit the "TV resolutions" data block:

Delete all of the 4096x2160 resolutions:

Click the "OK" button.

Edit the "HDMI support" data block:

In the "HDMI resolutions" section, delete 4096x2160 @ 24 Hz if it exists:

Click the "OK" button.

Edit the "4:2:0 resolutions" data block if it exists:

Delete all of the 4096x2160 resolutions:

Click the "OK" button on all of the dialogs. Then run restart.exe or reboot.

After following this guide, 4096x2160 should no longer exist. To revert all changes, run reset-all.exe and reboot.

Custom Resolution Utility (CRU) 1.5.1

Changes in 1.5.1:

  • Audio formats: added new formats from CTA-861-G/H
  • Colorimetry: added ICtCp from CTA-861-H
  • DisplayID 2.0 detailed resolutions: fix "Reset" button resetting to 6 Hz when adding a new resolution
  • Tiled display topology: split vendor and product IDs to accommodate OUIs (2.0) and non-letter IDs (1.3)
  • List boxes now retain scroll position after editing

Custom Resolution Utility (CRU) 1.5

Changes in 1.5:

  • Added DisplayPort YCbCr color formats and maximum color depth (use the "Edit..." button at the top)
  • Added HDMI 2.1 features including maximum FRL rate, variable refresh rate, and display stream compression
  • New and improved timing options for detailed resolutions:
    • "LCD standard" has been split into "Automatic (PC)" and "Automatic (HDTV)" to better accommodate different display standards.
      The main difference is how they handle resolutions greater than 1920x1080 @ 60 Hz and 21:9 resolutions. "PC" favors CVT-RB, while "HDTV" favors CTA-861.
    • "LCD native" has been split into "Native (PC)" and "Native (HDTV)" for the same reason.
    • "LCD reduced" has been eliminated because it was too arbitrary and only worked for certain resolutions. Try "Exact reduced" for an alternative.
    • "CRT standard" is now "Automatic (CRT)" and includes 4:3/5:4 VESA DMT resolutions. Use "CVT standard" for the old behavior.
    • Added "Exact" and "Exact reduced" to calculate exact integer refresh rates.
    • Added common display standards: CVT, CVT-RB, CVT-RB2, and GTF (previously "Old standard")
  • Detailed resolutions can now calculate frequencies for all possible pixel clocks (up to 167772.16 MHz for DisplayID 1.3)
  • CEA-861 extension blocks are now called CTA-861 to reflect the standard's new name
  • Added support for DisplayID 2.0 extension blocks
  • Export now saves the original unmodified EDID if no changes were made

Fixing overscan issues

Overscan is a common issue with HDTVs, but there are some steps you can take to disable overscan:

  • Check the TV's settings and see if there is an option to disable overscan.
  • Use CRU to edit the affected detailed resolution and choose "CVT-RB standard" timing. This will use a different timing standard that some TVs will not overscan.
  • If you don't need HDMI audio, use CRU to delete the extension block, or edit the extension block and delete HDMI support. This will cause the GPU to send a DVI signal, which most TVs will not overscan. This will not work with 4K TVs.
  • Use the graphics driver's control panel to scale the image down. This will affect image quality.

List of EDID editors

Custom Resolution Utility (CRU) is an EDID editor that focuses on custom resolutions. Besides CRU, here are some other EDID editors:

  • Phoenix EDID Designer - Commonly referenced on forums but out of date. Does not support EDID 1.4 or extension blocks.
  • Deltacast E-EDID Editor - Similar to Phoenix but updated to support EDID 1.4 and CTA-861 extension blocks.
  • AW EDID Editor - Supports EDID 1.4 and CTA-861 extension blocks but not HDMI data blocks. Has a Mac version as well.
  • Advantiv EEditGold and EEditZ - The most complete EDID editors. Supports EDID 1.4 and CTA-861 extension blocks with many types of data blocks.

CRU can import and export files compatible with these editors.

Timing parameters explained

Active is the visible resolution.

Blanking is the period between each line (horizontal blanking) and each frame (vertical blanking). This was originally intended to give CRT monitors time to move the electron guns. LCD monitors don't need as much time, so the blanking can be reduced.

Blanking = front porch + sync width + back porch

Front porch, also known as sync offset, is basically padding before the sync pulse.

Sync width is the duration of the sync pulse. The sync pulse marks the start of the next line (horizontal sync) and the next frame (vertical sync).

Sync polarity is whether the sync pulse voltage goes up (+) or down (−). Most monitors can handle both.

Back porch is basically padding after the sync pulse, before the start of the active pixels.

Total is the total number of pixels including blanking.

Total = active + blanking


Refresh rate is the number of screen refreshes per second.

Horizontal scan rate is the total number of horizontal lines per second including blanking.

Horizontal scan rate = vertical total × refresh rate

Pixel clock is the total number of pixels per second including blanking.

Pixel clock = horizontal total × vertical total × refresh rate

See also: Common pixel clock limits

What timing parameters should I use?

Use whatever works. Standards exist to make sure certain values always work so devices can operate with each other, but if you're trying resolutions or refresh rates that the monitor doesn't officially support, there's no guarantee any particular timing parameters will work.

Common pixel clock limits


LinksLimitData rateBandwidth
Single165 MHz3.96 Gbps4.95 Gbps
Dual330 MHz*7.92 Gbps9.9 Gbps

* Technically no limit defined by the DVI specification, but often limited to 330 MHz.


VersionLimitData rateBandwidth
1.0-1.2a165 MHz3.96 Gbps4.95 Gbps
1.3-1.4b340 MHz*8.16 Gbps10.2 Gbps
2.0-2.0b600 MHz14.4 Gbps18 Gbps

* AMD GPUs without HDMI 2.0 are limited to 297 MHz. Intel GPUs without HDMI 2.0 are limited to 300.99 MHz.


DisplayPort limits depend on the number of lanes and the link rate:

  • Reduced Bit Rate (RBR) and High Bit Rate (HBR) are supported by all versions of DisplayPort.
  • High Bit Rate 2 (HBR2) is supported by DisplayPort 1.2 and newer.
  • High Bit Rate 3 (HBR3) is supported by DisplayPort 1.3 and newer.

4 lanes

Link rate8 bpc limit6 bpc limitData rateBandwidth
162 MHz (RBR)216 MHz288 MHz5.184 Gbps6.48 Gbps
270 MHz (HBR)360 MHz480 MHz8.64 Gbps10.8 Gbps
540 MHz (HBR2)720 MHz*960 MHz*17.28 Gbps21.6 Gbps
810 MHz (HBR3)1080 MHz1440 MHz25.92 Gbps32.4 Gbps

* NVIDIA Kepler GPUs are limited to 540 MHz.

2 lanes

Link rate8 bpc limit6 bpc limitData rateBandwidth
162 MHz (RBR)108 MHz144 MHz2.592 Gbps3.24 Gbps
270 MHz (HBR)180 MHz240 MHz4.32 Gbps5.4 Gbps
540 MHz (HBR2)360 MHz480 MHz8.64 Gbps10.8 Gbps
810 MHz (HBR3)540 MHz720 MHz12.96 Gbps16.2 Gbps

1 lane

Link rate8 bpc limit6 bpc limitData rateBandwidth
162 MHz (RBR)54 MHz72 MHz1.296 Gbps1.62 Gbps
270 MHz (HBR)90 MHz120 MHz2.16 Gbps2.7 Gbps
540 MHz (HBR2)180 MHz240 MHz4.32 Gbps5.4 Gbps
810 MHz (HBR3)270 MHz360 MHz6.48 Gbps8.1 Gbps

DVI specification

Digital Display Working Group (DDWG), the group that created the Digital Visual Interface (DVI) standard, doesn't seem to exist anymore, so here's an archived copy of the DVI specification:

An interesting note is the DVI specification doesn't actually specify a maximum pixel clock, only that pixel clocks greater than 165 MHz must use two links. In fact, it states the first link can operate beyond 165 MHz if the pixel clock is greater than 330 MHz.