How to Fix GTA V ERR_GFX_STATE: Graphics Crash on PC
You are mid-heist, mid-race, or just cruising down Vinewood Boulevard — and suddenly the screen freezes, GTA V slams shut, and a crash dialog stares back at you with the dreaded words: ERR_GFX_STATE. Maybe it happens every twenty minutes, maybe every time you hit a specific intersection. If you are stuck in this crash loop, this guide explains exactly what the error means and walks you through 8 fixes that actually stop it.
In plain English, ERR_GFX_STATE means the game's graphics renderer crashed. GTA V asked your graphics card to do something — draw a frame, load a texture, compile a shader — and the driver or the card failed to complete it, so the game gave up and crashed to desktop. It hits both story mode and GTA Online on PC, and it is famous for striking systems that run every other game perfectly. The fixes below are ordered from most likely to least likely, and the first three resolve the overwhelming majority of cases.
What does ERR_GFX_STATE actually mean?
GTA V's engine (RAGE) has a catch-all crash handler for graphics failures, and ERR_GFX_STATE is its label for the render pipeline breaking mid-frame. The "GFX state" is the collection of settings, shaders, textures, and draw calls the game feeds your GPU. When one of those fails — a shader that will not compile, a texture that arrives corrupted, a GPU clock that glitches under load — the engine cannot safely continue, so it crashes and writes a crash log instead of rendering garbage.
That is why the error is so maddening: it tells you where it broke (the graphics pipeline) but not what broke it. The same crash message can come from a bad driver, an unstable overclock, a corrupted game file, an interfering overlay, or a dying GPU. The good news is that GTA V's engine is also unusually picky about graphics stability, which means many ERR_GFX_STATE crashes are software problems on otherwise healthy hardware. Work through the fixes in order — most players never need to get past Fix 3.
What causes ERR_GFX_STATE?
These are the usual suspects, in roughly the order of how often they are responsible:
- Unstable GPU clocks — including factory overclocks — GTA V is notorious for crashing on cards whose boost clocks are borderline unstable. This includes cards that came overclocked from the manufacturer and crash in GTA V while passing every stress test. The single most reported cause.
- Buggy or new graphics drivers — a driver update that shipped right when your crashes started is a prime suspect. Both NVIDIA and AMD have had releases that destabilize GTA V specifically.
- Corrupted graphics settings (settings.xml) — the game's graphics config in your Documents folder can end up with an invalid combination that crashes the renderer on launch or at a specific scene.
- Corrupted game files — one damaged texture, shader, or audio-asset bundle can crash the renderer every time the game tries to load it, which is why the crash sometimes happens at the same spot.
- Overlay and capture software — Discord, Steam, NVIDIA GeForce, Xbox Game Bar, and MSI Afterburner's on-screen display all inject into the render pipeline, a classic trigger for this exact crash.
- Outdated mods and script hooks — an ASI loader or mod that worked last patch can break the renderer after a game update.
- Windows power or GPU selection issues — laptops especially can run the game on the wrong GPU or in a power-saving mode that destabilizes rendering.
- Failing GPU hardware — the least common cause, but if everything else fails and other heavy games crash too, the card itself may be dying.
1Confirm the crash and clean-install your GPU drivers
First, make sure you are fixing the right crash. The Rockstar crash dialog or the crash log (in Documents\Rockstar Games\GTA V) should specifically mention ERR_GFX_STATE. Different codes (like ERR_GFX_D3D_INIT) point at different problems.
Graphics drivers are the most fixable trigger, but a normal driver update often is not enough — leftover files from the old driver survive and keep causing trouble. Do a proper clean install:
- Download Display Driver Uninstaller (DDU) and your GPU maker's latest stable driver — not the beta, and not necessarily the newest release. If the crashes started with a recent driver, roll back to the previous version instead.
- Boot Windows into Safe Mode, run DDU, and choose Clean and restart for your GPU brand.
- Install the fresh driver with the Clean installation option checked, then reboot normally.
NVIDIA players often have better luck with the Studio driver line for stability; AMD players should prefer the WHQL (recommended) Adrenalin release over optional ones. Launch GTA V and test for an hour before changing anything else — if the crashes started right after a driver update, this fix alone usually ends them.
2Kill the overclock — including the factory one
This is the fix that resolves the most stubborn ERR_GFX_STATE cases, because GTA V's engine trips on clock instability that no other game or stress test notices. Crucially, this applies even if you never overclocked anything yourself: many graphics cards ship factory-overclocked (OC editions), and those factory boosts are what GTA V chokes on.
- Install MSI Afterburner (or your card maker's utility) and hit Reset to return to stock clocks. Remove any user overclock or undervolt.
- If crashes continue, try a small downclock: drop the core clock by 50–100 MHz and the memory clock by 50–100 MHz. This sounds like giving up performance, but it is a diagnostic test — if the crash disappears, clock instability was the cause.
- Cap the frame rate at 60 fps (in-game, in the NVIDIA/AMD control panel, or with RivaTuner). Uncapped frame rates push the GPU to maximum boost constantly, which is exactly when borderline clocks fail.
- Make sure your power limit and temperature limit are at stock — aggressive power limits from mining or efficiency profiles can cause the same instability.
Thousands of crash reports over the years trace back to this one issue: a card that is perfectly stable in benchmarks crashes GTA V at its factory boost clock, and a modest downclock fixes it permanently. If the crash vanishes at lower clocks, you have your answer — run the slightly lower clock for GTA V, or investigate cooling and power delivery if you want the full clock back safely.
3Switch the DirectX version and reset graphics settings
GTA V lets you choose its rendering API, and the default (DirectX 11) is not always the most stable on a given system. The game stores your choice — and every other graphics option — in settings.xml, which can also end up with an invalid combination after updates:
- If the game launches, go to Settings → Graphics and change DirectX Version from DirectX 11 to DirectX 10.1 or DirectX 10. Apply, restart the game, and test. Some systems are rock-solid on DX10 while crashing on DX11.
- If the game crashes before you can change anything (or to be thorough), delete settings.xml: close the game completely, go to
Documents\Rockstar Games\GTA V, and deletesettings.xml(keep a backup copy elsewhere if you like). The game rebuilds it with safe defaults on next launch. - When you re-tune graphics, change one setting at a time and test — long shadows and high-resolution shadows are historically heavy triggers, so leave them at normal or off.
You can also force the DirectX version with a command-line switch: add -dx10 to the game's launch options in Steam (or a commandline.txt in the game folder for the Rockstar Launcher version). If deleting settings.xml fixed it, one of your old graphics settings was the crash trigger — leave the suspect settings at default and enjoy a stable game.
4Verify the game files
A single corrupted texture, shader, or audio bundle can crash the renderer every time the game tries to load it — which is why this error sometimes strikes at the exact same point in the map. Re-downloading clean copies fixes it:
- Steam: right-click GTA V → Properties → Installed Files → Verify integrity of game files. Let the scan finish and re-download whatever it flags.
- Rockstar Games Launcher: select GTA V → Settings → Verify integrity (under General). Same idea — it repairs damaged chunks.
Do this after a clean driver install if possible: a crash mid-verify is rare, but you want the system as stable as it can be before a multi-gigabyte scan. If verification finds and replaces files and the crash pattern was tied to one location, there is a good chance your problem just ended.
5Disable overlays and background capture tools
Every overlay that hooks into the game is another thing that can upset the render pipeline. Before launching GTA V, turn off everything you do not strictly need:
- Steam overlay: Properties → General → uncheck "Enable the Steam Overlay while in-game."
- Discord overlay: User Settings → Game Overlay → disable "Enable in-game overlay."
- NVIDIA GeForce / AMD Adrenalin overlay: disable the in-game overlay in the driver software settings.
- Xbox Game Bar: Windows Settings → Gaming → Xbox Game Bar → Off, plus disable background recording.
- MSI Afterburner OSD / RivaTuner: close them or at least disable the on-screen display (keep Afterburner running only if you need it for the downclock in Fix 2 — the OSD, not the app, is the trigger).
- Close streaming or capture software like OBS unless you are actively streaming.
Launch the game completely clean and play your usual session length. If it stays stable, re-enable overlays one at a time with a test session in between — the one that brings the crash back is your culprit, and most players end up permanently disabling just that one.
6Set Windows to use the right GPU and full performance
This matters most on laptops with dual graphics (integrated + discrete), but desktop users benefit from the performance settings too:
- Open Windows Settings → System → Display → Graphics, find GTA V (add it manually if it is not listed), and set it to High performance so Windows always uses your discrete GPU.
- Right-click GTA5.exe → Properties → Compatibility → check Disable fullscreen optimizations. This removes a Windows feature that has caused render instability for some players.
- In the NVIDIA Control Panel (Manage 3D settings → Program Settings → GTA V) or AMD Adrenalin, set Power management mode to Prefer maximum performance / disable power-saving for the game.
- As a diagnostic, drop the resolution to 1080p and the graphics preset to Normal/High. If the crash disappears at lower settings, the issue is load-related (clocks, thermals, or power) rather than a corrupted file.
Do not run the game as administrator as a permanent habit unless you must — but try it once as a test (right-click → Run as administrator), because permission problems with shader-cache writes have caused this crash for some players.
7Remove mods and corrupted script hooks
If you have ever modded the game, an outdated mod is a prime suspect — especially right after a GTA V update, when ASI plugins built for the old version start crashing the renderer. This applies even if you "are not using mods right now": leftover hook files load automatically:
- Open your GTA V install folder and look for dinput8.dll, ScriptHookV.dll, OpenIV.asi, and any other .asi files.
- Move them (and the mods folder, if present) to a backup folder on your desktop — do not delete them yet, just get them out of the game folder.
- Launch the game completely vanilla and test.
If the vanilla game is stable, re-add mods one at a time, testing between each. The one that brings back ERR_GFX_STATE gets updated or retired. And never copy an old mods folder over a freshly updated game — update your ASI loaders first, always.
8Rule out hardware and reinstall as a last resort
If seven fixes did not stop it, it is time to determine whether the problem is GTA-specific or system-wide:
- Stress-test the GPU: run a demanding benchmark (Unigine Superposition, 3DMark Time Spy) or a heavy game for an hour. If other 3D workloads crash or artifact too, the card itself is suspect — check temperatures, reseat the card, check power connectors, and look up your warranty before you do anything else.
- Full reinstall of the game: if the hardware tests clean, uninstall GTA V completely, delete any leftover files in the install folder, and re-download from scratch. Tedious, but it eliminates every possible local corruption in one move.
- Contact Rockstar Support: if a clean game on stock clocks with clean drivers still crashes, send them your dxdiag report and the ERR_GFX_STATE crash log from
Documents\Rockstar Games\GTA V. Include your GPU model, driver version, and which fixes you already tried — support threads move much faster with that evidence attached.
One more edge case worth checking before support: RAM instability. Unstable memory overclocks (XMP profiles included) can crash 3D renderers in ways that look like GPU problems. If you run XMP, try disabling it for one test session — it is a two-minute BIOS change that has resolved "GPU" crashes more than once.
Quick checklist to keep ERR_GFX_STATE away
- Keep GPU drivers current — but roll back immediately if a new driver and new crashes arrive together.
- Run stock GPU clocks for GTA V, or a slight downclock if your card is factory-overclocked and crash-prone.
- Cap the frame rate at 60 fps to keep the card out of peak-boost instability.
- Play overlay-free: disable Discord, Steam, NVIDIA/AMD, and Xbox Game Bar overlays before long sessions.
- Verify game files after every major GTA V update, and update ASI loaders before re-adding mods.
- Keep the GPU cool — clean dust regularly and make sure case airflow is real, not theoretical.
Frequently asked questions
What does GTA V ERR_GFX_STATE mean in plain English?
It means the game's graphics renderer crashed — GTA V asked your graphics card to do something and the driver or card failed to complete it, so the game crashed to desktop. The most common triggers are unstable GPU clocks (including factory overclocks), buggy graphics drivers, corrupted game files, and overlay software interfering with rendering.
Is ERR_GFX_STATE always a hardware problem with my GPU?
No — usually it isn't. Most ERR_GFX_STATE crashes trace back to software: an unstable overclock, a bad driver update, corrupted graphics settings, or an overlay. Hardware failure is the least common cause. If the crash happens only in GTA V and nowhere else, treat it as software first and work through this guide in order.
Can overclocking my GPU cause ERR_GFX_STATE even if other games run fine?
Yes — this is the single most reported cause. GTA V's engine is unusually sensitive to clock instability: a GPU that passes stress tests and runs other games fine can still crash GTA V at its boost clocks. Reset to stock clocks in MSI Afterburner, or try a 50–100 MHz downclock on the core, and many players see the crashes stop immediately.
Why does ERR_GFX_STATE keep happening at the same spot in GTA V?
Because the crash is triggered by something specific at that point — a corrupted texture or asset the game loads there, a graphics setting that pushes the card past its stable point, or a shader that fails to compile. Verify the game files to fix corrupt assets, delete settings.xml to reset the graphics config, and switch the DirectX version — one of those usually breaks the pattern.
Does disabling overlays really fix ERR_GFX_STATE?
Often enough that it's worth doing early. Discord, Steam, NVIDIA GeForce, and Xbox Game Bar overlays all inject code into the render pipeline, and that injection is a known trigger for this exact crash. A clean launch with every overlay off takes two minutes and has resolved ERR_GFX_STATE for many players when nothing else changed.
What should I do if ERR_GFX_STATE still happens after all the fixes?
Test whether the crash is GTA-specific by running a demanding benchmark or another heavy game. If other 3D workloads crash too, suspect the hardware: rising temperatures, artifacting, or crashes under load point to a failing card — check your warranty. If only GTA V crashes, do a full clean reinstall and send your dxdiag and the ERR_GFX_STATE crash log to Rockstar Support.
For most players, ERR_GFX_STATE ends at Fix 1 or Fix 2 — a bad driver or a borderline GPU clock was all it took. The crash looks terrifying because it kills the game with a cryptic dialog, but underneath it is usually the renderer tripping over something entirely fixable in software. And while your fresh install downloads, the free browser games here on GameAdda run entirely in your browser — no drivers, no launchers, no crashes. 🎮