"Core Temp" - A program for accurate K8 temperature monitoring

[The Coolest]

@The Coolest

You are possibily one of the best guys to ask this: Is there any Software approach to recognize properly what physical Core is a Athlon II/Phenom II really made with? Because all applications seems to not be able to do it properly. My AIIX4 620 is supposed to be a Deneb according to its Stepping, but the CPUID and Revision are those of a Propus BL-C2 instead of a Deneb RB-C2, that is what it really is.
For what I was capable of figuring myself, in this generation AMD is storing CPUID values and uses OPNs of the mainstream core that the model uses instead of appropiately differentiate what physical part it really is. If that is how things works, is no wonder that Software detecting may be tricky at best.

Well, basically you can tell the actual core that is in the CPU by the CPUID and the socket the CPU is run on.
I've simply decided to go by the same route as other ID programs to prevent confusion for users.

Hi, thanks for the update.

Core Temp now shows Turbo Core frequency on Thuban X6.
However, it reads my 1055T as '1005T' ??
The '% load' is a bit out of place as well.

Thanks for testing this, I wasn't sure I was doing it correctly, since the Thuban is not yet in the official docs.
There also seems to be a big with the placement of the load labels.
Could you please post a Register Dump file? (Go into Tools menu and click Register dump)

[KalTorak]

Thanks for testing this, I wasn't sure I was doing it correctly, since the Thuban is not yet in the official docs.
There also seems to be a big with the placement of the load labels.
Could you please post a Register Dump file? (Go into Tools menu and click Register dump)

Sure no prob.

I've attached the register dump (zipped).

Anyway found this in the txt,

Processor name: AMD Phenom II X6 1005T (Thuban)
Processor name string: AMD Phenom(tm) II X6 1055T Processor

[zir_blazer]

Well, basically you can tell the actual core that is in the CPU by the CPUID and the socket the CPU is run on.
I've simply decided to go by the same route as other ID programs to prevent confusion for users.

I think that you don't get my point. The CPUID tells that my Processor is a Propus when in truth it is a Deneb, according to Stepping. The issue is that in this generation, AMD can use two or maybe more different Cores for the same model, and all got the CPUID value of the flagship Core than that model uses instead of the CPUID of what they truly are (At least hold true for the AIIX4 line, where a Propus could be replaced with a Deneb with disabled Cache L3). The only accurate way to identify them is to look at the Stepping in the Heatspreader of the Processor, because no Software application says what it really is, and that is because what AMD seems to be doing with the CPUID value.

Historically, models with different physical Cores had different CPUID/OPN even if they share the same model specifications. If there was a Core with disabled parts, it still keep the CPUID of the full version instead of being replaced. For example:

S754 Athlon 64 3000+ (2 GHz, 512 KB Cache L2)
ADA3000AEP4AR Clawhammer SH-CG (CPUID F-4-A)
ADA3000AEP4AX Newcastle DH-CG (CPUID F-C-0)

The Clawhammer had 512 KB Cache L2 disabled, and instead of mixing it with the Newcastles like if they were the same thing, they had its own OPN (AR prefix), and keep the CPUID common to all Clawhammers. Same with, for example, Manchesters and Toledos with one core disabled. However, for the 45nm K10 generation (Not sure about 65nm), this is what we got...

SAM3 Athlon II X4 620 (Quad Core, 2.6 GHz, no Cache L3)
ADX620WFK42GI Propus BL-C2 (CPUID F-5-2)
Deneb RB-C2 (CPUID F-4-2)

That is fine by itself, however, as we know, AMD may use faulty Deneb RB-C2 Cores for that model because many people could unlock the Cache L3 that on a real Propus is nonexistant. Mine is precisely one of those Denebs, according to the Stepping written on the Heatspreader. However, the CPUID is reporting the value of a Propus. I consider than that is what really is confusing people, as it would be easier if those faulty Deneb still maintain its F-4-2 CPUID for easier recognision, but AMD seems to have overwritted it to that of Propus for the Denebs that were used for AIIX4 models. Even more laughtable is that for those people that did unlock their AIIX4s, the CPUID value got "upgraded" to that of a Deneb instead of being a fixed value.

The question is, do you know for any real reason that AMD may have opted to play dirty with the CPUID value? Even if they had the same OPN, it would be preferable than each different physical core had its own CPUID (Like they did on the entire K8 era) and wasn't changed for that of another physical core if they are selling it with disabled parts.

[initialised]

Still not working on unlocked X2 550s. Worked OK on x6 1090T

[ridney]

Thanks The Coolest works for me

[The Coolest]

I think that you don't get my point. The CPUID tells that my Processor is a Propus when in truth it is a Deneb, according to Stepping. The issue is that in this generation, AMD can use two or maybe more different Cores for the same model, and all got the CPUID value of the flagship Core than that model uses instead of the CPUID of what they truly are (At least hold true for the AIIX4 line, where a Propus could be replaced with a Deneb with disabled Cache L3). The only accurate way to identify them is to look at the Stepping in the Heatspreader of the Processor, because no Software application says what it really is, and that is because what AMD seems to be doing with the CPUID value...

I understood your point. To a degree Core Temp does report the actual core the processor uses.
If you have a problem with incorrect reporting of the codename, post a register dump and I'll take a look.

Still not working on unlocked X2 550s. Worked OK on x6 1090T

The DTS on unlocked chips is in most-to-all cases off, therefore you can't monitor temperature using it.

[Adam217]

The cpu frequency section is all messed up for me in the new version, previous version, 0.99.5 x64 works fine. Its the multiplier that jumps all over the place, finally settling on 6x when it should read 9x. System in sig, Win7 X64.

[The Coolest]

This is the reason why the speed looks all over.

*snip*
Core Temp's new algorithm basically measure the CPU's active clock cycles, and calculates the frequency based on that. Even if you disable speedstep, when the CPU is idle it skips clock cycles to save on power. Since this is the proper way to read clock speed for the Core i* series CPUs I thought I'd implement it for the C2D chips as well since the same code just works on these chips too.
I may have to revert back to the old way of speed detection for those processors, I'm still thinking about how to proceed.
Try to run Prime or superpi, you'll see it clock right up.

[zir_blazer]

I understood your point. To a degree Core Temp does report the actual core the processor uses.
If you have a problem with incorrect reporting of the codename, post a register dump and I'll take a look.

There it is. I figured out now than the Processor is reported as being Socket AM2+ instead of AM3 (Motherboard is a ASUS M4A785TD-V EVO). BTW, the last Core Temp version got the CPU Usage column one row lower than the Processor that it corresponds to...

Processor Frequency and Voltage are fine, I got it quite underclocked and undervolted.

[FlawleZ]

The DTS on unlocked chips is in most-to-all cases off, therefore you can't monitor temperature using it.

I would assume this applies to why my Sempron 140 unlocked doesn't read in Core Temp as well?

Also, any chance for a TDP rating on AMD or C2D/C2Q chips?

[The Coolest]

There it is. I figured out now than the Processor is reported as being Socket AM2+ instead of AM3 (Motherboard is a ASUS M4A785TD-V EVO). BTW, the last Core Temp version got the CPU Usage column one row lower than the Processor that it corresponds to...

Processor Frequency and Voltage are fine, I got it quite underclocked and undervolted.

I see that socket detection is still problematic. I'll make sure it is fixed for the next release.
The CPU you have IS a propus, so I don't see a problem there.
Regarding the CPU load, that is also fixed in the following bug-fix release coming soon.

I would assume this applies to why my Sempron 140 unlocked doesn't read in Core Temp as well?

Also, any chance for a TDP rating on AMD or C2D/C2Q chips?

Yes, that's why it doesn't work.
For TDP for AMD chips, I need to look at the tech docs again and see if this is possible by reading from the CPU directly. For Intel, I kind of don't see that happening, at least right now, since what I had before was completely inaccurate.

[zir_blazer]

I see that socket detection is still problematic. I'll make sure it is fixed for the next release.
The CPU you have IS a propus, so I don't see a problem there.

Impossible. Stepping is CACYC AC 0937DPMW. Many AIIX4 uses the CACYC Stepping and could unlock the Cache L3, meaning that they are Denebs, they can NOT be Propus because the Cache L3 is not there. In my case, I can't prove that by myself because the Cache L3 of my Deneb seems to be damaged as it doesn't POST when unlocking.
However, I did a search to actually prove my words, and found that the CPUID doesn't actually change. A guy here and some other that posted in that Thread, unlocked their Deneb based AIIX4 and the CPUID didn't changed from F-5-A (Propus) to F-4-2 (Deneb) though. So I was wrong in what I sayed about that a few Posts ago, but the fact that my Processor is a Deneb is still unquestionable. It just seems that the Denebs that got their Cache L3 disabled just get the CPUID of a Propus and that is. This is why identifing them is so hard with only Stepping being reliable, like in my case.
That is what I was whinning about from the moment that I started posting in this Thread

[The Coolest]

A real Deneb's CPUID is 0x100F42 (C2) or 0x100F43 (C3). The CPUID of a propus core is 0x100F52/0x100F53. I have seen Deneb cores that were cut down in cache given the same CPUID as real propus,
but there is currently no way to tell whether the CPU was a Deneb originally or that it's a real Propus, as far as I know, just by the data stored in the CPU via software. The best you can do is look at the chip.

[The Coolest]

Version 0.99.6.1 - 8th May, 2010

- Fix: Overheating protection.
- Fix: Incorrect detection of some Intel and AMD processors.
- Fix: Layout problems with AMD Phenom series and newer processors.

- Known issues: Intel processor speed detection displays extremely high numbers.

As you can see, most of the problems have been fixed. I'm still investigating the frequency issues, and will update as soon as I fix the problem.

[zir_blazer]

Well, this one (I forgot mention that I'm using the 32 Bits version) fixed the wrong column order for CPU Usage and also Package detection. BUT IS STILL A PROPUS!

Basically, if you have said me before that you was aware that some Denebs got hardcoded the CPUID of a Propus, we would have both saved ourselves of quite a bit of redundant Posting.

[The Coolest]

Yes, you are right.
Either way, nice too see that things are now being recognized and look correctly.

[zerodamage]

The temperature readings seem to be about 10C lower than what other temp tools are reporting. Is Coretemp reading the temps correctly or should I assume it is 10c warmer than what Coretemp is telling me?

[spacemonkey_15]

% Load is still off on x6 Thuban.


Ignore me, its fine :O)

[demonkevy666]

% Load is still off on x6 Thuban.


Ignore me, its fine :O)

is that on your current sig listed board ?

you still have the phenom 9950 listed along with M3A79-T-deluxe lol

[The Coolest]

The temperature readings seem to be about 10C lower than what other temp tools are reporting. Is Coretemp reading the temps correctly or should I assume it is 10c warmer than what Coretemp is telling me?

Temperature is not absolute, there is usually a 10-15c offset that has to be added to what core temp reports. You can do it from the Options menu.

[Naturecannon]

Version 0.99.6.1 - 8th May, 2010

- Fix: Overheating protection.
- Fix: Incorrect detection of some Intel and AMD processors.
- Fix: Layout problems with AMD Phenom series and newer processors.

- Known issues: Intel processor speed detection displays extremely high numbers.

As you can see, most of the problems have been fixed. I'm still investigating the frequency issues, and will update as soon as I fix the problem.

What about the temp issue? 10c off. Cores are correct but dont see my CPU temp as I did with the Phenom 965 and Core temp app. Cpuid Cpu temp matches my bios reading.
Or am I missing something here?

Thanks for the support




BTW: my temps are high as I am running prime.

[The Coolest]

Core Temp only displays a single temperature reading because all Phenoms (and derivatives) have a single thermal sensor in them. There's no point wasting space, showing 6 identical temperature values, while the core speed can be different among cores. This is why on Phenoms Core Temp looks differently than on K8 and Intel processors.

[The Coolest]

For the Intel guys:

Ok, I think I got the frequency issue eliminated. At least one computer I tested it on now reports frequencies properly, including Turbo mode.
0.99.6.2 - Beta
32 Bit
64 Bit

[The Coolest]

Version 0.99.7.0 - 26th June, 2010

- New: Implemented Windows 7 taskbar button features. (Under the Options menu)
- New: Clock modulation detection for Intel processors.
- New: Proper support the Phenom II X6 and Athlon L100 series.
- New: Support for the E3000 Celeron series.
- New: Displays the processor's manufacturing process. (Lithography)

- Fix: Intel frequency detection.
- Fix: Frequency doesn't update after exiting from Sleep or Hibernation. (Intel)
- Fix: Reading and logging intervals in Settings can't be changed.
- Fix: Minor Intel processor recognition issues.
- Fix: On some systems the System Information window would flood the screen with errors.
- Fix: G15 plugin restarts after resuming from sleep even if it was previously disabled from the menu.
- Fix: Overheating protection on AMD processors bug.

- Update: Rearranged the main GUI and added new information.
- Update: Added missing Intel Socket names.

There is also a new Media Center addon to see your CPU status here:
http://www.alcpu.com/CoreTemp/addons.html

[alpha0ne]

^ Thanks for your ongoing support