Fix STATUS_GRAPHICS_UAB_NOT_SUPPORTED 0xC01E0502 on Windows

What's Going On?

You're staring at error 0xC01E0502 with the message STATUS_GRAPHICS_UAB_NOT_SUPPORTED. It's a Windows DirectX or display driver error that pops up when your graphics driver doesn't recognize or support the UAB (Unified Access Buffer) feature. In plain English: your driver is out of date, corrupt, or the wrong version for your GPU.

This happens most often after a Windows Update pushes a generic driver over your proper one, or when you install a driver meant for a different GPU model. I've seen it on NVIDIA GeForce 900 series cards after a botched driver update, and on AMD Radeon RX 5000 series after Windows 10's 22H2 update. The fix is straightforward — start with the quick one below.

30-Second Fix: Restart the Display Driver

Sometimes the driver just gets confused. Hit Win + Ctrl + Shift + B together. Your screen will flash black for a second. That's it — that resets the graphics driver stack without a full reboot. If the error goes away, you're done. If not, move on.

This trick fixes maybe 1 in 10 cases. Don't count on it, but it costs you nothing.

5-Minute Fix: Roll Back or Reinstall the Driver

The culprit here is almost always a bad driver version. Here's the reliable fix:

1. Open Device Manager — right-click Start, choose Device Manager.
2. Expand Display adapters. You should see your GPU listed (e.g., NVIDIA GeForce RTX 3060 or AMD Radeon RX 6700 XT).
3. Right-click your GPU and select Properties.
4. Go to the Driver tab. If the Roll Back Driver button is available, click it. Follow the prompts — this reverts to the last known working driver. Reboot when done.
5. If Roll Back is greyed out, you need a clean install instead. Download the latest driver from your GPU vendor's site (NVIDIA or AMD). Don't use the Windows Update version — it's often stripped down.
6. Use DDU (Display Driver Uninstaller) in Safe Mode. This nukes all traces of the old driver. Boot into Safe Mode, run DDU, choose Clean and Restart. After reboot, install the driver you downloaded.

This fixes roughly 80% of 0xC01E0502 cases. Don't skip DDU — just uninstalling from Device Manager leaves junk behind that can cause the error again.

15-Minute Advanced Fix: DirectX Repair and SFC Scan

If the driver rollback didn't work, the error might come from a corrupted DirectX component or system file. Here's what I do next:

Step 1: Run System File Checker

Open Command Prompt as Admin (Win + X, then A). Run:

sfc /scannow

Let it finish. It'll replace corrupted system files from the Windows cache. Takes a few minutes.

Step 2: DirectX Repair Tool

Download and run the DirectX End-User Runtime Web Installer from Microsoft's site. Don't bother with the offline installer — the web one is smaller and does the same thing. Accept the license, let it install missing or corrupt files. Reboot after.

Step 3: Check for Windows Update Conflicts

If you got this error after a recent Windows Update, uninstall it. Go to Settings > Windows Update > Update history > Uninstall updates. Look for the most recent update listed by date. Right-click and uninstall. Reboot. If the error disappears, hide that update using Microsoft's Show or hide updates troubleshooter so it doesn't reinstall.

Step 4: Legacy UAB Workaround for Older GPUs

If you're running an older GPU — anything older than a GeForce GTX 900 or Radeon RX 400 series — the card may genuinely not support UAB. In that case, you can often force a compatibility mode by setting the registry key:

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"UABSupport"=dword:00000000

Create this as a .reg file and merge it, then reboot. This tells Windows to skip UAB requests. Only do this if you've confirmed your card is old — it can break modern DirectX 12 games if applied unnecessarily.

When to Throw in the Towel

If none of that works, you might have a failing GPU. Try the card in another machine if possible. If the error follows the card, it's hardware — time to replace it. But in my experience, 90% of these errors are driver-related. You'll likely fix it in the first 5 minutes.

One last thing: Don't bother with third-party driver updaters. They cause more problems than they solve. Stick to NVIDIA or AMD's official tools.