The Complete CS2 Crash & Launch Failure Guide: Fix 0x887A0006, VPK Errors, Mac Fatal Crashes, and Faceit AC Blocks

Error Code Quick Reference

Find your symptom and jump straight to the fix.

Diagnostic Checklist (Run This First)

Before diving deep, check these common points of failure. This solves a lot of simple oversights.

TL;DR: The One-Minute Fix Flow

1. Close everything. Exit CS2, Steam, Discord.
2. Kill hidden processes. Open Task Manager (Details tab), end any cs2.exe or GameOverlayUI.exe.
3. For crashes/black screens: Update your GPU driver. If that fails, use DDU (guide below).
4. For Faceit errors: After step 2, launch Faceit AC immediately.
5. For Mac crashes: Lower Shader Detail and Shadow Quality to Medium, delete the shader cache folder.
6. For stretched res crashes: Delete the custom resolution file in the CS2 cfg folder.

If that doesn't nail it, your specific fix is in the sections below.

The Fixes, Grouped by Cause

GPU & Driver Related Fixes (0x887A0006, General Crashes)

Clean GPU Driver Reinstall with DDU

When this applies: You're getting the 0x887A0006 black screen, random driver crashes, or general instability after a Windows/game update. This is the fix for 90% of GPU-related errors.

1. Download the latest driver from NVIDIA or AMD. Have the installer .exe ready on your desktop.
2. Download Display Driver Uninstaller (DDU) from guru3d.com.
3. Boot into Windows Safe Mode with Networking. Press Windows key + R, type msconfig, go to the Boot tab, check "Safe boot" with "Network" selected. Click OK and restart.
4. Run DDU in Safe Mode. Select your GPU brand (NVIDIA/AMD/Intel) from the dropdown. Click "Clean and restart". This nukes every driver file.
5. After the restart, install the driver you downloaded in step 1. Choose "Custom Installation" and check "Perform a clean installation".
6. Delete the DirectX Shader Cache. Press Windows key + R, type cleanmgr, select your OS drive (C:), click "Clean up system files". Check DirectX Shader Cache and click OK.
7. Disable GPU acceleration in Discord (Settings > Advanced) and Chrome/Brave (Settings > System).
8. Launch CS2. The game will rebuild shaders on first launch (you'll see a progress bar). This is normal.

Adjust In-Game Video Settings

When this applies: Crashes during gameplay, especially when new effects/smokes appear. A good secondary fix after DDU.

1. In CS2, go to Settings > Video > Advanced Video.
2. Set Shader Quality to Medium or Low. This is the most impactful setting for stability.
3. Set Texture Filtering Mode to Bilinear or Trilinear (away from Anisotropic).
4. Set Multisampling Anti-Aliasing Mode to None or 2x MSAA.
5. Click Apply. Restart the game for changes to take full effect.

Game File & Configuration Fixes

Fix Corrupt VPK Error on Stretched Resolutions

When this applies: Game crashes specifically when applying a stretched resolution like 1280x960 or 1024x768.

The issue is a leftover videodefaults.txt file from a custom resolution tool or a previous launch option.

1. Navigate to your CS2 config folder: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\
2. Look for a file named videodefaults.txt. If it exists, delete it.
3. Also, remove any launch options related to resolution or aspect ratio (like -w 1280 -h 960 -full).
4. Set your resolution in-game through the Video settings menu.
5. If the crash persists, verify game files (Steam > CS2 Properties > Installed Files > Verify Integrity).

Nuclear Option: Full CS2 Reinstall

When this applies: Multiple errors persist after all other fixes, or you suspect deep file corruption.

1. In Steam, right-click CS2 > Manage > Uninstall.
2. Navigate to the install folder (...\steamapps\common\) and delete the entire Counter-Strike Global Offensive folder if it remains.
3. Go to C:\Program Files (x86)\Steam\steamapps and delete appmanifest_730.acf.
4. Restart Steam and install CS2 fresh.

Anti-Cheat & Process Conflicts (Faceit AC Error)

Kill the Lingering CS2 and Overlay Processes

When this applies: Faceit AC gives the "You must exit any running games" error.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Go to the Details tab (Processes tab on older Windows 10).
3. Sort by name and look for:

• cs2.exe
• GameOverlayUI.exe (This is the most common hidden culprit)

1. Select each one, click End Task.
2. Immediately launch the Faceit Anti-Cheat client. Do not open Steam or anything else first.

Disable Conflicting Startup Software

When this applies: The process kill works but the error comes back later. Conflicting software hooks into the system at boot.

1. Open Task Manager and go to the Startup tab.
2. Disable everything non-essential. You can safely disable:

• RGB software (iCUE, SignalRGB, Armoury Crate)
• Hardware monitors (MSI Afterburner, NZXT CAM)
• Game launchers (Epic, Ubisoft Connect)
• Cloud storage (OneDrive, Dropbox)
• Leave GPU utilities (NVIDIA Container, AMD External Events) enabled.

1. Restart your PC. This is required.
2. Upon reboot, launch the Faceit AC client before opening any other program.

Mac Fatal Error Crash Fixes

Lower Critical Graphics Settings

When this applies: Any hard crash to desktop on macOS, especially during ranked matches.

1. Launch CS2 and go to Settings > Video > Advanced Video.
2. Set Shader Detail to Medium or Low. This is the #1 setting for Mac stability.
3. Set Shadow Quality to Medium or Low.
4. Click Apply. You must fully quit and restart CS2 for these changes to be effective.

Delete the macOS Shader Cache

When this applies: Crashes after a game update, or in combination with the settings change above.

1. Quit CS2 and Steam completely.
2. Open Finder. Press Cmd + Shift + G.
3. Paste this exact path and press Go: ~/Library/Application Support/Steam/steamapps/shadercache/
4. Find the folder named 730 and move it to the Trash.
5. Empty Trash, restart Steam, and launch CS2. It will rebuild the cache, which may cause a slight stutter on first launch on a new map.

Error Code Breakdown & Root Causes

0x887A0006 – "DXGI_ERROR_DEVICE_HUNG"

This is a DirectX error meaning your GPU driver took too long to respond, so Windows killed it to prevent a system freeze.

• Root Cause: Almost always a corrupted GPU driver installation, often caused by Windows Update overwriting your clean driver with an older, generic one. Can also be triggered by an over-aggressive GPU overclock or a physically failing GPU.
• Why DDU Works: Windows' standard uninstall leaves behind registry entries and old driver files. DDU scrubs everything, allowing a truly clean install. Deleting the DirectX Shader Cache forces the game to rebuild it from scratch with the new driver.

Corrupt VPK Error on Stretched Res

The VPK is Valve's package file format for game assets. The error indicates a mismatch.

• Root Cause: When you use a launch option or external tool to force a custom resolution, it can write a videodefaults.txt file. After a CS2 update, the game's expected video configuration changes, but your old file conflicts with the new VPK layout, causing a crash.
• The Fix Logic: Deleting videodefaults.txt lets the game generate a new one that matches the current game version.

Mac Fatal Error (No Specific Code)

macOS is less verbose with error codes, but the crash is consistent.

• Root Cause: macOS's graphics driver model and memory management are different from Windows. High Shader Detail uses complex shader programs that can cause the GPU driver to timeout during compilation. The Steam Overlay on Mac can also conflict with VRAM allocation for high-quality shadows.
• The Fix Logic: Lowering settings reduces shader complexity and VRAM pressure, keeping the system within stable limits. Deleting the shader cache removes any corrupted pre-compiled shaders.

Faceit AC "Exit Any Games"

The Faceit Anti-Cheat performs a process scan before launching.

• Root Cause: The AC is looking for any process named cs2.exe or any module (like the Steam Overlay GameOverlayUI.exe) that is associated with the game. If these don't terminate cleanly, they remain in memory. The AC sees them as an attempt to bypass it or a potential security risk.
• The Fix Logic: Manually killing the processes satisfies the AC's check. Disabling startup apps prevents software that injects into processes (like some RGB controllers) from triggering a false positive.

Platform-Specific Notes

Windows

• Driver Management is Key. Always use DDU when changing GPU driver versions. Letting Windows Update handle your GPU driver is a common source of crashes.
• Administrator Privileges. Run Steam as Administrator once if you have persistent launch issues (right-click Steam shortcut > Properties > Compatibility > Run as administrator). This can help with file permission errors, but don't leave it on permanently.
• BIOS/UEFI Setting: Ensure Above 4G Decoding is enabled if you have a modern GPU and CPU. This can resolve some memory-related crashes.

macOS

• No Driver Control. You cannot manually update your GPU drivers; they come with macOS updates. This makes the in-game settings adjustment your primary tool.
• Focus on Shader Detail. This is the single most important setting for stability on Mac. Keep it on Medium.
• Free Up VRAM. Before playing, close other GPU-intensive apps (Chrome with many tabs, video editors).

FAQ

Q: I ran DDU and reinstalled my driver, but I still get the 0x887A0006 error. What now?

A: Your GPU might be unstable. Go to your GPU control panel (NVIDIA Control Panel or AMD Adrenalin) and reset all settings to default. If you have an overclock (even a factory "OC" model), try underclocking the GPU core by 50-100MHz using MSI Afterburner. If it works, your GPU may be degrading or your power supply is struggling.

Q: Do I need to delete the shader cache every CS2 update?

A: On Windows, generally no. The game manages it decently. On Mac, it's a good practice after any major game update, especially if you start crashing again.

Q: The Faceit fix works, but I have to do it every single time.

A: A program launching with Windows is interfering. Follow the "Disable Conflicting Startup Software" steps. The most common culprits are RGB lighting controllers or "game booster" utilities.

Q: Will lowering my settings on Mac hurt my competitive performance?

A: Unlikely. The visual difference between High and Medium shaders is subtle, mostly in material reflections. The FPS gain and, more importantly, the stability gain far outweigh any minor visual downgrade.

Q: I use an autoexec.cfg for my settings. Could this cause crashes?

A: Yes, especially if it contains old commands from CS:GO that are not supported in CS2. Temporarily move your autoexec.cfg out of the cfg folder (to your desktop) and test. If the crash stops, your config has a problematic command.