0XC01E031D

STATUS_GRAPHICS_FREQUENCYRANGE_NOT_IN_SET (0XC01E031D) Fix

Your monitor can't handle the refresh rate your GPU is pushing. Usually happens after a driver update or plugging in a second screen. Fix is simple: cap the refresh rate or reset the display settings.

This error is a pain, I know

You're working, maybe gaming, then screen goes black or you get a pop-up with error code 0XC01E031D. Your monitor just told Windows: "I can't do that refresh rate." The fix is simple and doesn't require reinstalling drivers.

The quick fix: cap your refresh rate

Here's what's actually happening: your GPU sent a refresh rate (like 144 Hz) that's not in the monitor's approved list. The monitor knows its limits. Windows just didn't check. So you need to force a safe rate.

  1. Right-click on your desktop and pick Display settings.
  2. Scroll down to Advanced display.
  3. Under Choose a refresh rate, pick the highest value that's not the one that caused the crash. If you were at 144 Hz, drop to 120 Hz. If you were at 60 Hz, drop to 59 Hz or 50 Hz.
  4. Click Apply. Windows will ask if you want to keep changes. Click Yes.
  5. Reboot your PC.

That's it. The error should stop. If you still see it, go lower. 60 Hz works on almost every monitor made after 2005.

Why this works

The reason step 3 works is that every monitor ships with a built-in list of supported refresh rates, called the EDID (Extended Display Identification Data). Windows reads this list when you plug the monitor in. But sometimes — especially after a driver update or connecting a second screen — Windows ignores the list and tries a rate the monitor can't handle. Dropping to a lower rate forces Windows to stick to the monitor's real capabilities.

I've seen this most often with 144 Hz monitors on Nvidia GPUs after driver version 537.xx. The driver tries to enable 144 Hz on displays that only support 120 Hz at that resolution. AMD cards sometimes do it with FreeSync enabled. Intel integrated graphics? Rare, but happens when you hot-plug a display via HDMI.

Less common variations

Dual monitor setups

If you have two screens and one shows this error, unplug the second one. Reboot. Then plug it back in. What's happening is Windows is trying to mirror or extend at a frequency that only one monitor supports. You'll then need to set each monitor's refresh rate separately in Display settings > Advanced display.

Custom refresh rates (overclocking)

If you're using a custom resolution or refresh rate (like 75 Hz on a 60 Hz monitor), this error pops up when the GPU actually tries to push it. The fix is to remove the custom mode. Open Nvidia Control Panel > Change resolution > Customize and delete any custom modes. For AMD, use the Radeon Software > Display > Create Custom Resolution and delete it. Intel? Use the Intel Graphics Command Center > Display > Custom Resolutions.

HDMI vs DisplayPort

Some monitors have different frequency sets depending on the cable. For example, my Dell S2721DGF supports 165 Hz over DisplayPort but only 144 Hz over HDMI. If you switched cables, you might hit this error. Try the other cable type if you can.

Driver reinstall (last resort)

If none of the above works, uninstall your GPU driver entirely using DDU (Display Driver Uninstaller) in Safe Mode. Then install the latest driver from the manufacturer's site. Don't use Windows Update for this. The reason is that Windows Update often installs generic drivers that don't know your monitor's EDID properly. You want the OEM driver.

How to prevent this

Three things stop this error from coming back:

  • Keep your monitor's EDID intact. Don't use custom resolution tools unless you really know the monitor's limits. Check the manual for the exact refresh rate at each resolution.
  • When you update your GPU driver, check the refresh rate after. Drivers sometimes reset your display settings. Go back into Advanced display and make sure it's still at your chosen rate.
  • If you switch cables or monitors, reboot Windows once. This forces Windows to re-read the EDID from all connected displays.

That's it. No registry hacks, no long command lines. Just pick a safe refresh rate and move on with your day.

Related Errors in Windows Errors
0X000036B0 Fix ERROR_SXS_SECTION_NOT_FOUND (0x000036B0) on Windows 0X8009700D Fix MSSIPOTF_E_FILE_CHECKSUM (0x8009700D) in 3 Steps 0X000010D0 Fix ERROR_MEDIA_OFFLINE (0X000010D0) in Windows 0XC021000A STATUS_FVE_BAD_DATA 0XC021000A fix for BitLocker errors

Was this solution helpful?

EP
Erropedia Team
Tech Support Editors
The Erropedia editorial team researches and documents real-world tech errors from across Windows, Linux, macOS, networking, databases, cloud platforms, and more. Every solution is reviewed for accuracy and updated as software and systems evolve.