Performance Issue CS2

CS2 FPS Drops to 30 After Update - Game Fix Guide

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

🎯 Quick Answer

Disable the NVIDIA Reflex Low Latency setting in CS2's video options, as the January 22 update introduced a conflict causing a 30 FPS cap on affected systems.

SECTION 1: OVERVIEW

The CS2 FPS drop to 30 error is a performance regression where the game's frame rate becomes locked at approximately 30 frames per second (FPS) following a specific game update. This issue manifests exclusively on the Windows platform for the PC version of Counter-Strike 2. The error correlates directly with the game client update released on January 22, 2026 (or February 01, 2026, as referenced in patch notes). This is a common occurrence post-update, affecting a significant subset of the player base. The severity is game-breaking, as the locked low frame rate renders competitive gameplay non-viable and creates a substandard visual experience. No specific error code is generated; the primary symptom is a hard performance ceiling at 30 FPS regardless of in-game video settings or system hardware capability.

SECTION 2: SYMPTOMS

The application renders frames at a consistent maximum of 30 FPS. This performance cap occurs immediately upon launching a match or during the main menu. The frame rate counter, whether from an external tool or the game's cl_showfps 1 command, displays a value fluctuating near 30 (e.g., 29-31 FPS). This occurs despite graphical settings being set to low or high and persists across different maps and game modes. System monitoring software confirms GPU and CPU utilization are abnormally low, indicating an artificial bottleneck. The game remains responsive but visually stuttered due to the low frame rate.

SECTION 3: COMMON CAUSES

Category: Configuration Error Specific technical explanation: The NVIDIA Reflex Low Latency setting within CS2's video options is set to "Enabled + Boost". The January 22 update altered the interaction between this setting and certain GPU power states, forcing a persistent low-power mode that caps render latency and, consequently, frame rate. Why this causes the problem: The driver-level low-latency enforcement overrides standard performance scaling, locking the GPU to a pre-rendered frames value of 1 and a fixed clock state that results in a 30 FPS ceiling. Category: Game Bug Specific technical explanation: A bug in the update's implementation of the -freq launch option or monitor refresh rate detection incorrectly applies a 30Hz vertical sync cap during fullscreen exclusive mode. Why this causes the problem: The game engine misidentifies the display's supported refresh rates, defaulting to the lowest common denominator (often 30Hz for HDR or multi-monitor setups) and synchronizing the frame buffer accordingly. Category: Software Conflict Specific technical explanation: Outdated or corrupted Microsoft Visual C++ Redistributables (2015-2022). CS2's updated executable relies on specific runtime library functions for performance timing that fail or throttle when the required DLLs are missing or mismatched. Why this causes the problem: The game's internal high-resolution performance counter falls back to a low-resolution timer, causing the engine to artificially limit frame submission to maintain simulation integrity. Category: Configuration Error Specific technical explanation: An invalid or corrupted video.txt configuration file located in C:\Program Files (x86)\Steam\userdata\[STEAMID]\730\local\cfg\ contains deprecated commands from the previous version that conflict with new engine variables. Why this causes the problem: On launch, the game reads conflicting or malformed render pipeline instructions, forcing a fallback to a conservative, low-FPS compatibility mode. Category: Hardware Issue Specific technical explanation: The update enables a Windows "Battery Saver" or "Power Saver" plan profile for desktop systems, incorrectly detecting the platform as a laptop. This globally caps GPU and CPU performance. Why this causes the problem: The Windows Power Management subsystem restricts the maximum processor state to a low percentage, preventing the GPU driver and game engine from utilizing full system resources. Category: Driver Issue Specific technical explanation: NVIDIA GPU driver version 551.xx or AMD Adrenalin Edition 24.1.1 contain shader compilation changes that conflict with CS2's updated DirectX 11 runtime path, causing persistent driver-level frame pacing that manifests as a 30 FPS cap. Why this causes the problem: The driver's internal present queue is throttled due to a misinterpretation of the game's presentation flags, leading to consistent frame delivery delays.

SECTION 4: SOLUTIONS

Solution 1: Disable NVIDIA Reflex Low Latency

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

Launch Counter-Strike 2.
Navigate to the Settings menu and select the Video tab.
Locate the "NVIDIA Reflex Low Latency" dropdown menu.
Change the setting from "Enabled + Boost" to "Enabled" or "Disabled".
Click "Apply Changes".
Restart the game for the change to take full effect.

Technical Explanation: This resolves the primary conflict introduced in the January 22 update where the "Boost" mode incorrectly triggers a sustained GPU power state designed for idle desktop operation, capping render queue submission. Verification: Load any map and use the console command cl_showfps 1. The displayed FPS counter should now fluctuate according to your system's capability, significantly exceeding 30 FPS.

Solution 2: Reset Video Configuration Files

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

Exit Steam completely.
Navigate to the CS2 configuration directory: C:\Program Files (x86)\Steam\userdata\[YOUR_STEAM_ID]\730\local\cfg\.
Locate and delete the following files: video.txt, videodefaults.txt.
Open File Explorer and navigate to C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg\.
Delete the file named video.cfg if it exists.
Restart Steam and launch CS2. The game will generate new, default video configuration files.

Technical Explanation: This removes corrupted or deprecated graphical settings that force the engine into a compatibility mode. Fresh files ensure all new engine variables from the update are initialized with correct default values. Verification: The game's video settings will be reset to default. After re-configuring your settings, the FPS cap will be removed. Check FPS with cl_showfps 1.

Solution 3: Perform a Clean GPU Driver Reinstall

Difficulty: Advanced Time Required: 10 minutes Success Rate: Medium Prerequisites: Administrator access, internet connection to download driver. Steps:

Download the latest GPU driver from NVIDIA or AMD's official website.
Download Display Driver Uninstaller (DDU) from https://www.guru3d.com/download/display-driver-uninstaller-download/.
Boot Windows into Safe Mode.
Run DDU, select your GPU vendor (NVIDIA/AMD), and choose "Clean and restart".
After the system reboots, install the previously downloaded GPU driver package. Select "Custom (Advanced)" installation and check "Perform a clean installation".
Reboot the system normally.

Technical Explanation: A clean installation removes all previous driver files and registry entries that may contain incompatible frame pacing or power management profiles conflicting with the updated game executable. Verification: Open the NVIDIA Control Panel or AMD Software Adrenalin Edition to confirm the clean driver version is installed. Launch CS2 and confirm FPS is uncapped.

Solution 4: Modify Launch Options and Verify Integrity

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

Open Steam, right-click Counter-Strike 2 in your library, and select Properties.
In the GENERAL tab, locate the LAUNCH OPTIONS field.
Enter the following options: -freq 144 -refresh 144 (replace '144' with your monitor's native refresh rate).
Close the properties window.
In the same Properties window, go to the INSTALLED FILES tab.
Click "Verify integrity of game files". Wait for the process to complete.
Restart Steam and launch CS2.

Technical Explanation: The -freq and -refresh launch options force the game to recognize the correct display refresh rate, bypassing faulty auto-detection. File verification replaces any corrupted game binaries or shader files from the update process. Verification: The Steam client will report "All files successfully validated." In-game, the console command mat_info will display a line showing "Display mode: ... @ [Your Refresh Rate] Hz".

Solution 5: Adjust Windows Power & Graphics Settings

Difficulty: Medium Time Required: 4 minutes Success Rate: Medium Prerequisites: Administrator access Steps:

Open Windows Settings (Win + I) and go to System > Power & battery.
Set Power mode to "Best performance".
Open the Windows Settings again, go to System > Display > Graphics.
Click "Browse" and navigate to C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64\.
Select "cs2.exe" and click "Add".
Click on the added cs2.exe entry, select "Options", and set the Graphics preference to "High performance".
Click "Save".

Technical Explanation: This ensures Windows does not apply any power-saving throttles to the CS2 process and forces the game to utilize the dedicated GPU with maximum performance allowances. Verification: Launch CS2. The GPU activity icon in the system tray should show high usage when the game is running. Monitor FPS with cl_showfps 1.

Solution 6: Reinstall Microsoft Visual C++ Redistributables

Difficulty: Advanced Time Required: 5 minutes Success Rate: Low Prerequisites: Administrator access Steps:

Download the latest Microsoft Visual C++ Redistributable installer from the official Microsoft website. Get both the x64 and x86 versions of the 2015-2022 package.
Open Windows Settings > Apps > Installed apps.
Search for "Microsoft Visual C++". For each instance from 2015 through 2022, select "Uninstall". Follow the prompts.
Run the downloaded x64 and x86 installer files as Administrator.
Restart your computer.

Technical Explanation: This replaces potentially corrupted runtime libraries that the updated CS2 engine uses for critical timing and threading functions, ensuring accurate high-resolution performance counter access. Verification: After reboot, verify the redistributables are reinstalled in the Installed Apps list. Launch CS2 to test for the FPS cap.

SECTION 5: PREVENTION

Maintain a clean GPU driver installation schedule, using DDU every 2-3 major driver updates before installing the new version. Regularly delete the contents of the DirectX Shader Cache (C:\Users\[USERNAME]\AppData\Local\Temp) and the Steam Shader Cache (C:\Program Files (x86)\Steam\shadercache) after significant game updates. Avoid modifying advanced video settings via auto-configuration tools from GPU vendors. Before applying any major CS2 update, create a backup of your cfg directory. Monitor Windows Power Plan settings after system updates to ensure "Best performance" remains selected.

SECTION 6: WHEN TO CONTACT SUPPORT

Contact Steam Support only after confirming all solutions in Section 4 have been executed and the system's BIOS/UEFI and chipset drivers are updated. Provide the complete dxdiag report and the CS2 game console log. The console log is generated by launching CS2 with the -condebug launch option, reproducing the issue, and then locating the console.log file in the csgo game directory. Official support channels are accessed exclusively via the Steam Support website (help.steampowered.com). Include specific details: GPU driver version, Windows build number, and the exact steps taken to reproduce the 30 FPS lock.