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

I've tried the latest 64bit version, stops working straight away - heres the info.

Quote:

---

Problem signature:
Problem Event Name: APPCRASH
Application Name: Core Temp.exe
Application Version: 0.99.5.26
Application Timestamp: 4a778996
Fault Module Name: Core Temp.exe
Fault Module Version: 0.99.5.26
Fault Module Timestamp: 4a778996
Exception Code: c0000005
Exception Offset: 000000000001b609
OS Version: 6.0.6002.2.2.0.256.1
Locale ID: 2057
Additional Information 1: cce4
Additional Information 2: aa24106cd86c2603db6e670d79584df8
Additional Information 3: 870b
Additional Information 4: ec4d2ebce4538e5ee294ec45ae078f21

---

Hi, I've got a Phenom 2 X2-550 BE unlocked to X4.

I'll try both 0.99.5.25 and the 0.99.5.20 in a couple of hours and report back. It will be the 64bit versions on windows 7 64bit RC1.

I'll provide event log details if it crashes.

I'm in the same situation as Nelly. I get the exact same error. Using Vista x64.

I tried the 32-bit version as well and got a similar error.

Thanks guys, seems like a problem with K10 and up, as it works on my X2 3600+.
I will be working on a fix for this. for now beta build 20 is back on the front page in case anyone needs it.

Quote:

---

Originally Posted by Nelly

I've tried the latest 64bit version, stops working straight away - heres the info.

---

Same issue."... Stopped working..." right away as soon as i double click the .exe (i run it as administrator like it says in the readme).

ps: Vista Ultimate 64

PS2; I tried the BETA version of 0.99.5 and it warned me that it does not support my CPU (Phenom2 955) than i clicked Cancel and it worked...

Version 0.99.5.27 - 5th August, 2009

- Fix: Crash on AMD 45nm processors.

Works now thanks :up:

Hi,

I noticed that core temp doesn't read the core temps of an unlocked X2 to X4. I understand this is a hardware limitation.

However, if I use the Gigabyte provided utility (easytune), or say speedfan, it still picks up the temperature and label it as CPU temp. This is the same temp that is reported in the bios. The bios never reports core temps.

How wrong is the bios reported cpu temp ? If its a competent reading, would it be hard to patch coretemp to display the CPU temp for us unlockers ?

Edit : MMMh, I think I'll just test it myself by locking the X2 back to two core and comparing the readings. If they are the same under stress/idle, I'll conclude that it is a competent temp reading. Will report back.

Just curious but what was crashing the program ?

It was just a missed line of code, like it almost always is.
Accessing a NULL in memory = bad :p:

Quote:

---

Originally Posted by The Coolest

It was just a missed line of code, like it almost always is.
Accessing a NULL in memory = bad :p:

---

:clap: nice work

Seems to be working fine for me now, cheers.

First, let me make it clear I don't want to start a debate about wich utility is better for reading temps. I'm using SpeedFan because it reports the same reading as my motherboard bios.

I just want to get the "real" info and someone suggested I should use CoreTemp as the definitive application for that purpose.


So I've been testing Core Temp on my setup. X2-550 BE with Gigabyte GA-MA770T-UD3P.

I was shocked to see what CoreTemp reports as my CPU temp. Its telling me my temps are at 22C idle. Theorically, this is not even possible as my room temp is at 23C.

If I go in the BIOS, the reported CPU temp is 33C wich sound much more in line to what I would expect it to be. Also, Speedfan reports the exact same reading as the mobo (bios).

Something must be wrong with CoreTemp. Or is my Xigmatek HDT-S1283 really doing such an awesome job ...

If I stress the CPU for 5min, Core Temp read 32C while SpeedFan says 40C. Room temp is at 23C.

Here is a reading from the log file of CoreTemp :
20:53:19,32°,,,19°,32°,100%,3113.90 MHz

19C buahahahahah. I wish.:rofl:

Maregg:

Quote:

---

*K10 = Phenom (Agena), Opteron (Barcelona). The K10 reports a temperature value that is relative to a certain predefined value, it doesn't report the actual processor temperature! So take that into consideration.

---

This includes anything that came after the original K10

Maregg, the reason speedfan reads the same as the BIOS is it is reading the same thing (probably the bios value actually). Coretemp is reading a register in the CPU itself... but seems ever since Brisbane AMD has been rather lax about making it accurate :shakes:

Your the Coolest Cool:up:

Works fine now with new version on Vista32bit X2 550

But why first version has been 0.99.5.26 instead of 0.99.5.25?

alcpu.com is down. in the mean time you can use this:
Version 0.99.5.27 - 05 August, 2009

Quote:

---

Originally Posted by The Coolest

Version 0.99.5.27 - 5th August, 2009

- Fix: Crash on AMD 45nm processors.

---

Just to confirm, this works for me now. Thanks :)

Since Intel and AMD don't post their CPUs max temp ratings as core temps but as Tcase whats the point of reading core temps? :confused:

Quote:

---

Originally Posted by ReKcOlNu

Since Intel and AMD don't post their CPUs max temp ratings as core temps but as Tcase whats the point of reading core temps? :confused:

---

It’s just a value, something to go after, you know :)

Quote:

---

Originally Posted by 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 acceptable.

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.
:)

---

Version 0.99.6 - 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.

Quote:

---

Originally Posted by 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.
:)

---

Version 0.99.6 - 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.

@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.

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.

http://img199.imageshack.us/img199/2...5tcpuz0996.png