0x887A0006 CS2

CS2 Black Screen on Startup - Error 0x887A0006 Fix Guide

📅 Published: 2026-02-05 🔄 Updated: 2026-02-05 👥 Reports: 26 ⚡ Severity: 🟡 Medium

🎯 Quick Answer

The primary fix for Error 0x887A0006 is to disable the GPU hardware-accelerated scheduling feature in Windows 11, as this directly conflicts with CS2's rendering pipeline.

SECTION 1: OVERVIEW

Error 0x887A0006 is a DirectX-related graphics device initialization failure. The error code corresponds to DXGI_ERROR_DEVICE_HUNG, indicating the graphics processing unit (GPU) stopped responding to driver commands during the game's startup sequence. This issue affects the Windows platform exclusively, specifically Windows 10 version 22H2 and Windows 11. The problem manifests in Counter-Strike 2 (CS2) following the February 01, 2026 game client update. This is a common occurrence post-update, with a high frequency of reports from systems using both NVIDIA GeForce RTX 40-series and AMD Radeon RX 500-series GPUs. The error is game-breaking, as it prevents the application from launching and reaching a playable state. The exact error message presented is "Error 0x887A0006" accompanied by a black screen or immediate application termination.

SECTION 2: SYMPTOMS

The application terminates during the initial rendering phase, typically after the Valve intro video but before the main menu loads. A black screen persists for 2-5 seconds before the game window closes. In some instances, the game process remains active in Task Manager without a visible window, consuming minimal GPU resources. The Windows Event Viewer logs an Application Error for cs2.exe with faulting module nvwgf2umx.dll (NVIDIA) or amdxx64.dll (AMD), accompanied by exception code 0xc0000005. The Steam client displays the game status as "Running" for a brief period before reverting to "Play." No in-game error dialogue appears; the failure is silent aside from the black screen.

SECTION 3: COMMON CAUSES

Category: Configuration Error Specific technical explanation: Windows 11 Hardware-accelerated GPU Scheduling (HAGS) is enabled. This feature manages GPU memory and task scheduling directly via the Windows Display Driver Model (WDDM). CS2's rendering pipeline, particularly after the specified update, contains a timing conflict with HAGS, causing the GPU command queue to timeout. Why this causes the problem: The game's attempt to allocate and manage video memory through the driver is intercepted and delayed by the Windows scheduler, resulting in a device hang (0x887A0006). Category: Software Conflict Specific technical explanation: Outdated or corrupted Microsoft Visual C++ Redistributable and DirectX End-User Runtime libraries. CS2 requires specific versions of these runtime components for its engine to interface with the GPU driver. Why this causes the problem: Missing or mismatched DLL files cause function calls from the game executable to fail, preventing proper DirectX 11 context creation. Category: Game Bug Specific technical explanation: The game's video configuration file (videodefaults.txt or video.cfg) contains invalid or corrupted display mode settings, such as an unsupported refresh rate or resolution. Why this causes the problem: At startup, the game engine attempts to apply these corrupted settings before the display driver can validate them, triggering a device reset failure. Category: Hardware Issue Specific technical explanation: GPU instability due to factory-overclocked memory or core clocks. Some manufacturer overclocks, especially on RTX 4060 and RX 580 models, operate at the edge of stability and can fail under the specific load pattern of CS2's startup sequence. Why this causes the problem: The driver detects an unrecoverable fault from the hardware when the game initializes its shader cache and rendering contexts, forcing a device removal. Category: Software Conflict Specific technical explanation: Third-party overlay software (Discord, Xbox Game Bar, NVIDIA GeForce Experience Overlay, MSI Afterburner) injects its rendering hooks into the DirectX swap chain. Why this causes the problem: The injection occurs before the game has fully initialized its own rendering context, leading to a conflict for control of the presentation pipeline and subsequent device loss. Category: Configuration Error Specific technical explanation: NVIDIA Control Panel or AMD Radeon Software settings apply global 3D application settings that override the game's intended configuration. This includes forcing specific Anti-Aliasing modes, V-Sync, or Shader Cache size. Why this causes the problem: The driver applies these forced settings during device creation, which may be incompatible with the engine's internal rendering defaults, causing initialization to abort.

SECTION 4: SOLUTIONS

Solution 1: Disable Hardware-Accelerated GPU Scheduling

Difficulty: Easy Time Required: 3 minutes Success Rate: High Prerequisites: None Steps:

Right-click the Windows Start button and select Settings.
Navigate to System > Display > Graphics.
Click Change default graphics settings.
Locate the toggle for Hardware-accelerated GPU scheduling.
Set the toggle to Off.
Click Yes when prompted to restart your system. A restart is mandatory for this change to take effect.

Technical Explanation: This action reverts GPU scheduling control to the standard NVIDIA or AMD driver model, eliminating the timing conflict between the Windows WDDM and CS2's engine that causes the device hang error (0x887A0006). Verification: After reboot, launch CS2. Successful initialization past the black screen to the main menu confirms the fix. The setting remains off in Windows Graphics Settings.

Solution 2: Clean Reinstall Graphics Drivers with DDU

Difficulty: Medium Time Required: 15 minutes Success Rate: High Prerequisites: Admin access required, stable internet connection to download drivers. Steps:

Download the latest GPU driver from the manufacturer's website (NVIDIA or AMD) but do not install it.
Download Display Driver Uninstaller (DDU) from www.guru3d.com.
Boot Windows into Safe Mode. Access this by pressing Windows Key + R, typing msconfig, going to the Boot tab, checking "Safe boot" for Minimal, and restarting.
In Safe Mode, extract and run DDU. Select your GPU vendor (NVIDIA/AMD) from the dropdown menu.
Click Clean and restart. The tool removes all driver files and registry entries.
After the system restarts into normal mode, install the previously downloaded graphics driver package. Select "Custom Installation" and check "Perform a clean installation."

Technical Explanation: DDU removes corrupted driver files, registry entries, and leftover configuration from previous updates that can cause the nvwgf2umx.dll or amdxx64.dll fault. A clean install establishes a stable driver state. Verification: Open dxdiag (via Run command) and check the Display tab to confirm the correct driver version is installed. Launch CS2 to test.

Solution 3: Reset CS2 Video Configuration Files

Difficulty: Easy Time Required: 5 minutes Success Rate: Medium Prerequisites: None Steps:

Ensure Steam and CS2 are fully closed. Check Task Manager for any cs2.exe processes.
Navigate to the CS2 configuration directory: C:\Program Files (x86)\Steam\userdata\[Your Steam ID]\730\local\cfg\
Locate the file named video.cfg. Rename this file to video.cfg.old.
Navigate to the CS2 root directory: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\
Locate the file named videodefaults.txt. Rename this file to videodefaults.txt.old.
Launch Steam and verify CS2's game integrity (Right-click CS2 > Properties > Installed Files > Verify integrity of game files).
Launch CS2. The game will generate new configuration files with default settings.

Technical Explanation: Corrupted resolution, refresh rate, or fullscreen/windowed mode settings in these files force the engine to attempt an invalid display mode on launch, triggering the device error. Removing them forces a safe default. Verification: The game launches in a default display mode (typically 1920x1080 fullscreen). Check the new video.cfg file in the userdata directory to confirm it was created after a successful launch.

Solution 4: Disable Third-Party Overlays and Optimizations

Difficulty: Medium Time Required: 10 minutes Prerequisites: None Steps:

Disable Steam Overlay: In Steam, go to Library > Right-click Counter-Strike 2 > Properties. Under the General section, uncheck "Enable the Steam Overlay while in-game."
Disable Discord Overlay: Open Discord User Settings (gear icon). Go to Game Overlay. Toggle "Enable in-game overlay" to OFF.
Disable Xbox Game Bar: Press Windows Key + G to see if the Game Bar opens. If so, go to Windows Settings > Gaming > Xbox Game Bar. Toggle "Enable Xbox Game Bar" to OFF.
Disable NVIDIA GeForce Experience Overlay: Open NVIDIA GeForce Experience. Click the Settings (gear) icon. Toggle "In-Game Overlay" to OFF.
Close Monitoring Software: Exit applications like MSI Afterburner, RivaTuner Statistics Server, or any other hardware monitoring tool via the system tray.

Technical Explanation: These overlays inject DLLs into the game process to render their UI. This injection can corrupt the DirectX swap chain creation process during CS2's sensitive startup phase, leading to the DXGI_ERROR_DEVICE_HUNG. Verification: Launch CS2. Use Task Manager's Details tab, right-click cs2.exe, and select "Properties." Navigate to the "Digital Signatures" tab to see a list of signed modules; the absence of overlay-related modules (e.g., DiscordHook64.dll, GameBarPresenceWriter.dll) confirms they are not loaded.

Solution 5: Adjust GPU Control Panel Settings

Difficulty: Medium Time Required: 7 minutes Success Rate: Medium Prerequisites: Latest GPU drivers installed. Steps for NVIDIA:

Open NVIDIA Control Panel (right-click desktop).
Navigate to Manage 3D settings > Program Settings.
Select "Counter-Strike 2" from the dropdown or add cs2.exe manually (found in C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64).
Apply the following specific settings:

* Power management mode: Prefer maximum performance * Shader Cache Size: Driver default * Threaded optimization: Auto * Vertical sync: Use the 3D application setting

Click Apply.

Steps for AMD:

Open AMD Radeon Software.
Go to Gaming > CS2.
Click Reset to restore all game-specific settings to default.
Ensure Radeon Anti-Lag, Radeon Boost, and Radeon Image Sharpening are set to Off.

Technical Explanation: Aggressive global driver optimizations can interfere with the game's internal renderer. Resetting to application-controlled or safe defaults prevents the driver from issuing commands that conflict with the engine's initialization routines. Verification: The settings are saved per-application in the driver profile. Launch CS2. The applied settings can be confirmed by checking the NVIDIA Control Panel or Radeon Software profile for CS2 after the game has run.

Solution 6: Repair System Runtime Libraries

Difficulty: Advanced Time Required: 10 minutes Success Rate: Medium Prerequisites: Admin access required. Steps:

Press Windows Key + R, type appwiz.cpl, and press Enter.
In the Programs and Features list, uninstall all instances of Microsoft Visual C++ Redistributable from 2015 onward. Note the years.
Download the latest Visual C++ Redistributable package from the official Microsoft website. Install both the x86 and x64 versions.
Download the DirectX End-User Runtime Web Installer from Microsoft.
Run the installer (dxwebsetup.exe). It will download and install the necessary DirectX components.
Restart the system.

Technical Explanation: CS2 requires specific versions of the VC++ runtime for engine functions and DirectX user-mode libraries for GPU communication. Corrupted or missing DLLs (d3d11.dll, dxgi.dll) prevent successful device creation. Verification: Run dxdiag and check the System and Display tabs for no reported errors. Navigate to C:\Windows\System32 and verify the modified dates on key files like d3d11.dll and dxgi.dll are recent.

SECTION 5: PREVENTION

Maintain a regular schedule for graphics driver updates, verifying new versions for known issues before installation. Configure Windows Update to delay major feature updates by 30 days to avoid conflicts with game stability. After any game update, systematically verify the integrity of game files through Steam. Periodically clear the DirectX Shader Cache by accessing Windows Settings > System > Storage > Temporary Files and selecting "DirectX Shader Cache" for