Why does Valorant freeze on the loading screen?

Almost always Vanguard, Riot's anti-cheat, which has to load while Windows starts. If it didn't load, Valorant hangs with nothing to talk to. Use Start → Power → Restart rather than Shut down — Windows Fast Startup means a shutdown doesn't fully reload the driver. Check it with sc query vgc in Command Prompt; STATE should read RUNNING.

Why does Valorant crash after one match?

That timing points to heat. One match is roughly how long it takes a dusty or poorly ventilated PC to reach the limit where it shuts down to protect itself. Clear the vents and fans of dust, make sure a laptop is on a hard flat surface, and watch the temperature while you play.

Do I need to reinstall Valorant to fix crashes?

Usually not. Use the Riot Client's Repair option instead — it checks every file and replaces only the damaged ones, which is far faster than a reinstall and fixes the same problem. Try a real restart, a clean graphics-driver install, and Repair before reinstalling anything.

Can Discord cause Valorant to crash?

Yes. Discord's in-game overlay hooks into the game's graphics to draw on top of it, and Vanguard is strict about anything reaching into Valorant that way. Turn the overlay off in Discord's User Settings → Game Overlay and see whether the crashes stop. NVIDIA's overlay and Xbox Game Bar can do the same.

How do I know if it's my graphics driver?

Run Get-WinEvent -LogName System -MaxEvents 200 | Where-Object {$_.Message -like '*display driver*'} in PowerShell. Entries about the display driver stopping and recovering that line up with your crash times point at the driver. Fix it with a clean install from NVIDIA, AMD or Intel — not an update over the top.

Valorant Crashing or Freezing on PC? How to Fix It (2026)

Valorant either won't get past the loading screen, drops you to the desktop mid-match, or locks the whole PC hard enough that you have to hold the power button. Valorant runs an anti-cheat driver that loads before Windows finishes starting, so a Valorant problem is often not a Valorant problem.

The first thing to sort out is when it fails. A freeze on the loading screen points somewhere completely different from a crash ten minutes into a match. Below are the causes, most common first. Fix it by hand, or let Noah check the graphics driver, Vanguard's state and what else is running, and clear it with your approval (more at the end).

Vanguard didn't load with Windows

Stuck on the loading screen, or the game closes straight away with no error message.

Valorant will not run without Vanguard — Riot's anti-cheat. It is a driver, a piece of software that loads as part of Windows itself, and it has to start while Windows does. If it didn't, the game has nothing to talk to, and it hangs or quits silently.

Windows has a feature called Fast Startup, which makes shutting down closer to hibernating than genuinely powering off — so "Shut down, then turn it back on" does not reload Vanguard's driver. Only a real restart does.

Fixuse Start → Power → Restart, not Shut down. If it still hangs, turn Fast Startup off. Open Control Panel → Power Options → Choose what the power buttons do, click Change settings that are currently unavailable, then untick Turn on fast startup.

If it still fails after a real restart, check that Vanguard's service is actually running:

zsh — Terminal

% sc query vgc

Run in Command Prompt. STATE should read RUNNING. If it says STOPPED, Vanguard isn't loaded — restart first, and reinstall Vanguard if that doesn't take.

NoahNoah checks whether Vanguard's service and driver actually came up, and whether Fast Startup is quietly preventing it — the two things that make this look like a game bug when it isn't.

The graphics driver crashed

The game closes to the desktop mid-match, sometimes after a black screen or a brief flicker.

Valorant is light on graphics compared to most shooters, which misleads people into ruling the graphics driver out — the software that lets Windows talk to your graphics card. Light load or not, a driver that has been upgraded repeatedly on top of itself accumulates leftovers, and when it fails the game is closed instantly to protect Windows.

The fix that works is a clean reinstall, not the ordinary one. An ordinary update installs over the top and keeps whatever was broken.

Fixget the current driver straight from NVIDIA, AMD or Intel — not from a driver-updater tool — and during setup pick Custom install → Perform a clean installation. Expect the screen to flicker and go black briefly; that's normal. Restart afterwards even if it doesn't ask.

To confirm it really was the driver, check Windows' own record of it:

zsh — Terminal

% Get-WinEvent -LogName System -MaxEvents 200 | Where-Object {$_.Message -like '*display driver*'}

Run in PowerShell. Entries about the display driver stopping and recovering line up with your crashes if this is the cause.

The PC is overheating

The first match is fine, then it freezes or the whole PC locks up — reliably, after roughly the same amount of play.

"It crashes after one match" is a temperature pattern, not a software one. A game keeps the processor and graphics chip at full load, they heat up, and once a chip passes its safe limit the PC either slows hard or cuts out to protect itself. Dust in the vents and fans that have stopped spinning up are the usual reasons, and both get worse gradually.

Fixshut down, unplug, and clear the dust from the vents and fans with short bursts of compressed air. Make sure a laptop is on a hard, flat surface — never a bed or a lap — and that a desktop has clear space at the front and back. Then watch the temperature while you play, using your graphics card's own tool (NVIDIA app, AMD Adrenalin) or Task Manager's Performance tab.

NoahNoah can rule the software causes out — whether Vanguard came up, whether the graphics driver failed, what else was running — so heat is what's left, not what you guessed. Noah cannot read this PC's temperatures; use your graphics card's own tool for that.

The shader cache is corrupted

It freezes at the same moment every time — almost always the loading screen or the first seconds of a map.

Windows keeps a shader cache — a store of ready-made graphics instructions, so a game doesn't have to build them again every time it launches. If a crash happens while that file is being written, the cache is left damaged, and the game freezes at the exact point it tries to read the damaged part.

Fixclear it and let Windows rebuild it. Open Disk Cleanup, tick DirectX Shader Cache, and click OK. Nothing is lost — the first launch afterwards is just slightly slower while it rebuilds.

A game file is damaged

Crashes that don't follow a pattern, often after an update or an unclean shutdown.

An interrupted update or a power cut mid-write can leave a single game file damaged. The game runs until it needs that file, then quits — which looks random from the outside. You don't need a full reinstall to fix it.

Fixopen the Riot Client, click the settings icon next to Valorant, and choose Repair. It checks every file and replaces only the broken ones. It takes a while; it's still much faster than reinstalling.

Overlays and background apps are interfering

Crashes that started after installing or updating Discord, a recording tool, or an RGB/fan-control utility.

An overlay — the layer an app draws on top of a game so you can see messages or record — has to hook into the game's graphics to work. Vanguard is deliberately strict about anything reaching into Valorant that way, and the collision shows up as a crash. Fan-control and RGB utilities cause the same trouble for the same reason.

Fixturn off in-game overlays one at a time and see which one stops it. Discord (User Settings → Game Overlay), NVIDIA (NVIDIA app → Overlay), Xbox Game Bar (Settings → Gaming → Xbox Game Bar), and any recording tool. Close RGB and fan-control software entirely while you test.

Commands in this guide are standard, read-only macOS diagnostics unless noted; anything that changes your system is called out. When in doubt, back up first with Time Machine.

Valorant crashing or freezing? Here's how to fix it