Fix ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED (0XC0262349)

When does this error hit?

You're working on a multi-monitor setup or connected via Remote Desktop (RDP) to a machine with an NVIDIA or AMD GPU. Maybe you just installed a new display driver or switched to a higher resolution. Suddenly the screen goes black, the connection drops, or an app spits out ERROR_GRAPHICS_MULTISAMPLING_NOT_SUPPORTED (0xC0262349). I've seen this most often on Windows 10/11 Pro workstations running multiple 4K monitors through a single GPU output.

The exact trigger I've run into twice this month: a client plugged a 4K TV into a GTX 1650 via HDMI, then tried to extend displays at 60Hz. Boom—error code popped up in the Event Viewer under Microsoft-Windows-DxgKrnl. The GPU could handle the resolution, but the display path didn't support the multisampling level the system tried to use.

Root cause

In plain English: your graphics driver or DirectX tries to apply multisample anti-aliasing (MSAA) to a display path that doesn't support it. The VidPN (Video Present Network) is the driver's map of how display outputs connect to monitors. If the monitor, cable, or GPU can't handle the MSAA sample count (like 4x or 8x) at that resolution and refresh rate, the whole display pipeline crashes.

Sometimes it's a corrupt driver cache. Other times it's RDP trying to use hardware acceleration that the remote GPU can't deliver. Either way, the fix is the same: disable or lower multisampling.

Fix step-by-step

1. Restart in Safe Mode and uninstall the display driver
   Boot into Safe Mode (hold Shift while clicking Restart). Open Device Manager, expand Display adapters, right-click your GPU, select Uninstall device, and check "Delete the driver software for this device." Reboot normally.
2. Install the latest driver from the GPU manufacturer
   Skip Windows Update—it often pushes generic drivers. Go to NVIDIA, AMD, or Intel's site. Download the latest Game Ready or Pro driver. During installation, choose Custom install and check "Perform a clean installation." This wipes old settings that might be forcing MSAA.
3. Disable multisampling in the driver control panel
   
   • NVIDIA: Open NVIDIA Control Panel → Manage 3D Settings → Global Settings. Find "Antialiasing - Mode" and set to "Off." Then find "Antialiasing - Setting" and set to "None."
   • AMD: Open AMD Radeon Software → Gaming → Global Graphics. Turn off "Anti-Aliasing" and "Morphological Anti-Aliasing."
   • Intel: Open Intel Graphics Command Center → System → 3D → Set "Multisampling" to "Disabled."
4. Force RDP to use software rendering
   If this happens over Remote Desktop, disable hardware acceleration in the RDP session. On the client machine, open Remote Desktop Connection, go to the Experience tab, and uncheck "Persistent bitmap caching." Then, on the remote machine, run gpedit.msc and go to Computer Configuration → Administrative Templates → Windows Components → Remote Desktop Services → Remote Desktop Session Host → Remote Session Environment. Enable "Use hardware graphics adapters for all Remote Desktop Services sessions" and set it to Disabled.
5. Registry tweak to disable multisampling globally (if still failing)
   Open Regedit as admin, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Direct3D\Drivers. Create a new DWORD (32-bit) named DisableMultisampling and set its value to 1. Reboot. This is a nuclear option—it forces DirectX to skip all MSAA requests.

What to check if it still fails

• Cable quality: Cheap HDMI 1.4 cables can't handle 4K @ 60Hz with HDR. Use a certified HDMI 2.1 or DisplayPort 1.4 cable.
• Monitor EDID: Some monitors report bogus capabilities. Boot with only one monitor connected, then add the second. If the error goes away, the secondary monitor's EDID might be corrupt—try a different monitor or a custom resolution via CRU (Custom Resolution Utility).
• BIOS update: Had a Dell Precision workstation that kept throwing this error until we updated the BIOS. The GPU's PCIe link speed was unstable.
• Windows Display Settings: Drop the refresh rate from 60Hz to 59Hz or 30Hz and see if the error stops. If yes, the monitor's scaler can't handle the MSAA at that rate.

If none of that works, the GPU itself might have a hardware fault. Swap in a known-good card to test. I've had two NVIDIA cards with dying memory controllers that only showed up under multisampling load.