Windows 10: Help what should I do? Host Service Applications are eating up my memory. I just started...

submitted by /u/LucasNagy
[link] [comments]

:)

 

Service Host applications EATING up Memory

Hey,

I have exactly the same problem with this person *, only his solution does not work for me. I tried a lot of other things and it just seems to get worse. It has now been 4-5 days since it has started. It seemed to start when I was connecting xbox with my
computes to be able to play minecraft with friends (crossplay) after playing I got a black screen and many of my open app and my screen fell out. since then I have been very careful before my computer crashed.

* Service Host applications EATING up Memory

 

Service Host applications EATING up Memory

When I start my computer I have a good 60+ service host applications running and after about an 1 or 2 of just having my computer on or playing on it in general all 60+ of those service host application are taking up all of my memory. I have a custom built
pc with 24gbs of ram and I cant even play games for more then 2 hours without having to restart my computer. They max out at about 300-400mb per application before my pc will just crash and go black. I would really appreciate some help on this. I have been
researching this issue for a while now and i have been able to solve nothing.

 

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_...