Windows 10: RunTimeBroker using 80% of CPU

I cleaned installed 1809 (Windows 10 Enterprise 3) after running 1803... since then whenever that computer runs either one of the below listed live web cams the RunTimeBroker.exe starts hitting 75 to 85 percent of the CPU.


http://sfbayospreys.org/


https://hdontap.com/index.php/video/stream/golden-gate-osprey-1?utm_source=hdontap.com&utm_medium=homepagecarousel


Both of those links - link to the same live web cam out of San Francisco.


This is my mother's favorite bird cam and she is upset because the system gets very hot and the fan loud and she knows something isn't running right.


I have tweaked some settings to no avail... obviously I can kill the process but it reinitiates. I had her try running it on Internet Explorer but the same problem.


I do not know why it happens only with this cam - all her other live bird cams, or any other internet website do not cause this...


All the other machines are running W10 E3 1803 so I can't try and replicate it. The 1803 machines do not have any RunTimeBroker issues running this live cam.


Is there something I am missing or something I can try to get her to be able to run this without interference from RunTimeBroker?


Here are two pictures as an example...







Thanks!

:)

 

RuntimeBroker consumes high CPU while running GrooveMusic

As of the latest Groove update (version 10.16092.1031.0), this high CPU usage problem has mostly gone away for me. RuntimeBroker will use a lot of CPU for a short period of time after Groove starts up (as its syncing the OneDrive library), then it will stop
using the CPU and playback will use minimal CPU power. Even if I minimize the Groove app, CPU usage still stays low unlike before this update. This update allows me to minimize Groove, enjoy my OneDrive library, and not waste CPU power and battery life.

I observed this both on my desktop and my Surface Pro 3, both running fully updated Windows 10 Anniversary Update.

 

[FS][US] CPU, NForce4 skt 754 motherboard (with PCI-express slot, rare!), DDR RAM

bump, CPU's stepping is now listed.

 

Runtimebroker.exe high cpu

Ruth, how can you conclude it is a faulty app? Task manager is showing RunTimeBroker as the one that is burning CPU cycles. so it is the process with the design flaw that allows this to happen. RunTimeBroker should be made smarter to prevent this cpu
loop or at least indicate which app has invoked it. If you won't fix it, at least provide information to disable it with what the ramifications are for not having RunTimeBroker.