Custom Resolution Utility, or CRU, lets you add resolutions and refresh rates your monitor supports but does not advertise, tighten timing to unlock a few extra hertz, or fix a display that reports the wrong native mode. It is powerful and mostly safe, but because it writes directly to the display’s EDID overrides, a careless entry can throw a black screen. This guide covers doing it methodically with an easy escape hatch.
What CRU is good for
People reach for CRU to enable a mild refresh-rate overclock, to add a missing resolution a GPU refuses to expose, to force a specific timing standard that reduces bandwidth, or to add custom scaling modes. It does not physically change what the panel can do; it only tells the GPU which modes to offer, so the panel still has to accept the signal.
Set up your safety net first
Before changing anything, know that CRU cannot brick hardware; a bad mode just produces no image, and you recover by booting into Safe Mode or using the included reset executable. Windows also reverts an untested resolution after 15 seconds if you do not confirm it. Keep those two escapes in mind and the whole process is low-risk.
| Goal | CRU action | Risk level |
|---|---|---|
| Add missing resolution | Add detailed resolution | Low |
| Mild refresh overclock | Raise refresh in small steps | Low-medium |
| Reduce bandwidth | Switch to CVT-RB timing | Low |
| Aggressive overclock | Large refresh jump | High (black screen) |
Step-by-step
Run CRU, select your monitor from the dropdown, and add a new detailed resolution under the Detailed Resolutions box. Enter your target resolution, set the timing to Automatic (CVT-RB) to minimize bandwidth, and type the refresh rate you want. Click OK, then run the included restart64 utility to reload the graphics driver, or reboot. The new mode now appears in Windows display settings.
Overclock in small steps
If you are chasing extra refresh, raise it a little at a time, such as 60Hz to 65Hz to 70Hz, testing each. After applying, run a moving test pattern and watch for frame skipping, where the panel silently drops frames instead of showing them. The highest rate that passes a frame-skip test without artifacts is your real ceiling; anything above it is fake.
Recovering from a black screen
If a mode produces no image and the screen does not auto-revert, do not panic. Reboot into Safe Mode, run the CRU reset executable to wipe your overrides, and reboot normally. Everything returns to the factory EDID. This is why aggressive single jumps are the only real risk, and why small increments are the smart approach.
Common real-world uses
Beyond overclocking, CRU solves several everyday annoyances. If a monitor reports a wrong or missing native resolution after a driver update, adding the correct detailed resolution forces the right mode back. If a display advertises a refresh rate the GPU refuses to offer, CRU can expose it. It can also add integer-friendly or scaling resolutions for retro gaming and reduce signal bandwidth by switching to reduced-blanking timing, which sometimes fixes flicker or lets a mode fit within a cable’s limits. When adding entries, keep the monitor’s genuine native resolution as the first detailed resolution so the system always has a safe fallback, and avoid deleting the existing standard modes. Because CRU changes take effect only after a driver restart, test each change immediately and keep the reset utility on hand. Used for these targeted fixes rather than extreme overclocks, CRU is one of the safest and most useful tools for getting a stubborn display to behave exactly as it should.
Frequently asked questions
Can CRU damage my monitor?
No. It only changes the resolutions and timings the GPU offers. The worst outcome is a temporary black screen from a mode the panel rejects, which you fix by resetting overrides in Safe Mode. The hardware is never at risk.
How do I know if an overclock is actually working?
Run a frame-skipping test, which scrolls vertical bars and reveals dropped frames as gaps. If the higher refresh rate passes cleanly, the extra hertz are real. If bars smear or skip, the panel is not truly displaying every frame and you should dial it back.
Bottom line
CRU is a safe, useful tool when you move deliberately: add modes with relaxed CVT-RB timing, overclock in small tested steps, and keep Safe Mode plus the reset utility as your fallback. Respect the frame-skip test as the truth teller and you can squeeze out real, stable extra performance without any hardware risk.
