P
Pouki
Guest
Why is the ntoskrnl running at a continuous high CPU rate?
First, I have seen the other threads or forum discussions concerning high CPU utilization concerning the system task identified as ntoskrnl. Some dating back to 2015, then 2017, the most recent Dec 2019 from the Windows Server admin. And I have followed all the recommendations to do this or that, remove this, uninstall that, do a clean boot - to NO permanent affect. Put everything back the way it was.
Here is the interesting part of this: Start the system, run task manager, see that system task (ntoskrnl) is high and steady at 16-17% CPU. This utilization rate stays the same for as long as the system is up. Just select restart, system restarts, in about 15-20 seconds, entire CPU utilization is down to 3-5%. The system-ntoskrnl task is idle - 0% CPU utilization. At this point I am only running task manager and observing the tasks running on the system, the system is running whatever programs it is configured for automatically.
My system is an ASUS All-in-one workstation, with Windows 10 Pro installed, 16GB RAM, iNTEL CORE I7-6700T CPU, all updates current under version 1903 as of Dec 30, 2019.
Around Dec 23 - 24, 2019 I noticed programs I was starting like Outlook, Word, Firefox, were taking a significant more time to start. That caused me to go into task manager and notice the system task ntoskrnl running a high CPU utilization rate. Go back to the start of this description and here we are.
One last piece of info that I hopes helps. In doing all of the above actions I went into Settings -Update and Security - View Update History and here is what I found:
December 10, 2019-KB4533002 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM and Windows 10, version 1909 and Windows Server, version 1909 and December 10, 2019—KB4530684 (OS Builds 18362.535 and 18363.535)
And the system started this high CPU utilization shortly after that.
Would appreciate any feedback or suggestions and I hopes this helps the Microsoft team in tracking this down.
Thanks!
More...
First, I have seen the other threads or forum discussions concerning high CPU utilization concerning the system task identified as ntoskrnl. Some dating back to 2015, then 2017, the most recent Dec 2019 from the Windows Server admin. And I have followed all the recommendations to do this or that, remove this, uninstall that, do a clean boot - to NO permanent affect. Put everything back the way it was.
Here is the interesting part of this: Start the system, run task manager, see that system task (ntoskrnl) is high and steady at 16-17% CPU. This utilization rate stays the same for as long as the system is up. Just select restart, system restarts, in about 15-20 seconds, entire CPU utilization is down to 3-5%. The system-ntoskrnl task is idle - 0% CPU utilization. At this point I am only running task manager and observing the tasks running on the system, the system is running whatever programs it is configured for automatically.
My system is an ASUS All-in-one workstation, with Windows 10 Pro installed, 16GB RAM, iNTEL CORE I7-6700T CPU, all updates current under version 1903 as of Dec 30, 2019.
Around Dec 23 - 24, 2019 I noticed programs I was starting like Outlook, Word, Firefox, were taking a significant more time to start. That caused me to go into task manager and notice the system task ntoskrnl running a high CPU utilization rate. Go back to the start of this description and here we are.
One last piece of info that I hopes helps. In doing all of the above actions I went into Settings -Update and Security - View Update History and here is what I found:
December 10, 2019-KB4533002 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM and Windows 10, version 1909 and Windows Server, version 1909 and December 10, 2019—KB4530684 (OS Builds 18362.535 and 18363.535)
And the system started this high CPU utilization shortly after that.
Would appreciate any feedback or suggestions and I hopes this helps the Microsoft team in tracking this down.
Thanks!
More...