AMD Can’t Create Custom Resolution | Fix It In Minutes

Guide / By

If amd can’t create custom resolution, set a safe refresh rate, turn off GPU scaling, and try the custom mode again.

Custom resolutions are handy when you’re trying to run an odd ultrawide mode, match a capture card, remove overscan, or squeeze a little extra clarity out of an older panel. When AMD Software refuses to save the mode, it feels like you’re stuck in whatever your monitor reports, even when you know the screen can handle more.

The good news is that most failures come from a short list of causes. Once you line up the right display, refresh rate, and timing style, the Create button starts behaving again. This article walks you through the checks that solve the issue on most Windows 10 and Windows 11 PCs with Radeon graphics.

Why Custom Resolutions Fail In AMD Software

AMD’s custom mode tool sits between Windows and your display’s EDID, the data that tells the PC what the panel accepts. If the driver thinks the mode breaks the EDID limits, it blocks the save, even if the panel might still show an image. Some displays also report conservative limits through certain adapters or docks, which makes the driver extra strict.

Most “can’t create” errors boil down to timing math. Pixel clock, total pixels, and refresh rate have to fit the link bandwidth of HDMI or DisplayPort and the limits the display reports. A tiny tweak, like lowering refresh rate first, often turns a rejected mode into an accepted one.

Common Triggers You Can Spot Fast

  • Picked The Wrong Display — If you have two monitors, a laptop panel plus an external screen, or a capture device, the custom mode may be pointed at the wrong target.
  • Refresh Rate Too High — Many displays accept a new resolution at 60 Hz but reject it at 120 Hz or 144 Hz because the pixel clock jumps.
  • GPU Scaling Mismatch — Some scaling modes can block certain timing combinations until you switch scaling off or choose a different scaling mode.
  • Link Bandwidth Limit — HDMI version, cable quality, adapters, and docks can reduce the usable bandwidth and make a mode fail even with the same monitor.
  • Windows Overrides — Windows can keep applying a “known good” mode, so the custom entry never shows up as selectable even after it saves.

A Quick Compatibility Table

What You See Likely Cause First Fix To Try
Create fails instantly Timing values out of range Lower refresh to 60 Hz and retry
Mode saves but won’t appear Windows still on old mode Select it in Windows display settings
Black screen after applying Mode not truly accepted Wait for revert, then reduce pixel clock
Only fails on one cable Adapter or cable limit Switch to DisplayPort or a better cable

AMD Can’t Create Custom Resolution In Adrenalin

If you’re seeing the “not compatible” style message or the Create button does nothing, start with a clean, repeatable setup. The goal is to remove variables so you can tell which change fixes the block. Keep one monitor connected for now while you test, since multi-display setups can complicate which EDID the driver trusts.

Open AMD Software: Adrenalin Edition, go to the display section, and find the Custom Resolutions area. If you use a laptop with hybrid graphics, make sure the external monitor is running through the Radeon GPU path, not a different output route.

Step-By-Step Create Workflow That Avoids Most Errors

  1. Switch To A Safe Refresh Rate — Set the display to 60 Hz in Windows first, then return to AMD Software before you add the mode.
  2. Turn Off GPU Scaling — Disable GPU scaling for the test, since scaling can change which timing set is accepted.
  3. Start From The Native Mode — In the custom window, begin with values close to the panel’s native resolution and adjust only width and height first.
  4. Use A Conservative Timing Standard — If the tool offers multiple timing styles, pick the more standard option rather than a tight, aggressive timing.
  5. Create One Change At A Time — Save a single mode, test it, then move to the next tweak. Big jumps make it hard to isolate the blocker.

What To Change And What To Leave Alone

In the custom window, the tempting part is the long list of timing numbers. You rarely need to touch most of them. When you change too many fields at once, the driver can’t reuse a safe baseline and it rejects the whole entry.

  • Edit Only Width And Height First — Leave porch and sync values alone on the first attempt so the tool can stay close to a known-good mode.
  • Keep Refresh Rate Modest — Get the new resolution accepted at 60 Hz, then raise refresh in small steps if you still want it.
  • Watch The Total Pixels — Big totals raise pixel clock fast, so a tiny cut in blanking can make a mode pass on the same cable.
  • Use Standard Polarity — Stick with the default sync polarity unless you have a reason to change it for a projector or older panel.

Fixing AMD Custom Resolution Not Creating New Modes On Windows

Once the basic workflow is set, focus on the settings that commonly interfere with custom entries. Most of these checks take a minute. A few feel boring, but they solve a lot of real cases where the driver refuses to store the mode or Windows refuses to show it.

If your screen is connected through a USB-C dock, try a direct cable to the GPU as a test. Docks often alter what the display reports, and that can make the driver reject the same numbers that would work with a direct DisplayPort link.

Driver And App-Level Fixes

  • Reset Display Settings — In AMD Software, restore display settings to default, restart the PC, and try again with a single monitor connected.
  • Reinstall With A Clean Baseline — Remove the driver, reboot, install the latest package, and skip extra tuning until the custom mode works.
  • Disable Extra Display Features — Turn off HDR, variable refresh features, and custom color modes while you test the mode creation.
  • Try A Different Scaling Mode — If you must keep scaling on, change the scaling mode and retest the Create action.

Connection And Bandwidth Fixes

  • Swap The Cable — A weak cable can pass a native mode but fail on a higher pixel clock custom mode.
  • Move To DisplayPort — DisplayPort often has more headroom than older HDMI paths, especially through adapters.
  • Remove Adapters And Splitters — Test with a direct link, since adapters can change EDID data and reduce bandwidth.
  • Use One Monitor While Testing — Disconnect the second screen, create the mode, then reconnect after it’s stable.

Windows Settings That Can Block A Custom Resolution

Even after AMD Software saves the mode, Windows still controls what you can pick day to day. If Windows thinks the mode is risky, it may hide it, revert after a few seconds, or keep defaulting back after sleep. That can make it feel like the custom entry never worked.

Start in Windows Settings under System and Display. Confirm you’re changing the correct monitor, since Windows can swap numbering when you reconnect cables. A saved custom mode won’t help if you keep adjusting the wrong display panel in Settings.

Windows Checks That Make Modes Show Up

  1. Select The New Mode In Windows — After saving, open Windows display settings and pick the new resolution from the list.
  2. Match Color Depth — Drop to 8-bit color while testing to reduce bandwidth and keep the link stable.
  3. Set A Lower Refresh Rate First — Choose 60 Hz in Advanced display settings before you apply a higher refresh custom mode.
  4. Turn Off Custom Scaling — Reset custom scale and sign out if needed, since odd scaling can cause strange mode behavior.
  5. Reboot After A Big Change — A reboot clears stuck display state that can survive restarts of the AMD app.

Using CRU When The Driver Won’t Save Your Mode

If the built-in tool still refuses to store your numbers, Custom Resolution Utility, often called CRU, can add an EDID override in Windows. This works by inserting the mode into the override data Windows presents to the graphics driver. It can help in cases where the panel accepts the mode but the driver UI blocks it.

CRU can also cause a black screen if you add a mode your panel can’t display. Plan a safe exit before you start. Keep a second display available or be ready to boot into Safe Mode to remove the override if the screen goes dark.

Safer CRU Habits That Reduce Risk

  • Start With A Small Change — Add one modest resolution step first, not a huge jump in both pixels and refresh rate.
  • Keep A Known-Good Detailed Mode — Do not delete the native detailed resolution until the new mode has proven stable.
  • Restart The Graphics Driver — Use the restart tool included with CRU, or reboot, so Windows reloads the new EDID override.
  • Test In Short Sessions — Apply the mode, use it for a few minutes, then switch away and back to confirm it’s stable.

Make The New Resolution Stable After You Create It

Once the mode is available, stability is the real win. You want the system to keep the mode through sleep, driver updates, and game launches. Many people stop after the mode appears, then a week later it vanishes because a setting reset or Windows update changed the display path.

If you still see the same block and the message reads like amd can’t create custom resolution, treat it as a signal that the link budget is tight. Reduce refresh rate first, then try a slightly smaller resolution step, and keep notes of what changes. Small, measured moves beat random toggling.

Stability Checklist You Can Reuse

  1. Save A Profile Screenshot — Write down your working width, height, and refresh so you can rebuild it after an update.
  2. Lock The Refresh Rate — Keep a steady refresh in Windows, since automatic switching can make modes disappear.
  3. Check After Driver Updates — Reopen the AMD app and confirm the mode still exists before you launch a game.
  4. Avoid Fast Cable Changes — Hot-plugging different adapters can change EDID readings and cause the driver to drop custom entries.
  5. Use Game-Side Resolution Controls — When a game ignores Windows settings, set the custom resolution inside the game after the mode is active.

If you’re still stuck, repeat the core loop: one monitor, 60 Hz, scaling off, conservative timing, and one change at a time. When you find the first mode that saves, you can build up from there until you hit the limit your display link can handle.