简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Custom Resolution Utility (CRU)?
Custom Resolution Utility (CRU) is a small Windows tool by ToastyX for editing a monitor's Extended Display Identification Data (EDID)—the information a display reports about which resolutions and refresh rates it supports. Rather than being limited to the modes Windows exposes in its display settings, you use CRU to add, remove or adjust entries, so a monitor can be driven at a resolution or refresh rate that its hardware supports but that Windows does not list by default. It also lets you adjust FreeSync-related settings and address common display problems such as flickering, an incorrect screen size, or issues tied to certain graphics cards.
Who it is for
- Gamers pushing a monitor to a higher refresh rate or an unusual resolution than the standard list offers.
- Ultra-wide and high-resolution display owners whose preferred mode does not appear in Windows.
- People troubleshooting persistent display glitches where the reported EDID seems to be the cause.
What it does in practice
The page describes it as an EDID editor that shows how a monitor's resolutions are configured, with options to add new ones, delete unneeded ones, and tune FreeSync settings. It lists multi-monitor support, refresh-rate optimization, TMDS clock limits for HDMI, and handling of DisplayPort-to-HDMI adapters among its features.
Compatibility to check first
CRU depends on a proper graphics driver. The page states it works with AMD/ATI and NVIDIA cards with the correct driver installed, and that the Microsoft Basic Display Adapter driver will not work. Intel GPUs and laptops with switchable graphics are supported only with the right drivers—the latest for newer Intel chips, and specific older Intel graphics drivers for 6th-generation (Skylake) and 4th/5th-generation (Haswell/Broadwell) hardware. Windows Vista through Windows 11 is listed; Windows XP does not support EDID overrides.
A practical next step
Before changing anything, note your monitor's native resolution and refresh rate, then open CRU and look at the existing entries so you understand the baseline. Make one change at a time and keep a way to revert it, since a bad EDID override can leave a display blank until you reset it. If you would rather avoid editing EDID directly, standard driver control panels from AMD and NVIDIA offer simpler custom-resolution options for many common cases.
How do I safely create and apply a custom resolution or refresh rate in CRU without leaving my monitor with a black screen?
Test each new timing with the F8/VGA-mode fallback ready and change one setting at a time. CRU edits your monitor's EDID—the list of modes Windows reads—so a bad entry can produce a black screen or an out-of-range signal. The safe workflow is to keep a way back into a usable display before you commit.
Safe workflow
- Note your current values. Open CRU, select your monitor under the active display, and look at the existing detailed resolutions and refresh rates. Write down or screenshot them so you can restore them.
- Prefer small steps. Add one detailed resolution or one refresh rate at a time. Keep within what your monitor's specs say it supports (check the manual for maximum resolution and refresh rate). A modest increase, such as a slightly higher refresh rate at a resolution you already use, is far safer than jumping to an extreme mode.
- Watch the pixel clock. CRU's page notes a TMDS clock limit for HDMI and separate handling for DisplayPort-to-HDMI adapters. If you exceed the link's bandwidth, the signal may simply not appear. Lower the refresh rate or reduce blanking if a mode is rejected.
- Restart the graphics driver rather than the PC. CRU's standard method is to run
restart64.exe(orrestart.exeon 32-bit Windows) from the CRU folder, which reloads the driver and applies the EDID. If the screen goes black, wait a few seconds—Windows often reverts to a default mode. If it doesn't, reboot. - Know the recovery path. If you're locked out, boot into Safe Mode or use Windows' low-resolution video mode (F8 at startup on older systems; on Windows 10/11 use Advanced Startup → Startup Settings → Enable low-resolution video). Then run the CRU reset tool (
reset-all.exe) to clear overrides, or delete the CRU entries and restart the driver. - Test before trusting it. Once applied, check the mode in Windows display settings and run a short stability test—a game or a refresh-rate test pattern—to confirm no flicker or dropouts. CRU's page also mentions using it to fix flickering or incorrect screen size, so if a mode misbehaves, revert rather than stacking more changes.
Decision points
| Situation | Safer choice |
|---|---|
| Laptop with switchable graphics or Intel GPU | Confirm the correct Intel driver first; CRU's page notes specific driver versions for older Intel generations |
| HDMI connection | Respect the TMDS clock limit; try DisplayPort if available |
| Unsure the monitor supports the mode | Add it, test, and remove it immediately if the screen blanks |
| Multi-monitor setup | Change one display at a time so you can recover on the other |
For background on EDID and driver-level overrides, the official documentation for AMD and NVIDIA driver tools is a useful cross-check, since CRU's page states it depends on a proper AMD or NVIDIA driver being installed.
Next step: before adding anything, open CRU, screenshot your current monitor entry, and confirm you can launch restart64.exe and reset-all.exe from the same folder. That two-minute check is what turns a black-screen risk into a recoverable experiment.
Can CRU help fix problems like flickering, incorrect screen size, or a resolution that Windows won't offer on my monitor?
Yes. CRU is built for exactly those situations: it edits the monitor's EDID so Windows and the graphics driver see resolutions, refresh rates and timing details that standard display settings hide. The page describes adding new resolutions, removing unwanted ones and adjusting FreeSync settings, and it specifically names flickering, incorrect screen size and certain graphics-card display problems as things CRU can address by changing how the monitor reports itself.
What it can realistically fix
- Missing resolution: your panel supports a mode that Windows never lists; CRU lets you add it as a custom profile.
- Incorrect screen size or overscan: scaling or timing details can be adjusted so the image fills the panel properly.
- Flickering or unstable modes: often caused by timings or refresh rates the driver handles poorly; adjusting or removing those entries can help.
- Refresh-rate limits: useful for high-refresh or ultra-wide monitors where the desired mode isn't exposed.
Practical cautions
- Driver dependency: the page states it works with AMD and NVIDIA cards, and with Intel GPUs only with the correct drivers (not the Microsoft Basic Display Adapter). Check your driver first.
- Recovery plan: a bad EDID override can leave you with a black screen. Know how to boot into safe mode or reset the display before you start.
- Not a hardware fix: if flickering comes from a failing cable, backlight or panel, CRU won't cure it.
For step-by-step guidance and version notes, the official source is Custom Resolution Utility (CRU by ToastyX). As a next step, note your monitor's native resolution and refresh rate, then change one setting at a time so you can tell which edit actually solved the problem.
Is CRU compatible with my graphics card and Windows version, including Intel integrated graphics or laptops with switchable graphics?
CRU is compatible with most Windows systems and the three major GPU brands, but Intel integrated graphics and laptops with switchable graphics carry the most conditions.
Compatibility at a glance
| Setup | Supported? | What to know |
|---|---|---|
| Windows Vista–11 | Yes | Windows XP is not supported because it lacks EDID override support |
| AMD/ATI or NVIDIA card | Yes | Requires the proper vendor driver; the Microsoft Basic Display Adapter driver will not work |
| Newer Intel GPUs | Yes, with conditions | Needs the latest Intel graphics driver |
| 6th-gen Intel (Skylake) | Yes, with conditions | Requires the Intel Graphics Driver for Windows 15.45 specifically |
| 4th/5th-gen Intel (Haswell/Broadwell) | Yes, with conditions | Requires the appropriate Intel driver for those generations |
| Laptops with switchable graphics | Yes, with conditions | Supported only when the correct drivers are installed |
The pattern is that CRU edits the monitor's EDID, so the graphics driver must be able to apply those overrides. A generic or missing driver blocks that, which is why Intel support depends on driver version rather than the chip alone.
A practical example: if you have a Skylake laptop with switchable graphics and want to add a custom refresh rate, check the Intel driver version first. If it is a generic Windows driver, install the correct Intel driver before opening CRU, or your changes may not take effect.
For a definitive check, confirm your exact GPU model and installed driver version against the requirements above before making changes.
How do I remove an unwanted resolution or reset EDID overrides if a custom setting causes display issues?
Use CRU to delete the unwanted entry from the monitor's EDID in the utility, then restart the graphics driver so Windows re-reads the display data. If the screen is unusable, boot into Safe Mode (or use another display) and run the "reset-all.exe" file that ships with CRU to clear all EDID overrides, then reboot normally.
Removing one resolution
- Open CRU and pick the correct monitor from the dropdown at the top — with multiple displays, each has its own EDID block.
- Under "Detailed Resolutions," select the custom entry you added and delete it. If you added it under "Standard Resolutions" or as an extension block, remove it from that list instead.
- Click OK, then run "restart64.exe" (or "restart.exe" on 32-bit Windows) from the CRU folder to restart the graphics driver. A full reboot also works.
- Check Windows display settings to confirm the resolution is gone.
Resetting everything
If a bad setting leaves you with a black screen, corrupted image, or no signal, the reset-all.exe utility removes every EDID override CRU has written. Run it from Safe Mode or from a second monitor, then reboot. This is the fastest recovery path and is worth knowing before you experiment.
Practical cautions
- Keep a note of your original resolution and refresh rate before editing, so you can restore them if a change misfires.
- Laptop panels with switchable graphics and Intel GPUs are the most likely to behave unpredictably; per the site, they need specific driver versions to work with EDID overrides at all.
- Removing a resolution does not change the monitor's physical capabilities — if a mode caused flickering or overscan, the panel or cable may simply not support it.
If you want a simpler route
For a single custom mode, the GPU vendor's own control panel is less invasive than editing EDID: AMD Software's custom resolution options and NVIDIA Control Panel's "Change resolution" page both let you add and delete modes without touching the monitor's EDID, and deleting the mode there is a one-click undo. CRU remains the better choice when Windows hides a mode the display actually supports, or when you need to fix an incorrect EDID reported by a monitor or adapter.
As a rule of thumb: use CRU for persistent, system-wide EDID corrections; use the driver panel for quick per-mode experiments you may want to revert.
Does CRU work with FreeSync, HDMI, and DisplayPort-to-HDMI adapters when setting up a high refresh rate or ultra-wide display?
Yes—CRU is built for exactly that kind of setup, but each of the three areas has its own limits.
FreeSync
CRU can edit the monitor's EDID to adjust FreeSync-related settings, so it is a legitimate tool when a FreeSync range or flag is missing or misreported. The practical caveat is that FreeSync behavior is ultimately enforced by the GPU driver and the monitor's firmware; CRU changes what the system believes the display supports, not what the panel can physically do. If you widen a FreeSync range beyond the panel's real capability, you may get flickering or blackouts rather than a better experience. Use it to restore or correct a range, not to invent one.
HDMI
CRU explicitly lists a TMDS clock limit option for HDMI, which matters when pushing high refresh rates or resolutions over HDMI: many displays report a lower pixel-clock ceiling than they can actually handle, and raising the limit is how people unlock modes like high refresh at 1440p or 1080p over HDMI. The trade-off is cable and port quality—if the link can't sustain the clock, you get no signal or intermittent dropouts, so test with a known-good cable before blaming the setting.
DisplayPort-to-HDMI adapters
CRU lists adapter handling among its features, which is useful because adapters often pass through or rewrite EDID in ways that hide modes. Editing the EDID can expose resolutions and refresh rates the adapter chain was suppressing. The catch: cheap adapters may not actually support the bandwidth of the mode you enable, so a mode that appears in Windows can still fail to display. Prefer active, rated adapters and verify one change at a time.
Ultra-wide and high refresh in practice
For an ultra-wide or high-refresh panel, the typical workflow is: read the existing EDID, add or adjust a detailed resolution and refresh rate, raise the HDMI TMDS limit if needed, then restart the graphics driver and test. Keep a recovery path—booting into safe mode or using the reset option—because a bad EDID override can leave you with a blank screen.
A reasonable decision rule: use CRU when a mode your monitor and cable can genuinely handle is missing from Windows; don't use it to force modes beyond the panel's or adapter's real limits. For driver-side alternatives, NVIDIA and AMD both offer custom resolution tools, documented at NVIDIA and AMD.
Cloudflare
User reviews (0)