Free Download Core Temp
Sasha Stolt
To make sure your software is giving you an accurate reading you could compare the results with those of another temperature monitoring application. There are several free lightweight tools to monitor your CPU temperature, one of which is Core Temp.
It would be advisable to check your heat sink to see if it has been dislodged, or that the thermal paste is still connecting the heat sink to the CPU, as running your CPU at that temp is sure to cause damage in the long run.
You're well into the range that can cause permanent damage to the CPU. Most consumer electronics (including CPUs) are not designed to operate above 85 C for any extended period of time, and most will actually shut down when they get over about 100-105 C. Provided you have a working (and properly sized) cooling system and are not somewhere with unusually high temperatures to begin with (40 C or higher), you should not be seeing temperatures that high no matter how hard you push the CPU.
However, I'm inclined to believe something is wrong with your system due to that insane discrepancy between reported package and core temperatures. In particular, the possibilities that come to mind are:
CPU core temperatures of more than 110 degrees is too high and make the processor stop working. If really temp is over 110 degrees system will likely crash and there could be nasty situation. HWMonitor is showing incorrect values.
Go to your BIOS and check temperatures there, and if BIOS also says nothing this could be indicative that your Motherboard dosen't have any temperature sensors, thus explaining why HWMonitor is showing strange values.
Your CPU temperature is reaching its very maximum. I think, any PC component having temperature over 100C is too much for extended period of time. It is recommended to keep it under 80C in the long run, 60-something is even better.
The iGPU (Radeon R6) temp of 66C appears to be much more believable. Since this matches the "Package Temp" then I would surmise that your actual temp is 66C since the CPU cores and iGPU are in the same housing.
Given the fact that your cores are all running well above the stock 1900 MHz and one of them running near the max 3200 MHz turbo, it tells me that the temperatures are not affecting performance. If you're temperatures were too high then your CPU would throttle down to prevent damage.
You can download other temp monitoring software and see if you get similar results. Also, if your BIOS reports temps then you should check temps in your BIOS since that should be the most accurate reading.
Although it's generally not an ideal temperature for a computer, but if the temperature stays while you do simple working and light or mid high works in your computer then it can be your cooling system. Which is failing!
And the more I experiment, the more the measurements appear to have at least reasonable face validity. Now I just need to be able to record skin temperature to evaluate thermal flux with even greater precision!
I write about physiology and endurance training optimisation.
I'm a PhD candidate in exercise physiology, physiotherapist, and endurance coach / consultant.
I try to integrate ideas from the perspectives of an athlete, performance specialist, clinician, researcher, and especially as a curious enthusiast who just wants to learn from the smartest people in the room.
Everything written is my own inexpert opinion. Any good ideas should be attributed to the many smart people I have learned from. Any bad ideas are due to my own temporary misunderstanding. My current opinions will most certainly change as I continue to learn. Nothing I write should be taken as professional advice.
We've had a few great threads recently where members contacted AMD and asked what temps they should be looking at, what the max temp was on, and what programs should be used and why. But this information is still scattered and not well defined in one place. It also doesn't quite explain when you should be looking at certain temps. Well I've made it my mission to insure that people are reading the right temps and have been trying my best to give all the information each time I respond without sounding like a broken record. So I decided to write this information thread and little guide to help you out there.
"Core Temp" is what AMD refers to as "TCTL" and 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.
AMD designed this equation to accurately read peak (45C+) and load temps. It has an equational offset to determine said temps which equalizes at 45C. Since it's designed for peak temps and is a non-physical temperature it cannot read idle temps or account for ambient temps correctly.
At peak temps this value is typically 7-10C higher (depending on motherboard) than the actual temp due to it being a physical sensor. At idle it's a little more accurate, but still not dead on, and besides idle temps do not matter near as much as load temps do.
Hey there, I am getting around 80C after about 1h of usage, the temperature doesnt damage the board, but you can hear the fan sometimes.
The computer inside the SQ-5 should have no problem with temperature up to 90C, based on my experience. But if you get a warning, you should take a look inside.
Bye
I tried to follow this tutorial in order to get my temperature in the graphs from OMV 5 but without success. It seems that lm-sensors can't find anything on my RPi board.
Can you point me out on how to do this as i wasted my google searches a couple of hours by now.
On Raspberry Pi 4B, the temperature sensor data is accessed via `/sys/class/thermal/thermal_zone0/temp` file. It would be nice if OMV can let you specify a command for a generic collectd-rrd graph in the panel. That way temperature can be collected by putting this script in a file in path:
So I need to build this script to enable the thermal chip to report the temp, and enable the fan accordingly, like you would expect on any bog standard laptop. I just can't find where the actual core temps are located. Watch sensors can find them but I can't.
On my system, there are three sub-directories under /sys/class/hwmon/: there are hwmon0, hwmon1 and hwmon2. In my case, the coretemp module happens to be hwmon1: on your system this may be different. You can identify each sub-directory simply by doing cat /sys/class/hwmon/hwmonN/name, where N is the number.
The coretemp temperature values are on my system at /sys/class/hwmon/hwmon1/temp2_input and /sys/class/hwmon/hwmon1/temp3_input. The numbers on those tempN_input filenames may also be different for you, depending on the exact CPU model. The values will be integer numbers of thousandths of degrees Celsius, i.e. 41000 will be 41.0 degrees Celsius.
After windows 10 boot, Core Temp (v1.17.1) showed a temp of around 90 degrees for my Ryzen 9 5950x while idling on the desktop and a Max T of more than 100 degrees (from loading win10). First time this occured (several months after building PC) I shut down the PC immediately, 10 seconds later I rebooted and everything was normal, i.e. idle around 33 deg and a Max of 53. When playing CPU intensive games in VR max temps I usually see are 72-74 deg (generally spiking from loading stuff from my NVMe drives), 10 min of CinebenchR23 multicore test yields much lower temps, i.e. around 50 deg although I must admit that I have limited my PPT levels in BIOS (I'm fine with that, noise levels are reduced while performance is still great); I btw also reduced the temp limit for thermal throttling in BIOS.
The 2nd time a similar scenario played out (much later), I was initially looking around in BIOS for a couple of minutes to check - not change - something and then the temps were totally normal (35 moving slowly up to 40 over the course of a couple minutes) and all my fans were spinning normally, but when exiting BIOS (without changes or reboot) and arriving at the desktop after loading win10 I saw that temps were abnormal again, a max of 105 and idle around 95. Overheat protection from Core Temp (which I enabled after the first occurence, i.e. about 5-6 weeks earlier) kicked in and the PC was restarted (setting in Core Temp was to put PC asleep in case of overheat, so I assume restart was initiated by the BIOS ?). Subsequent boot everything returned to normal.
I don't understand how these abnormal high temps can only occur 2 times during a 5 month (almost) daily usage and only after win10 boot, i.e. never when actually using the PC during CPU intensive tasks (Cinebench, flightsim in virtual reality, etc.). I now recently removed my PPT limit in BIOS and now with stock settings (PBO off) everything continues to be normal. But very possible that I will sooner or later run into a 3rd case of overheating, the question is when.
I understand that too much thermal paste can cause temp spikes and since this was my first PC build I know that I certainly used a bit too much to err on the safe side, but I didn't use crazy amounts IMO. I remember that I tightened the cooler base very well to the CPU as well. And wouldn't too much paste not result in more frequent and continuous temp problems than I observed ? I want to stress that I had only 2 such events over a period of 5 months.
And--not that this would be easy--I'm running a Conky desktop on a TFT that's attached to my Raspi 3 which automagically gives me the load on the four cores which are in it. This appears to be the underlying code which reports the CPU load of each core.
Core Temp Gadget is a free Windows gadget that displays the temperature and load of your CPU's cores as well as basic information about your processor and platform. To use it, you must have ALCPU's Core Temp installed and running. Core Temp is a small, free application that extracts critical data from sensors and displays it in a compact interface. Core Temp Gadget simply displays data from Core Temp in an unobtrusive desktop gadget.
3a7c801d34