How can I determine what is murdering my CPU?












0















My system is periodically becoming very sluggish. Everything is hard to do when it gets like this, including typing. The mouse pointer is generally fairly responsive, but clicking is not. After a while (5 mins or so), it seems to return to normal.



The machine is quite new (Surface Book 2), as is the Windows 10 installation. It has a heap of free space on the SSD drive. I run only Windows Defender.



I've already run sfc /scannow to no avail:



sfc results



I also ran chkdsk /r and it reported nothing (though it was unclear whether it would report problems if it found them).



Process Explorer shows an awful lot of red (kernel?) activity during these periods, but there doesn't appear to be any one process that is clearly a culprit. Here's a capture I took during one of the periods of poor performance:



process explorer



What techniques/guides can I follow to get to the bottom of this problem? Specifically, how can I identify the root cause of the high kernel load?










share|improve this question























  • run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

    – Stese
    Jan 22 at 10:30











  • Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

    – Ben
    Jan 22 at 11:25


















0















My system is periodically becoming very sluggish. Everything is hard to do when it gets like this, including typing. The mouse pointer is generally fairly responsive, but clicking is not. After a while (5 mins or so), it seems to return to normal.



The machine is quite new (Surface Book 2), as is the Windows 10 installation. It has a heap of free space on the SSD drive. I run only Windows Defender.



I've already run sfc /scannow to no avail:



sfc results



I also ran chkdsk /r and it reported nothing (though it was unclear whether it would report problems if it found them).



Process Explorer shows an awful lot of red (kernel?) activity during these periods, but there doesn't appear to be any one process that is clearly a culprit. Here's a capture I took during one of the periods of poor performance:



process explorer



What techniques/guides can I follow to get to the bottom of this problem? Specifically, how can I identify the root cause of the high kernel load?










share|improve this question























  • run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

    – Stese
    Jan 22 at 10:30











  • Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

    – Ben
    Jan 22 at 11:25
















0












0








0








My system is periodically becoming very sluggish. Everything is hard to do when it gets like this, including typing. The mouse pointer is generally fairly responsive, but clicking is not. After a while (5 mins or so), it seems to return to normal.



The machine is quite new (Surface Book 2), as is the Windows 10 installation. It has a heap of free space on the SSD drive. I run only Windows Defender.



I've already run sfc /scannow to no avail:



sfc results



I also ran chkdsk /r and it reported nothing (though it was unclear whether it would report problems if it found them).



Process Explorer shows an awful lot of red (kernel?) activity during these periods, but there doesn't appear to be any one process that is clearly a culprit. Here's a capture I took during one of the periods of poor performance:



process explorer



What techniques/guides can I follow to get to the bottom of this problem? Specifically, how can I identify the root cause of the high kernel load?










share|improve this question














My system is periodically becoming very sluggish. Everything is hard to do when it gets like this, including typing. The mouse pointer is generally fairly responsive, but clicking is not. After a while (5 mins or so), it seems to return to normal.



The machine is quite new (Surface Book 2), as is the Windows 10 installation. It has a heap of free space on the SSD drive. I run only Windows Defender.



I've already run sfc /scannow to no avail:



sfc results



I also ran chkdsk /r and it reported nothing (though it was unclear whether it would report problems if it found them).



Process Explorer shows an awful lot of red (kernel?) activity during these periods, but there doesn't appear to be any one process that is clearly a culprit. Here's a capture I took during one of the periods of poor performance:



process explorer



What techniques/guides can I follow to get to the bottom of this problem? Specifically, how can I identify the root cause of the high kernel load?







windows-10 cpu performance diagnostic






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 22 at 9:28









me--me--

1351312




1351312













  • run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

    – Stese
    Jan 22 at 10:30











  • Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

    – Ben
    Jan 22 at 11:25





















  • run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

    – Stese
    Jan 22 at 10:30











  • Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

    – Ben
    Jan 22 at 11:25



















run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

– Stese
Jan 22 at 10:30





run a malware scan with MalwareBytes anti Malware... Cake.Bakery.exe seems odd given the other things running on the machine.

– Stese
Jan 22 at 10:30













Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

– Ben
Jan 22 at 11:25







Are you using Powershell DSC to install windows components? Perhaps using the xDismFeature from the Windows Powershell Desired State Configuration (DSC) Resource Kit?

– Ben
Jan 22 at 11:25












3 Answers
3






active

oldest

votes


















1














First, check if you have Powershell Desired State Configuration using the xDismFeature plugin. This plugin is extremely slow and I have experienced exactly this issue due to that plugin. It's associated with high CPU and disk IO in the WinPrvSE process (the WMI host process). If it is xDismFeature, then you might mitigate it by running DSC less frequently, or by patching xDismFeature to reduce the disk usage.




  • https://github.com/PowerShell/xDismFeature/pull/15


Otherwise, read on:



TL;DR: it looks like you are running a lot of resource-hungry software.



As you can see Windows Defender is using 7% of cpu and so is WmiPrvSE. This generally indicates it's trying to do a malware scan or an auto-update. You should allow this to finish, then check for updates, and install any pending updates.



Next do a full malware scan with Windows Defender.



I can see that ShareX is using a lot of CPU and RAM. Consider using Microsoft Terminal Services/Remote desktop instead. You can also screenshot with the built-in tool using Win+Shift+S.



Finally, you are clearly hosting docker instances. This is not free either, and you can expect these to use RAM, IO, and CPU.






share|improve this answer
























  • I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

    – me--
    Jan 30 at 3:29











  • @me-- Run Get-DscConfiguration from an elevated powershell session.

    – Ben
    Jan 30 at 14:11











  • OK thanks: "Current configuration does not exist", so I guess it's not that then :)

    – me--
    Jan 30 at 23:44



















0














Run it in safe mode and see if problem remains, if it doesn't you will know that it is an application problem if it does it is either windows or hardware problem.






share|improve this answer































    0














    You need to rule out where this is coming from, by doing it in steps.




    1. Run a full malware scan with Malwarebytes Anti-Malware or similar.

    2. Run a 3rd Party Anti-Virs scan, such as Trend House-Call.

    3. Check Event viewer for errors during the 'slow' time' Check both System and Application logs.

    4. Run under safe mode, as in WooHoos answer.

    5. Ensure windows is fully up to date. It can be updating in the background.

    6. Disable/Stop/Kill programs one by one to see if there is a specific process causing the issues.


    One of these things should highlight/fix the issue.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396935%2fhow-can-i-determine-what-is-murdering-my-cpu%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      3 Answers
      3






      active

      oldest

      votes








      3 Answers
      3






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      1














      First, check if you have Powershell Desired State Configuration using the xDismFeature plugin. This plugin is extremely slow and I have experienced exactly this issue due to that plugin. It's associated with high CPU and disk IO in the WinPrvSE process (the WMI host process). If it is xDismFeature, then you might mitigate it by running DSC less frequently, or by patching xDismFeature to reduce the disk usage.




      • https://github.com/PowerShell/xDismFeature/pull/15


      Otherwise, read on:



      TL;DR: it looks like you are running a lot of resource-hungry software.



      As you can see Windows Defender is using 7% of cpu and so is WmiPrvSE. This generally indicates it's trying to do a malware scan or an auto-update. You should allow this to finish, then check for updates, and install any pending updates.



      Next do a full malware scan with Windows Defender.



      I can see that ShareX is using a lot of CPU and RAM. Consider using Microsoft Terminal Services/Remote desktop instead. You can also screenshot with the built-in tool using Win+Shift+S.



      Finally, you are clearly hosting docker instances. This is not free either, and you can expect these to use RAM, IO, and CPU.






      share|improve this answer
























      • I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

        – me--
        Jan 30 at 3:29











      • @me-- Run Get-DscConfiguration from an elevated powershell session.

        – Ben
        Jan 30 at 14:11











      • OK thanks: "Current configuration does not exist", so I guess it's not that then :)

        – me--
        Jan 30 at 23:44
















      1














      First, check if you have Powershell Desired State Configuration using the xDismFeature plugin. This plugin is extremely slow and I have experienced exactly this issue due to that plugin. It's associated with high CPU and disk IO in the WinPrvSE process (the WMI host process). If it is xDismFeature, then you might mitigate it by running DSC less frequently, or by patching xDismFeature to reduce the disk usage.




      • https://github.com/PowerShell/xDismFeature/pull/15


      Otherwise, read on:



      TL;DR: it looks like you are running a lot of resource-hungry software.



      As you can see Windows Defender is using 7% of cpu and so is WmiPrvSE. This generally indicates it's trying to do a malware scan or an auto-update. You should allow this to finish, then check for updates, and install any pending updates.



      Next do a full malware scan with Windows Defender.



      I can see that ShareX is using a lot of CPU and RAM. Consider using Microsoft Terminal Services/Remote desktop instead. You can also screenshot with the built-in tool using Win+Shift+S.



      Finally, you are clearly hosting docker instances. This is not free either, and you can expect these to use RAM, IO, and CPU.






      share|improve this answer
























      • I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

        – me--
        Jan 30 at 3:29











      • @me-- Run Get-DscConfiguration from an elevated powershell session.

        – Ben
        Jan 30 at 14:11











      • OK thanks: "Current configuration does not exist", so I guess it's not that then :)

        – me--
        Jan 30 at 23:44














      1












      1








      1







      First, check if you have Powershell Desired State Configuration using the xDismFeature plugin. This plugin is extremely slow and I have experienced exactly this issue due to that plugin. It's associated with high CPU and disk IO in the WinPrvSE process (the WMI host process). If it is xDismFeature, then you might mitigate it by running DSC less frequently, or by patching xDismFeature to reduce the disk usage.




      • https://github.com/PowerShell/xDismFeature/pull/15


      Otherwise, read on:



      TL;DR: it looks like you are running a lot of resource-hungry software.



      As you can see Windows Defender is using 7% of cpu and so is WmiPrvSE. This generally indicates it's trying to do a malware scan or an auto-update. You should allow this to finish, then check for updates, and install any pending updates.



      Next do a full malware scan with Windows Defender.



      I can see that ShareX is using a lot of CPU and RAM. Consider using Microsoft Terminal Services/Remote desktop instead. You can also screenshot with the built-in tool using Win+Shift+S.



      Finally, you are clearly hosting docker instances. This is not free either, and you can expect these to use RAM, IO, and CPU.






      share|improve this answer













      First, check if you have Powershell Desired State Configuration using the xDismFeature plugin. This plugin is extremely slow and I have experienced exactly this issue due to that plugin. It's associated with high CPU and disk IO in the WinPrvSE process (the WMI host process). If it is xDismFeature, then you might mitigate it by running DSC less frequently, or by patching xDismFeature to reduce the disk usage.




      • https://github.com/PowerShell/xDismFeature/pull/15


      Otherwise, read on:



      TL;DR: it looks like you are running a lot of resource-hungry software.



      As you can see Windows Defender is using 7% of cpu and so is WmiPrvSE. This generally indicates it's trying to do a malware scan or an auto-update. You should allow this to finish, then check for updates, and install any pending updates.



      Next do a full malware scan with Windows Defender.



      I can see that ShareX is using a lot of CPU and RAM. Consider using Microsoft Terminal Services/Remote desktop instead. You can also screenshot with the built-in tool using Win+Shift+S.



      Finally, you are clearly hosting docker instances. This is not free either, and you can expect these to use RAM, IO, and CPU.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Jan 22 at 12:54









      BenBen

      1,3311911




      1,3311911













      • I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

        – me--
        Jan 30 at 3:29











      • @me-- Run Get-DscConfiguration from an elevated powershell session.

        – Ben
        Jan 30 at 14:11











      • OK thanks: "Current configuration does not exist", so I guess it's not that then :)

        – me--
        Jan 30 at 23:44



















      • I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

        – me--
        Jan 30 at 3:29











      • @me-- Run Get-DscConfiguration from an elevated powershell session.

        – Ben
        Jan 30 at 14:11











      • OK thanks: "Current configuration does not exist", so I guess it's not that then :)

        – me--
        Jan 30 at 23:44

















      I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

      – me--
      Jan 30 at 3:29





      I'm struggling to find any information on how I can check whether Powershell Desired State Configuration using DISM is enabled or not. I haven't explicitly enabled it, but maybe it comes out of the box? Any ideas how I can check?

      – me--
      Jan 30 at 3:29













      @me-- Run Get-DscConfiguration from an elevated powershell session.

      – Ben
      Jan 30 at 14:11





      @me-- Run Get-DscConfiguration from an elevated powershell session.

      – Ben
      Jan 30 at 14:11













      OK thanks: "Current configuration does not exist", so I guess it's not that then :)

      – me--
      Jan 30 at 23:44





      OK thanks: "Current configuration does not exist", so I guess it's not that then :)

      – me--
      Jan 30 at 23:44













      0














      Run it in safe mode and see if problem remains, if it doesn't you will know that it is an application problem if it does it is either windows or hardware problem.






      share|improve this answer




























        0














        Run it in safe mode and see if problem remains, if it doesn't you will know that it is an application problem if it does it is either windows or hardware problem.






        share|improve this answer


























          0












          0








          0







          Run it in safe mode and see if problem remains, if it doesn't you will know that it is an application problem if it does it is either windows or hardware problem.






          share|improve this answer













          Run it in safe mode and see if problem remains, if it doesn't you will know that it is an application problem if it does it is either windows or hardware problem.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Jan 22 at 10:03









          woohooswoohoos

          1




          1























              0














              You need to rule out where this is coming from, by doing it in steps.




              1. Run a full malware scan with Malwarebytes Anti-Malware or similar.

              2. Run a 3rd Party Anti-Virs scan, such as Trend House-Call.

              3. Check Event viewer for errors during the 'slow' time' Check both System and Application logs.

              4. Run under safe mode, as in WooHoos answer.

              5. Ensure windows is fully up to date. It can be updating in the background.

              6. Disable/Stop/Kill programs one by one to see if there is a specific process causing the issues.


              One of these things should highlight/fix the issue.






              share|improve this answer




























                0














                You need to rule out where this is coming from, by doing it in steps.




                1. Run a full malware scan with Malwarebytes Anti-Malware or similar.

                2. Run a 3rd Party Anti-Virs scan, such as Trend House-Call.

                3. Check Event viewer for errors during the 'slow' time' Check both System and Application logs.

                4. Run under safe mode, as in WooHoos answer.

                5. Ensure windows is fully up to date. It can be updating in the background.

                6. Disable/Stop/Kill programs one by one to see if there is a specific process causing the issues.


                One of these things should highlight/fix the issue.






                share|improve this answer


























                  0












                  0








                  0







                  You need to rule out where this is coming from, by doing it in steps.




                  1. Run a full malware scan with Malwarebytes Anti-Malware or similar.

                  2. Run a 3rd Party Anti-Virs scan, such as Trend House-Call.

                  3. Check Event viewer for errors during the 'slow' time' Check both System and Application logs.

                  4. Run under safe mode, as in WooHoos answer.

                  5. Ensure windows is fully up to date. It can be updating in the background.

                  6. Disable/Stop/Kill programs one by one to see if there is a specific process causing the issues.


                  One of these things should highlight/fix the issue.






                  share|improve this answer













                  You need to rule out where this is coming from, by doing it in steps.




                  1. Run a full malware scan with Malwarebytes Anti-Malware or similar.

                  2. Run a 3rd Party Anti-Virs scan, such as Trend House-Call.

                  3. Check Event viewer for errors during the 'slow' time' Check both System and Application logs.

                  4. Run under safe mode, as in WooHoos answer.

                  5. Ensure windows is fully up to date. It can be updating in the background.

                  6. Disable/Stop/Kill programs one by one to see if there is a specific process causing the issues.


                  One of these things should highlight/fix the issue.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 22 at 10:36









                  SteseStese

                  947414




                  947414






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1396935%2fhow-can-i-determine-what-is-murdering-my-cpu%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Mouse cursor on multiple screens with different PPI

                      Agildo Ribeiro

                      Sometime when accessing a menu: “Ubuntu 16.04 has experienced an internal error”