CS2 Crashes at Valve logo on start
Your system information
- System information from steam (
Steam->Help->System Information) System Information - Have you checked for system updates?: Yes
Please describe your issue in as much detail as possible:
Launching the game with or without launch options (gamescope, mangohug, etc) leads to the game starting and showing the valve logo before crashing shortly after. CS2 coredump after crash
Steps for reproducing this issue:
- Launch the game
- It crashes
Could you launch Steam from a terminal, run CS:2, and share the terminal output in a gist?
Here's the entire Steam Terminal Output when launching cs2.
Could you please provide your launch options as well? Additionally, I have to ask the obvious question: have you attempted to verify the integrity of the game files?
same here, new nvidia drivers are great 😁
launching with proton experimental no flags i'm able to get to menu. upon attempting to queue i get a weird vac error about signatures. i verified and tried a multitude of other things to no avail. launching native and proton with -vulkan flag hangs on valve splash.
Could you please provide your launch options as well? Additionally, I have to ask the obvious question: have you attempted to verify the integrity of the game files?
I used no launch options for that particular launch of the game, however I get the same exact error when launching with gamescope or mangohud. Also, I did try verifying but all files successfully verified.
launching native and proton with -vulkan flag hangs on valve splash
CS:2 utilizes Vulkan as its default graphics API, the -vulkan flag is redundant. Which version of the Nvidia driver are you currently using? I've experienced no problems with 535.129.03. However, there have been reports of issues from users using version 545.x.x.
I used no launch options for that particular launch of the game, however I get the same exact error when launching with gamescope or mangohud. Also, I did try verifying but all files successfully verified.
The only other suggestion I can offer is to reinstall your GPU driver.
I'm having this issue on the amdgpu drivers as well. It's only in X, not on wayland. But on wayland, the rendering performance is so bad that the game is unplayable, so I have to use X.
Looks like mine is a different issue.
https://gist.github.com/sparkie3/e0c95206274a12df12d5c528bf1d47fd
I can confirm this issue on Arch Linux, since updating to Nvidia 545 the Game Crashes on Launch (on Wayland), it just shows the Valve Logo for a long time then crashes.
EDIT: Only happens on Wayland, on X11 the game launches fine
There is this bug with latest nvidia driver https://forums.developer.nvidia.com/t/cs2-stuck-on-valve-logo-on-startup-545-beta-branch/269778
Rolling back the Nvidia driver to 535.98 fixes the Problem. If you're on Arch, you can go to the Arch Linux Archive and download the 535.98 Version of nvidia-dkms (important, otherwise you have to downgrade the kernel) nvidia-utils and lib32-nvidia-utils, then install them with sudo pacman -U
Rolling back the Nvidia driver to
535.98fixes the Problem. If you're on Arch, you can go to the Arch Linux Archive and download the535.98Version ofnvidia-dkms(important, otherwise you have to downgrade the kernel)nvidia-utilsandlib32-nvidia-utils, then install them withsudo pacman -U
This solved it for me. There is also the downgrade utility (in the AUR) that can help downgrading in pacman:
sudo downgrade lib32-nvidia-utils nvidia-utils nvidia-dkm
Issue with 545.29.02 is tracked here (fixed already, waiting for new driver release)
https://github.com/ValveSoftware/csgo-osx-linux/issues/3504
So I imagine its a similar cause with AMD drivers since I'm having the same issue with an AMD gpu.
That's not going to be the same issue, as the game freezes indefinitely on Nvidia 545, it does not result in a crash.
Using NVIDIA on a laptop, downgrading the drivers solved it for me on both CS2 and Dota 2, issue only happens with NVIDIA 545
Had to downgrade NVIDIA drivers and kernel, works perfectly now.
The NVIDIA 545 driver issue is being tracked in #3504. Since @Goldensliv's issue in the opening post is with an AMD GPU, their issue takes priority and all NVIDIA GPU based feedback is off topic here.
All NVIDIA oriented comments past this point will be marked off topic. Please use #3504 if you have anything constructive to add related to that video driver regression.
Correct me if I’m wrong, but this shouldn’t happen on an RX 6300 + i5 8500T setup like it did on my UHD 630, right? On Windows, I never ran into this issue.