What is DXGI-ERROR-WAS-STILL-DRAWING?
Image rendering conflict is a low-severity graphics API (DirectX) issue. Attempting to access the surface that the GPU is currently drawing on. The usual suspects are bad synchronization of application threads and unstable G-Sync/FreeSync. Use the steps below to track down and fix the cause.
Common Causes
- Bad synchronization of application threads
- Unstable G-Sync/FreeSync
Step-by-Step Fix Guide
-
1
Turn V-Sync on or off
As a first move, Turn V-Sync on or off handles the most common scenario behind DXGI_ERROR_WAS_STILL_DRAWING.
-
2
Update the game
A recurrence usually points to a rarer directx instability cause, which is what the following steps are meant to catch.
Commands & Diagnostics
dxdiag
Frequently Asked Questions
In most cases, bad synchronization of application threads is behind DXGI-ERROR-WAS-STILL-DRAWING. Unstable G-Sync/FreeSync can trigger it too.
Try "Turn V-Sync on or off" first — it resolves most DXGI-ERROR-WAS-STILL-DRAWING cases on its own. Only work through the rest of the guide above if it comes back.
As a low-severity issue, DXGI-ERROR-WAS-STILL-DRAWING is more of a stability annoyance than a hardware risk — the steps above should clear it up.
Usually. DXGI-ERROR-WAS-STILL-DRAWING is fixable with the steps above; a full Windows reinstall is rarely necessary unless everything else has failed.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database