Quick fix: Use Custom Resolution Utility (CRU) from monitortests.com — free, no driver replacement. Add a custom resolution to your monitor’s EDID, run restart64.exe to reload the GPU driver, then pick the new resolution from Settings → Display → Advanced display.
You want a resolution that isn’t in Windows’s dropdown — a 21:9 letterbox, an unusual refresh rate (75 Hz instead of 60 or 144), or a non-native resolution that your monitor actually supports but Windows doesn’t advertise. The GPU driver respects only the resolutions reported by the monitor’s EDID (Extended Display Identification Data). CRU edits the EDID overlay in the Windows registry so Windows believes the monitor supports your custom mode.
Affects: Windows 11 (and Windows 10) with Intel/AMD/Nvidia GPU.
Fix time: ~10 minutes.
What causes this
Monitors transmit their supported resolution and timing list to the PC via EDID — a small data block over the HDMI/DisplayPort link. Windows reads EDID, filters for safe combinations the GPU can drive, and shows the result in Display Settings. CRU overrides EDID on the PC side: Windows reads the override before the real EDID, so custom resolutions can be added or modified without changing anything on the monitor itself.
Important caveat: a custom resolution outside your monitor’s actual range can cause a no-signal blackout. CRU includes a recovery utility (reset.exe) that wipes the override even if you can’t see the screen.
Method 1: Custom Resolution Utility (CRU) — recommended
The standard tool used by enthusiasts since 2012. Free, no installer.
- Download CRU from monitortests.com (search “Custom Resolution Utility”).
- Extract the ZIP to a folder, e.g.,
C:\Tools\CRU. No install required — runs from extracted location. - Run CRU.exe as administrator.
- The top dropdown shows connected monitors. Pick the one to modify.
- In the Detailed resolutions section, click Add. A dialog appears.
- Set Active pixels (your desired resolution), refresh rate, and timing. For most cases, leave timing as Automatic – LCD standard. Click OK.
- Click OK at the main CRU window to save.
- Run restart64.exe (in the same folder) as administrator. Screen will flicker for 5 seconds while the GPU driver reloads.
- After restart64, open Settings → System → Display → Advanced display. The new resolution and refresh rate should appear in the dropdowns.
- Select it. Windows asks “Keep these display settings?” — confirm if the screen looks right.
If the screen goes black after applying: run reset-all.exe from the CRU folder to wipe overrides, or wait 15 seconds for Windows’s auto-revert.
Method 2: Use Intel Graphics Command Center / NVIDIA Control Panel / AMD Software
For users who want a vendor-supported path. Each major GPU has its own custom resolution dialog.
- Intel: open Intel Graphics Command Center (from Microsoft Store). Go to Display → Custom Resolutions tab. Click the + button. Enter values; pick a timing preset (CVT-RB is typically safest).
- Nvidia: open NVIDIA Control Panel (right-click desktop → Show more options → NVIDIA Control Panel). Go to Display → Change resolution → Customize. Tick Enable resolutions not exposed by the display. Click Create Custom Resolution. Enter values; test before applying.
- AMD: open AMD Software (right-click desktop). Go to Display → Custom Resolutions → Create New. Enter horizontal/vertical pixels, refresh rate, timing.
- For all three: the custom resolution appears in Windows’s Display Settings dropdown after the vendor tool applies it.
- The vendor tools are GUI-friendly but less flexible than CRU. They’re also slower to update for newer monitors.
Use the vendor tool first; fall back to CRU only if the vendor tool refuses your specific values.
Method 3: ToastyX’s Display Driver Uninstaller + CRU combo
For when previous custom resolution attempts have left the system in a partly-broken state.
- Download Display Driver Uninstaller (DDU) from guru3d.com.
- Boot Windows into Safe Mode: Settings → System → Recovery → Advanced startup → Restart now, then Troubleshoot → Advanced → Startup Settings → Restart → press 4.
- Run DDU in Safe Mode. Select your GPU vendor (Nvidia/AMD/Intel). Click Clean and restart. DDU removes the driver and all leftover registry entries including any old custom resolutions.
- After reboot, install the latest GPU driver from the vendor’s site.
- Once on fresh driver, install CRU (Method 1) and add the resolution.
- This combination clears all prior overrides and ensures a clean baseline.
This is the right route after multiple failed custom-resolution attempts where Windows is in a weird state.
How to verify the fix worked
- Open Settings → System → Display → Advanced display. The new resolution appears in the resolution dropdown, and the refresh rate dropdown shows your custom value.
- Select the custom resolution. Screen reconfigures within 1–3 seconds. No flickering, no out-of-range message.
- Run a test pattern (Windows has built-in: Settings → System → Display → Advanced display → Display adapter properties → List All Modes). Confirm the new mode is listed and selectable.
If none of these work
If the custom resolution causes “out of range” on the monitor, the monitor genuinely can’t handle that combination. Lower the refresh rate to a safer value (60 Hz instead of 75) and try again. Check the monitor’s manual for actual maximum pixel-clock — if your custom mode exceeds it, no software trick fixes it. For users specifically chasing high refresh rates (144 Hz on a 60 Hz panel): the panel may be limited but the GPU can still send the signal; some monitors accept high refresh and downsample, others go blank. Test with very small overshoots (65 Hz, 70 Hz) before jumping to 75 or higher. For HDMI-only monitors: HDMI versions limit available bandwidth (HDMI 1.4 = 4K@30 max; HDMI 2.0 = 4K@60). Check both PC’s output port and monitor’s input port specs. Use DisplayPort cable if your monitor supports it — DP almost always has more bandwidth than HDMI of the same generation.
Bottom line: CRU is the universal tool — adds custom resolutions to EDID overrides, the GPU driver picks them up after restart64. No driver hacks, no kernel mode changes, no SecureBoot issues.