Windows 10: Service Host processes eating my memory

Over the past week, applications, games and web pages keep crashing after about an hour or two after I start my computer. I checked task Manager and saw my memory usage was ridiculous high for what I was running. Something like 95% just for running Discord. There are at least 50+ service host processes running, and the amount of memory they use slowly increases the more I use my computer, maxing out at around 1.2-1.5% memory usage each.
I have an Omen by HP, I've checked to see if I had any drivers or software to update, and everything seems to be good, but my memory still keeps increasing. And I have no idea what to do

These are some of the processes running, there are more. I've been using my computer for about 45 minutes now

Anything I can do to stop this?

:)

 

service host intrusion eating resources

REMOVE ALL UNNECESSARY USELESS service host processes, they are intrusive and eating resources. how fking dumb can u be microsoft? nobody wants those dumb XBOX ****, candycrush rubbish. holyshit windows 7 so much better but you chose to not provide further
updates.

 

Service Host applications EATING up Memory

Hi CrowRade

My name is Andre Da Costa; an Independent Consultant, Windows Insider MVP and Windows & Devices for IT MVP. I'm here to help you with your problem.

What you are actually seeing is by design and it was first introduced in Windows 10, version 1703. Here is an explaination of how it works and why you are seeing so many:

The Service Host (svchost.exe) is system process capable of hosting multiple Windows services. Using this shared-service process, numerous Windows services can share a single process, reducing overall resource consumption. The service-host groups are determined
by combining the services with matching security requirements. For the services critical to network and internet connectivity this translates to at least 16 services across 11 different service groups. While on the plus-side, this helps reduce the security
vulnerability footprint, it increases the likelihood that a user-mode crash from a non-critical service can affect network connectivity.

Separating SvcHost Services

Beginning with the Windows 10 Creators Update (v1703), previously grouped services will be separated such that each will run in its own SvcHost process. This change is automatic for systems with greater than 3.5 GB of RAM running the Client Desktop SKU. On
systems with 3.5 GB or less RAM, services will continue to be grouped into a shared SvcHost process.

Benefits of this design change include:

Increased Reliability by insulating critical network services from the failure of another non-network service in the host, and adding the ability to restore networking connectivity seamlessly when networking components crash.

Reduced Support Costs by eliminating the troubleshooting overhead associated with isolating misbehaving services in the shared host.

Increased Security by providing additional inter-service isolation

Increased Scalability by allowing per-service settings and privileges

Improved Resource Management through per-service CPU, I/O and memory management and increase clear telemetry (report CPU, I/O and network usage per service).

Source:
https://blogs.technet.microsoft.com/tip_of_the_...

 

Service Host memory leak?

are you serious?



did you even read my post?
edit- i can't believe you are a senior member here... i guess i better look for help elsewhere