You're in the middle of a game, or maybe you just plugged in a second monitor, and suddenly the screen goes black—then this error pops up in the Event Viewer or as a blue screen. The exact code is 0XC0262352, and it tells you the graphics driver (or an app like a video player) tried to set a scanline ordering type that the display doesn't support. That typically happens when something requests interlaced output on a progressive-only monitor, or vice versa. I've seen this most often with older capture cards or when switching between 1080i and 1080p in a media app.
What's actually going on?
Scanline ordering is simply whether a display draws lines top-to-bottom (progressive) or alternates odd/even lines (interlaced). Modern monitors are almost always progressive. But some video apps, TV tuners, or custom resolution utilities try to force interlaced modes. When the driver rejects that request, you get this error. It's a mismatch between what the software asks for and what the hardware can do.
The root cause is often a driver bug or a stale display mode that Windows has cached. I've also seen it after a failed driver update where remnants of the old driver linger.
The fix: reset the display mode and drivers
Here's the order I recommend. Start easy, go deeper only if needed.
- Change the resolution and refresh rate. Right-click the desktop, go to Display settings > Advanced display settings. Pick a different refresh rate (e.g., from 60Hz to 59Hz or 50Hz), apply it, then switch back. This forces Windows to rebuild the mode list and often clears the bad cached interlaced mode.
- Reinstall your graphics driver with a clean install. Download the latest driver from NVIDIA, AMD, or Intel. Use Display Driver Uninstaller (DDU) in Safe Mode to remove the current driver completely, then boot normally and install the new one. This removes any leftover registry entries that might still reference interlaced modes.
- Check your custom resolutions. If you've created custom resolutions in the NVIDIA Control Panel or AMD Radeon Software, delete them. A custom mode with interlaced timing can trigger this error every time you run an app that tries to use it.
- Update or disable the problematic app. If this happens when you open a specific program (like a media player or capture software), check its settings for a "video mode" or "TV standard" option. Set it to Progressive or Auto. Also check for an app update—some older versions had bugs that requested interlaced modes incorrectly.
If it still fails
Sometimes the issue isn't the driver but a hardware handshake problem. Try a different cable—especially if you're using an HDMI-to-VGA adapter, which can confuse the scanline negotiation. Also test a different monitor port (DisplayPort instead of HDMI) to isolate whether the monitor's EDID data is wrongly advertising interlaced support.
Still stuck? Check the Windows Event Log under System for the exact time of the error. Look at the source—if it's Display, it's the driver; if it's Kernel-Power, the display might be going to sleep incorrectly. In rare cases, a BIOS update for your motherboard or graphics card fixes these low-level mode negotiation bugs.
I know this error is infuriating because it doesn't tell you which app or setting caused it. But in 90% of cases, a clean driver install plus clearing custom resolutions does the trick. If you're still seeing it after that, you're likely dealing with faulty adapter or monitor firmware—test that hardware on another PC to confirm.