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
The first is an issue with the way CSGO is programmed and how it attempts to utilize cores and threads, in combination with Windows 10. If you have Windows 7 or earlier, you probably don't need to worry about this issue, because windows 7 did not query home base for so much info. CSGO tends to utilize the first 2 cores of CPU, regardless of how much usage is stacked on those 2 cores, versus how much availability other cores have. It's poor optimization. What you can do, is when you launch CSGO, open your task manager, find the process "csgo.exe", right click, and find the option called "Set Affinity". This allows you to restrict CSGO to only use certain cores on the CPU. The best option here is to force CSGO to NEVER EVER use core 0. Core 0 is the first core windows 10 slams with operations when updates or background network traffic start happening, and often, the spike although it only lasts for less than a second, even half a second in csgo feels like an eternity. You may even notice a small sound loop when the mini freeze happens. Either way, change CSGO to never use core 0, and the problem usually subsides significantly, if not entirely. Keep in mind, there's no way to force CSGO to remember this setting, so EVERY single time you launch the game, you have to do it again.
In the event that it does NOT subside after doing so, it can also very easily be the fault of a dying hard drive, or a catalyst to a malfunctioning hard drive (aka dying PSU).
The problem was SO incredibly widespread about 2 years ago, that I ended up spending over 400 hours doing research, and testing on over 20 different machines both desktops and laptops alike (I own a computer company) with different configurations to make sure I was finding the right answers. It was ESPECIALLY prominent on FX Series AMD processors because of their lack of multi-threading, and when core 0 got hit with more load, it could freeze CSGO for as long as 3 whole seconds before coming out of the audio loop.
Ultimately, it boils down to bad coding, but do your best to combat it by giving CSGO it's own exclusive cores to play with, and making sure your gear is in good shape.
I will try your suggestion, thanks. I've read that some people say I should put -threads 4 in my launch options because my CPU uses 4 threads, you know anything about it? That did not fix my problem though.
make a small NON-ADMIN batch file and put this in it
by default it uses 3 threads. You can manually command it to use more threads but this has a negative effect and makes the game more instable than it helps.
It is not a core parking effect, I've tested that already with a core parking program. There's a program that forces all cores to remain unparked. That never fixes it. Only my suggestion ever did, and I've had countless forum users have it work wonders for them, specifically with the FX cpu's because of how frail they are.
Also, as far as how common it is, it's called "Micro Stutter" and there's literally THOUSANDS of forum posts about it.
p:s never changed and tweak anything to my hardware and software.
also there is a simple control panel setting that sets min parked cores
https://i.imgur.com/yde2nAG.jpg
Minimum processort state 0% or 100%? right now im at 0%
tbth i wouldnt mess with any of that stuff... if you follow the school of thought that core 0 has windows calls that interferes with the csgo, then by all means you can remove that...
I wouldnt mes with any of the power settings for the cpus except for the over arching balanced/high performance/power saving selection...
truth be told i had to enable those additional settings for the parked and unparked cores, but honestly something as generic as a micro stutter or lag could be so many things for so many different people that to just generalize what it is is really not doing anyone any justice...
microstutter could easily be equated to:
1) network overload (ie to many people on your houses wifi, valves servers just sucking, you trying to stream or watch youtube while you game... etc etc)
2) mouse input issues...
3) driver issues....
4) some secondary program running in the background that is doing something...
there really is way to many things that could be the culprit and all i jumped into this thread for was to post how to automate the start up of csgo without the 0 core enabled....
also you really have to watch what settings you flip switches on, because there are sooooo many switches to flip that you may actually make your situation worse, or fix the original problem but have flipped so many configs that it still feels broken...
for instance... i have multiple gateway routers due to upgrades and other circumstances, and my wrt3200acm which is supposedly a more endowed linksys router than my wrt1900ac, the 3200 causes me such wierd lag that i can barely hit anything, but when i utilize my wrt1900ac the wierd lag goes away. I equate this to the 1900 having a fan that i can max out and keep the board cool, and the 3200 doesnt...
idk