- May 18, 2006
For some reason I've always preferred the layout of coretemp, and I like that the tray icon is configurable.
This was discussed in length a couple of years ago, mostly on ocforums.com and XS, when Intel has just released its specs.Hi, I notice you are making TjMax updates in CoreTemp to properly reflect Intel's specs.
Any chance in updating CoreTemp to use the correct TjMax for the G0 Q6600?
Currently CoreTemp uses 100°C as the TjMax but the correct TjMax for the G0 is 90°C per Intel's specs.
Spec was published by Intel in 2006 at their fall IDF. See page 15 of http://lenry.atw.hu/tjmax.pdf
As iCyborg said, the new generation of Core CPUs do not report VID back to applications, so it can't be read. VID and VCore are not the same, Core Temp's FAQ explains it in section #14 & #15.My i5-540M doesn't display the VID.
The TjMax in the K10\K10.5 is encoded into the processor's registers, it should react similar to how Intel CPU's react when reaching TjMax, but I don't know at what exact point that happens. Also, adjusting TjMax is currently not possible, it also doesn't do anything for you except see a higher digit.what about thuban? tjmax is listed as 70c on my 1055t but I ran it as high as 88c (before using the 15c offset that was recommended) overnight with zero thermal throttling, performance degradation or problems of any kind. I'm thinkin' that might be a bit off.
Is there a way to manually enter tjmax?
Its not clear whether you are saying you believe the Intel spec itself is wrong (i.e. you claim TjMax of 90°C itself is wrong) or whether you are saying the DTS slope error is large and thus results in the reported temps at idle being "off by a big margin".This was discussed in length a couple of years ago, mostly on ocforums.com and XS, when Intel has just released its specs.
They are clearly off by a big margin. Their 45nm Core 2 specs were pretty accurate, but just didn't make sense for the 65nm chips, where most users were reporting idle temps way below ambient.
Q - so if my Thuban @ 3.1 is running @ 46c, full load (Prime 95, small FFT's), am I really 16c away from throttling? (AMD says the Thubans should go no higher than 62c.)The TjMax in the K10\K10.5 is encoded into the processor's registers, it should react similar to how Intel CPU's react when reaching TjMax, but I don't know at what exact point that happens. Also, adjusting TjMax is currently not possible, it also doesn't do anything for you except see a higher digit.
Core temp isn't bad, but I only use it on my Thuban b/c realtemp, as mentioned, doesn't support amd cpus. Maybe if BD ends up being a hit Kevin will take the time to add in the support, but I wouldn't hold my breath at this point.First of all Core Temp has support for AMD processors, RealTemp doesn't.
Besides that Core Temp also has a few addons that RealTemp doesn't, you can check them out here:
Other than that it has a few small features like Window 7 taskbar support and several other small additions that RealTemp may not have implemented.
Of course there are several things that RealTemp has which Core Temp doesn't.
I think that both programs are mostly an acquired taste, try it and see if you like it better than RealTemp or not, you can always delete it if you don't want to keep using it.
I've said this for years. Of course, I still don't do it, either... I'm making a new years eve vow to start it in 2012, however!You bring a valid point. But there is a but:
Most people who use temperature monitor applications will not bother reading up on them or the sensors, or look into how they work in reality. They won't bother with sensor calibration, and they won't appreciate "inaccurate" readings that make no common sense. Most people want stuff that you click and see the result right away without much messing around. Even though I'm a developer, and consider myself an enthusiast, I still notice that for most hardware and applications that I use, I prefer to install and go, without spending hours configuring it to work right from the get go.
The slope error of the sensor is problematic, since it's not a constant, there are no numeric ranges to allow Core Temp to accurately or even approximately calculate the correct temp distance from the TjMax.
In my personal opinion, the best way to monitor temperature would be to look at the raw TjMax figure. And as long as it's 20C+ away from 0 you're perfectly fine. Most people would find this unnatural and confusing, and they would prefer to see absolute values.
There are other apps, such as RealTemp, which allows sensor calibration, for example. I'm not sure what TjMax values are used in it exactly, but I'm pretty sure that they are also not the ones posted in that Intel document.
Something to consider: Since the original Nehalem, the TjMax is pre-programmed into the CPU. This makes the guessing games we had with Core 2 irrelevant. It may not be 100% accurate, but it's probably the closest you can get without going to extreme measures to obtain an accurate reading....
I've said this for years. Of course, I still don't do it, either... I'm making a new years eve vow to start it in 2012, however!
That is indeed a new bug. I'm working on getting it fixed.Buggy?
Under load, it will for a second flash a yellow 98C? temp and record this as the max temp for that core. Does it for all cores.
The watts jump all over the place, from 11.2W to 1200W.
Compared to V0.99.8 temps are ~the same.
|Thread starter||Similar threads||Forum||Replies||Date|
|Discussion Intel Core i7-11370H is it power hungry?||CPUs and Overclocking||14|
|A||Question 5800X and Prime95 core wattage||CPUs and Overclocking||2|
|Question How to stabilize a 5950x all-core overclock? Currently 4.3Ghz at 1.281V||CPUs and Overclocking||4|
|Question 5800X fails single core cycler test||CPUs and Overclocking||79|
|Review Anandtech: Intel Core i7-10700 vs Core i7-10700K Review||CPUs and Overclocking||4|