[CS2] Severe FPS drops & low GPU usage ONLY when connected to the internet – Tried everything, need help

Resolving Severe FPS Drops and Low GPU Usage in Counter-Strike 2 When Connected to the Internet

Counter-Strike 2 (CS2) enthusiasts often prioritize optimal performance to enjoy competitive gameplay. However, a troubling issue has emerged among some players: significant FPS drops and underutilized GPU resources that only manifest when the game is connected to the internet. This article delves into the problem, explores the troubleshooting journey, and offers potential solutions and insights to help affected players regain stable, high-performance gameplay.

Understanding the Issue

Players experiencing this problem report the following symptoms:

• Severe FPS reductions: Dropping from 200–300+ FPS down to below 100, sometimes as low as 40–60 fps on certain maps.
• Low GPU utilization: Maxing out at approximately 25–40% on systems with an RTX 3050 Laptop GPU.
• Frame inconsistency: Micro-stuttering and unstable frame pacing.
• Persistent across servers: The problem occurs not only in Valve’s official matchmaking but also on private or community servers.

Interestingly, disconnecting from the internet or blocking CS2 through firewalls restores normal performance, with GPU usage soaring to 90–99% and FPS stabilizing at high levels.

System Specifications

The affected setup includes:

• Laptop Model: Dell G15
• Processor: AMD Ryzen 5 5600H
• Graphics Card: NVIDIA RTX 3050 Laptop (4GB VRAM)
• Memory: 16GB DDR4
• Operating System: Windows 11 (fully updated)

Troubleshooting Efforts Made

An extensive range of troubleshooting steps has been undertaken, including:

• Reinstalling and verifying game files.
• Clearing configuration files, shaders, and cache.
• Testing with different launch options (-autoconfig, -vulkan, etc.).
• Switching between DirectX 11 and Vulkan.
• Conducting a clean Windows 11 installation with minimal background software.
• Monitoring hardware performance with MSI Afterburner and HWiNFO.

Network tests included:

• Switching between Wi-Fi and Ethernet.
• Disabling IPv6, DNS-over-HTTPS, and network discovery.
• Flushing DNS and renewing IP addresses.
• Using VPNs and testing multiple ISPs—including mobile hotspots—without success.

System adjustments involved:

• Enabling Windows Ultimate Performance power plan.