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
https://help.steampowered.com/es/faqs/view/22C0-03D0-AE4B-04E8
------------------
i know for a fact that razer synapse don't conflict with steam platform anymore
but that patch was not applied to steam games
i don't remember exact error, but it was along the same lines that VAC is not able to verify or work on your PC properly.
as a pc expert, i know issue was not on my side. i tried everything i could think of, i even tried fresh install on other pc. i think it might be related to steam account itself as that was only thing in-common between those PCs. also wi-fi (as i didn't have access to cable).
only thing i forgot, was to clear steam and csgo settings completely, it might have used cloud sync or some other personal setting that carries from pc to pc via steam. back then i was on win 7 and i also went onto win 10 and still had that issue, but again my steam was installed on games drive, not on primary. never install games on primary drive, worse idea.
steam support was just yanking my chain and telling me basic nonsense like "restart your pc".
in fact this issue started when i was playing with friend, everyone in match got kicked with that same message, then there was small csgo update. we both downloaded the udpate and tried to rejoin the match, but it kicked us. we both restarted our PCs and my friend was able to get back in, i did not. this is when it started randomly doing it.
i got so frustrated that i deleted the game and moved on. only about 6 months ago i reinstalled as i noticed csgo has turned into cs2.
haven't had this happen in cs2, but i've had BSOD and random game "crashes" where game just closes.
i think it's related to either your internet or steam account (anything that is able to carry from pc to pc via steam account, such as personal settings or game settings via cloud sync).
both make sense. there could be something in your router, pc or on ISP side, that VAC doesn't like.
for example about 3 years ago some ISPs started using "ds-lite" which is ipv4 over ipv6 and this caused lot of issues in lot of games. i know this for a fact, cuz i was playing one mmo and i had issues accessing in-game markets and other stuff that required real-time internet connection to list items. i contacted their support and they specifically said it's related to ds-lite, but since it's 3 years old, i assume every game dev has heard of it and it shouldn't be an issue.
i'm saying this as example, cuz your ISP might have introduced something that VAC doesn't like or it could be your router or PC settings. for example if you had windows update, it could have messed something up aswell. it could be anything that auto-updates.
i don't think you can fix this by reinstalling the game or steam, this issue is probably somewhere deeper. OR .. it could be something simple.
your best chance of fixing it, is to contact steam support and tell them everything you have already tried and ask if it could be related to internet, such as "ds-lite" or anything similar.
from what i understand, any VAC errors are because it doesn't have necessary access to be able to verify that you're not running cheats. it won't ban you for tampering with VAC itself, but if there's something VAC doesn't like, it won't let you play either.
another example is EAC and procmon (process monitor), it uses its own driver to intercept and monitor everything that is being read/written from/to your drive and EAC doesn't like that driver. or maybe it was battleye, i forgot :/
i think it was battleye, but point is that i got specific error that said this driver is considered as "suspicious" and i must close it before i can play the game, but VAC doesn't give such specific errors, it gives you generic error instead. that's valve's way of saying "it's your own fault, don't install anything other than steam on your pc"