ValveSoftware
[CSS] Crash with scoped in weapons
6 users (https://steamcommunity.com/app/240/discussions/0/603022666611345229/) have reported crashing when firing with scoped in weapons. They didn't provide much detail but I do believe this should be documented given the multiple reports and how much of an issue this will be for those players.
I'll encourage them to provide their specifications here on this issue too.
It may be random? I've played CS:S a couple of times after the update and only once did a scoped weapon (the scout) crash my game. It was the first round and server I got into that day. Can't remember exactly if the game crashed from me firing or scoping in. Haven't had it happen again yet.
It's definitely not random. For me what is random is when the scope actually works. I'd say it crashes about 90% of the time.
It's definitely not random. For me what is random is when the scope actually works. I'd say it crashes about 90% of the time.
Is it hard to take a video record ?
*edit Or even mention, what kind PC you have and all those details included.
I found a way to replicate the crash every time.
- Open game and create a server via the menu. Only setting that matters is having enough money to afford at least a Scout
- Pick any team, buy a scout, scope in a fire a few shots.
- Create another server without shutting down the previous server, leave all settings the same.
- Repeat step two, and upon firing the Scout, the game crashes
Swapping teams between server launches and firing the Scout still causes the crash. Firing a different weapon before using the Scout doesn't seem to cause the game to crash when firing the Scout. Swapping maps between server launches doesn't cause the crash to occur (at least in my testing). Happens in both DirectX and Vulkan.
Link to video of my testing: https://youtu.be/KLnqtKdaReY
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7112#issuecomment-2683616803
I don't get that crash like in video. You people really need tell, what are your PC specs. This topic is turning into discord chat already.
- For note: Long time in these Source games, it is not recommended to jump in different servers without re-launching game. Because game will glitch/crash on sv_pure bugs.
OS: Windows 10 Home Edition 64bit CPU: AMD Ryzen 9 5950x RAM: DDR4 64GB GPU 1: RTX 4090 GPU 2: RTX 3090
Video https://www.youtube.com/watch?v=0CHSVTPHEAU
My output from dxdiag.exe = DxDiag.txt
My method to replicate that crash doesn't seem to be as consistent as I though, as I couldn't get it to crash again today despite following the same steps I did last time. Maybe it's a due to the memory being moved around, but that's a complete guess only going off a crash dump file.
Steam Crash Dump File Output from WinDbg Not sure the best way to share Dump files, or if I even should on github cause idk if they contain any sensitive info.
I noticed the same console errors as in the Video above, which were reported by players on our CS:S server when bugs occurred. Maybe it's just a coincidence, as nothing else was logged, but in the past, it was not uncommon that sound crashed the game so I'm just sharing in case it's related:
Cannot figure out which search path sound\player\pl_swim3.wav came from. Not playing.
Cannot figure out which search path sound\player\pl_swim1.wav came from. Not playing.
Cannot figure out which search path sound\player\pl_pain4.wav came from. Not playing.
Cannot figure out which search path sound\physics\flesh\flesh_break1.wav came from. Not playing.
Cannot figure out which search path sound\weapons\extinguisher\fire1.wav came from. Not playing.
Cannot figure out which search path sound\weapons\extinguisher\release1.wav came from. Not playing.
Cannot figure out which search path sound\ambient\energy\zap4.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_huge3.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_huge4.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_huge5.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_large2.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_large3.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium1.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium2.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium3.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium4.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium5.wav came from. Not playing.
Cannot figure out which search path sound\physics\nearmiss\whoosh_medium6.wav came from. Not playing.
Cannot figure out which search path sound\doors\door_locked1.wav came from. Not playing.
Cannot figure out which search path sound\doors\door_screen_open1.wav came from. Not playing.
Cannot figure out which search path sound\doors\door_screen_close1.wav came from. Not playing.
Cannot figure out which search path sound\doors\doorstop6.wav came from. Not playing.
Cannot figure out which search path sound\doors\doorstop2.wav came from. Not playing.
Cannot figure out which search path sound\doors\doormove4.wav came from. Not playing.
Cannot figure out which search path sound\doors\doorstop4.wav came from. Not playing.
Cannot figure out which search path sound\doors\handle_knob_locked2.wav came from. Not playing.
Cannot figure out which search path sound\doors\latchunlocked2.wav came from. Not playing.
Cannot figure out which search path sound\doors\handle_locker_locked1.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button7.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button20.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button21.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button22.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button23.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button12.wav came from. Not playing.
Cannot figure out which search path sound\buttons\button13.wav came from. Not playing.
Cannot figure out which search path sound\buttons\combine_button4.wav came from. Not playing.
Cannot figure out which search path sound\buttons\combine_button6.wav came from. Not playing.
Cannot figure out which search path sound\ambient\water\seaice1_loop.wav came from. Not playing.
Cannot figure out which search path sound\ambient\machines\floodgate_move_long1.wav came from. Not playing.
Cannot figure out which search path sound\ambient\water\water_pump_drainout1.wav came from. Not playing.
Cannot figure out which search path sound\ambient\levels\generic\dam_water_loop2.wav came from. Not playing.
OK, I did some testing and I think was able to narrow down the issue a little bit. I am on Linux, but I see the same crash with scoped in weapons (both scout and awp). Can reproduce the crash almost 100%. I am using opengl (-gl) renderer, because the default vulkan freezes the game on start and it is totally unplayable. Workaround: when using Zink (opengl over vulkan) I don't see the issue anymore and the game is stable: no more crashes with scoped in snipers. Hope it helps others too.
Specs: OS: Linux (Ubuntu 24.04 LTS) CPU: AMD Ryzen 7 5700X GPU: Radeon RX 6600
I can confirm I have this same issue from time to time. Wasn't able to reproduce it though. It might go well for a while and suddenly when shooting zoomed in game just closes to desktop.
OS: Windows 11 24H2 CPU: 9800X3D RAM: 32 GB 6000Mhz GPU: RX 7800 XT
I don't understand the companies that beak their software with bugdates (NO, I will not even touch CS2 because of your breaking bugdates). The game was working beautifully. Now some maps have broken or missing textures. And I can't zoom with AWP or Scout, without game crashing. And you know what? Valve doesn't even care, and they don't revert their forced bugdate, to previous game working state. Even, they announce the bugdate as something good. Really? They break their working software and even they don't revert back to working state. I am sure, they even didn't test it before release, because what? Because they don't play their own games. Hey Valve, remove bugdate, or at least fix it to a working state.
I have a strong feeling this will never get fixed as the only updates CS:S really gets are from TF2
It's crashed a handful of times for me since the 64-bit update. There's like a 0.5% chance it'll instantly crash to desktop for me when shooting someone with an AWP.
Is anyone here who is able to get the crash more consistently able to test with the 32-bit client instead and confirm if the issue exists there too? I will use the 32-bit client from here on and see if I still get any crashes in the coming months. Realistically if it doesn't crash anymore for me I will probably forget about it and not report back here in the future as I don't care for GitHub.
To use 32-bit instead:
- Rename cstrike_win64.exe as cstrike_win64.exe.bak
- Make a copy of cstrike.exe and rename the copy as cstrike.exe.bak
- Rename cstrike.exe as cstrike_win64.exe to trick Steam into launching 32-bit instead.
It'd be nicer if Valve added support for the "-force32bit" option for CS:S like it does for TF2 so you wouldn't have to do the above trick.
One time a few weeks ago it crashed instantly after I shot someone with a Desert Eagle in cs_crackhouse and it actually gave the below error message (which isn't very useful), but I have a feeling it's unrelated to this scoped weapon crashing bug that doesn't output any error: "Engine Error: Failed to lock vertex buffer in CMeshDX8::LockVertexBuffer: nVertexCount=4, nFirstVertex=0"
Specs: OS: Win10 LTSC 2021 (21H2) x64 GPU: GeForce GTX 960 GPU Driver: 572.83 (2025-Mar-18)
@amp123456789 Not need to do too complex for setup 32bit cs:s. Create new shortcut. https://github.com/ValveSoftware/Source-1-Games/issues/7040#issuecomment-2888820961
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7112#issuecomment-2923363094
I tested in GNU/Linux -force32bit option, now I can use scope/zoom with scout or AWP and game doesn't crash. Without that, my game crash always if I use scope and shoot.
EDIT: the game (still) crashes on some maps.
Well I played a little CS:S with the 32-bit client (Windows) and a bunch of sounds don't work, e.g. bomb ticking sound, radio messages, "Terrorists/Counter-Terrorists win!", night vision power on, etc. Can you confirm if Linux is also affected?
So even if using the 32-bit client fixes the scoped shooting crash, it's less playable for me because this 2025-Feb-18 update screwed up the 32-bit client with a different regression. I'd rather have a 0.5% crash chance when shooting scoped with the 64-bit client than not being able to hear a bunch of vital sound effects with the 32-bit client.
EDIT: Played some more last weekend, and I'm underestimating the crash chance, it's more like 5% any time I shoot with a scoped AWP, it happened a few times.
I've also gotten the "Engine Error: Failed to lock vertex buffer in CMeshDX8::LockVertexBuffer: nVertexCount=4, nFirstVertex=0" once more and it happened randomly on a zombie mod server this time not with a scoped weapon.
I've never had either of these crash issues before the 64-bit update. Honestly I hope the Valve team just fixes the missing audio sounds regression with the 32-bit client in the next update so I can just play with that client, this missing audio regression must be far easier to fix than these difficult-to-reproduce 64-bit client crash issues, so that at least people who complain on the Steam Community forum about the crashes could be told to just use the 32-client. And please add proper support for "-force32bit" in the game's Steam launch options instead of requiring a workaround involving shortcuts or renaming executables.
I've played several sessions since my last comment and haven't had it since. Very irregular. Must've been like 20 hours combined.
I've played several sessions since my last comment and haven't had it since. Very irregular. Must've been like 20 hours combined.
I am having game crashes again, when aiming with scope. EDIT: only happens with some maps.
Try this console command:
cl_localnetworkbackdoor 0
No, the game still crashes the same way, shooting when scoping.
Try this console command:
cl_localnetworkbackdoor 0No, the game still crashes the same way, shooting when scoping.
Record video and show us
I will try to keep the recorder on all the times when playing, I'll create a compilation of the crashes when they happen, what else should I keep track of ? Which logs should I see and how
Try this console command:
cl_localnetworkbackdoor 0No, the game still crashes the same way, shooting when scoping.
Record video and show us
https://github.com/user-attachments/assets/5697cc17-3383-4ebe-9fd1-ec2d9528cd7e
I will try to keep the recorder on all the times when playing, I'll create a compilation of the crashes when they happen, what else should I keep track of ? Which logs should I see and how
I really tyred of that stupid company that breaks the game, and don't give a FU.... and we having to work for them for free?? Really? I am thinking of removing all Steam crap and not using it again.
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7112#issuecomment-3095802205
the video doesn't load
Replying to #7112 (comment)
the video doesn't load
Compressed the video, hope it works:
https://github.com/user-attachments/assets/15858157-e06b-43bd-bfe3-fa9aab3befd9
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7112#issuecomment-3096241043
still doesn't load
it says the file is corrupted
i think it's a problem with my browser (firefox)
Replying to https://github.com/ValveSoftware/Source-1-Games/issues/7112#issuecomment-3096241043
still doesn't load
it says the file is corrupted i think it's because the video is encoded in h.264 maybe?
It works for me
Replying to #7112 (comment)
still doesn't load
it says the file is corrupted i think it's because the video is encoded in h.264 maybe?
https://youtu.be/Pv9ADEs0SVc
I also had this damn problem, neither the logs nor the memory dump could provide any information that could help me identify the fault, I was told I could try switching from fullscreen to borderless fullscreen and switching back to exclusive fullscreen to deal with the problem, but I don't think this method will work. I sent a memory dump from a crash and my pc's DxDiag.txt to see if someone could help me identify this issue (You may see some garbled characters in the console output, these should be Chinese characters)
crash_cstrike_win64.exe_20250725162307_1.dmp
This fixed it for me:
Deleted config.cfg from both (Please try to remember your past settings, key binds, spray path... because this will reset all your settings):
- cstrike/cfg/ (I also deleted 360controller.cfg just in case)
- Steam/userdata/<yourID>/240/remote/cfg/
Disabled Steam Cloud for CS:S (important!).
Auto applied this console command on launch via cs source launch options by adding this line: +cl_localnetworkbackdoor 0
I played the game with this fix for 4 days using Scout, and the crash never happened again.