The real cause: a dead or mismatched GPU driver
Nine out of ten times this error shows up because the display driver crashed or got replaced mid-session and Windows can't hand the display mode management interface over to the kernel component that needs it. You'll usually see it right after a Windows Update forced a newer driver over the one you installed, or after a GPU driver auto-update on a laptop with switchable graphics.
The specific trigger I see most: someone runs a Windows 10 22H2 machine with an NVIDIA RTX 3060, applies a cumulative update, and Windows quietly swaps in an older WHQL driver. Next reboot, apps that call D3DKMTOpenAdapterFromDeviceName blow up with 0XC0262341. Games crash on launch, OBS won't capture, some VMs refuse to start.
Don't waste time in Device Manager hitting "Update driver." It'll tell you you're already on the latest. The real fix is a full clean reinstall.
- Download the current driver package from your GPU vendor first — NVIDIA, AMD, or Intel. Get it on disk before you uninstall anything.
- Grab DDU (Display Driver Uninstaller) from Wagnardsoft. It's the only tool I trust for this.
- Boot into Safe Mode. Hold Shift while clicking Restart, then Troubleshoot → Advanced → Startup Settings → Restart → press 4.
- Run DDU. Pick your GPU vendor, hit Clean and restart. Don't skip the cleanup of NVIDIA/AMD/Intel folders — leftover INF files are exactly what causes this error to come back.
- After reboot, install the driver you downloaded. Choose Custom install and check Perform a clean installation if the installer offers it.
- Reboot one more time, then check Event Viewer under
Applications and Services Logs → Microsoft → Windows → Kernel-PnP. You should see a clean driver load with no 0XC0262341 entries.
That fixes it in most cases. If it doesn't, keep reading — the cause is deeper.
Cause two: TDR timeout killing the driver before it can hand off
Windows has a watchdog called TDR (Timeout Detection and Recovery). If a display driver doesn't respond within 2 seconds, TDR resets the GPU. If that reset lands at the wrong moment, the display mode management interface never gets created and you get 0XC0262341 instead of the usual "display driver stopped responding" toast.
You'll see this on older GPUs driving 4K monitors, on systems with PCIe risers that introduce latency, and on mining or compute workloads that hammer the GPU.
Bumping the TDR delay is worth trying. Open regedit and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
Create a DWORD called TdrDelay and set it to 10 (decimal). Optionally add TdrDdiDelay set to 10 as well. Reboot.
Don't set these higher than 10. I've seen people go to 60 trying to "fix" a crashing card — that just hides a hardware problem and makes the machine feel frozen when the GPU actually fails.
If the error persists with a 10-second TDR delay, the GPU is probably on its way out or the power delivery is bad. Test the card in another slot or another machine.
Cause three: switchable graphics on laptops with a broken MUX or BIOS handoff
Laptops with both Intel integrated graphics and a discrete GPU (NVIDIA Optimus or AMD's equivalent) rely on a BIOS-level handoff. If that handoff breaks — usually after a BIOS update, a Windows feature update, or a liquid metal repaste gone wrong that bent something — the discrete GPU can't grab the display mode management interface and you get 0XC0262341 any time an app tries to force it.
Signs this is your problem: the error only appears when you launch a game or app that uses the dGPU. Desktop and browsers work fine on the iGPU.
Fixes that actually work, in order:
- Roll the BIOS back to the version that worked, or update to the latest if you're on the broken one. Check the vendor's release notes — several Dell XPS 15 and Razer Blade BIOSes had this specific regression.
- In Windows, go to Settings → System → Display → Graphics, find the app, and force it to High performance. That tells Windows to route through the dGPU explicitly instead of relying on the broken handoff.
- Disable "Hybrid graphics" or "Optimus" in BIOS if the option exists. On some machines running in discrete-only mode sidesteps the handoff entirely. You'll lose battery life, but the machine works.
- Reinstall both drivers — Intel first, then the discrete GPU. Order matters. Install the iGPU driver, reboot, then the dGPU.
Laptop users on Windows 11 23H2: there was a known issue where the Graphics Driver Installer service (GDI) would partially install the Intel driver, complete the reboot, then trip over itself on the NVIDIA side. Microsoft patched it in KB5034765. If you're on an earlier build, updating Windows might resolve this before you touch anything else.
Things that don't help — skip these
- System Restore. It restores the registry but leaves the driver files, which is exactly the mismatch causing the error. You'll reinstall the bad state.
- SFC / DISM. These fix OS corruption. 0XC0262341 isn't OS corruption. Run them if you want, but don't expect them to do anything here.
- Rolling back the driver through Device Manager. It looks like it works, then Windows Update re-installs the broken driver overnight. You'll be right back here in 24 hours.
- Third-party "driver updater" utilities. Driver Booster and its cousins install whatever's newest, not whatever matches. This error is often caused by them in the first place.
Quick reference
| Cause | Symptom | Fix |
|---|---|---|
| Dead or mismatched GPU driver | Error on boot or app launch after update; happens across all apps using the GPU | DDU in Safe Mode, then clean-install vendor driver |
| TDR timeout | Error on heavy GPU load; often followed by display blink or reset | Set TdrDelay to 10 in HKLM\\SYSTEM\\CurrentControlSet\\Control\\GraphicsDrivers |
| Broken MUX / hybrid handoff | Error only on dGPU apps; iGPU works fine | BIOS rollback, force High Performance, reinstall drivers iGPU-first |
| Leftover driver remnants | Error recurs every few days | DDU with vendor-folder cleanup enabled; block driver auto-updates via Group Policy |
If you've done all three of these and you're still getting 0XC0262341, the card itself is suspect. Put it in a known-good machine. If it fails there too, you've got your answer — RMA or replace.