Thanks for this wonderful program.
Printable View
Now when you ask this i think the Tjunction is right?
One time, i lapped my IHS, and it was so shiny and flat...i thought, yes stupid , but i had never tried that...i did mount on the block without any coolingpaste, and wow, the paste really does it job, but anyway..
the temp did hit 79c in load with the OLD coretemp...
so that'll be about 95c in correct temp, and it did NOT throttle...
sooo...i think we have our tjunction 100 correct anyway regarding this?'
Regards.
It shows for me.. 35-36-32-25 for my Quad 6600
Version 0.96 - 31st December, 2007
- Add: System tray icons configuration.
- Add: Support for Intel's latest CPUs.
- Add: ClearType font support.
- Add: Time\Date column to the log file.
- Add: Always on top option.
- Fix: Core Temp does not proprerly display temperature and CPU select fields.
- Fix: Log file layout.
- Fix: Hide\Show does not properly Minimize\Restore window.
- Fix: Core code names aren't properly detected. (Intel)
- Fix: Incorrect\Missing CPU rating when not using stock\maximum multiplier. (Intel)
- Fix: Wrong CPU clock is reported when using EIST\non-maximum multiplier. (Intel)
- Fix: Wrong detection of Merom based CPUs.
- Fix: Single core Athlon 64s and Semprons reading -49C constantly. (Rare)
- Fix: C2D M0 rev. report very low temperatures. (Tjmax to 100C)
- Fix: Layout and display of tool tip text in the system tray. (Now shows a core per line)
- Change: Log the start and end of a session even if logging is disabled.
- Change: Settings and Systray settings windows appear in center of main window.
- Change: Rename "Tjunction" field to "Tj. Max" to make things clearer.
Happy new year to everyone :)
Any chance we'll see a 64-bit version of CoreTemp in 2008?
Thanks,
-bZj
why am i getting a large difference in temps at idle????
core #0 reads 51C regardless untill i load it enough to go above that temp.
core #1 reads slightly below core #0 by a minus 7C.
cores #2 & 3 could be accurate...not really sure.
---------------------------------------------------
the load temps appear to be close except maybe core #3.
You should check out what programs are running in the background,
Core 0 often runs a bit hotter than the others. Shouldnt be that much though.
Nice programme, idling at 30 and load at 40 with my Q6600 at 3.2.
There is a fix for 64Bit : http://forums.erodov.com/local_links.php?catid=18
i have....there are just the ordinary apps associated with XP SP2: avast (AVG), comodo firewall, nvidia driver, HP printer driver, windows defender and diskkeeper pro.
here are temps for idle and load at default (stock) speed (used wPrime 1024M bench to load cores).
still have core #0 at 51C and it won't budge even under load conditions.
The fix from .95.4 also works for .96, at least on Vista x64. Copy coretemp-startup.bat, ALSysIO64.sys and Atsiv.exe to the new coretemp directory, run the coretemp-startup.bat file and then run coretemp. It works great. This version matches Everest temps on my Yorkfield.:up:
how about posting your core temps to see what yours are for comparison for idle and then while benching with wPrime 1024M
I get the same major temp differences too...Iam on a 780i mobo not sure if that is the problem..
37/33/27/26
Im hearing alot that the 9650's temp problems are literally a problem on the chip itself. I wouldnt take much into it being wrong in core temp.
Oh no :(
Perhaps that explains ACE's and my problem with Coretemp
Everything Idle and At Stock
http://img220.imageshack.us/img220/4...etemp96gk2.jpg
With anyluck a BIOS Microcode update will fix this?
(ASUS P5E3 BIOS 0703)
John
So far no temp problem with QX9650
http://img221.imageshack.us/img221/7523/image1bk8.jpg
It's a boxed one.
L739 A646
Running on IX38-QuadGT with 12B06 BIOS.
i'll probably persue a RMA with intel....i think intel had a manufacturing problem with getting the DTS readouts to work properly for my pack date.
thanks for your help!:)
You're welcome :) keep us to date when your RMA arrives
Ace a Rue what happens if you lower your OC to his ? just to try , kindda following this issue as my QX9650 should be with me the next week(s) I rather too have a decent read out with an eqal temp accross the cores then some erratic reading and smoke it (unconciously sort off lol)