Counter-Strike 2

Counter-Strike 2

View Stats:
Creager Apr 23, 2024 @ 7:05pm
Cs2 constantly crashing as soon as I load into a lobby.
Os- Windows 10
CPU- i7 14700k
MOBO- Z690-e wifi
GPU- Asus Tuf Gaming 3060 12gb
RAM- Corsair vengeance 32gb 6000mhz
PSU- Corsair 850w
BOOT DRIVE- Samsung 970 500gb
Game runs on Samsung 990 2Tb

This all started after updating to the most recent graphic drivers, 552.22 4/16/2024, since then whenever I boot the game it will load to the main menu, but as soon as I join a lobby whether it be custom map or a deathmatch etc my game will just close. I have tried numerous things to try and solve this issue and all it does is vary the time it takes for the game to close, from instantly joining the lobby to it will give me a minute or two before closing. Besides CS2 every other game I have runs completely fine, from games such as valheim or civ6 to other shooters like R6 or Overwatch2.

Reviewed dumpfile to best of my ability and it said the cause of the crash was a graphic related issue

Some things I have tried to fix this issue

-Rolling back to previous graphic drivers that CS2 ran fine on

-Fresh installing windows and all drivers

-Tried switching out displayport/hdmi cables and ports

-Verifying files and reinstalling

-booting the game in -vulkan

-booting the game in compatibility mode

-Tried swapping out gpu for an older 1060(tried most of other fixes with this gpu in as well)

-Ran Furmark and had no issues

-Tried changing resolution/refresh rate in game and in monitor settings

All of these have been either tried by themselves of mixed together and have similar results as I said above. Either crashing the game instantly as I join a lobby or within a few minutes.
< >
Showing 1-4 of 4 comments
bump
Lega Apr 24, 2024 @ 12:23pm 
Well, it's most likely your CPU and a well known problem.

Join the bios and look for Asus Multicore Enhancement and use the setting

"Disable Enforce all limits".

Don't worry it sounds more brutal than the regular Auto setting but it's the opposite.

https://www.youtube.com/watch?v=HIubZYwBfPc&t=1101s

Undervolting/down-clocking is the other option but I would test the first point first.

Either, way you should stick with the Non-Auto setting regardless what you do but the video explained it very well and this also matters for 14700k processors.
Last edited by Lega; Apr 24, 2024 @ 12:28pm
Creager Apr 24, 2024 @ 6:23pm 
Originally posted by Lega:
Well, it's most likely your CPU and a well known problem.

Join the bios and look for Asus Multicore Enhancement and use the setting

"Disable Enforce all limits".

Don't worry it sounds more brutal than the regular Auto setting but it's the opposite.

https://www.youtube.com/watch?v=HIubZYwBfPc&t=1101s

Undervolting/down-clocking is the other option but I would test the first point first.

Either, way you should stick with the Non-Auto setting regardless what you do but the video explained it very well and this also matters for 14700k processors.

Bro thank you so much this fixed it
Lega Apr 25, 2024 @ 4:14am 
Originally posted by Creager:
Originally posted by Lega:
Well, it's most likely your CPU and a well known problem.

Join the bios and look for Asus Multicore Enhancement and use the setting

"Disable Enforce all limits".

Don't worry it sounds more brutal than the regular Auto setting but it's the opposite.

https://www.youtube.com/watch?v=HIubZYwBfPc&t=1101s

Undervolting/down-clocking is the other option but I would test the first point first.

Either, way you should stick with the Non-Auto setting regardless what you do but the video explained it very well and this also matters for 14700k processors.

Bro thank you so much this fixed it

You're welcome! :cozybethesda:
< >
Showing 1-4 of 4 comments
Per page: 1530 50

Date Posted: Apr 23, 2024 @ 7:05pm
Posts: 4