Latest CS2 update crashes GPU drivers for many, but there's a quick fix
To fix it, limit your GPU Clock Maximum to 2500mhz
2 min. read
Updated on
Share this article
Read our disclosure page to find out how can you help Windows Report sustain the editorial team Read more
After updating Counter-Strike 2, a lot of users complained that the game crashed GPU drivers with no logs.
One of the Reddit users, SKYTRIXSHA mentioned the issue, and stated,
After playing CS2, the GPU drivers crash with no proper logs or such. Nothing in Event Manager outside of “Display driver crashed”.
I had these issues last year, but the system was completely stable for multiple months before the latest CS2 update which changed how smokes and such work.
And, he further mentioned that he tried to update drivers, cleared CMOS, and even reinstalled Windows 11, but there was no luck.
Other users Darkraptor19, and Frolleferm, also mentioned facing the same issue.
Some users claimed that by disabling NVIDIA & Discord In-Game Overlay, not using Low Latency mode, reinstalling all games related to drivers, or reinstalling Windows 11 without removing everything, the game crashes were reduced to a minimum.
The issue is not exclusive to users with AMD graphics cards, as some users with Intel and NVIDIA drivers also reported the issue on multiple forums, like the Intel community, NVIDIA, and GitHub.
SKYTRIXSHA then finally updated that they fixed the issue by limiting the GPU maximum clock to 2500mHz via Adrenaline while leaving the other settings, including Power Limit, to default.
He also emphasized setting the -Vulkan launch option to fix the problem but warned that you could get bad frame times and random stutters while using it.
A lot of users have also responded that applying these settings helped them fix the problem with the game, while some insisted that with these fixes, a user might also have to reinstall Windows to resolve the issue.
A user on Steam, Trevics with an AMD processor, mentioned that by disabling the AMDÂ FidelityFX Super Resolution feature.
So far, users on multiple forums and threads are testing different solutions to fix the problem, but CS2 has not commented on the issue and has not offered any resolution.
Did any of the fixes mentioned here help you stop the game from crashing? If yes, then share your experience and also mention if you have found another way to fix the problem.
