My CPU temp sensor is not designed to actually report CPU temp?


Recommended Posts

So, I have a motherboard CPU temperature sensor, but I also saw that 4 individual core temperatures were detected under the name "AMD Athlon II X4 620" in OHM in Windows, and the readout was precise to 0.1*c, so I thought surely that's a more accurate temperature reading for my CPU.  And sure enough, when I displayed it on a line graph along with the motherboard CPU sensor, it was like looking at a more precise version of the motherboard sensor line... 7 degrees lower.  So I just assumed the individual core one was right, and the motherboard one was wrong, and set a -7 degree offset to the motherboard one, and they lined up perfectly.

 

I had been doing that for years, thinking my CPU was running at 30*c idle, 45*c max.  

 

Then I read this:

 

  Quote

 

K10-Tctl is a non-physical temperature on an arbitrary scale measured in degrees. It does _not_ represent an actual physical temperature like die or case temperature. Instead, it specifies the processor temperature relative to the point at which the system must supply the maximum cooling for the processor's specified maximum case temperature and maximum thermal power dissipation. 

 

Boy do I feel stupid.  Especially because I'm having a really hard time understanding all of that.  Could someone please explain to me what that means?  Given that the exact same sensor also reports a "high" value of "70.0*c", does that mean that if I add up the moboCPU-sensor, plus the average of the 4-core precise sensor, it should equal 70*c (it equals about 74)?  And right now it is specifically reporting a + positve value, shouldn't it be reporting a negative value if it is relative to the maximum temperature?

On my Dell XPS 730x, I run BOINC distributed computing on my 8 logical CPUs (I have a hyper-threaded 4-core i7 965 XE) and all 3 of my GPUs (GTX 660 Ti, GTX 460, GTS 240).

I monitor the CPU temps using Core Temp, and I monitor the GPU temps using Precision X. I have a tray icon for each of the 4 CPU core temperatures, and each of the 3 GPU temperatures.

My System usually runs very hot, and I try to control the cooling the best I can. I have water cooling for the CPU, I've added an extra system fan, and I use a custom fan profile within Precision-X to make the GPU fan go maximum speed at a point before the GPU hits 70 *C, so that my GTX 660 Ti does not ever underclock when computing or gaming.

 

The routine temps for my system components are:

 

CPU full load: 80-88 *C

CPU idle immediately after full load: 55 *C

CPU idle for 10+ minutes: 30-45 *C

 

GPU full load: 68-84 *C

GPU idle immediately after ful load: 55-70 *C

GPU idle for 10+ minutes: 30-60 *C

 

I am used to seeing the CPU temps IMMEDIATELY jump from 85 *C to 55 *C when load is released.

They also change from 55 *C to 85 *C IMMEDIATELY when load is applied.

 

Regards,

Jacob

  On 27/07/2013 at 14:01, Mindovermaster said:

Sensors are guidelines, not the 100% true temperature. Your CPU can go to 40C to 45C to 30C back to 40C in milliseconds.

 

No no no what I'm saying is that THIS particular sensor is apparently not a guideline for CPU temperature!  It's an arbitrary relative number, a number of degrees Celsius relative to some temperature point (IE NOT the actual temperature relative to 0*c like a thermometer) I think, IF I understand that quoted text properly.

  On 27/07/2013 at 21:01, the evn show said:

Put all of that together and what have you got? Well I'm not really measuring a physical temperature, but the value I'm returning is related to temperature. I'm not really reporting a core temperature either - but the value is related to that. The scale that I report the result on is somewhat arbitrary. On one CPU the max temp is 100C but it reports 80, on another the max temp is 80C but reports 80. It's not really a linear scale - temperature goes up, amount of cooling goes up, but they're not necessarily 1:1 related and I might even change this ratio for different kinds of CPUs.

Maybe I shouldn't call this "Tcore" or "Tcpu" because that would be misleading. It's more of a control value for the cooling system. Maybe I should call that "Tctl" for "temperature control".

That's the basic thought process that lead to Tctl.

See here: (search for TCTL Max) Tctl max is always 70 for AMD chips. tctl is 'how close' to 'tctl max' are you on this particular processor. If Tctl = Tmax then the cpu thinks it's overheating no matter what processor you have or what the actual maximum/current temperature of the CPU is. Also notice the 'thermal profile': that's the log vs linear scale I used as an example which would let some cpus scale up cooling faster than others.

 

Wow, thanks for that very informative post!  I ask all this because I am not using the BIOS's fan control, it spins too fast when idle.  I'm using lm-sensors and pwmconfig in Linux, and I was wondering which temperature sensor to bind the fans to; the imprecise (1.0*c) mobo sensor, or the precise (0.1*c) AMD Tctl.  I can guarantee you that Tctl is not on a logarithmic scale, because when I line-graph it and the mobo-cpu-temp sensor, it creates the exact same line that the mobo sensor does, it has the same slopes when the CPU temp increases and decreases, only the AMD Tctl is always exactly 7 degrees cooler than the Mobo temp.  

 

So if the AMD Tctl is reporting temperature in a linear scale, but not relative to 0*c, in theory I could just add a +7*c offset to the Tctl sensor, and have a much more precise version of my mobo sensor (I have tried this in the graph, the two line graphs of Tctl and mobo-cpu-temp line up perfectly when I add a 7 degree offset to one of them), right?  I assume I would not want to add the minus 7 degree offset to the mobo-cpu-temp sensor.

Also, I've told pwmconfig to spin the CPU fans at minimum speed (45%, since I can't hear the difference between 0% and 45%) when they are below 38*c and to spin them at near-max (90%) speed when they are above 46*c, do these sound like good values?  I've actually been using the AMD Tctl to do this for 2 years now, which is apparently 7 degrees cooler than the actual CPU temp, so it's actually been told to spin at 45% below 45*c and 90% above 53*c, but since I've never had any problems with this CPU, I assume that was okay too?

 

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Whack another 1-2% tax on multinational tech giants, with those funds going directly to this. They wouldn't notice it, despite no doubt fighting like hell saying it'll bankrupt them! It also shouldn't be up to the EU to facilitate this, nor directly fund it, despite it ideally being for a social good. Open source definitely needs a heck of a lot of help. The brain drain is real, and it shows. But again, that's because people follow the money, because we've been forced into needing it so desperately.
    • Brave 1.80.124 by Razvan Serea Brave Browser is a lightning-fast, secure web browser that stands out from the competition with its focus on privacy, security, and speed. With features like HTTPS Everywhere and built-in tracker blocking, Brave keeps your online activities safe from prying eyes. Brave is one of the safest browsers on the market today. It blocks third-party data storage. It protects from browser fingerprinting. And it does all this by default. Speed - Brave is built on Chromium, the same technology that powers Google Chrome, and is optimized for speed, providing a fast and responsive browsing experience. Brave Browser also features Brave Rewards, a system that rewards users with Basic Attention Tokens (BAT) for viewing opt-in ads. This innovative system provides an alternative revenue model for content creators and a way to support the Brave community. Brave 1.80.124 changes: Updated Brave Leo in sidebar so input field is selected/focused by default when opened. (#47796) Removed hardcoded client side context limits for Brave Leo which will now be enforced server side. (#41620) Upgraded Chromium to 138.0.7204.168. (#47844) Download: Brave Browser 64-bit | 1.2 MB (Freeware) Download: Brave Browser 32-bit View: Brave Homepage | Offline Installers | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • While I support Wikipedia, and use it constantly, I don't use Mastodon, or even know what it is. The internet is currently going through a dramatic shift, and will forever be changed, for better or for worse. The fear I have is loosing resources, like Wikipedia, which while it still has its flaws, is just about the best possible site that exists. Why? Well: - It's an information resources on just about any topic, the modern day encyclopaedia - It is constantly updated, and publicly edited, with measures in place to prevent misuse - Its information and policies are not being swayed by money, as it's mostly funded independently - It's simple, low resources, and not using addictive techniques to hook you - It provides an actual free service: education, unlike most others which provide a "platform" that costs and still generally has an underlying goal of profits - No ads. Refreshing in this day and age. - No clickbait, there are still standards which are all ignored on "news" sites, even publicly funded ones as they try to compete with commercial players who at the end of the day, just want ad revenue. For all its flaws, it is the pinnacle of the internet. Even if they do decide to add an AI overview of each article at the top.. I hope Mastodon finds a way to continue in this ######ed up money crazed world.
    • I certainly hope you're right, but I put nothing past Microsoft these days. Writing Microsoft with a dollars sign used to be a joke because they charged for their software, but now they charge for their software "and" shove ads and recommended products down your throat at every turn, revert settings changes after updates, etc., so perhaps it's time to start spelling it Micro$oft again, :-p
    • Glow 25.08 by Razvan Serea Glow provides detailed reporting on every hardware component in your computer, saving you valuable time typically spent searching for CPU, motherboard, RAM, graphics card, and other stats. With Glow, all the information is conveniently presented in one clean interface, allowing you to easily access and review the comprehensive hardware details of your system. Glow provides detailed information on various system aspects, including OS, motherboard, processor, memory, graphics card, storage, network, battery, drivers, and services. The well-organized format ensures easy access to the required information. You can export all the gathered data to a plain text file, facilitating sharing with others for troubleshooting purposes. No installation needed. Just decompress the archive, launch the executable, and access computer-related information. Glow runs on Windows 11 and Windows 10 64-bit versions. Glow 25.08 release notes: What's new Glow's render engine has been improved. The program now supports high-resolution displays even on multi-monitor setups and monitors with varying DPI levels. It delivers sharp and clear visuals on 8K and higher DPI screens. The TSImageRenderer algorithm has been integrated into Glow. All visual icons in the interface are now automatically resized in a DPI-aware manner, ensuring high-resolution display quality. We know that Glow's Installed Drivers and Installed Services sections load slowly. That's why the loading algorithms have been reprogrammed into a parallel structure. Now it loads with up to 95% speed increase compared to the processor core. Glow's monitor testing tools have been reprogrammed. The Dead Pixel Test and Dynamic Color Range Test now function with improved accuracy. The Screen Overlay Tool has been redesigned, featuring theme sensitivity and new functions such as a close button. The startup engine for all Glow tools has been redeveloped, allowing for more efficient and effective management of the tools. The search engine's clear button in the "Installed Drivers", "Installed Services" and "Installed Applications" sections has been refreshed with a DPI-aware design for enhanced visibility. Icons have been added to the BIOS Update, Battery Report Generation, and Export buttons. Icons have been added to all buttons across Glow's tools. The Tab key functionality in Glow's interface has been improved, enabling more precise and stable navigation between elements. Glow's logo has been updated with a new design, offering a more elegant and modern appearance. Glow's primary colors have been redesigned within the Adobe RGB Color Space, giving the interface a more contemporary look. The About section has been reprogrammed. All social media buttons now feature icons, and the close button is DPI-aware and more prominent. Fixed Bugs Fixed an issue causing control buttons to overlap and shift position at high DPI settings. Resolved a DPI-related issue where checkmarks in the top menu distorted visually at high DPI values. Fixed a parallel processing error that caused the program to crash after clicking and closing information text in any monitor test tool. Corrected a bug in the Dynamic Color Range Tool that caused white space to appear on the right and bottom when resizing. Fixed calculation errors affecting the color scale and ratios in the Dynamic Color Range Tool. Resolved a layering issue that sometimes caused message boxes to appear behind the program window. Changes The backend code structure of Glow has been improved to a modular architecture, ensuring full compatibility and easier integration with other Türkay Software products. Tools have been moved back to the top menu. Some interface icons have been replaced to provide better visual clarity. A YouTube link has been added to the About section. Note: Always unzip the program before using it. Otherwise you may get an error. Download: Glow 25.08 | 3.1 MB (Open Source) View: Glow Homepage | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Collaborator
      fernan99 earned a badge
      Collaborator
    • Collaborator
      MikeK13 earned a badge
      Collaborator
    • One Month Later
      Alexander 001 earned a badge
      One Month Later
    • One Month Later
      Antonio Barboza earned a badge
      One Month Later
    • Week One Done
      Antonio Barboza earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      592
    2. 2
      ATLien_0
      225
    3. 3
      Michael Scrip
      167
    4. 4
      Xenon
      140
    5. 5
      +FloatingFatMan
      128
  • Tell a friend

    Love Neowin? Tell a friend!