\\chris-ryzen\process(lightingservice)\% processor time lightingservice 1.55796336647317 \\chris-ryzen\process(phoneexperiencehost)\% processor time phoneexperiencehost 3.11592673294633 + FullyQualifiedErrorId : CounterApiError, + CategoryInfo : InvalidResult: (:), Exception + $Procs = Get-Counter -Counter "\Process(*)\% Processor Time" PerformanceCounterSample object to make sure it contains valid data. Get-Counter : The data in one of the performance counter samples is not valid. > Format-Table -Property Path, InstanceName, CookedValue -AutoSize > Sort-Object -Property CookedValue -Descending | > Where-Object -Property CookedValue -GT 0 | PS C:\WINDOWS\system32> $Procs = Get-Counter -Counter "\Process(*)\% Processor Time" I tried to run it but this is what I got. However I do not know how to wrap this code in a loop or know where to find the information I need. That's assuming the cause is the obvious one, that some process is ramping up, using a lot of CPU, generating heat, and the fans are just doing what they are supposed to do in that situation. Wrap that in a loop which captures and logs the data, and you should be able to see exactly what is chewing CPU. Sort-Object -Property CookedValue -Descending | Where-Object -Property CookedValue -GT 0 | Here's a version which filters out all the processes sat on 0: That gives you a snapshot of per-process CPU% at the time (with 100 being 100% of a single logical CPU, so the total adds up to 3200% on a 5950X with 32 logical CPUs (16 dual-thread cores)). $Procs.CounterSamples | Sort-Object -Property CookedValue -Descending |įormat-Table -Property Path, InstanceName, CookedValue -AutoSize $Procs = Get-Counter -Counter "\Process(*)\% Processor Time" Here's an example from the MS docs (example 14 in the PS 7.2 docs for Get-Counter) which gives you a starting point: To find the actual process(es) using CPU heavily, you could use PowerShell and Get-Counter to capture and log per-process CPU usage. It looks like it can log CPU utilisation, so you could use that to confirm that it's actually CPU activity that's doing it (the most likely cause), and log whatever other system stats you think might be enlightening. I've not really played with it much myself, but AIDA64 has sensor logging. I'm at a loss as to what is causing this as I can't find what is running or starting up when my display turns off.Īny ideas as to what I can do to resolve this issue other than shut the machine off when I'm not using it? Even if I reboot and not open any programs, and then use the Windows Key + L to lock my machine right away, right after the screen shuts off the CPU and fans jump again. I've checked the task manager but nothing out of the ordinary is there. My first thought is that something in Windows 11 is running causing the CPU temp and fans to jump. The power plan is based off the Balanced Power plan and I've set it to only turn off the display and never go to sleep. Note that the machine is not set to go to sleep at all. After that the CPU temperature will jump from 40c to 60c and the CPU fans spin up and it will sit like that until I come back and wake the screen and log back in then the CPU temp will lower back to around 40c and the fans quiet down. For example:Īfter I press the Windows Key + L to lock my machine, the screen will show the lock screen for a minute or so then the screen shuts off. The issue only occurs when I leave my machine. All temperatures and fan speeds are normal. I have a strange issue I hope someone can help with.Įverything is running fine when I am using the machine.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |