Game Crashes on Startup: The Repair Order That Works

A game that dies before the main menu is almost always one of five things: files that no longer match, a graphics driver that fails to initialise, an overlay injecting a DLL into the process, an anti-cheat driver that Windows refuses to load, or a background program holding a file the game needs. The repair order below is the one Valve, Microsoft and the anti-cheat vendors publish for their own products, and it runs from cheapest to most invasive. Start by timing the crash — no window at all, death on the publisher logo, or a fall at the menu are three different diagnoses.

Short answer

Time the crash before you touch anything: the moment the window dies narrows it to one family.
Verify the game files first. A few files failing verification is normal and safe to ignore, in Valve's own words.
Kill every overlay — storefront, chat, GPU recording — before you go near drivers. Overlays inject into the game process.
Anti-cheat crashes are their own branch: BattlEye documents a direct conflict with Windows 11 Kernel-mode Hardware-enforced Stack Protection.
If nothing sticks, clean boot through msconfig and halve the list until the guilty program appears.

Where the window dies tells you what broke

Watch the screen and Task Manager once, deliberately, before you start fixing. Five seconds of attention here saves an evening.

What you see	Usual family	Where to start
Nothing at all; the process appears and vanishes	Anti-cheat driver or launcher	The anti-cheat section below
Black window, then it closes	Display mode or GPU driver	Force windowed mode, then the driver
Crash on the publisher or engine logo	Driver initialisation, damaged files	Verify files, then a clean driver install
Menu loads, crash a minute later	Overlay or background app	Clean boot
Started only after a game update	Files or an anti-cheat update	Verify files
Started only after a Windows update	Security feature versus anti-cheat driver	The anti-cheat section

Forcing windowed mode is the quickest of these tests, because it removes the fullscreen handover from the equation without changing anything permanent. Most engines accept a launch flag for it; our CS2 launch options guide covers where those flags go and which of them the engine still reads.

Verify the files, then read the result properly

This is the first step for a reason: it is fast, it is reversible, and Valve names damaged files as a cause of both missing content and crashing in play. In Steam it lives under the game's Properties → Installed Files → Verify integrity of game files.

Two warnings from the same Steam Support page get ignored constantly. Do not run verification while another disk-heavy job is running — Valve names defragmenting and virus scanning specifically. And do not verify several games at once.

Then read the outcome correctly. Steam Support says outright that one or more files may fail to verify, that this is normal for most games, and that those files are local configuration files which should not be replaced.

A verification that "fails" on a handful of files is a pass.

Chasing that message with a reinstall is the single most common wasted evening in this whole category. If the storefront threw a coded error instead, that is a different problem — the Steam error messages guide sorts those by the words in the brackets.

Why does the game close without an error message?

Because nothing that could draw a message has loaded yet. The renderer is not up, the game has no window, and the process is gone before the first frame.

The components that do talk are the anti-cheat and the storefront. BattlEye's launcher window prints [INFO] Blocked loading of file: … lines, and BattlEye states these are files the game process itself tried to load, that they are not grounds for a ban, and that they can be ignored when the game runs fine. Riot Vanguard is even more explicit: it shows a numbered code, and every number maps to a documented cause in the VAN error code guide.

So before reinstalling, screenshot whatever those two printed. That text names the file or the setting.

Overlays, injectors and the DLLs left in your game folder

Overlays work by loading their own code into the running game. Most of the time you never notice; when a game and an overlay disagree, the game usually loses at startup.

BattlEye's troubleshooting list is the concrete version of this advice, and it is worth copying: check the game directory and make sure there is no d3d9.dll, dxgi.dll or dsound.dll sitting there, and remove or rename one if you find it. Those three filenames are how graphics-layer injectors and visual mods attach themselves.

Two more from the same list, both easy to check and both non-obvious:

File permissions on the game folder. Right-click the directory, Properties, Security tab, select the SYSTEM entry and confirm it has full access. BattlEye lists a broken SYSTEM permission as a cause of blocked-file spam.
The anti-cheat service through the firewall. BEService.exe in C:\Program Files (x86)\Common Files\BattlEye must not be blocked, and the BE launcher needs unrestricted internet access to update before the game starts.

Valve's own list of interfering software runs in the same direction: antivirus that hooks deep into disk operations, IP filtering tools, and recording utilities all sit in the category Steam asks you to disable for testing.

When it is the anti-cheat, not the game

This branch has grown fast, because kernel-level anti-cheat and new Windows security features keep landing on the same machine.

BattlEye documents the sharpest example. Failed to initialize BattlEye Service: Driver Load Error (1275) appears when Windows 11 blocks the BE driver because Kernel-mode Hardware-enforced Stack Protection is on. BattlEye's answer is to click Disable in the Windows popup and reboot, or search "Core isolation" in the Start menu and switch that specific option off. They also state they fixed the incompatibility on their side and are waiting on a Windows update to unblock the driver — so this one may quietly disappear on your machine without you doing anything.

A second BattlEye code worth knowing: Driver Load Error (577) comes from SHA-2 code-signing support missing on an old, unpatched Windows 7 install.

Riot's side of the world is numbered rather than named, and the numbers separate a ban from a missing BIOS setting. Do not guess between them — look the code up. For Valve's anti-cheat, the session errors have their own family and their own fixes, collected in the VAC verification guide.

One thing this guide will not help with: spoofers, HWID cleaners and "unbanners". They are a Terms of Service violation in themselves and turn a fixable problem into a permanent one.

Do I reinstall the driver, or Windows?

Neither, in that order. Update the graphics driver first — Microsoft's article covers the manual route through Device Manager and Windows Update, which is enough when the driver is merely old. A full removal and fresh install is the step after that, because it costs you every per-game graphics profile you have built.

Valve adds a hardware step people skip because it feels unrelated: disable overclocking. Steam Support states that running hardware outside manufacturer-recommended settings can cause memory and file corruption. A CPU or memory overclock that is stable in a browser and unstable under a loading screen looks exactly like a broken game.

Only then comes the clean boot, and it beats a Windows reinstall because it tells you the name of the culprit. Microsoft's procedure: msconfig → Services tab → Hide all Microsoft services → Disable all → Startup tab → Open Task Manager → disable every enabled startup item → restart. Microsoft warns the machine will temporarily lose some functionality, which is expected and reversible.

If the game launches in that state, something you disabled was killing it. Microsoft's isolation method is the efficient one: re-enable half the list, restart, and repeat on whichever half brings the crash back. A hundred startup entries collapse to one guilty item in about six or seven restarts.

Then put everything back through the same screens — General tab → Normal Startup, Enable all, re-enable the startup apps.

What usually goes wrong

"Verification failed again, so I reinstalled." Symptom: a few files fail every single run. Why: those are local configuration files Steam deliberately does not replace. Fix: ignore the message and move to the next step; a reinstall changes nothing here.
Verified during a virus scan. Symptom: verification is slow, then reports problems that were not there an hour later. Why: Valve warns against running it alongside disk-intensive jobs. Fix: re-run on an idle machine before drawing conclusions.
Turned off one overlay out of three. Symptom: the crash survives disabling the storefront overlay. Why: chat clients and GPU recording tools inject too. Fix: disable all of them, confirm the game launches, then re-enable one at a time.
A stray dxgi.dll from an old visual mod. Symptom: the game worked for months and stopped after an anti-cheat update. Why: BattlEye blocks the load and the process dies. Fix: remove or rename the file in the game directory.
Fixing the game on a failing drive. Symptom: repeated corruption after every repair. Why: Valve's own advanced list includes checking the drive for errors and testing the install on an alternate drive. Fix: create a second library folder on a different disk and install there before touching anything else.

After a clean driver install or a game reinstall your video settings and sensitivity usually come back at defaults, and muscle memory notices within one round. Put your old figure through the sensitivity converter, check the result against pro ranges with the eDPI calculator, and if the mouse started acting strange around the same time, the mouse test says whether the hardware is at fault.

If the game launches now but runs badly, that is a separate investigation: start with FPS drops and stutters, or with keyboard not working in game if the keys went quiet instead. And if the reinstall itself is crawling, the slow Steam download guide has the settings that matter.

FAQ

Why does my game crash on startup with no error message?

Because the crash happens before the game has a window to print one in. The parts that do report are the anti-cheat and the storefront: BattlEye's launcher window prints lines such as "[INFO] Blocked loading of file: …", and Riot Vanguard shows a numbered VAN code. Read those before you reinstall anything — they name the file or the setting that is blocking the launch.

Does verifying game files fix crashes?

It fixes the crashes caused by damaged or missing files, which Valve lists as a reason for both missing content and crashing during play. It will not fix a driver or anti-cheat failure. Valve also warns not to verify while an antivirus scan or a defrag is running, and not to verify several games at the same time.

Some files always fail verification. Is my install broken?

No. Steam Support states plainly that one or more files failing to verify is normal for most games, because those are local configuration files that should not be replaced. The message can be safely ignored, and repeating the check will not change it.

Can an overlay really crash a game?

Yes, and the anti-cheat vendors document it. BattlEye's own troubleshooting asks you to make sure there is no d3d9.dll, dxgi.dll or dsound.dll sitting in the game directory — those are the filenames injectors and visual mods use. Valve separately lists recording software and system tools among the programs that may interfere with games.

Do I need to reinstall Windows if nothing helps?

Not before a clean boot. Microsoft's article walks through msconfig, hiding Microsoft services and disabling the rest, then isolating the guilty item by enabling half at a time — around six restarts finds it out of a hundred entries. Reinstalling Windows removes the same conflict without ever telling you what it was.