Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
That error can often be associated with Visual C Runtimes.
Try uninstalling all of those off your system. Reboot, and then download and install them all again via > https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one (extract the contents, then run the BAT file to automate the installers); when done reboot and then manually click "Check for Updates" in your OS' Windows Updates section.
Recent update caused the crash issue. below is the way how to fix it, hope Valve can fix it soon in next update.
Find the cs2.exe, normally under this folder: C:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\game\bin\win64
RMB the exe file, click the "compatibility" , enable the checkbox for "Run this program in compatibility mode for 'windows8'"
I have tested over 10 times, the crash issue was gone after this change.
Can try verifying game files
There's apparently youtube videos.
Can search cs2 forum for crashing
get the correct drivers from the mobo mfg site
post a cpuz validation link
http://www.cpuid.com/softwares/cpu-z.html
cpuz -> validate button -> submit button
it will open a browser, copy the url (address) and paste it here
psu brand/model/age?
Definitely run 16gbx2 on an xmp profile
Adjust timings on them after setting xmp. Just *barely*. I'm talking about lowering the cl# by 1, the next two values by 2 each, and the refresh tRC = 2+2. Otherwise if these timings are not measured out properly, it can lead to ram running sporadically or being unstable. So a good timing would be something like 32 - 36 - 36 - 72. 36+36=72. Having the middle two timings add up to the total tRC timing
Use process lasso to whip your cpu into allocating as much computational power to cs2 as possible whilst keeping it stable. Cs2 needs dx12 in source 2 to take advantage of more than a few cores of a cpu. Process lasso is literally the only solution I have found for now..
Put steam.exe at "memory priority set by registry". Allocate cpu cores and set affinity to groups of 2, starting with core 1 if you're amd, core 0 if Intel.
So an Intel user would be setting cpu priority and affinity to core/threads 0,1,2,4,5,8. Amd users would set it to core1,2,5,6,9,10
Cs2.exe in process lasso should be set to high or extra high priority (one level below real-time priority)
Set I/O as normal
Check cpu-z, make sure the timings and frequency is where it should be at. Also useful to check the frequency of the cpu clock.
Cs2 is not optimized. It's still just only over a year after the beta was released to everyone.
For some reason, I am completely convinced that to entirely eliminate your stuttering or bad performance, is after maxing out your cpu and have it be stable and not overheat, and make sure your gpu is not bottlenecked ( it should reach maybe 60%), you *need* to lower those four latencies that are listed on the ddr5 xmp timings. If you have a good kit of ram, you can get slightly faster timings and still have it on xmp with minimal loss to frequency clock
Ram does the job of juggling all the temporary files, specific information on frame pacing and times, it will hold onto net code information for the packets you're buffering, etc. Think of the timings as how a juggler paces the objects they are juggling. If the timings are not optimized, things get messy....especially in a game like cs2 which runs at high fps. If a juggler doesn't have good timing, they will drop their items they're juggling
If the timings are too slow, you will experience bad 0.1% and 1% fps lows, as well as a lot of stuttering
Find an option that's not vsync that helps with frame timings and placement....without limiting frames. Preferably async for nvidia.
Turn off the UI option to see teammate weapons and utility loadouts through walls.
Limit your fps value to 10fps below your slowest 0.1% and 1.0% fps lows for the value of the in game menu fps limit
Put the fps_max at 0
Lower settings to bilinear/trilinear for texture filtering, and 2x msaa instead of 4x
If running nvidia, use launch options -dx12, -high, -novid, -nojoy
In windows, disable fullscreen optimizations, and also disable high dpi scaling.
If all this doesn't work, delete temporary files, delete the dx11 shader cache, uninstall, and then reinstall the same. That fixed nearly all my performance issues
I ran tests on the CPU using Intel diagnostics and it came out fine
Bios is already to date and back to defaults
Caping my CPU at 5 GHz has seemed to fixed things for now
Have already tried rmbing the CS2. .exe
Forgive me that i didn't already mention as I've already done so many things.
Understood cs is not optimised yet but also sad as the game is 1 year old.
If the ram is overclocked manually try using xmp settings or run the ram at default speeds for testing.
Something else to try is with RAM at default/JEDEC speeds. That's basically troubleshooting 101 when you start having stability issues.
https://www.youtube.com/watch?v=P7Eyv5d2Rq8