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
From what I guess it seem like it just crash that about it, and from your log it said crash which I assume correct.
Just testing when have friend window close does it still happen?
Another testing, disable animated avatars go to steam settings > friends & chat > disable "enable animated avatars" > restart client, and test does it still happen?
The interesting part is that disabling "animated avatars" seemed to prolong the time of the client not being black, I sat like 20 more minutes than I usually do, with a game open, and it didn't go black. But it inevitably did after a while.
The new update just makes it far, far worse. Where those Chromium parts used to be isolated before, there's now one big overarching Chromium 'tab' for everything.
If the renderer goes dead; the client goes dead entirely.
Valve added a safety feature which kicks in if the process actually crashes. In this case it pops up a VGUI (yes; the irony...) powered dialog that gives you the option to relaunch Steam incl. options to do so without HW-accelerated rendering or without browser sandboxing. (Please; never do the latter! Major security hazard with the outdated Chromium on which Steam is built!)
However, if the renderer goes dead and black screens, that's not a process crash - so you don't get that dialog. (And you can't close off Steam in the normal way to restart it either.)
FWIW AMD GPUs have always been wonky with HW-accelerated rendering in the Steam Client. Keep it disabled, is what I'd do.
More about the whole "VGUI mode" thing here:
https://steamcommunity.com/discussions/forum/0/6516193260168294059/
I kind of don't trust it though, since I think I notice stray "client restarts" from within the client itself.
I'll post an update after some usage, probably.
I "fixed" the issue, with something that is NOT a fix by any stretch of the imagination, and I won't straight out give it out here in case Steam decides to ♥♥♥♥ it up for even more years - but let's just say that steamwebhelper isn't running anymore.
Would be nice to hear about this fix, sadly I cannot hop onto dms since Steam won't even get past the bootstrap (when checking the updates. It just throws the ''Steamwebhelper, a critical... blah blah''). Can't even get to log in.. lol. Tried everything I could think of (firewall & windows defender exceptions/downgrading Steam/putting commands at the steam startup properties/opting in the beta.... nothing yet, this started happening since the weekend, which means I haven't played since then.
The most strange thing is getting this error out of nowhere, I did not update anything driver-related nor Windows, yet when wanting to play I've hop onto that error.
Gotta love how Valve has enough time to get rid of most commands that fix these issues, but won't move a finger when it comes to memory leaks and general trouble with the new and ''revolutionary'' Steam client. But anyways, like we say, PRAISE LORD GABEN!!!!
But what is the common denominator - what are you guys doing that makes me not see this.
Older Computer?
Are you using something that is different?
I'm just morbidly curious.
An Y540 laptop should be more than enough to not stumble upon these issues. Did Steam change those minimum specs to some prototype-type computer? Doubt yet.
It's just me the one having this error atm, although the steam support said they're aware of the issue ''We are aware of the problem and most of the users having this issue has bitdefender antivirus and/or malwarebytes running. Please try to confirm again and making an exception for the entire Steam folder in your antivirus.'' , which is not because it has been ongoing for a while really.
EDIT: Something I noticed in the logs is ''Failed to load cached hosts file (File 'update_hosts_cached.vdf' not found), using defaults'' did google a fix, threads couldn't find a way to circumvent it sadly...