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
http://steamcommunity.com/discussions/forum/1/864974467385793171/
Launching the Steam client causes CPU usage to rise with the sole cause being the svchost.exe process associated with plugplay and Dcomlauncher.
Fully closing the Steam client causes the CPU usage and behaviour of svchost.exe to return to normal levels.
I attempted a more indepth analysis by using Sysinternals process explorer and process monitor. In particular I noted that it seem tied to audio behaviour and after trying various solutions as detail in forums such as these ones I:
- Validated that the correct audio drivers were loading and no other audio devices or drivers were present.
- Traced the usual svchost behaviour and the behaviour when the Steam client was active.
One obvious effect is that as soon as the Steam client runs it causes the svchost process to start enumerating all the audio devices, including the Vista system audio mixer services.
https://support.steampowered.com/kb_article.php?ref=9828-SFLZ-9289&l=english
I've got an open Steam support ticket so I'll add a reference to your workaround and hopefully get something positive back.
I don't know if steam will and fix it as it uses so little CPU on newer chips. I only noticed as I am using a crappy Pentium D and it was using 18 to 20 percent of it's power. Contact steam and see what they can do.