Page 1 of 1

Current frequency & multiplier in Core Temp?

Posted: Wed May 21, 2008 10:53 am
by theshadowrunner
Hello Arthur, here is a small request:
If on the "Frequency" field, Coretemp could (also) display the current frequency and multiplier?
I use a E2180 overclocked at 2.6Ghz and the C1E feature from BIOS (sets multiplier is 6x when idle and 10x at full load).
It would be great if CoreTemp could indicate at which speed the CPU is currently running.
At the moment Core always displays "2661.28Mhz (266.13x10)" even if the current real multiplier is x6..)
Cpuz does this and I think it would be a nice Core feature too!
Thanks a lot,

TSR

Posted: Tue Jun 10, 2008 12:29 am
by The Coolest
CPU-z has a much more efficient design that what I currently have in Core Temp for CPU frequency.
You could hit F5 to refresh the main window (and the speed), I know it's not a real solution but this is currently the most I can do without making Core Temp become a resource hog.

Posted: Fri Jun 13, 2008 1:50 pm
by theshadowrunner
Hey Coolest, thanks for your answer.
Unfortunately, it doesn't work. I can refresh all I want, Frequency and multiplier reported by Coretemp never, EVER change.
I open CPU-Z and Coretemp side by side, CPU-Z reports x6, Coretemp x10. Refreshing Coretemp doesn't correct the issue. I know for a fact that at this point the multiplier is really x6. I'm using build 0.99 on XP SP3. CPU is E2180, mobo Asus P5K-VM.
Thanks for your support,

TSR

Posted: Sun Jun 22, 2008 8:40 pm
by bartb
F5 works fine here (Conroe switching between 6x and 9x).

If reading out the multiplier is expensive, maybe it's an idea to use the load, which is measured anyway, to determine when to try to re-read the multiplier: i.e. only when the load has significantly increased or decreased across thresholds which mimic the speedstep feature of the core.

Posted: Mon Jun 23, 2008 10:48 pm
by theshadowrunner
Hmm maybe this explains why Coretemp doesn't seem to be able to read my CPU multiplier even after manual refresh.. I don't use Speedstep (I disabled it in BIOS), rather I use the C1E feature of the CPU. Although Windows decides what's going on with SpeedStep, C1E is completely out of Windows control...
CPU-Z does manage to detect current multiplier w/ C1E on my system though.
Thanks for your support,

TSR

Posted: Wed Jul 30, 2008 9:42 pm
by The Coolest
Next Core Temp release should fix this issue.

Posted: Wed Aug 20, 2008 12:24 am
by theshadowrunner
Hi Coolest,
I see for 0.99.2 : - Add: On the fly CPU speed detection.
Unfortunately it still doesn't work. CT always reports 266.13 x 10.0 even if the real current multiplier is x 6.0.
CPU-Z must work differently, or possibly CT uses speedstep status to detect CPU speed and I'm not using speedstep, i'm using the "C1E" feature of my E2180 to control the multiplier.
Hoping there's a solution ^^
(I may be totally off in this explanation of why it doesn't work though, i'm by no means a cpu expert)

Image

Posted: Wed Aug 20, 2008 1:51 am
by The Coolest
Interesting.
I only tested it on my E6400 with EIST enabled, and it worked. I guess I'll try it again with just C1E and see what happens on my system.

Posted: Thu Aug 21, 2008 10:47 am
by The Coolest
Well I encountered the same problem when I set my C2D to C1E only.
I was able to fix this for the multiplier, but VID still reads the same.

Posted: Thu Aug 21, 2008 11:50 pm
by theshadowrunner
Oh great, thanks for fixing it. I don't look at VID value that much so it's fine with me if only multiplier is fixed honestly ^^;
See you,

TSR

Posted: Tue Aug 26, 2008 10:25 pm
by theshadowrunner
Hello Coolest,
I tried the new 0.99.3 extensively today.
Indeed, the mutiplier isn't stuck anymore to x10 in Coretemp, great.

However the reported multiplier changes in a strange way in Coretemp..

If I open both CPU-Z and Coretemp side by side, I can see that the multiplier doesn't vary the same way.
When computer is completely idle (20minutes after startup, minimum services running, no antivirus, etc..), CPUZ has a rock solid x6. However Coretemp goes berserk between x6 and x10 every 10 seconds or so, very strange...

I can take a video if you wish.
Would you know why Coretemp behaves that way?
See you,

TSR

Posted: Wed Aug 27, 2008 12:17 am
by The Coolest
To tell you the truth, I'm not quite sure why that happens. One possible reason is that Core Temp somehow brings the CPU out of pure idle state for several milliseconds while it does it's thing.
CPU-z may be a little bit more optimized in this regard. I know for sure that when EIST is enabled the multiplier on both of my systems is a rock solid x6 at all times. (Same with my AMD X2 system with CnQ enabled, BTW)

Posted: Tue Oct 14, 2008 1:51 pm
by hathor
Shalom, Arthur,
how do You calculate the cpu frequency, the current working speed?
It is never the same like CurrentMhz of the WINDOWS PROCESSOR_POWER_INFORMATION.

Greetings!

TiuHathor
:cry:

Posted: Tue Oct 14, 2008 4:13 pm
by The Coolest
In Core Temp 0.99.3 the system is a mess.
In the upcoming version, Core Temp attempts to detect the FSB, after it has the FSB it can multiply it by the current core\cpu ratio to get more accurate clock speeds.