Svchost.exe constantly taking up about 50% CPU and lots of memory.

The problem is svchost.exe (localservice). I have posted an image which contains all services under that process.

Please help me SevenForums, you're my only hope.

Is this happening every boot? Open a resource monitor and switch to CPU tab, sort by CPU. See if you can get additional info, take a screenshot if you can and post here.

It does not start at boot, it seems to be random as to when it starts but once it begins it does not go away. As for what you want can you be more specific? I opened the resource monitor but am not sure what you want me to show you.

Here is two images from the resource monitor.

In CPU tab of Resource Monitor sort by CPU (like you did), now tick the "svchost.exe (LocalService)" at left most column (Services part will now show only LocalService ones). Lets see which one actually consumes CPU time.

The few links I found for NIS suggest:
- a clean startup - Troubleshoot Application Conflicts by Performing a Clean Startup
- a scan with Malwarebytes Anti-Malware (enable root kit scanning in settings - detections too).

The problem with this is that I have never updated the graphics driver. Any suggestions on this?

As for Malwarebytes Anti-Malware, wouldn't this conflict with Eset Smart Security?

I will look into the clean start up but honestly I am not sure how far I will be able to get with that due to this issue not popping up at a predictable time.

Could this have anything to do with an issue that the Eset firewall had recently?

7/12/2015 6:02:55 PM Duplicate IP addresses detected in network ***.***.1.5 ***.***.1.2 ARP
7/12/2015 6:02:02 PM Detected ARP cache poisoning attack ***.***.1.5 ***.***.1.2 ARP

I did a check and everything seemed to say that it is just something that Eset picks up sometimes. After checking to make sure it was not someone trying to get into my network I should add the 1.5 (which is another system in the network) to the zone as being exempt from active protection.

MBAM is not an AV itself. It supplements and works nicely (and advised to run) along with a proper AV.

You will have to wait for the issue to happen and decide if it has been fixed with a clean startup (after waiting for enough time). Then you can start enabling services and startup programs a few at a time and wait again. It is tedious especially when issue doesn't happen every boot.

I will get it.

Could clean startup cause system instability or cause issues somewhere like in the browser? Would that also turn of Eset?

Would turning down the priority help or hurt?