Why CS2 Keeps Crashing on PC (and How to Fix It)

CS2 keeps crashing on PC most often because of damaged game files, a launch option or config line the current build doesn’t handle, or an unstable GPU driver. Verify the game files in Steam, remove your launch options, then clean-install your graphics driver; most Counter-Strike 2 crashes stop there. The rest of this guide covers the specific crashes Valve has fixed in 2026 patches, and the hardware causes to check if the crash follows you into other games.

Start with Steam. Most CS2 crash fixes take a few minutes.

Quick answer: match the crash to the fix

When CS2 crashes	Most likely cause	Fix first
On startup, before the menu	Damaged files, launch options, audio device override	Verify files, clear launch options
With “FATAL ERROR: Failed to on-demand compile shader”	Outdated build or driver on an older GPU	Shader error fix
Mid-match, randomly	GPU driver, overlays, unstable memory overclock	Driver, XMP test
In every game, not just CS2	Hardware or Windows	Hardware checks

1. Verify CS2’s game files in Steam

Damaged or missing files are the most common reason Counter-Strike 2 crashes, and Steam can repair them without a reinstall.

1. Open your Steam Library.
2. Right-click Counter-Strike 2 and choose Properties.
3. Open Installed Files and click Verify integrity of game files.

Steam checks every file and re-downloads only the ones that fail (Steam Support: Verify Integrity of Game Files). Launch CS2 again when it finishes.

2. Remove launch options and config overrides

Launch options and autoexec lines are applied before CS2 reaches the menu, so a bad one can crash the game at startup every time.

1. In Steam, right-click Counter-Strike 2 → Properties → General.
2. Copy whatever is in Launch Options somewhere safe, then clear the box.
3. Launch CS2. If it now starts, add your options back one at a time to find the one causing the crash.

Valve’s 24 April 2026 update fixed a random startup crash “when a non-default Audio Device was specified in settings or when sound_device_override was specified in a config file or on the command line” (CS2 update notes). If CS2 still crashes at launch and you use that command, remove sound_device_override from your launch options and autoexec, set your headset as the Windows default playback device, and test again.

If you added a launch option to change CS2’s renderer, remove it too, so the game starts on its default renderer. Valve shipped “stability improvements for Vulkan renderer” on 14 October 2026, so if you do run the Vulkan renderer, make sure the game is fully updated first.

3. “FATAL ERROR: Failed to on-demand compile shader”

This fatal error appeared on some older graphics cards, and Valve’s 30 April 2026 update notes list it as fixed: “Fixed ‘FATAL ERROR: Failed to on-demand compile shader’ affecting some older GPUs.”

If you still see it:

1. Let Steam finish updating CS2, then verify the game files.
2. Clean-install your GPU driver.
3. Check your graphics card against Valve’s minimum: DirectX 11 support with Shader Model 5.0 and at least 1 GB of video memory. A card below that can’t run CS2 reliably.

4. Clean-install your GPU driver

A corrupted or half-updated graphics driver causes random crashes to desktop mid-match. Install the latest driver for your card from NVIDIA, AMD or Intel; if crashes started right after a driver update, remove it completely with DDU first. Our DDU clean install guide walks through it step by step.

Valve also patches GPU-specific bugs from its side. For example, the 28 October 2026 update fixed liquid rendering black on AMD cards, so keep both the game and the driver current.

5. Close overlays and background tools

Overlays and monitoring tools hook into CS2’s renderer, and any one of them can crash it. Close or disable them one at a time to test:

• The Steam overlay, the Discord overlay, and the NVIDIA or AMD overlay.
• FPS and hardware monitors such as MSI Afterburner and RivaTuner. If you still want an FPS counter, use one built-in option at a time; see how to show FPS in any game.
• RGB and peripheral software you don’t need while playing.

6. Test without XMP or EXPO

An unstable memory overclock produces crashes that look like game bugs. If CS2 crashes at random points with no pattern, turn XMP or EXPO off in the BIOS and play a few matches. If the crashes stop, your RAM isn’t stable at its rated profile: update the BIOS, then try the profile again or lower the memory speed one step. Our XMP and EXPO guide shows where the setting lives on each board brand.

7. If every game crashes, check the hardware

When CS2 isn’t the only game crashing, the cause sits below the game:

• Windows system files: run sfc /scannow and DISM from an elevated command prompt; see fixing DLL errors with DISM and SFC.
• BIOS: Intel 13th and 14th gen desktop processors received microcode stability fixes through motherboard BIOS updates. If you have one of those CPUs, update your BIOS safely.
• RAM and storage: CS2’s minimum is 8 GB of RAM and 85 GB of free space. A nearly full drive or too little memory can crash the game while loading maps.
• Temperatures: a GPU or CPU that overheats under load shuts the game down. Watch temperatures with an overlay during a match.

CS2 crashes Valve has fixed in 2026

Valve lists crash fixes in its Counter-Strike 2 update notes. If you hit one of these, updating the game is the fix:

Update	Crash fixed
22 Oct 2026	Crash in GameRules.AddTeamMoney (custom-map scripting)
14 Oct 2026	Stability improvements for the Vulkan renderer
18 May 2026	A potential crash in exception handling
30 Apr 2026	”FATAL ERROR: Failed to on-demand compile shader” on some older GPUs
24 Apr 2026	Random startup crash with a non-default audio device or sound_device_override
20 Apr 2026	Crash at halftime when switching from CT to T

Related guides

• CS2 Stuttering Fix: when the game runs but hitches instead of crashing.
• Best CS2 Settings for FPS
• CS2 Lowest Input Lag Settings
• CS2 “VAC Was Unable to Verify Your Game Session” Fix
• CS2 Stretched Resolution