0XC026230A: Invalid video signal frequency fix

What's actually happening here

The 0XC026230A error means Windows or the graphics driver tried to set a display mode — resolution and refresh rate combo — that the monitor flat-out rejected. This typically happens in two scenarios: you just installed a new GPU or monitor, or you've been fiddling with custom resolutions in Nvidia Control Panel or AMD Adrenalin. The monitor's EDID (Extended Display Identification Data) tells the OS what it can handle, and your requested frequency doesn't match any of those timings.

I've seen this pop up on Dell U-series monitors with 1440p at 144Hz when someone accidentally sets 165Hz. Also common after a Windows update that forces a display driver reinstall, leaving old registry timings behind.

Here's the drill: start with the 30-second fix. If that doesn't work, move to the next. Don't skip ahead.

Fix 1: Safe mode reset (30 seconds)

The fastest way to undo whatever bad display setting you applied is to boot into Safe Mode, which defaults to 800x600 at 60Hz. Once there, you can clean the slate.

1. Hold Shift while clicking Restart from the Start menu.
2. Choose Troubleshoot > Advanced options > Startup Settings > Restart.
3. Press 4 or F4 when the PC reboots to enter Safe Mode.
4. Once at the desktop, press Win + R, type desk.cpl, and hit Enter.
5. Click Advanced display settings, then Display adapter properties.
6. In the Monitor tab, set the refresh rate to 60 Hz and resolution to a known-safe value like 1920x1080.
7. Reboot normally.

Why this works: Safe Mode loads the basic VGA driver with zero custom resolutions. Resetting from there overwrites whatever garbage timing was stuck in the registry. I'd say this resolves about 60% of cases — especially if the error just started after a game or monitor swap.

Fix 2: Delete bad custom resolution (5 minutes)

If Fix 1 didn't work, the error is probably baked into a custom resolution you created — or worse, left over from a previous GPU. Nvidia and AMD store these in registry keys that survive a driver reinstall.

For Nvidia users

Open Nvidia Control Panel (right-click desktop). Go to Display > Change resolution. Under Custom resolutions, if you see any entries you created, delete them all. But if the error is actively preventing display output, you'll need to nuke the registry by hand:

1. Press Win + R, type regedit, and hit Enter.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video. You'll see GUID-named subkeys. Expand each, then look for 0000, 0001, etc., until you find one containing NV_Modes or DALRMP entries.
3. In the right pane, locate NV_CustomRes or NV_RefreshRates. Delete those keys.
4. Reboot.

For AMD users

Open AMD Adrenalin, go to Display > Custom Resolutions, and remove all entries. If the app crashes in normal mode, boot into Safe Mode again, run regedit, and delete keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Video\{GUID}\0000 that contain DALRMP or DalCustomRes.

I've seen cases where an old Nvidia custom resolution from a previous GPU install persists after switching to AMD. The registry doesn't clean itself. That's why this fix is manual.

Fix 3: EDID override or driver reinstall (15+ minutes)

Sometimes the monitor itself sends bad EDID — or the driver misreads it. This is rare but happens on some BenQ and Acer monitors with firmware bugs. You have two paths here.

Path A: Force the monitor to re-read EDID

1. Unplug the monitor's power cable for 60 seconds. Not just the video cable — power.
2. While the monitor is off, run devmgmt.msc from Win+R.
3. Expand Monitors. Right-click your monitor and select Uninstall device.
4. In View menu, enable Show hidden devices. Uninstall any ghosted monitors too.
5. Plug the monitor back in and reboot. Windows will re-discover it and fetch fresh EDID.

Path B: Nuke the GPU driver and start clean

If EDID re-read doesn't help, the driver itself has cached bad timings. Use DDU (Display Driver Uninstaller) in Safe Mode:

1. Download DDU and extract it.
2. Boot into Safe Mode (same method as Fix 1).
3. Run DDU. Select your GPU vendor (Nvidia or AMD), then click Clean and restart.
4. After reboot, install the latest driver fresh from the vendor's site — not Windows Update.

The reason step 3 works: DDU removes all registry remnants, including any corrupt EDID overrides or custom resolution data the driver cached. A clean driver install then renegotiates the display mode from scratch using the monitor's actual capabilities.

When none of these work

If you've done all three and the error persists, the monitor's EDID is likely corrupt. You can try an EDID override — but that's advanced and involves hex editing. Instead, try a different monitor or cable. I've had a cheap DisplayPort cable cause this exact error by failing to transmit EDID properly. Swap to HDMI if possible just to test.

Also check if the monitor has a hidden service menu that lets you reset its firmware. Search your model number + "factory reset". Sometimes the monitor itself remembers a bad timing from a previous input source.