Fix GPU Exception 0xC0262200 in Visual Studio & DirectX

When This Error Hits

You're working in Visual Studio, running the Graphics Debugger on a DirectX 11 or 12 project. The scene looks fine for a few seconds, then boom — the debugger freezes and you get ERROR_GRAPHICS_GPU_EXCEPTION_ON_DEVICE (0xC0262200). Or maybe you're just running a game or a rendering app and it crashes with the same error in Event Viewer.

I saw this last week on a client's machine — a Dell Precision with an Nvidia Quadro RTX 4000. They were debugging a DirectX 12 raytracing demo, and the error showed up every time they tried to capture a frame. The GPU driver was hanging, Windows' Timeout Detection and Recovery (TDR) kicked in, and the device got reset.

Root Cause in Plain English

The GPU is taking too long to finish a command. Windows has a watchdog timer — the TDR — that's set to 2 seconds by default. If the driver doesn't respond within that window, Windows assumes the GPU is frozen. It resets the device, and your app gets error 0xC0262200.

Common triggers:

Heavy compute shaders or raytracing workloads that exceed the TDR timeout
Debugging with Visual Studio's graphics tools, which add overhead and make the GPU slower
Buggy or mismatched GPU drivers (especially after a Windows update)
Power management settings that throttle the GPU during long renders

The Fix (Step by Step)

Don't waste time reinstalling drivers or running Windows repair tools. Here's what actually works.

Step 1: Increase the TDR Delay

This gives your GPU more time to finish before Windows kills it. You need to add a registry key.

Press Win + R, type regedit, hit Enter.
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
Right-click in the right pane, choose New > DWORD (32-bit) Value.
Name it TdrDelay.
Double-click it, set the value to 8 (decimal). That gives 8 seconds instead of 2.
Also create another DWORD named TdrDdiDelay and set it to 8.
Close regedit and restart your machine.

Step 2: Disable GPU Power Throttling

Laptops and some desktops with Nvidia Optimus or AMD Switchable Graphics often throttle the GPU under load. That can trigger the timeout.

For Nvidia: Open Nvidia Control Panel > Manage 3D Settings > Power Management Mode > set to Prefer Maximum Performance.
For AMD: Open Radeon Settings > System > Switchable Graphics > set your app to High Performance.
For laptops: Set the power plan to High Performance in Windows Control Panel.

Step 3: Roll Back or Clean Install GPU Drivers

If the error started after a driver update, uninstall the current driver with DDU (Display Driver Uninstaller) in Safe Mode, then install the previous stable version. I've seen Nvidia's Game Ready drivers cause this on workstation apps — use Studio Drivers instead.

Step 4: Tweak Visual Studio Graphics Debugger Settings

If you're only seeing this in VS Graphics Debugger:

Go to Debug > Graphics > Graphics Debugging Options.
Uncheck Enable GPU-based validation.
Set Maximum number of frames to capture to a lower value, like 30.
Disable Use hardware accelerated GPU scheduling if that option is available.

What to Check If It Still Fails

Temperature: Overheating GPUs cause driver crashes. Run FurMark or Heaven Benchmark while monitoring temps with GPU-Z. If you hit 90°C+ on the GPU, clean your fans or repaste.
PSU Wattage: A power supply that's too weak or old can cause voltage drops under load. Check your PSU rating vs your GPU's recommended wattage.
Multiple GPUs: If you have integrated + discrete graphics, the debugger might be targeting the wrong one. In Visual Studio, go to Debug > Graphics > Adapter and pick your discrete GPU explicitly.
Windows Update: Sometimes a Windows patch adds new TDR-related behaviors. Check for pending updates or roll back the last one.

If none of that works, you're looking at a hardware defect. RMA the GPU if it's under warranty. I've had to replace a card exactly once in my career — a bad VRAM chip that only showed up under sustained compute loads.