locked
High CPU Svchost.exe (Windows Event Log Service) RRS feed

  • Question

  • Hi all,

    I'm running Windows 10 Pro Insider Preview Build 10130 and CPU is running at 35% after a clean boot.

    The culprit is the Svchost.exe: (Security Centre, Windows Connection Manager, TCP/IP NetBIOS Helper, Windows Event Log, DHCP Client and Windows Audio)

    I've tried stopping some of these services and found that when I stop Windows Event Log service, the CPU utilisation drops to pretty much 0%.

    Is anyone else having this issue, and is there a fix in sight?  

    Cheers!

    Thursday, June 25, 2015 12:23 AM

Answers

  • In order to diagnose your problem we need to run Windows performance toolkit the instructions for which can be found in this wiki

    If you have any questions feel free to ask

    Please run the trace when you are experiencing the problem

    Wanikiya and Dyami--Team Zigzag

    Thursday, June 25, 2015 12:37 AM
    Moderator
  • Hi,

    Automatic update also could cause this issue. Please stop Automatic Update service to see if the issue disappear.

    Meanwhile, update all your device driver and perform a Clean boot to see if there is third-party software conflict:

    How to perform a clean boot in Windows

    https://support.microsoft.com/en-us/kb/929135


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, June 26, 2015 8:38 AM
    Moderator

All replies

  • In order to diagnose your problem we need to run Windows performance toolkit the instructions for which can be found in this wiki

    If you have any questions feel free to ask

    Please run the trace when you are experiencing the problem

    Wanikiya and Dyami--Team Zigzag

    Thursday, June 25, 2015 12:37 AM
    Moderator
  • Hi,

    Automatic update also could cause this issue. Please stop Automatic Update service to see if the issue disappear.

    Meanwhile, update all your device driver and perform a Clean boot to see if there is third-party software conflict:

    How to perform a clean boot in Windows

    https://support.microsoft.com/en-us/kb/929135


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, June 26, 2015 8:38 AM
    Moderator