Search results

I still find this to be an issues. Now Windows 11 22H2 on a Z790/13th gen. Why does HWinfo not subtract the sensor polling time from its polling rate to keep in sync? So if 1000 ms polling rate is set and all sensors take 100 ms to read, why not poll after 900 ms and thus stay at 1000 ms...

Thanks for the clarification. :-)

I did some more tests and as far as I can tell HWinfo always reports the "highest VF point" offset that is non zero, regardless of the specific offset value. So if 43x is the last VF point to use a non zero offset then HWinfo will report that as long as all higher VF points (51x, 55x, 57x, 58x)...

Hello. I wonder if HWinfo's "IA voltage offset" measurement is dynamic or fixed? I set varying offsets based on CPU frequency (ranges) in my BIOS, but HWinfo always shows a single value. Now I wonder if this is a BIOS problem or a HWinfo limitation? I tried to start HWinfo during idle and high...

Thanks, too bad, though. Constant instant tooltip redrawing increases CPU load in a way that affects the measurements. So it has to stay off then.

I fail to see the advantage of reporting 5% when the real CPU usage is over 60%, though?! This seems like a complete bogus number, neither relating to real load nor C state percentage. W11 tends to shifts more and more load from P cores to E cores so load decreases over time, but here is a...

Are you suggesting that 5% CPU Usage is correct while running highly multi-threaded AI image upscaling then, even while my CPU temps increase and C states don't match? The load is real, the measurements are all rather misinforming for the time being, be it HWinfo or other software.

This only applies to the first tooltip popping up or when you move the mouse to another column. Within each column tooltips are still redrawn instantly when the mouse is moved to different counters and sometimes changing columns also keeps instantly redrawing if the mouse was moved quickly.

Some Windows counter seems to be broken concerning CPU load and how various software like HWinfo measure it?! Process Explorer is affected the worst, because you cannot use its Threads display properly anymore. But HWinfo also shows more zeros than usage, which is not correct. Look the the...

But how can Core Utility be 86.4% (with some core reporting over 1005) while Core Usage is 4.6%? Obviously the cores are used more than about 5%, which my fans ramping up agree with.

13900k, virtualization disabled. Latest Win11 22H2: Software like Windows' Resource Manager and Process Explorer get confused, too.

The latest beta lists that a tooltip delay was added? I don't see that here, though.

Ahoi. Will this be looked into? Currently we have to disable tooltips to keep them from messing with CPU readings.

Yep, conflict with CTR. Good to know.

Today I observed the following max Effective Clock readings while C-states were enabled, Snapshot was enabled and CPU clocks were controlled by CTR. Unfortunately I did a reset after startup of HWiNFO, so it was at a later point after the start. Maybe a collision with CTR running in the...

Thanks for the information and effort to investigate and share these things (as much as being permitted). I am interested in facts, not opinion, so I can perfectly well accept that something other than clock stretching (and C1) is used to reduce the effective clock. In the end it is just...

I created these custom sensors to calculate clock stretching and visualize CCD differences. Anything below 0% is clock stretching (mostly) independent of C-states, listing the percentage of how much the effective clock is below the core clock. 0% is 100% C0 without clock stretching, effective...

On my Ryzen based board it shows the same 1.84 V as the CPU +1.8V sensor.

Try as I may, I could not find a correlation between HWiNFO's core effective clock, core C0 residency and core multiplier. Too bad.

I used 7.04 and Snapshot Polling in those screenshots. It's more of a report than a question about HWiNFO's different behavior compared to RyzenMaster. HI drops Effective Clocks considerably more when a core leaves C0 compared to RM (which often does not even budge). Unfortunately it does not...