As you can see, the math doesn't even add up to the actual usage
This has been happening ever since I have been using my monitor on my laptop. Please do help.
As you can see, the math doesn't even add up to the actual usage
This has been happening ever since I have been using my monitor on my laptop. Please do help.
Your question refers to the CPU-usage while your referenced image shows sorting by GPU-usage.
Assuming you indeed meant CPU-usage:
Look out for the System Interrupts as well. Also the task-manager shows the CPU-Load absolute not relative to the actual CPU-Frequency (and -Threading/-HyperThreading if applicable to your CPU). When you switch to the Performance-tab you will see that depending on your actual Frequency the percentage reflects the used potential not the amount of processing-power relative to the actual frequency. For example: If you limit your 3.2GHz CPU to max 50% it will be limited to 1.6GHz and the percentage reflects that cap-limit not the Utilization relative to the available 1.6GHz.
Yes, it is annoying.
If you actually meant the GPU-usage, you are in a similar situation, where you have to differ by calls made via GDI/DirectX/OpenGL/Vulkan (which are measured) versus Hardware-Overlays, which are not represented in the overall-load shown, but are added in the application-specific load.
Also the GPU-load is reported by the GPU, which is driver/vendor-dependent - if you need exact numbers you might want to find the specific monitoring-software for your graphics-card.
Yes, it is annoying.
Regarding GPU, if you use Hyper-V/RemoteFX/gWSL - depending on the family, version and edition of your Windows OS - different techniques are used to either passthrough or partition the GPU-capabilities and performance. This affects the sum-up in task-manager as well.
In short: The task-manager is (sadly) not a reliable hardware-monitoring-tool as it relies on the reporting of the subsystems.
The only data shown in TaskManager that is actually safe to use/interpret is:
Speed, Processes, Threads, Handles, Uptime in standard-view or core-specific split-view, as well as the optional kernel-times visualization.
Yes, it is annoying.