Valorant Crashing on PC: Fix Every Crash Type

Valorant crashing on PC almost always comes from one of four things: the “Graphics driver crashed” error (an outdated driver, a GPU overclock or a conflicting driver profile), a crash on startup or the loading screen from damaged game files or a broken local config, a silent crash to desktop from overlays or memory instability, or a Riot Vanguard failure that shows a VAN code — and the message you see, or don’t see, tells you which one to fix first. Match your symptom in the table below, then work only that section.

Getting a VAN code or “Vanguard not initialized” instead of a crash? That’s the anti-cheat, not a crash, and it has its own guide: how to fix Valorant VAN errors.

Match your crash to the fix

What you see	Most likely cause	Go to
”Graphics driver crashed” error window	GPU driver, overclock/undervolt, or a driver profile overriding the game	Fix 1
Crash on launch, at the loading screen or right after a patch	Damaged game files or a broken local config	Fix 2
Crash to desktop mid-match, no error at all	Overlays, memory (XMP/EXPO) or CPU instability	Fix 3
A VAN code, “Vanguard not initialized”, or the game closes before it opens	Riot Vanguard failed to start	VAN error guide

Why Valorant started crashing more in 2025

Valorant moved from Unreal Engine 4.27 to Unreal Engine 5.3 with patch 11.02 on 29 July 2025. The system requirements barely changed and the game still runs on DirectX 11, but the new engine shook loose crashes on PCs that had been stable for years — mostly older or lower-end systems — and Riot shipped follow-up fixes in later patches. The practical lesson: after any big patch, repair the files and update the driver first, before you start changing Windows settings.

Fix 1 — “Graphics driver crashed”

This is Valorant’s most common crash message, and it tells you to make sure your graphics driver is up to date. That’s the right first step, but on a PC with a current driver the cause is usually clocks or a profile, not the driver version.

1. Clean-install the driver. Don’t install over the top — remove the old one with DDU and install the latest from NVIDIA, AMD or Intel. If the crash started right after a driver update, install the previous version instead.
2. Remove every GPU overclock and undervolt — MSI Afterburner curves, AMD Software tuning and factory “OC mode” profiles included. Unreal Engine 5 can expose a clock that passes other games.
3. Reset the driver profile for Valorant. In NVIDIA Control Panel (Manage 3D settings → Program Settings) or AMD Software, reset any per-game profile for VALORANT-Win64-Shipping.exe to default. Forced anti-aliasing, frame limits or low-latency overrides from another game can conflict with it.
4. Laptops: force the dedicated GPU. Settings → System → Display → Graphics, add Valorant and set it to High performance. Running on the integrated GPU by mistake is a common cause on gaming laptops.
5. Test in windowed mode. Pressing Alt+Enter as the game loads switches it to windowed mode, which players widely report stops the error. Treat it as a test: if windowed is stable and fullscreen isn’t, the problem is the display path — see fullscreen vs borderless vs windowed.

If the window names a DirectX failure such as DXGI_ERROR_DEVICE_REMOVED or DXGI_ERROR_DEVICE_HUNG, the GPU stopped responding and Windows reset the driver — the deeper fixes are in the DXGI_ERROR_DEVICE_REMOVED guide and the DXGI_ERROR_DEVICE_HUNG guide.

Fix 2 — Crash on startup or after a patch

When Valorant closes on launch, hangs and dies on the loading screen, or starts crashing the day a patch lands, the usual cause is a damaged download or a local config file the new version can’t read.

1. Repair the game in the Riot Client. Open the Riot Client, click your profile icon (top right) → Settings → VALORANT → Repair, and let it finish. This replaces damaged files without reinstalling the whole game.
2. Reset the local config. Close Valorant and the Riot Client, press Win+R and open %LOCALAPPDATA%\VALORANT\Saved\Config, then delete everything inside the Config folder — this is the step Riot’s own support guide uses to clear broken settings. Launch, reset your settings to default in Settings, then close and relaunch. Your crosshair and keybinds are stored on your Riot account.
3. Make sure there’s free space. The UE5 update needed around 30 GB free to install; a nearly full drive can leave the game half-patched.
4. Reinstall as a last resort. Uninstall Valorant (and Riot Vanguard if Fix 3 didn’t help), restart, and reinstall from the Riot Client.

Fix 3 — Silent crashes to desktop

A crash with no error window at all usually isn’t the graphics driver — DirectX and driver failures name themselves. Look at what’s hooking into the game, and at stability.

1. Close overlays and hooks while testing — Discord, NVIDIA app and AMD overlays, MSI Afterburner/RTSS, Xbox Game Bar, RGB and fan-control software. Re-enable them one at a time once the game is stable. Some low-level tools also clash with Vanguard; the VAN guide’s software-conflict step lists the usual suspects.
2. Disable XMP/EXPO as a test. An overclocked memory profile can pass everyday use and still crash a game. If that fixes it, re-enable it at a slightly lower speed — see how to enable XMP or EXPO for where the setting lives.
3. Remove CPU overclocks and “enhancement” settings. Reset Precision Boost Overdrive, multicore enhancement or any manual CPU overclock to defaults. On Intel Core 13th and 14th Gen desktop CPUs, update the motherboard BIOS to the latest version with Intel’s microcode fix — those chips are a well-documented source of game crashes on old BIOS versions.
4. Check temperatures. A laptop or small case that crashes only after 10–20 minutes of play is often overheating — monitor it with an FPS and hardware overlay.

Check the basics

Valorant runs on very modest hardware — Riot’s minimum is an Intel i3-540 or Athlon 200GE class CPU, Intel HD 4000 or Radeon R5 220 class graphics and 4 GB of RAM — so crashes are rarely about power. What it does require is Windows 10 (build 19041+) or Windows 11, 64-bit, a DirectX 11 GPU, and on Windows 11 TPM 2.0 and Secure Boot for Vanguard. If Vanguard keeps failing, the Secure Boot and TPM explainer covers why it needs them.

Once it stops crashing

Stable but hitching? That’s a different problem — see the Valorant stuttering fix, then tune with the best Valorant settings for FPS and the Valorant lowest input lag settings. For smoother frame pacing underneath, the timer resolution guide covers the Windows scheduling layer.

Related: Fortnite crashing fix · Marvel Rivals crashing fix · Unreal Engine D3D device lost crash