Core Temp 0.99.6

[The Coolest]

Hi everybody!

I know an update is long overdue but real life kind of got in the way. With college, work and other related projects taking up the majority of my time I simply didn't have much or any time to work on Core Temp.
Anyway, the new version is now up on the main Core Temp page here:
http://www.alcpu.com/CoreTemp/

You'll notice that there are not many changes, mostly bug fixes and other small improvements.
Core Temp is now built on Visual C++ 2010, which means that the oldest supported operating system is Windows XP SP2, which I think should not be a problem.

Of course all new and some of the upcoming processors are now supported. For the Intel camp, in theory newer processors should not need Core Temp to be updated to be able to report accurate temperatures anymore (even if it doesn't recognize the processor itself).

One other major difference, and this goes to the Intel guys, is a totally new algorithm for clock speed detection.
The first and biggest change is that the new algorithm is now monitoring on a per-thread scale. This means the main window will display the highest processor speed out of all the running threads, and in System Information window you will be able to see the frequency of every single thread. (I'm saying "thread" because in the HT enabled Core i7 processors the frequency reported by each thread of a single core could differ).
It measures the frequency every 50ms and displays an average frequency over the span of 1 second. This should allow for more stable and accurate clock speed.


Here is the usual change log:

Version 0.99.6.0 - 26th April, 2010

- Add: Support for new and upcoming Intel and AMD processors.
- Add: Better recognition of AMD dual/tri core unlocked CPUs.
- Add: Optional 24 hour display on G15 LCD.

- Fix: Platform field blank for newer AMD CPUs.
- Fix: Some K8 CPUs were unknown or recognized incorrectly.
- Fix: Overheat protection "Activate at specified temperature" problems were fixed.
- Fix: Overheat detection does not show a Balloon Tip when user specified temperature value is set.
- Fix: Temperature displays a negative value when core temperature reaches over TjMax (Intel).
- Fix: Intel W3500 series Xeons recognized with Core i7 model numbers (ie W3520 shown as Xeon 920)
- Fix: In certain cases Core 2 Duo T5500 was recognized as a T5450.
- Fix: G15 LCD display is no longer always-on-top after coming out of sleep or hibernation.
- Fix: G15 won't display 0.0000v in case VID readings are not supported by the CPU.
- Fix: In some cases, at Windows startup systemtray icons would not appear.

- Change: Windows XP SP2 or higher is now required.
- Change: Completely new processor frequency detection algorithm. (for Core 2 generation and newer only)
- Change: Remove "APICID" from main window as it has very little use.

[imposter]

*like*

[The Coolest]

Here's the bug release version I have promised:

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.

[The Coolest]

I've located the problem, but I need to make sure of something before I proceed trying to fix it.
Does the weird frequency readings only appear when you launch the program or do they also happen while it is running?

[The Coolest]

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

[stasio]

Bug still persist.
BCLK ok,multi still wrong(idle).
Edit:
Multi in full load OK.

[The Coolest]

I've been working on redoing the algorithm to work correctly, and I believe I've got it now.
Beta 0.99.6.3
32 Bit
64 Bit

Please let me know if there are any more problems with it.

[matthewwai]

The bug in overheating protection remains unchanged in Beta 0.99.6.3
The "Activate at the specified temperature" function cannot be activated and thus unworkable.

[The Coolest]

What processor do you have?
Because I just tested it and it works fine here.

[matthewwai]

My processor information is shown in the second attachment.
The "Activate at the specified temperature" function was deactivated automatically after I had activated it and restarted Core Temp, as shown in the first attachment.

My OS is Windows XP Home Edition service pack 3
And I had removed the previous version before using Beta 0.99.6.3

[The Coolest]

The only reason this would happen is that the Core Temp.ini file is not created.
This occurs if you run Core Temp from the ZIP\RAR archive directly or if you extracted it into a read-only folder or a folder with limited access.

[matthewwai]

I just moved the Core Temp folder onto the desktop. The folder was not inside any compressed folder such as ZIP or RAR. I could successfully create a new testing file inside the folder, which could be accessed by anyone without any restriction. Then I tried to activate the "Activate at the specified temperature" function but failed again.

In the attachment below, you can see all files inside the Core Temp folder after doing the above. The "Tesing file created by the user" was created by myself before running Core Temp.

I don't see any Core Temp.ini file inside the folder? Is it not created?

[The Coolest]

Could you please attach the CoreTemp.ini file right after you set "Activate at the specifed temperature" and clicking OK for me to take a look at it?

[matthewwai]

I just did it exactly as what you told me, I have saved the attached CoreTemp.ini file immediately after setting "Activate at the specifed temperature" and clicking "OK", even without closing the CoreTemp program.

[The Coolest]

I just put your ini file in my Core Temp folder, and ran Core Temp.
When I opened the overheat protection, I saw that the "Activate at the specified temperature" was selected, and when I changed the threshold temperature and reran it and got a overheating warning right away. I don't know why it doesn't work for you. I wonder if it could somehow be related to system localization? Is there a way for you to test with Windows in English mode?

[matthewwai]

My Windows XP is a Chinese version which can't be switched into English.
Perhaps that's why "Activate at the specified temperature" is unworkable.
I hope that the upcoming new version of Core Temp can support Chinese system, as well as other languages'.

[The Coolest]

It is strange that it's not working, since Core Temp is unicode, but I will try to see what the problem could be.

[matthewwai]

I have just installed "SpeedFan" which has a function similar to Core Temp's "Overheat Protection", and SpeedFan can function perfectly on my computer.
So I think the above-mentioned problem lies in Core Temp rather than on my computer.
SpeedFan can be downloaded freely from http://www.almico.com

[kbot]

does 0.99.6.8 recognize the temps of i7-processors correct?

it still shows a Tj.max of 97°C and the temps of the cores are 80-90°C on full load ( i7-920 - original 2.8GHz; little OC to 3.0GHz using the big cooler 'Alpenfohn Matterhorn')
it show the same like 0.99.6.1 did
i can't believe, that i'm almost at critical temperature o,0

[The Coolest]

Yes, the displayed temperatures are pretty accurate.

[gpgalazka]

I Have the same problem with setting "Activate at specified temperature" after CoreTemp restart its off. I am running 64 bit Win 7 and it is not a problem with ini file becoue it exists

[The Coolest]

Could you please tell what Windows localization you are using, if any?

[MisterPinst]

I'm experiencing the exact same bug as matthewwai....

Running Win 7 x64 on the following hardware:

Motherboard: MSI 785GT-E63
CPU: Phenom II X4 965 C3
RAM: (forget the brand) 800 Mhz DDR2

I am using the English (Canada) localization. The install is 1 day old, and I have repreated the same issue on a 2nd partition running the same OS with UAC disabled.

I have also installed it on a netbook and laptop and the bug does not occur. Maybe there's a common hardware type that is causing this problem to surface?

[The Coolest]

Very strange. I'll take a closer look it at. Seems that you and matthewwai both have AMD. Maybe that is why I'm missing this bug, as I run Intel.

[The Coolest]

Well I just had another look, and the answer was obvious. It ended up being a problem in my code for AMD processors.
This should be resolved in the upcoming version, I'll make sure of it. Will test it on my X2.