Steam Running in Background, Throttling GPU memory. [SOLVED]
Whether it is after I restart my computer, or play a game and exit steam, I find that Steam.exe is throttling my nVidia GTX 770 Ti ; the GPU memory is maxed at 99.0%. After doing some research, I found that Steam.exe is causing a high number of CPU cycles in Resource Manager, after killing Steam.exe, whether it is active running, or running in the background (not started or open at all), the GPU temp exponentially cools off; GPU memory is back to normal, temperature is back to normal. (This will usually repeat if I start Steam.exe the following day, "Exit" from the task tray, and let it idle for a period of time.

I have tried regular uninstall + restart
I have tried Revo uninstall (registry files) + restart.
I have tried regular uninstall + CCleaner + restart
I have tried Revo uninstall + CCleaner + restart.

Does anyone have a fix or even heard of such process event?

Thanks in advance,
-Mike

-Mobo: Gigabyte x79-up4
-CPU: i7-4820k 3.70 GHz
-RAM: 16 GB DDR3
-GPU: nVidia 770 Ti
-Disk Drives: 120 SSD (boot), 1TB HDD, 3TB HDD
Last edited by `,⊙ . | ᴮʳᵉᵃᵗʰ; Jul 1, 2015 @ 6:24pm
< >
Showing 1-5 of 5 comments
Bad 💀 Motha Jun 1, 2015 @ 8:15pm 
Go into NVIDIA Control Panel > Manage 3D Settings > click the Program Settings tab.
See what the two Valve/Steam .EXE are set to for Power Management.

Is Steam Client actually installed on the SSD? That would help greatly. You can have all your games on the HDD if u wish.
Unfortunately, this didn't work. I completely deleted Steam and steam games, reinstalled Steam on SSD, and the GPU core still has full usage (this usually brings my GPU to 80 degrees Celsius until "Steam *32" is killed).
It seems that I have to find "Steam *32" and kill the process. "Steam.exe *32" will still be running and will resume Steam as normal. I am just not sure why and what "Steam *32" (not "Steam.exe *32") is doing.
8472 Jun 23, 2015 @ 6:55am 
I have the exact same problem. It was driving me nuts seeing my 660GT at full power while there was nothing else on other than chrome. I saw the Steam*32 in the process tab, killed it and Boom everything back to normal. I dont like progz that do stuff I dont know about, specially if it drives my hardware insane.
I resolved the issue with ComboFix **Be Careful Before Use!**

I found out that the svchost.exe and Steam *32 were linked to a bitmining-pool link. My assumption is that my CPU @50% and GPU @99% were most-likely mining for someone elses bitcoin. Pshh...

@DEUS EX: Try to use ProcessExplorer to analyze the data in the Steam *32 file.
8472 Jul 2, 2015 @ 11:40am 
to be honest. stem*32 is a proof that your torrent client has caught something. I found it in my dir, deleted it and everything was good
< >
Showing 1-5 of 5 comments
Per page: 1530 50

Date Posted: Jun 1, 2015 @ 8:09pm
Posts: 5