Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU speed misdetected #56

Closed
Anaerin opened this issue Jun 27, 2021 · 12 comments
Closed

CPU speed misdetected #56

Anaerin opened this issue Jun 27, 2021 · 12 comments
Assignees
Labels
bug Something isn't working

Comments

@Anaerin
Copy link

Anaerin commented Jun 27, 2021

My CPU is being detected as 800MHz, which is it's minimum frequency with power saving:
image
This might be related to Hyper-V being enabled.

@rcmaehl
Copy link
Owner

rcmaehl commented Jun 27, 2021

Are you running the application in the Hyper-V VM?

@rcmaehl rcmaehl self-assigned this Jun 27, 2021
@rcmaehl rcmaehl added bug Something isn't working awaiting reporter Awaiting response from reporter / submitter labels Jun 27, 2021
@ghost
Copy link

ghost commented Jun 27, 2021

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

@rcmaehl
Copy link
Owner

rcmaehl commented Jun 27, 2021

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

Pretty sure I'm already getting this value in Line 22 of \includes\WMIC.au3

@Anaerin
Copy link
Author

Anaerin commented Jun 27, 2021

I'm not running it in a Hyper-V VM, but because of the way Hyper-V works, the "Host" OS is still a Guest, albeit one with a lot more access.

And for reference:

PS C:\WINDOWS\system32> Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed
801
PS C:\WINDOWS\system32> Get-CimInstance Win32_Processor

DeviceID Name                                     Caption                              MaxClockSpeed SocketDesignation
-------- ----                                     -------                              ------------- -----------------
CPU0     Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel64 Family 6 Model 60 Stepping 3 801           SOCKET 1150


PS C:\WINDOWS\system32>

The reason I mentioned Hyper-V is: https://www.hanselman.com/blog/windows-task-manager-shows-wrong-cpu-speed-when-using-hyperv

Apparently there's a "Fix": https://docs.microsoft.com/en-US/troubleshoot/windows-client/performance/task-manager-shows-incorrect-cpu-speed - Use the "\Hyper-V Hypervisor Logical Processor\Frequency" performance counter.

@ghost
Copy link

ghost commented Jun 27, 2021

Hypervisor detection:
Get-CimInstance Win32_ComputerSystem | Select-Object -Expand HypervisorPresent
https://devblogs.microsoft.com/scripting/use-powershell-to-detect-if-hypervisor-is-present/

@mooms06
Copy link

mooms06 commented Jun 28, 2021

Maybe this will help:
Get-CimInstance Win32_Processor | Select-Object -Expand MaxClockSpeed

This incorrectly detect 2101 MHz, my CPU can reach 4.8 GHz

image

image

@ghost
Copy link

ghost commented Jun 28, 2021

Spent a bit of time looking for a good solution to this and pretty sure there isn't one.
Removing the CPU Frequency check is probably fine, nobody legitimately fails it, all the complaints are either because the printed number is wrong or because of virtualisation. The CPU Compatibility check indirectly covers it anyway.

@rcmaehl
Copy link
Owner

rcmaehl commented Jun 28, 2021

What I'll do is grab the @ from the CPU string and report that if there's a discrepancy. Although this will only work for Intel CPUs

@mooms06
Copy link

mooms06 commented Jun 28, 2021

What I'll do is grab the @ from the CPU string and report that if there's a discrepancy. Although this will only work for Intel CPUs

And only for non overclocked CPU. Look at mine, it report 2.10 GHZ, it actually runs between 800-4800 MHz.

@micwoj92
Copy link
Collaborator

In my opinion only stock speeds should be supported, sure, you can oc many cpus to 5ghz but have fun trying to run that.

@micwoj92 micwoj92 removed the awaiting reporter Awaiting response from reporter / submitter label Jul 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants