Introducing EDID/DisplayID Writer, a new program for Windows that can write a new EDID or DisplayID to a monitor if it's not write-protected.
Screenshot

Testing the limits...
Introducing EDID/DisplayID Writer, a new program for Windows that can write a new EDID or DisplayID to a monitor if it's not write-protected.
Introducing Scaled Resolution Editor (SRE), a new program that lets you edit the list of GPU-scaled resolutions that are automatically added by the graphics driver. For AMD GPUs, you can also add custom VSR resolutions.
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:
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.
https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU
Changes in 1.5.1:
https://www.monitortests.com/forum/Thread-Custom-Resolution-Utility-CRU
Changes in 1.5:
Overscan is a common issue with HDTVs, but there are some steps you can take to disable overscan:
Custom Resolution Utility (CRU) is an EDID editor that focuses on custom resolutions. Besides CRU, here are some other EDID editors:
CRU can import and export files compatible with these editors.
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 gun. 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
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.
Links | Limit | Data rate | Bandwidth |
---|---|---|---|
Single | 165 MHz | 3.96 Gbps | 4.95 Gbps |
Dual | 330 MHz* | 7.92 Gbps | 9.9 Gbps |
* Technically no limit defined by the DVI specification, but often limited to 330 MHz.
Version | Limit | Data rate | Bandwidth |
---|---|---|---|
1.0-1.2a | 165 MHz | 3.96 Gbps | 4.95 Gbps |
1.3-1.4b | 340 MHz* | 8.16 Gbps | 10.2 Gbps |
2.0-2.0b | 600 MHz | 14.4 Gbps | 18 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:
Link rate | 8 bpc limit | 6 bpc limit | Data rate | Bandwidth |
---|---|---|---|---|
162 MHz (RBR) | 216 MHz | 288 MHz | 5.184 Gbps | 6.48 Gbps |
270 MHz (HBR) | 360 MHz | 480 MHz | 8.64 Gbps | 10.8 Gbps |
540 MHz (HBR2) | 720 MHz* | 960 MHz* | 17.28 Gbps | 21.6 Gbps |
810 MHz (HBR3) | 1080 MHz | 1440 MHz | 25.92 Gbps | 32.4 Gbps |
* NVIDIA Kepler GPUs are limited to 540 MHz.
Link rate | 8 bpc limit | 6 bpc limit | Data rate | Bandwidth |
---|---|---|---|---|
162 MHz (RBR) | 108 MHz | 144 MHz | 2.592 Gbps | 3.24 Gbps |
270 MHz (HBR) | 180 MHz | 240 MHz | 4.32 Gbps | 5.4 Gbps |
540 MHz (HBR2) | 360 MHz | 480 MHz | 8.64 Gbps | 10.8 Gbps |
810 MHz (HBR3) | 540 MHz | 720 MHz | 12.96 Gbps | 16.2 Gbps |
Link rate | 8 bpc limit | 6 bpc limit | Data rate | Bandwidth |
---|---|---|---|---|
162 MHz (RBR) | 54 MHz | 72 MHz | 1.296 Gbps | 1.62 Gbps |
270 MHz (HBR) | 90 MHz | 120 MHz | 2.16 Gbps | 2.7 Gbps |
540 MHz (HBR2) | 180 MHz | 240 MHz | 4.32 Gbps | 5.4 Gbps |
810 MHz (HBR3) | 270 MHz | 360 MHz | 6.48 Gbps | 8.1 Gbps |
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:
https://www.monitortests.com/download/pdf/dvi_10.pdf
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.