Well... VID is not VCore. VID is the Voltage ID setting on which the mobo bases the VCore setting on.
What I am interested in is why the temperature is different between TAT and Core Temp?
Printable View
Well... VID is not VCore. VID is the Voltage ID setting on which the mobo bases the VCore setting on.
What I am interested in is why the temperature is different between TAT and Core Temp?
coretemp and tat give identical results for me.. ~88c core 1, 91c core 2, 98c zone 1.... :D
i seeQuote:
Originally Posted by The Coolest
well both my E6600 B1 and E6700 B1 show TAT under report temps under load and over report temps at idle see http://i4memory.com/showthread.php?t=3082
What we need to do is figure out at what temp 'CoreTemp' reads to be the safe temp of 60c. Right now no one knows what the hell temp there cpu is really at since there is no one way to measure it. I say we all use coretemp, one it's free, works on most rigs (speedfan and tat do not work on my rig so they are not a good choice, lol) and is easy to use.
So what everyone needs to do is find out what temp in coretemp is = to intels 60c and we can all rest easy:toast:
the link to the prg doesn't work ever for me, i am located in Egypt and don't know what si wrong
can you please host it on filefront or here on the forum for example so i can get it
sorry for bothering but i have been facing this problem since the start of your thread with all versions
Are you reading the dts output from the msr or through the peci interface?Quote:
Originally Posted by The Coolest
Could be this a reason for different readings.
Also i would like to know where you read TJunction, it is from a msr? I can't find nothing related in all the datasheets of core 2 processors. Well it's obvious that the DTS is referenced to a temperature higher than TCasemax, but in the datasheets intel did not mention nothing about this temperature...so maybe you have a friend at intel :)
The core 2 duo processors can take 85 C of TJunction without problems, because intel has planned this and even inserted a circuit that throttle the processor at this temp. When the processor reach a critical temperature (higher than 85) another control circuit kicks in and shut down the processor.Quote:
Originally Posted by rodman
please correct this error when we enable EIST :
http://www.persianpcshop.com/EIST.JPG
another Mirror for CoreTemp v0.93 :Quote:
Originally Posted by SaFrOuT
I upload it here for you : ;)
http://www.savefiles.net/d/mpdynjqh3kmq.html
That error is due to the fact that core temp is not able to read the FSB from the mobo pll (well The Coolest correct me if i'm wrong :p: ), is the same bug of sandra that made some people think the northbridge clock was linked to the cpu multiplier :DQuote:
Originally Posted by HamidFULL
Quote:
Originally Posted by HamidFULL
Thank you, Thank you, Thank you
seems that i am not the only one facing the same problem since it has been already downloaded for 6 times
The temps are read from the MSR. Regarding the Tjunction... Well I wish I had a friend at Intel, heh. But I do have a friend who does, so he sends me some interesting bits of information, also I spoke to someone who decompiled TAT and found out that it was looking at the same MSR as I am and checking it for 85C or 100C.Quote:
Originally Posted by astaris
That is unfortunatly still a problem.Quote:
Originally Posted by astaris
Franck (CPUz), had to write a completely new way of detecting CPU clock speed using a special hardware based timer, which means some major recoding of that part.
I don't have much free time anymore, and I still have some other parts of the program that I want to improve or add, so we'll see what gets the priority.
I know this is a confusing and sometimes looks weird/funny but there's not much I can do right now. All I can say is that I will get it done eventually.
Well, thank you for your answer. Still, it is really strange that tat and you prog give different temps. Also some people reported that after updating the bios, coretemp would give totally different temps...but sincerly i can't see how this can happen...Quote:
Originally Posted by The Coolest
Anyway thank you for your great prog, i used it for my beloved opty 165 and i'll use it for my 6600. And about the fsb thing, i think this is really a minor issue, after all i use coretemp for the temps, not to monitor my system frequency. Well i mean, i know my fsb, i don't need a prog for that :D
another Mirror for CoreTemp :
Download v0.93 Here 100% Uptime
astaris:
Thank you :)
HamidFULL:
Thanks, both mirrors are now posted on Core Temp's frontpage now.
my temps are a couple degrees lower than TAT, and TAT is a couple degrees lower than asus probe
my coretemp software's been crashing lately 10secs following startup of app everytime......:shrug:
old and new versions
asus probe runs perfect but reads 3-4C higher consistently no matter what temp range
Go into the options, and try to disable the logging feature.
yeah that fixed it :toast: lolQuote:
Originally Posted by The Coolest
So I (we) understand it as to keep temps (using coretemp) below 80c to be on the safe side? LOL, no problems there;) Are we all in agreement?
FWIW TAT and coretemp give me different temps too... about a 3-5C difference with coretemp being reported hotter.
Yes under 80 and you are safe, but as always in this case lower is better :DQuote:
Originally Posted by rodman
See post 102 just above yours by 5 posts: http://www.xtremesystems.org/forums/...&postcount=102Quote:
Originally Posted by astaris
I run ~85c when gaming, up to 91c when running both CPU cores under load and no GPU load.......
Are they ever going to get this proggy to read negative temps from the bios?
And you are sure that your cpu does not throttle? Also do you have enabled Thermal monitor control in bios?Quote:
Originally Posted by STEvil