CPU-Z - Official 1.62 Released.

How Wierds this:confused: 1.61.3 shows 1600MHz and 1.080v while my systems Idle and 1.62.0 Shows 4500.09MHz and 1.080v while Idle. Is the new version showing the overclocked speed Full Time? like Core Temp does?
 
zepzeppelin said:
How Wierds this:confused: 1.61.3 shows 1600MHz and 1.080v while my systems Idle and 1.62.0 Shows 4500.09MHz and 1.080v while Idle. Is the new version showing the overclocked speed Full Time? like Core Temp does?
Any of the beta's after 1.61.3 had the same issue for me i.e. no downclocking when using EIST with power saving features.

I didn't check to see if it was fixed in this official release.
 
Not sure they will be able to fix it.

CPU-Z is using a very handy timer named "APIC timer" for clocks computation. Unfortunately for us, Windows 8 does use that timer as well, and the simultaneous use of that timer by an application causes big troubles (system crash). Microsoft declared that this timer is a not a shareable resource, so we have no other choice than to stop using that timer.

Version 1.60 is the last that use that timer, and version 1.61 is the 1st version that does not use the APIC timer anymore, and as you may have noticed, the alternate methods are not working very well yet. We updated to 1.61.1 and 1.61.2 to fix several issues. Today, we released 1.61.3, that does still add several fixes. We hope to be close to the complete solution of that problem, and to be able to provide a CPU-Z as good as it used to be.
 
Is the new version showing the overclocked speed Full Time? like Core Temp does?

Core Temp/Real Temp doesn't do this. If you are running Windows 8 or 7 and are experiencing this issue with Core/Real Temp then you most likely have the power options set to "high performance" under which windows will be forcing max Turbo 24/7, in order to undo this go to Power Options>Advanced Settings>Processor Power Management and change "Minimum Processor State" from 100% to something lower (I use 5%).

EDIT:

This new version of CPU-Z is also showing correct CPU speed for me like Real/Core temp do with the 100% minimum CPU state issue fixed.
 
Last edited:
This is great news. For years RealTemp has been telling users that just because their CPU is lightly loaded does not necessarily mean that it is using the minimum multiplier.

http://img197.imageshack.us/img197/6694/realtempcpuz.png

RealTemp has been using the same multiplier reporting method since late 2008 when the Core i CPUs were first introduced. There has been no need to update this method since then because this monitoring method was fully documented and recommended by Intel in their November 2008 Turbo White Paper. Thanks rge at XtremeSystems for originally sending me this information.

CPU-Z has not been accurate on a lightly loaded Core i CPU for the last 4 years. Version 1.62 looks to be an improvement but it still makes you wonder why the Intel recommended method has been ignored all this time.

The other problem is that Intel CPUs use monitoring timers that are a shared resource within the CPU. That means if you run 5 different monitoring programs, each program can screw up another monitoring program if it decides to randomly reset these high performance timers. Some apps do this continuously. Your best bet is to find a single monitoring program that you can trust and stick with that.
 
Last edited:
Back
Top Bottom