How to Fix CS2 Crashes: Every Method That Works in 2026

CS2 crashes on launch, drops out mid-match, or freezes the screen entirely. It's one of the most frustrating problems you'll encounter. Causes vary: corrupted files, outdated drivers, overlay conflicts, broken shader cache. Let's work through every effective fix in order, from simplest to most involved.

Method 1: Verify File Integrity

The first thing to do with any crash. Takes 5–10 minutes and repairs corrupted or missing game files.

1. Steam → Library
2. Right-click on Counter-Strike 2 → Properties
3. Installed Files tab
4. Click "Verify integrity of game files"

Restart CS2 after it completes. If this fixed it, there was a file error. If not, keep reading.

Method 2: Update or Reinstall GPU Driver

An outdated or conflicting driver is one of the top 3 causes of CS2 crashes.

NVIDIA update via GeForce Experience:

1. Open GeForce Experience → Drivers tab
2. Click Download → Express Installation

NVIDIA clean install via DDU (for persistent crashes):

1. Download Display Driver Uninstaller (DDU) from guru3d.com
2. Reboot into Safe Mode (Win + R → msconfig → Boot → Safe boot)
3. Run DDU, select GPU → Clean and Restart
4. After reboot, install the latest driver from nvidia.com

AMD: AMD Adrenalin → Drivers → Check for Updates → Install.

If a new driver itself causes crashes, roll back via Device Manager → Display Adapters → right-click GPU → Properties → Driver → Roll Back Driver.

Method 3: Launch Options

Some launch options stabilize CS2; others cause crashes.

1. Steam → Library → CS2 → Properties → General tab
2. Launch Options field

Add for stability:

• -novid skips startup video (always safe)
• -nojoy disables joystick detection
• -dx11 forces DirectX 11 (more stable on older NVIDIA cards)

Remove if present (these can cause crashes):

• -vulkan is unstable on many configurations, especially NVIDIA
• +cl_forcepreload 1 is outdated and causes crashes during map loading
• -threads X: manual thread count worsens stability
• -dx12 is officially unsupported in CS2

If crashing on launch, try -safe: it launches CS2 with minimal settings and resets graphics configs.

Method 4: Clear Shader Cache

Corrupted shader cache is a common cause of crashes after CS2 updates.

Step 1. Delete CS2 shader cache:

• Path: C:/Program Files (x86)/Steam/steamapps/shadercache/730
• Delete all contents of the folder (don't delete the folder itself)

Step 2. Clear DirectX Shader Cache via Windows:

1. Win → search → Disk Cleanup
2. Select drive C → find DirectX Shader Cache
3. Check the box → OK

Step 3. NVIDIA cache (cmd as administrator):

• DEL /Q /F /S "%USERPROFILE%AppDataLocalLowNVIDIAPerDriverVersionDXCache*"

Shaders rebuild automatically on next launch, so the first startup will take longer than usual.

Method 5: Disable All Overlays

Overlays are the most invisible and most common cause of mid-match crashes. Each overlay injects into the CS2 process and can conflict with rendering.

• Discord Overlay: Discord → Settings → Activity Privacy → disable "Enable Game Overlay"
• NVIDIA GeForce Experience: Settings → General → disable "In-Game Overlay"
• Steam Overlay: Steam → CS2 → Properties → uncheck "Enable the Steam Overlay while in-game"
• Xbox Game Bar: Windows → Settings → Gaming → Xbox Game Bar → Off
• Others: NZXT CAM, MSI Afterburner, Razer Cortex; close or disable the overlay in each

Disable one at a time to identify the specific culprit.

Method 6: Lower Graphics Settings

Crashes under load (at round start, during grenade throws) often indicate GPU overheating or an unstable overclock. Lowering settings is a quick diagnostic.

• Display Mode → Borderless Windowed (removes fullscreen conflict with Windows DWM)
• Global Shadow Quality, Model / Texture Detail → Low
• Multisampling Anti-Aliasing Mode → None
• NVIDIA Reflex Low Latency → On (without Boost, reduces GPU load)
• Console command: fps_max 144 (or match your monitor's refresh rate), which removes peak GPU load

If crashes stopped after lowering settings, the issue is overheating. Check temps via HWiNFO64: GPU above 85°C, CPU above 90°C means you need to clean the cooler or replace thermal paste.

Method 7: Reset CS2 Config Files

Corrupted or outdated configs cause crashes especially after major patches.

1. Save a copy of your autoexec.cfg (if you have one)
2. Navigate to: C:Program Files (x86)SteamsteamappscommonCounter-Strike Global Offensivegamecsgocfg
3. Delete the entire cfg folder
4. Steam → CS2 → Verify integrity of game files (folder recreates automatically)

If Steam Cloud restores old settings, temporarily disable sync: CS2 → Properties → General → uncheck "Keep games saves in the Steam Cloud."

Also delete user settings files:

• Path: C:/Program Files (x86)/Steam/userdata/{SteamID}/730/local/cfg/
• Delete: cs2_video.txt, cs2_machine_convars.vcfg

Method 8: Windows and Hardware

XMP / EXPO (RAM):

If XMP (Intel) or EXPO (AMD) is enabled in BIOS, temporarily disable it and run RAM at the base JEDEC speed. If crashes stop, your XMP profile is unstable on your hardware. You'll need to either raise DRAM voltage in BIOS or adjust timings.

Disable Fullscreen Optimizations:

1. Find cs2.exe: …SteamsteamappscommonCounter-Strike Global Offensivegameinwin64cs2.exe
2. Right-click → Properties → Compatibility tab
3. Check "Disable fullscreen optimizations" → Apply

Reinstall Visual C++ Redistributables:

1. Windows → Settings → Apps → find all Microsoft Visual C++ Redistributable 2015–2022 (x86 and x64)
2. For each: Modify → Repair
3. If Repair doesn't help: uninstall all, download fresh ones from Microsoft, reinstall
4. Reboot your PC

If Nothing Worked: Known Valve Bugs

Sometimes crashes are a Valve-side bug, not a hardware issue:

• Premier Mode freeze / BSOD is a documented bug: deadlock between fullscreen exclusive renderer and Windows DWM. Workaround: switch to Borderless Window in CS2 settings.
• Post-patch crashes: Valve regularly releases same-day hotfixes. Check Steam News for CS2 for a patch and update the game.
• Crashes on one specific map? Delete its workshop cache: C:/Program Files (x86)/Steam/steamapps/workshop/content/730/

If nothing worked, contact Steam Support with an attached crash dump. The dump file is located at: C:/Users/{Username}/AppData/Local/Temp/dumps/

If the game doesn't crash but just runs slow, see how to boost FPS in CS2. And for connection drops, the how to fix packet loss guide will help. Once the game stops crashing, it is time for settings: pro sensitivities and crosshairs are collected in the settings database.