Thanks for taking the time to test it out :)
Ok, I think I got it now. same links
Printable View
Thanks for taking the time to test it out :)
Ok, I think I got it now. same links
SAA-WEEAT! Thank you very much. Now I know my D0 i930's temps and loads:up:
Version 0.99.6.7 show correct.
I did more research on the accuracy and on most Core2 and Atom CPUs:
- Temperatures below 50°C should be ignored
- At temperatures ~ 50°C the inaccuracy is 10-15°C so not very usable too.
Man maybe you miss this thread. ;)
Two years ago unclewebb, rge and others did a wonderful job debunking those cheap Intel sensors readings and guesstimate various TJMax values.
That's why RealTemp has a calibration option for those who want to approximate "real" values for core temps in idle. That's why RealTemp (and now CoreTemp too, kudos to The Coolest for taking Kevin's advice :up:) are two almost perfect tools for showing real data for Intel CPU's not only fancy colors or graphs. ;)
Determining a correct Tj,max for a particular CPU is something different.
I don't think that anything can solve a problem of hardware inaccuracy of a sensor. Once it gets saturated at certain threshold, the values returned below might be totally irrelevant and not corresponding to real situation. Then you can guesstimate what you want..
EDIT: Trying to make sense of nonsense data (high entropy) seem more fancy to me than something else.. I know there was a large effort to achieve that, but I don't think it's possible - it will never be accurate for certain models.
Quote:
Originally Posted by burebista
Core Temp 0.99.6.7 is working great. I tried 101 tricks to fool it but everything looks good.
Now I have to go fix a few bugs in RealTemp to try and get caught up. :)
Don't believe everything Intel says. Some of what they have publicly stated about their sensors is misleading. Most of the Core 2 65nm sensors are excellent when you are using the correct TJMax and not Intel's TJ Target numbers that they also released at the IDF conference. There are many 45nm sensors that work very well below 50°C and don't get stuck at normal operating temperatures. Intel's statement is a worst case but it doesn't apply to all sensors. I've seen bad sensors in forums but all the Core 2, 45nm and 65nm, CPUs that I've owned have had very usable sensors.Quote:
- Temperatures below 50°C should be ignored
Even when a sensor is not 100% accurate, they tend to be very consistent from day to day. The data might not be accurate enough to make comparisons to your neighbor's computer but it is usually consistent enough to see if your computer is running hotter or colder than it was yesterday or if there was a core temperature change due to some hardware you changed. That's useful information to me and many other users.
If you believe Intel and think that all this data is bad then as the programmer of HWiNFO32, why don't you remove the reporting of this data from your program?
Cool, thanks.
Could guys with 655k and 875k post register dumps of Core Temp? I need this to add proper detection for these chips.
Is this any better than Real Temp for i7 chips?
By default, both of them should report the same values. Which one to use? I guess it depends on personal preference.
Ah, well Core Temp was reporting my CPU speed incorrectly unlike Real Temp. Still, both seem like great programs! :)
Certainly.Quote:
Originally Posted by The Coolest
SimpleTECH, thanks.
Another strange issue that I've noticed is that Core Temp reports many nehalem CPUs having a default multiplier which is lower by x1 than the real multiplier.
See x21 in the register dump when it's supposed to be x22.
Could you please post a Core Temp/CPUz screenshot and a cpuz Report?
I just tried version 0.99.6.8 64bit with my q6600 and whilst the fsb frequency is now correct, the multiplier at idle read 7 when it should be 6 (with 8 at load which is detected fine)
EDIT: the 32bit version shows the multiplier of 7 as well
EDIT2: The latest beta of realtemp (3.59 i believe it was) also has the exact same issue
same here.
Actually I was using the 21x multiplier at the time.Quote:
Originally Posted by The Coolest
@ SimpleTECH: That's what I thought, thanks. But does CPUz still detect it properly, even at x21?
We changed the algorithm of cpu frequency detection.
Instead of just reporting the static multiplier every second we now calculate the average frequency every second. Since EIST is quick, it may report a little higher frequency than you ever saw before, in any other application.
Quote:
Originally Posted by leo27
Quote:
Originally Posted by Kanabanoid
Isn't 21 the HFM and 22 a turbo bin?Quote:
Originally Posted by The Coolest
Tried a quick run on high multiplier and coretemp seemed okay except there was a short time it was showing 60.5 instead of 60.0, the maximum set. Realtemp and i7 turbo seemed to stay at what was ever the highest set multi when started (32x at the time) but when the programs were closed and restarted they seemed to pick up the higher multi okay.
http://img514.imageshack.us/img514/8231/tempo.gif
Here's a 655k coretemp dump.
It's time for 0.99.7 ?;)
Yep, coming very soon :)
The multiplier at idle is likely showing 7 because you don't have your computer set up correctly. If you want a 6 multiplier at idle then you need to have your Control Panel -> Power Options -> Minimum processor state set to a low percentage like 5%. What OS are you using? Windows XP has a slightly different adjustment to take care of this. At idle your CPU really is bouncing the multiplier back and forth between 6 and 8 and averaging about 7. That's why it reports the 7 multiplier. Having the Minimum set to 100% and C States enabled can cause the multiplier to hunt up and down at idle.
some_one: Thanks for posting that. I knew RealTemp was going to have this problem with these new CPUs because it doesn't recalculate the base multiplier. Before the K CPUs came along, the base multiplier was fixed and never changed so I thought it would be more efficient to only calculate that once. I'll get that fixed up in the next release, hopefully later today.
Thanks unclewebb, that explains it i'll change the power setting btw i'm on win7 x64
Here is a 875K
Can core temp properly report dual Xeon hexcores?
It should, otherwise I'd like to know :)
It works great ....... good readings all 12 cores displayed and frequency is reading correctly :up:
Thank you!
Any last quick requests? New version is going through final testing right now.
A small update :)
Quote:
Originally Posted by 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
@ some_one
Thanks, it's now fixed, you can download again.
0.99.7.1
IMHO reporting SLFM and FSB dynamic switching comes with it's own problems. Whether to report an "effective BCLK with technically correct multi" or a "technically correct BCLK with effective multi".
While using an "effective BCLK" may show a technically correct multi it does have some disadvantages. For instance when showing a multi of 6x the user now has to check BCLK or Freq to see if it's say 133 x 6 or 266 x 6 whereas using an effective multi (3x) it is immediately obvious. Also note that in the above screen shot showing a 5x multi (0.99.7.1 now shows 5.0 too), technically it is a 10x multi with SLFM enabled 100% of the time. You can see how this can get very confusing. At least your not having to show FSB which would make things even harder while dynamic switching is involved.
Though neither method is perfect I would have thought the "effective multi" would be the better way to go, after all this is the ratio that you are calculating using the performance counters. Just a personal thought and whatever you decide do remember the saying "you can't please all the people all of the time". ;)
Yes I noticed that the multiplier jumps around, and goes lower than the lowest possible multiplier.
I still think that I'm going to stick to this method, because as a user, you don't sit and stare at the FSB x multiplier the whole time. You simply glance at it once in a while.
Well, if you take it as an effective multiplier then it really is correct. But I hear you, after all the primary thing here is reading core temperatures.Quote:
Originally Posted by The Coolest
I definitely agree with that. Internally, the multiplier and SLFM mode can be rapidly cycling so it's a compromise no matter what you report and depending on the timing of when two different programs read data from the CPU can result in slightly different results.Quote:
Originally Posted by some_one
I just switched RealTemp too since
6.0 x 133 MHz = 798 MHz
is technically more accurate than
3.0 x 266 MHz = 798 MHz
Unfortunately, the correct way can make it more difficult to see the data with a quick glance. Doing things the correct way means now you have to look at both the bus speed and the multiplier. CPU-Z just reports the 3.0 effective multiplier and reports a constant bus speed so maybe I'll just go back to that to keep things simple.
I've talked to Franck and he said that handling SLFM is a pain, too.
I personally am going to stick to the method I have going right now. I think that it doesn't make sense to change the frequency detection or the way the frequency is reported every other day, it gets old :)
Right now all of us have it working one way or another, and overall, reporting correct clock speeds. That's the most important thing.
May this cooperation will result in a new prog, Real CoreTemp maybe...? :cool:
:D
Been pretty quiet this week.
Haven't seen any more reports about incorrect clock speeds or anything else for that matter :p:
Any requests/suggestions for future versions?
Also are the K series CPUs recognized properly in the new version?
Why does not report the correct frequency?
[IMG]http://img193.imageshack.us/img193/195/corezq.jpg Uploaded with ImageShack.us[/IMG]
Is that speed shown constantly or does it vary?
Because your CPU could be entering a low power mode and so the speed is lower.
the speed varies from 13 to 17 and I have disabled all the power saving options in bios.cpu-z shows the correct frequencyQuote:
Originally Posted by The Coolest
Just out of interest, could you try the latest RealTemp and see what frequency it reports?
I can report that 0.99.7 works okey with my i7 875k, now the multiplier stays steady when I have set it fixed in the bios with the powersaving disabled, with 0.99.6 the multiplier went up and down during idle and load as if powersaving was enable in bios but it wasn´t.
Great work :up:
Great
Is it recognized correctly as well?
panosk: It's usually C1E that is enabled that causes your multiplier to hunt up and down at idle. CPU-Z ignores this but that's what is happening within your CPU. Turning something off in the bios does not guarantee that it gets turned off in the CPU. Some settings get ignored.
RealTemp has an option to turn C1E off in the Settings window if you want your multiplier to be steady at idle.
http://www.fileden.com/files/2008/3/...alTempBeta.zip
Is working great. Thanks !
Version 0.99.7.3 - 5th July, 2010
- New: "Start Core Temp with Windows" feature on Windows Vista and 7.
- Fix: Taking a screenshot would not capture the whole window in Vista/7 with aero mode.
- Fix: Windows 7 taskbar Cycle mode only shows up after the first interval has elapsed.
- Fix: Overheating protection UI bug.
- Fix: The Mini-mode menu was not checked when Mini-mode was activated.
- Fix: Corrected the placement and size of the load label on Phenom based processors.
- Fix: Order of appearance of the system tray icons in Windows 7.
- Update: The appropriate G15 menu is now checked depending on the status of the G15 plug-in.
- Update: Added support for 12 core processors to temperature offset adjustment window.
When you set it to start with windows... at the start always shows a message "Another instance of Core Temp is already running!"
Core Temp 0.99.7.3 64bit version.
Well, if you had it previously setup to start up automatically, you'll need to remove that setting and keep "Core Temp Autostart" from the Task Scheduler.
Version 0.99.7.7 - 31st July, 2010
- New: Core Temp FAQ is now available online, see About Core Temp dialog.
- New: System tray icons for CPU speed and CPU load - see System Tray setup under Options.
- New: Support for the latest mobile AMD processors.
- Fix: Multiple "Fail" messages when the computer exits sleep or plugged into/unplugged from power (laptops).
- Fix: Several mobile Intel processor recognition issues.
- Fix: When disabling Windows 7 Taskbar feature with Cycle mode, icons still continue to cycle.
- Fix: Windows 7 Taskbar settings UI bug.
- Update: "Start with Windows" function in Vista and 7 now works on a per-user basis.
- Update: Change the time and date layout of the log file name to YYYY-MM-DD HH-MM-SS.
- Update: All of the readings logged are now numeric only.
- Update: In single instance mode, the previous instance will be brought to the screen.
- Known issue: Core Temp may stop responding for a period of time or completely lockup on some systems when switching between power supplies (wall/battery) or exiting sleep/hibernation mode.
There is also a new version of the Core Temp sidebar gadget with many improvements and tweaks and a Media Center addon that I recommend you to check out here:
http://www.alcpu.com/CoreTemp/addons.html
Version 0.99.7.10 - 1st September, 2010
- New: Enable overheat protection to execute a command every time an overheating occurs or just once.
- New: TjMax for AMD 10H and 11H family processors (K10/K10.5/Puma - older Turions)
- Fix: Several mobile Intel processor recognition issues.
- Fix: Mobile AMD processor recognition issues.
- Fix: Problem with Settings window throwing errors about Scheduled tasks if "Start with Windows" was not checked.
- Fix: Core Temp may crash on systems when switching between power supplies (wall/battery) or exiting sleep/hibernation mode.
- Fix: TCaseMax calculation for socket 939 AMD processors.
- Update: Shared memory applications and AMD Phenom derivatives will now show temperature for all of the cores.
- Update: Core Temp will remember proper screen position on multiple displays, when the 1st display is on the right.
Version 0.99.8.0 - 3rd October, 2010
- New: Completely new settings dialog, much clearer and easier to use.
- New: Added Hibernation to Overheat protection options.
- Fix: Mobile Intel Core2 Quad processor recognition issues.
- Fix: Pentium Dual-Core E6000 series model detection was incorrect.
- Update: TjMax adjusted to 100c (Intel's specs) for 400 and 500 series Atom processors.
I'm getting an issue with the new version where the G15 applet won't stay enabled upon start up. It takes enabling the applet twice through the menu system to get it to start and then when it finally does, it just shows temperature readings, rather than showing the date, time, and other information. Also, the G15 applet font settings get reset to "Use selected font" rather than "Use built-in font" which is what I would like it to be set on. It's like the G15 applet settings are resetting themselves every time I restart Windows.
Try to click on the defaults button in the G15 section of the settings, then apply.
This should save your settings, and reapply them the next time you start Core Temp.
Core Temp will not be able to enable the applet if it is started before the Logitech software, so you may need to tweak the startup order of your applications.
I disabled Core Temp from starting with windows and then put a shortcut in the Startup folder, this seems to have solved the startup issue. I will give your suggestion a try tonight when I get home. I thought there might have been a problem since it's worked just fine with every other release!
The way Core Temp now automatically starts itself in Windows 7 and Vista has changed in 0.99.7, it now works with scheduled tasks, to allow it to start even on UAC enabled systems without problems and this will in some cases make it start before other applications are started.
Ah. Well, it seems to be working just fine now. Totally unrelated question: Do you have any plans to add reading GPU sensor in to this at all?
Core Temp is getting a plugin manager in the next release.
And I will be making a GPU temp plugin for it in the future.
In addition anyone else will be able to write their own plugins for Core Temp.
Awesome.
Looking forward to the GPU plugin! Thanks.
Hey folks, having an issue with CoreTemp. I like the program, nice and clean and small but it's not recognizing my setup for some reason:
http://img811.imageshack.us/img811/1...empfailure.jpg
Temps aren't showing. Tried the 32 and 64 bit both, no go. Tried SpeedFan and HWMonitor and they both work but not exactly what I was looking for. If I have to choose between the two I'll go with SpeedFan, but I'd like to find out if there's something to be done with CoreTemp. Thanks!
Make sure you turn off ACC or any core unlocking in the BIOS. This is usually the main cause for temps not to show up.
Ah OK, I'll check it out tomorrow. Thanks!
Hey guys...
I know it took forever, but Core Temp version 1.0 (RC1) is here at last!
There were many delays due to life, college projects and other things that just got in the way.
I hope that the improvements and enhancements which v1.0 brings will make up for it.
So without further ado here is the change log for the new version.
Version 1.0 RC1 - 18th August, 2011
*** Core Temp Monitor is now available, an Android app to monitor your machines from anywhere in the world!
More information is available here
- New: Multilingual interface. Core Temp now natively supports adding non-English languages.
- New: Plugin system - 3rd party developers can now create plugins and extensions for Core Temp, both native code and .Net is supported, please see this for more information.
- New: Intel Sandy Bridge and AMD Fusion (Brazos, Llano) support.
- New: Max TDP detection on supporting processors.
- New: Power consumption on Intel's Nehalem and newer processors.
- New: Added support for VIA processors. (C3 - detection only, Temperature by Acpi Thermalzones)
- New: Added support for Intel Pentium and AMD K5 and newer processors. (detection only, Temperature by Acpi Thermalzones)
- Fix: All of the user reported bugs and many more unreported problems.
- Update: Optimized the startup code, Core Temp should now launch 2 to 4 times faster.
- Update: Optimized many other aspects of the code, Core Temp should now consume much less CPU time than before.
- Update: Restored support for older OS: Windows XP is now fully supported, Windows 2000 requires security updates KB935839, KB835732 and GDI+. In some cases hotfix KB816542 may be needed as well.
does coretemp read wrong numbers?
cpu-z and realtemp is showing me 21x191 = 4Ghz
coretemp shows me 12x191 = 2,2Ghz
if i run prime95, it jumps to 21x191..
??
i disabled C1E and EIST to clarify things and it still shows 12x191
This happens due to the new frequency calculation algorithm, it will go back to the previous one with the next RC, which should be out this week.
More info on the change here.
Version 1.0 RC2 - 7th September, 2011
- Fix: Temperature spikes to TjMax on Sandy Bridge CPUs.
- Fix: Settings not saved properly bug.
- Change: Changed frequency detection back to the original for Intel processors.
- Change: Removed power consumption feature on older CPUs (only supported by Sandy Bridge now).
- Known issues: Occasionally wrong FSB detection (Workaround: Press F5 in Core Temp).
- Known issues: Recognition of Atom E600 series.
I find the spyware added on to the download and installation to be distasteful. Nod32 halts my download so I can not install and halts do to the additional spyware toolbar.
http://pressf1.pcworld.co.nz/showthr...2-going-bezerk
wtf?
http://download.cnet.com/Core-Temp/3...-10794077.htmlQuote:
I can't add anything to the PROS section because I didn't install the product - the malware scared me away from Core Temp and CNet!
Cons
Stay away from this program! Spybot reports Malware! CNET, I'm very disappointed with this. You are no longer a reliable site to download programs! Better clean this up fast and apologize to your patrons!
Summary
Stay away from this program! Spybot reports Malware! CNET, I'm very disappointed with this. You are no longer a reliable site to download programs! Better clean this up fast and apologize to your patrons!
Read more: Core Temp - Free software downloads and software reviews - CNET Download.com http://download.cnet.com/Core-Temp/3...#ixzz1jOebQn7U
Quote:
Originally Posted by DerekT
Thanks for the links, i almost installed this software full of malware.
CNet seems to be wrapping any software they host in their own installer, with their own revenue-producing add-ons.
Core Temp does come with an installer which sometimes gets flagged incorrectly by NOD, there were some other AV software at the beginning, but it has been dealt with.
The installer Core Temp now comes with may not look very trustworthy or professional from perspective of power users, but it is safe. It allows you to opt-out of the offers by clicking Decline.
Also, if interested you can get a standalone version (no installer), in a ZIP archive by clicking on "More downloads..."
Never had a single problem...I always download the latest version in the way described above, Standalone...
Thank you for this software
Quote:
Originally Posted by The Coolest
Way to blame CNET, while you package it with toolbars and god knows what else! :rolleyes:
Where in my post have I blamed CNet? I was simply stating a fact, where their installer "installs" my installer.
My package does offer to install additional items, as I said you can opt-out or just download the standalone version if you don't like it.
I had to go looking for an alternative download.Quote:
Originally Posted by KGB7
Not cool at all and one can not choose to install only Coretemp and leave the CRAP out of the install. Yes, there's an alternate route that you have to be told or be quite observant OR you are hit with crapware.
Then you have to go and uninstall some of the crap.
Coolest? Too bad that such a fine piece of software has to go this route and that the creator follows behind those distasteful software wrapping b'tards.
:down:
if more people were willing to donate, then the bloatware probably wouldn't be necessary
It's NOT necessary.Quote:
Originally Posted by t_ski
Evar!
I don't think The Coolest would agree. Busting his ass trying to make this run for everyone under the sun for free? Buying hardware for testing constantly? I agree that it sucks to have bloatware installed, but I don't blame him for wanting to justify some of his time. Just my $.02 - you have yours, too.
Core Temp 1.0 RC3
http://www.alcpu.com/CoreTemp/CoreTemp32.zip
http://www.alcpu.com/CoreTemp/CoreTemp64.zip
Version 1.0 RC3 - 25th January, 2012
*** Core Temp Monitor is now available, an Android app to monitor your machines from anywhere in the world! More information can be found here.
- New: Multilingual interface. Core Temp now natively supports adding non-English languages.
- New: Plugin system - 3rd party developers can now create plugins and extensions for Core Temp, both native code and .Net is supported, please see this for more information.
- New: Added support for Intel Pentium and AMD K5 and newer processors. (detection only, Temperature by Acpi Thermalzones)
- New: Added support for VIA processors. (C3 - detection only, Temperature by Acpi Thermalzones)
- New: Intel Sandy Bridge (SB & SB-E) and AMD Bulldozer and Fusion (Brazos, Llano) support.
- New: Max TDP detection on supporting processors.
- New: Power consumption on Intel's Sandy Bridge (SB & SB-E) processors.
- Fix: All of the user reported bugs and many more unreported problems.
- Update: Optimized the startup code, Core Temp should now launch 2 to 4 times faster.
- Update: Optimized many other aspects of the code, Core Temp should now consume much less CPU time than before.
- Update: Restored support for older OS: Windows XP is now fully supported, Windows 2000 requires security updates KB935839, KB835732 and GDI+. In some cases hotfix KB816542 may be needed as well.
Load much faster !!!!
Your words.Quote:
Originally Posted by The Coolest
Quote:
CNet seems to be wrapping any software they host in their own installer, with their own revenue-producing add-ons.
How is it blaming? I was simply stating a fact about CNets new policies.
CNet just wraps anything uploaded to them with their own installer. Be it an executable, a zip file or another installer.
It's very improved. Will use it as my main temp indicator. Thank you.
Yes it's sad it goes this route, but I suspect if more than just a few appreciative people had been willing to donate a couple of bucks it might not have happened.Quote:
Originally Posted by DerekT
Even worse if you can not find a certified third party driver for today's Windows OS's to use with the hardware then using your own driver can possibly cost the hundreds of dollars a year just to for the privilege of being certified so it can be used by everyone.
IMHO try to see both sides of the fence, how can freeware be truly free when the authors have to give up their time and money in providing it and then possibly later provide improvements and/or support.
Many thanks 'The Coolest'................your a legend :up:
Hey guys. I know I haven't updated RC3 in a very long time, and since we got Ivy Bridge, BD and now Trinity, and soon we'll have PD CPUs that the current version doesn't properly support.
Well at last I've had the chance to finish up RC4. It adds support for all of the CPUs I just mentioned and fixes some minor bugs and problems we still had with RC3.
It's now available in both the installer version, and as always a standalone version is there too, so if you're still with me feel free to check it out.
Wanted to update this thread a bit. As most of you know, there is an Android app which can connect to your PC.
I've been working on an app for Windows Phone, and the beta has been released. At this point only people with phones that have been dev-unlocked can install it as the app itself is not on the market place yet, but I would appreciate feedback on it before it goes through admission to the market place.
Download link
http://i.imgur.com/ZfoQTAI.png
Core Temp 1.0 RC5
http://www.alcpu.com/CoreTemp/CoreTemp32.zip
http://www.alcpu.com/CoreTemp/CoreTemp64.zip
All downloads:
http://www.alcpu.com/CoreTemp/
Can you list any changes updates made in this version? I'm curious if it resolvbes an issue I've been having with Core Temp since I've moved to Windows 8.
I'm using a G15 ver 1 keyboard with LCD and use Core Temp to display info on the LCD. Since moving to Windows 8, I have to always enable the G15 applet, close Core Temp, then reopen it to get it to display the CPU info.
RC5 mostly fixes bugs and crashes, there are no significant changes in this build.
@ t_ski
In Task Scheduler try to add a delay for the Core Temp task. The applet needs Logitech's software to be running before Core Temp starts.
Thanks. I'll give that a shot when I get home.Quote:
Originally Posted by The Coolest
Core Temp Monitor for Windows Phone is now available for download from the Windows Phone Store
http://i.imgur.com/irRPXIt.png
There is currently 2 bugs I found in this release:
1. If the phone is locked while CTM is still running and some time passes, CTM doesn't resume properly. It won't display any monitors and will probably crash. So I would recommend to close the app when you're done with it, before locking the phone.
2. There is a mysterious issue when some times when the application starts, it will display a 'Connection interrupted' dialog with a 'Parameter: index' error. In such case, just exit the app and launch it again.
I'm working on getting these two problems sorted, but would really appreciate feedback on other serious problems so they can be fixed before I resubmit the app, which can take several days to be approved.
Version 1.0 RC6 - 9th October, 2013
- New: Digital signature. Core Temp is digitally signed by 'Artur Liberman', it is now easy to tell that you have a genuine copy of Core Temp.
- New: Update Checker. Core Temp can now notify you when a new version is available.
- New: You can now hide the taskbar button and use the system tray icons to pop the window back up.
- New: Added support AMD's new Richland APU.
- New: Added support for Intel Haswell and Ivy Bridge-EP CPUs.
- New: Preliminary support for Bay Trail-T Atoms.
- Fix: BSOD on some Windows 7/8 + UEFI enabled machines.
- Fix: AMD FX system freezes/crashes/BSOD.
- Fix: Driver failure when closing Core Temp on another Windows user account.
- Fix: Corrected detection of certain Xeon processors.
- Update: Ram utilization notification icon added to the Settings --> Notification Area.
- Update: Logitech G15 applet now supports CPUs with up to 10 cores.
- Update: System tray icons' tooltips now display their respective core information.
- Update: Log file will now also contain power consumption.
- Update: Log file will now keep track of each core on AMD CPUs as well.
Version 1.2 - 13th August, 2016
- Fix: Recognition for some Xeon processors.
- Fix: Driver load failure on Windows 7 and Vista.
- Known issues: Some systems running Windows 10 Anniversary may still have driver load failure.
Note:
With this version I have entered a new partnership with Goodgame Studios, they're a German company who develops free-to-play online games.
This installer includes an option to choose whether you want a shortcut linking to their Empire online game website to be put on your desktop or not. As some of you may have had negative experiences with installers including 3rd party garbage, I thought it was important to let everyone know that even if you don't opt-out of this option, the installer will NOT install anything on your system except a *.url file and an icon.
Thanks for the update!:up:
Version 1.3 - 10th September, 2016
- New: Support for Xeon D processors.
- Fix: K8 generation of AMD CPUs displayed "Distance to TjMax" text when it was not actually doing that.
- Fix: Recognition for Xeon W3670, W3680 processors.
- Known issues: Some systems running Windows 10 Anniversary may still have driver load failure.
Note:
Regarding Core Temp and Windows 10 Anniversary Update. This Windows release requires drivers to be submitted to Microsoft for them to digitally sign them, and this in turn requires the developer to have an EV (extended validation) code signing certificate. At the time of writing, I still don't have an EV certificate and I'm waiting for my certificate provider to start supplying them. As soon as I am able to acquire an EV certificate and get the drivers properly signed, Core Temp will be updated again.
Until this issue is resolved, Core Temp 1.0 RC9 should still work with Windows 10 Anniversary Update. You can download it here.
One more workaround, which I don't recommend, is to turn off Secure Boot in the BIOS.
Nice update :clap:
Or to have an old MB without UEFI. ;)Quote:
Originally Posted by The Coolest
I am using version 1.3 on two old X58 motherboard without any issue.
That is true. This only affect newer systems with Secure Boot + Clean install of Win10 AU.