NTOSKRNL.exe is a system file of the computer responsible for many tasks such as hardware emulation, memory processing. In addition, it is responsible for managing and compressing temporary files (page files)
to reduce memory usage. If one day you discover that this process is using a lot of resources like CPU, Disk or Memory, please do the following:
NTOSKRNL stands for NT Operating System Kernel and to fix this problem, you try one of the following 8 ways:
1] Scan your computer for malware
At times the machine will be infected with malware, and the malware will sometimes attach to the file NTOSKRNL.exe and will consume a lot of machine resources. In these cases, you need to have a virus scanner to scan these types of malware. In particular, you should try to scan the C:WindowsSystem32 folder (where NTOSKRNL.exe is stored).
2] Uninstall unneeded or incompatible programs
Sometimes, you install and run some software is not compatible with Computer. It will cause some abnormal error of the machine.
So, you should find and delete any software that is not compatible with your computer to avoid causing conflicts in the system.
Recognizing is not difficult, a software that is not compatible will often cause machine crash, slow down the machine immediately after installation.
3] Run the DISM command
You can try running the following command with Admin privileges
DISM /Online /Cleanup-Image /RestoreHealth
When you run this command, it will automatically correct errors related to the system image and related components. At that time, all related errors will be automatically corrected. You do not need to do anything else.
4] Turn off Runtime Broker process
RuntimeBroker.exe is a program of the system used to monitor applications to ensure that applications do not harm the security mechanism of Windows. monitors access to Windows API’s and ensure that apps do not violate the core security of Windows. RuntimeBroker.exe typically consumes less memory, but in some cases it consumes a lot of resources and usually does not return memory to Windows, and will cause memory loss and lead to system overload. many resources.
To turn it off, you open the task manager, look for the Runtime Broker name in the Process tab, if it uses more than 15% of the memory, it may have problems, what you need to do is right click on it and select End Task.
 Update Drivers
In some cases, incompatibility between drivers and the operating system can also cause full load of the computer, in which case you can try to update the old drivers, I often see the brother This issue when you update from the old windows up. In some cases Windows is too new, you should check if the driver is compatible before updating offline.
6]Use Performance Troubleshooter
To open this application, go to Start / Run, type in
msdt.exe /id PerformanceDiagnostic
7] Check with Clean Boot State
You can debug using Clean Boot, by default Clean Boot will start as minimal as possible, you can start Clean Boot mode, then enable any process you suspect has Can cause full load to the system. Please try each testa case one, hopefully be able to find out which process causes system errors.
8] Use Windows Performance Toolkit to find the root cause
I found this tool quite nice, it is in the Windows 10 Toolkit SDK, brother download here then you can use it to find the cause of this error by running the following command in cmd:
xperf -on latency -stackwalk profile -buffersize 1024 -MaxFile 256 -FileMode Circular && timeout -1 && xperf -d cpuusage.etl
After running this command, the system will record the operation of the computer at a certain speed, and save it to a file called cpuusage.etl in C:WindowsSystems32.
You can open this file and check the progress of each process related to CPU, Memory …. then if there is an abnormal process, you will be able to test it.