I'll take a look, thx.
I'll take a look, thx.
awesome tnx for the new release
Congrats on great work!!
BTW
code name for Turion X2 Ultra ZM8x series of AMD's mobile processors is Griffin not Lion ;)
Reads my 5000be x2 perfectly on 1 core..second core is off by 10c...can you make it so the offset can be set individually for the cores?
this is such a cool program..you are a smart guy to be able to build this .....
Are you sure, I looked it up on Wikipedia, in 0.99.3 it was Griffin.
http://en.wikipedia.org/wiki/Griffin_(processor)
I'll look into it, I know this is a problem with many X2s.
Great program finally something that can show the temps on my 65nm Brisbane correctly, AMD Athlon x2 4000+ 2,1ghz @ 300 x 10 = 3000mhz 1,41v
Idletemps was:
Core #0: 31-34
Core #1: 30-33
So i tried running LinX with this and here's the results.
But as above the temps is abit off:
Core #0: 48 - 52
Core #1: 58 - 63
So i can only assume that Core #1 is correct while Core #0 is off, but this only at load, seems to show correctly idle. Never thaught my temps was that high lol.
Also it shows my CPU at 285.75 x 10 = 2857.54mhz and that the voltage is at 1.3000v. CPU-Z shows correctly.
All I can say is keep up the good work!
Core Temp only shows the VID, not actual vcore.
Regarding speed, there is a problem, especially with AMD CPUs... I'm working on it
All OK on Phenom II 940BE :up:
yeah it's Griffin
http://hosting03.imagecross.com/imag.../1483CPU-Z.jpg And this is how CoreTemp see it: http://hosting03.imagecross.com/imag...-0.99.4-2-.jpg
Heh, you know that Franck is also human. I will talk to him and try to see who is right on this one.
Either way if he's right I'll fix this.
*EDIT:* Ok I think you're right, I just didn't read that article on wiki correctly. I'll fix this in the upcoming bug fix release. Thanks.
Very nice Coolest, supporting 64 bits is aways a great deal :up:
No VID.
Foxconn Bloodrage mobo G16 bios.
http://www.xtremesystems.org/forums/...1&d=1232759189
Although this should be in the Intel Core Temp thread. Nehalem does not report VID, so this is not a bug.
That's really not a big problem, but this is:
http://www.abload.de/img/error7xk4.png
Vista Ultimate x64, Phenom X3 8750@ 3 GHz, ASUS M3A32-MVP Deluxe
Previous version is working just fine.
funny enough, all cool here too !!! (under water)
http://media.bigoo.ws/content/saint_...gif/gif_85.gif
This is a Beta bug-fix release. Please report if you find any problems or have any suggestions please let me know so they can be fixed/implemented before the final release.
Version 0.99.4 (Build 75) - 27rd January, 2009
- Add: Show high/low temperatures. (Press F6 or the Tools menu to reset values)
- Add: On/Off switch for G15 applet in Tools menu.
- Fix: Settings window would open centered, and sometimes out of the desktop area.
- Fix: System tray icon very small in Windows 2000/XP/2003.
- Fix: AMD Athlon X2 4x50e series detected as 3x50e.
- Fix: Add support for Mobile Athlon 64 X2 TK-xx series and Turion 64 MK-xx series.
- Fix: Workaround added for when Core Temp fails to find supported CPUs on Phenom based systems.
- Change: Reorganized menu.
- Change: Only detect ES status for Core 2 series. Core i7 and Atom detection was incorrect.
- Change: TjMax for mobile Atom processors changed to 90C.
- Change: "Lion" codename for AMD Turion was changed to "Griffin".
32bit
64bit
Thanx for fix...
This beta build 0.99.4 is showing good temps with my Brisbane G2(~30ēC idle and ~48ēC full @ 2800MHz 1.30v). Previous versions were showing wrong temps like 5ēC. Can I trust in the temps now? Something have changed to adapt the program to the readings of the internal sensor in Brisbane?
They meant AM2 65nm processors, I think I got confused and wrote the wrong socket in the change log
hmm... got plus 21degree on my x2, that´s 67/69 under load. Should I trust the new Core Temp version and check my mount or ignore it ?
(231x13 1,5V)
edit: nvm, checked coretemp forums, set -21 offset. Still going to check hsf mount.
I set coretemp to load in startup...after getting into windows, low temp values do not appear (shows 0 deg ) at all unless i reset high/low. Normally lowest temps should be the ones first recorded after startup, correct ?