It takes up 80-100% of my CPU.
what is runtime broker, and why does it use so much memory?
in task manager there is process called Runtime Broker. and it uses over 600 MB of my ram. putting my average usage at 60% on my 4 gig laptop. not noticed any performance issues yet. just a lot memory being used. makes me think of windows vista almost bc it had same issue in past. it would use all system resources.
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
134 answers
Sort by: Newest
-
Anonymous
2015-08-07T10:10:17+00:00 -
Anonymous
2015-08-06T20:51:52+00:00 So I "solved" the problem through deactivating OneDrive from Autostart. After a new start Runtime Broker had nearly zero CPU usage. It was not helpful if I only shut down OneDrive.
(Win8.1/10)
Tsk man > Startup > Disable Onedrive?
Call me stupid but just making sure.
P.S
I can easily fix this problem with a fresh boot, so it seems to happen at random; I'm not suffering as much as you guys. I'm getting about 6-15% CPU usage from this program. It's just not my cup of tea to do a boot every time I see a system hog.
-
Anonymous
2015-08-05T03:29:27+00:00 My problem wit Runtime Broker it's the CPU's usage, it's using an average of 15% out of my cpu, and it's an i7-4710 for crying out loud. The memory usage it's about 11mb though.
-
Anonymous
2015-08-03T19:10:56+00:00 So I "solved" the problem through deactivating OneDrive from Autostart. After a new start Runtime Broker had nearly zero CPU usage. It was not helpful if I only shut down OneDrive.
-
Anonymous
2015-08-03T09:54:17+00:00 Thanks for the explanation of the DWORD coding.
I used this registry change and it finally stopped Runtime Broker from melting my laptop.
The program now sits at a nice low percentage of CPU and isn't intruding into the rest of the system.
However, the software still needs to be fixed and I find it appalling that it has existed since Windows 8 and has still not been corrected.
Come on Microsoft, respond to your customers and fix the problem!