How to fix VALORANT crashing and freezing with no error code
A crash with no code still leaves fingerprints. The way it fails, silent close, mid-game freeze or blue screen, points at a different culprit each time, and matching the shape first saves you the generic ten-step slog.
By Neeraj Singh ~10 min Updated Jul 2026 84% found this helpful
Error message
VALORANT closes silently, freezes mid-game or crashes to desktop with no error code shown
Quick fix
Game closes silently at launch, no error at all? That is the Vanguard service in a broken state, the classic no-code crash. Reset it: services.msc > vgc > Automatic > Start, and turn off Fast Startup. Method 1 walks you through it.
Blue screen, or the whole PC locks with sound looping? Deeper than this page: if the stop screen names vgk.sys, go straight to our vgk.sys BSOD guide.
Seeing an actual VAN code with the crash? The code names your guide, start at the Vanguard error index and match it, coded crashes have exact fixes.
No code? The crash shape is your code
Coded errors hand you a number to look up. A no-code crash makes you read the failure itself, and the shapes separate cleanly. A silent close at launch, where the game never reaches the menu, points at the Vanguard service sitting in a broken state, often after a Windows update or a Fast Startup boot. A mid-game freeze or crash to desktop under load points at the graphics driver, an unstable overclock or a conflicting overlay. A machine-wide lock with looping audio, or a blue screen, is below the game entirely, driver or hardware territory, and a stop screen that prints vgk.sys has a dedicated guide. Riot's Windows 11 requirements sit underneath all of it: a system missing TPM 2.0 or Secure Boot fails before crashing even becomes possible, which the VAN 9001 guide covers. Match your shape, work its lane and skip the lanes that are not yours.
Figure 1: four crash shapes, four different roads
✓ How to fix it
Work the lane your crash shape picked. Method 1 owns silent launches, Methods 2 to 4 own the mid-game failures, Methods 5 and 6 are the file-level and last-resort layers for either lane.
Method 1
Silent close at launch: reset the Vanguard service properly
1Press Win+R, run services.msc, find vgc, set Startup type to Automatic, click Apply and then Start if it is stopped.
2Kill the boot state that breaks it: search Choose what the power buttons do, click Change settings that are currently unavailable and untick Turn on fast startup. Fast Startup resumes Windows from a saved kernel state, which is exactly what a kernel-level anti-cheat hates waking up in.
3Do one real restart, not shutdown-and-power-on, and launch as administrator. The game reaching the menu and a match is your success sign, this lane clears most silent launch closes.
Method 2
Mid-game crashes: clean-install the graphics driver
1Skip the plain update button. Download the current driver from NVIDIA, AMD or Intel directly, and pick the installer's clean install option, a standard update can carry damaged files and stale settings straight into the new version.
2For crashes that survived a normal update, go the whole way: run DDU (Display Driver Uninstaller) in Safe Mode to strip the old driver completely, then install the fresh one on the blank slate.
3Play a few matches. Freezes that die to the clean driver were driver-state corruption, the usual first suspect in the mid-game lane, and you are done.
Figure 2: why an update can fail where a clean install works
Method 3
Return overclocks, XMP and tuning to stock
1In the BIOS, disable CPU and GPU overclocks and set the memory profile (XMP or EXPO) to off or default. A profile that survives other games can still fail VALORANT's load pattern, stability is per-workload, not universal.
2On Intel 13th and 14th Gen systems, also install the board maker's latest BIOS, the microcode updates for those CPUs' instability issues have ended many mystery crash streaks on otherwise healthy machines.
3Test at stock for a session, and watch temperatures while you do, Task Manager's GPU readout is enough. Sustained overheating produces exactly these under-load freezes, and a dusty cooler is a cheaper fix than anything else on this page. Stable and cool at stock means the tuning was the culprit, re-apply it in smaller steps if you want it back, testing between each.
Method 4
Strip the conflict layer: overlays and monitoring tools
1Turn off every overlay while you test: Discord, Steam, GeForce Experience or the NVIDIA App, Overwolf and the tracker apps built on it, plus any RGB or monitoring suite that draws on top of games. Overlays inject into the game's rendering, which is a classic crash source next to an anti-cheat.
2Close MSI Afterburner, RivaTuner and similar tuning tools completely, their hooks conflict with Vanguard often enough to earn a permanent spot on this list.
3Crashes gone with everything off? Re-enable one tool per session until the culprit shows itself, then leave that one retired during VALORANT.
Method 5
Repair the game files, then Windows itself
1Open the Riot Client, go to the settings for VALORANT and run Repair. It verifies and replaces damaged game files without a full redownload, the right tool after a patch left something torn.
2Run Windows Update to the end as well, graphics and kernel components the game leans on ship through it.
3Launch and play. A crash streak that started with a patch and ends with Repair was damaged files, one of the most satisfying closes on this page.
Method 6
Last resort: reinstall Vanguard, then the game
1Give the anti-cheat a fresh state first: open Command Prompt as administrator, run sc delete vgc and sc delete vgk, restart, delete the Riot Vanguard folder in C:\Program Files, then launch the game so Vanguard reinstalls and restart once more.
2Still crashing? Uninstall VALORANT too, restart and install fresh from the official Riot site, slow but occasionally the only cure for a deeply corrupted install.
3Your progress, rank and purchases live on your Riot account, so nothing is lost in either reinstall. A clean install that holds through several sessions closes the software side entirely.
Crashed out of a competitive match? Rejoin before you troubleshoot: VALORANT lets you reconnect to a live match from the play screen, and the penalty system punishes absence, not misfortune. Fix the machine after the match, not during it.
Common causes of VALORANT crashes and freezes
The vgc service in a broken state after a Windows update or Fast Startup boot (silent closes).
Corrupted or outdated graphics driver state (mid-game freezes and crashes to desktop).
Unstable overclocks and XMP or EXPO memory profiles, including Intel 13th and 14th Gen instability.
Overlays and monitoring hooks, Discord, GeForce, Afterburner and RivaTuner, conflicting with the game.
Game files damaged by an interrupted patch, or a system below Riot's requirements.
Expert insight
“I never start a crash case with a fix, I start with a question: what does the failure look like? A game that dies silently before the menu has a service problem, and I am in services.msc within a minute. A game that folds ten minutes into a match has a graphics or tuning problem, and my money is on the driver state or the XMP profile long before the game files. The habit that saves the most time is the clean driver install, people update drivers five times and stay broken, then a DDU pass fixes it in one, because the update kept dragging the corruption along. And overlays earn their retirement one crash at a time.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
Make sure this is the error you have
This page is for crashes without a code, and three neighbours handle the rest. A blue screen naming vgk.sys belongs to the vgk.sys BSOD guide. Stutter, frame drops and a fan-spinning CPU without a crash belong to the high CPU and stutter guide. And any crash carrying an actual VAN code, or a “Vanguard not initialized” popup, starts at the Vanguard error index or the vgc guide respectively, coded failures have exact fixes and deserve them.
Frequently asked questions
Why does VALORANT crash with no error message?
A silent close, especially at launch, usually means the Vanguard service was in a broken state before the game could even draw an error, commonly after a Windows update or a Fast Startup boot. Resetting the vgc service and restarting properly clears most of these, which is why it is Method 1 rather than anything graphics-related.
Is Vanguard causing my VALORANT crashes?
Sometimes, and the crash shape hints when. Silent closes at launch point at the Vanguard service, and blue screens naming vgk.sys are Vanguard's kernel driver colliding with something, that one has its own guide. Mid-game freezes and crashes to desktop usually sit with graphics drivers, overclocks or conflicting tools rather than the anti-cheat itself.
Why did the crashes start right after a game patch?
Patches change what the game asks of your drivers and can leave files half-updated. Give the Riot Client one full update cycle, run its Repair function so damaged files are replaced, and update the graphics driver, that trio settles most post-patch crash waves.
Why does my whole PC freeze with the sound stuck in a loop?
A machine-wide freeze with looping audio is deeper than the game: it is the signature of a driver or hardware-level fault, unstable overclocks and memory profiles included. Return the CPU, GPU and XMP or EXPO profiles to stock and test, and if the freezes end in a blue screen naming vgk.sys, follow that dedicated guide.
Do I get penalized when VALORANT crashes mid-match?
Rejoin quickly and usually not. VALORANT lets you reconnect to a match in progress from the play screen, and penalties are aimed at players who stay away rather than the crash itself. Get back in first, then come back to fixing once the match is done.
Should I clean-install the graphics driver instead of updating it?
For crash troubleshooting, yes. A standard update can carry old settings and damaged files forward, while a clean install, the option in the installer or the full DDU route, rebuilds the driver state from zero. Crashes that survive updates often die to a clean install for exactly that reason.
Why do overclocks and XMP cause VALORANT crashes when other games run fine?
Stability is per-workload: an overclock or memory profile can pass one game's load pattern and fail another's. VALORANT plus Vanguard's kernel presence stresses systems in its own way, so a profile that is marginal shows up here first. Testing at stock costs nothing and instantly rules the whole category in or out.
When is reinstalling the game the right move?
Last, after the Repair function, a clean graphics driver and a fresh Vanguard have all had their chance, because a full reinstall mostly replaces the same files Repair already checks. If you do reach it, uninstall both VALORANT and Vanguard, restart, then install fresh from the Riot site, with your progress safe on your account.
Still not working?
A no-code crash that survives every lane deserves a look at the evidence Windows kept: open Event Viewer > Windows Logs > System, find the errors stamped at your crash times and read what faulted, a repeating driver or hardware source there turns guesswork into a named suspect. Check your specs against Riot's minimums too, including the Windows 11 TPM and Secure Boot requirements in the VAN 9001 guide, and on a machine near those minimums, lower Settings > Video > Graphics Quality in the game, Riot's own crash guidance recommends reducing the load, and marginal systems crash less when less is asked of them. Browse the full set of Riot Vanguard error guides, or submit your error to us for a tailored fix.
