Wszystkie dyskusje > Fora Steam > Help and Tips > Szczegóły wątku
Elitehunter34 2 września 2013 o 19:44
Svchost.exe plug and play using CPU cycles only when Steam is active
I'm not sure if it's always been like this, but I find it strange how svchost.exe plug and play is using CPU cycles only when Steam is active. Offline mode doesn't seem to make a difference. I don't have any controllers plugged in at the moment, but I do use an Xbox 360 controller sometimes. Restarting my computer also didn't seem to make a difference. I don't remember this happening before. To be fair, it's only using 1-2% of my CPU, but I don't see why it's even active in the first place.
< >
Wyświetlanie 16-23 z 23 komentarzy
kalel 25 września 2013 o 12:57 
big picture mode works for me to, thanks alot! I will also send it to my open ticket.
VR VR VR CHAT 28 grudnia 2013 o 11:14 
This problem also happened on Castle Crashers.
mattmacks 14 czerwca 2014 o 3:22 
Just posting this here to add another possible solution for people with issues.

Today I noticed that Steam.exe on my computer was occupying one whole CPU core as well constantly. Switching to Big Picture mode and back did not fix it for me, neither did enabling Push-To-Talk as someone had suggested. Process Explorer showed that the main thread of Steam.exe was hogging all the CPU for whatever reason.

What worked for me was switching the Library view from the Full Details view to one of the other views (list, icons) and back. Steam.exe is happily using ~0% afterwards when idle, which is how it should be.
ImTheCaptainNow 15 czerwca 2014 o 9:35 
OMG i have tried everything which is found on the internet and i am still having this problem i have tried Push to talk, switching to big picture mode and back, and i have tried switching the library view from the full details view to the other available views, and it is still not working for me! ;( HELLLPP
Ostatnio edytowany przez: ImTheCaptainNow; 15 czerwca 2014 o 9:36
tjplayss 17 czerwca 2014 o 4:12 
Maybe just re-install steam, back your games up first though! Sorry I can't be more help!
MKANET 6 listopada 2017 o 11:52 
This solution didn't work for me (changing to big picture and back). Plus, its not an automated solution; even, if it did work. I was able to safely do this by making a powershell script suspending two specific process threads under two different processes (steam and steamwebhelper)... in a specific order. My script runs on Windows startup (shortly after Steam launches).

There are 2 process threads that keep blindly banging away at the CPU (albeit, only consuming less than 1.5% of my fast 4.4Ghz multicore CPU) when Steam is idle. This activity appears to be "by design". Anyway, now, Steam consistently uses 0% CPU (when I'm not using the Steam app). Steam will still process updates on startup. The suspended threads will go active only when they're actually needed.

Since Its pretty clear to me that Steam developers intended for Steam to work this way; I will NOT be posting the actual code to do this. I would rather stay in good standing with Steam and Steam community. :) ...just know, there's a programmatic automated solution for this.
Ser-volk 23 kwietnia 2019 o 9:16 
Początkowo opublikowane przez tjplayss:
go in to big pic mode and then exit big pic mode and that stopped it for me!

did worked for me too. But only till next steam restart. After that I need to do it again.
< >
Wyświetlanie 16-23 z 23 komentarzy
Na stronę: 1530 50

Wszystkie dyskusje > Fora Steam > Help and Tips > Szczegóły wątku
Data napisania: 2 września 2013 o 19:44
Posty: 23