WmiPrvSE.exe cause high CPU usage

Hello Seven Forums members. First of I am sorry if this post is in the totally wrong category or if there is already a solution for this but I am not sure if the solution for this applies to every laptop/pc. My sister is asking me to help her fixing her Laptop which is really slow. I opened up the task manager while leaving the laptop in idle state and found out that some process is using up to 30 % of the CPU. So I clicked on the "show processes from all users" button and I could see the culprit: WmiPrvSE.exe.
I assume it's a vital process for Windows to run so killing the process wouldn't work. Therefore I opened up the services and looked for the service that is associated with it. Pausing the "Windows Management Instrumentation" service made the CPU usage go to normal. I went to the properties of this service to look up the dependencies but it showed me nothing. Furthermore, other services didn't show any dependencies either. After a while it showed this window:"Windows:Server execution failed".
But back to the actual problem: What can I possibly do to fix this service or process to make the CPU usage normal again?
If there is any more information required I will edit this post as fast I can.

Thx! I will try to follow the steps and report back later.

At one point in the tutorial there is a step that I cannot execute because it says there is an error.

Yes I am using that website.The step after "Enable logging". It gives me this error message: "The requested operation cannot be performed over an enabled direct channel.The channel must first be disabled before performing the requested operation.
I will be back tomorrow.

Ok, I will try out Process Explorer and the "clean boot in Windows". Sorry for my lack of activity.

I have used Process Explorer and used the "find" function to find all processes related to the "WmiPrvSE.exe" process.
I made a screenshot of the processes or "handles" ( no idea what that is) and the one marked blue and all the other ones under it are related to the WmiPrvSE.exe process. What would be the next step to determine the real cause? Also how would performing a clean boot help?