- Nov 28, 2019
- 1
- 0
- 10
Recently installed my i7-9700k and I don't think the paste got spread across my CPU cooler properly (I think it's a Dark Rock 4). Just wondering if my Idle temps look normal.
[SOLVED] Cooling temps
- Thread starter capnbinary
- Start date
Solution
Darkbreeze
Retired Mod
- Jun 24, 2014
- 82,681
- 8,320
- 176,790
Idle temps really don't matter, at all, unless peak maximum temperatures are beyond the recommended range, which for that CPU would be 80°C.
And, I can see you are using either HWmonitor, Open hardware monitor or something else, other than HWinfo. I'd recommend making a change and switching to HWinfo.
HWmonitor, Open hardware monitor, Realtemp, Speccy, Speedfan, Windows utilities, CPU-Z, NZXT CAM and most of the bundled motherboard utilities are often not the best choice as they are not always accurate. Some are actually grossly inaccurate, especially with certain chipsets or specific sensors that for whatever reason they tend to not like or work well with. I've found HWinfo or CoreTemp to be the MOST accurate with the broadest range of chipsets and sensors. They are also almost religiously kept up to date.
CoreTemp is great for just CPU thermals including core temps or distance to TJmax on older AMD platforms.
HWinfo is great for pretty much EVERYTHING, including CPU thermals, core loads, core temps, package temps, GPU sensors, HDD and SSD sensors, motherboard chipset and VRM sensor, all of it. When starting HWinfo after installation, always check the box next to "sensors only" and de-select the box next to "summary".
Run HWinfo and look at system voltages and other sensor readings.
Monitoring temperatures, core speeds, voltages, clock ratios and other reported sensor data can often help to pick out an issue right off the bat. HWinfo is a good way to get that data and in my experience tends to be more accurate than some of the other utilities available. CPU-Z, GPU-Z and Core Temp all have their uses but HWinfo tends to have it all laid out in a more convenient fashion so you can usually see what one sensor is reporting while looking at another instead of having to flip through various tabs that have specific groupings, plus, it is extremely rare for HWinfo to not report the correct sensor values under the correct sensor listings, or misreport other information. Utilities like HWmonitor, Openhardware monitor and Speccy, tend to COMMONLY misreport sensor data, or not report it at all.
After installation, run the utility and when asked, choose "sensors only". The other window options have some use but in most cases everything you need will be located in the sensors window. If you're taking screenshots to post for troubleshooting, it will most likely require taking three screenshots and scrolling down the sensors window between screenshots in order to capture them all.
It is most helpful if you can take a series of HWinfo screenshots at idle, after a cold boot to the desktop. Open HWinfo and wait for all of the Windows startup processes to complete. Usually about four or five minutes should be plenty. Take screenshots of all the HWinfo sensors.
Next, run something demanding like Prime95 (With AVX and AVX2 disabled) or Heaven benchmark. Take another set of screenshots while either of those is running so we can see what the hardware is doing while under a load.
*Download HWinfo
For temperature monitoring only, I feel Core Temp is the most accurate and also offers a quick visual reference for core speed, load and CPU voltage:
*Download Core Temp
As far as thermal testing is concerned, there is basically one acceptable way to test thermal compliance and that is using a steady state workload. Using fluctuation workloads like most benchmark utilities, or Realbench, or other "stability" tests, or games, is really not acceptable for thermal testing.
And, I can see you are using either HWmonitor, Open hardware monitor or something else, other than HWinfo. I'd recommend making a change and switching to HWinfo.
Monitoring software
HWmonitor, Open hardware monitor, Realtemp, Speccy, Speedfan, Windows utilities, CPU-Z, NZXT CAM and most of the bundled motherboard utilities are often not the best choice as they are not always accurate. Some are actually grossly inaccurate, especially with certain chipsets or specific sensors that for whatever reason they tend to not like or work well with. I've found HWinfo or CoreTemp to be the MOST accurate with the broadest range of chipsets and sensors. They are also almost religiously kept up to date.
CoreTemp is great for just CPU thermals including core temps or distance to TJmax on older AMD platforms.
HWinfo is great for pretty much EVERYTHING, including CPU thermals, core loads, core temps, package temps, GPU sensors, HDD and SSD sensors, motherboard chipset and VRM sensor, all of it. When starting HWinfo after installation, always check the box next to "sensors only" and de-select the box next to "summary".
Run HWinfo and look at system voltages and other sensor readings.
Monitoring temperatures, core speeds, voltages, clock ratios and other reported sensor data can often help to pick out an issue right off the bat. HWinfo is a good way to get that data and in my experience tends to be more accurate than some of the other utilities available. CPU-Z, GPU-Z and Core Temp all have their uses but HWinfo tends to have it all laid out in a more convenient fashion so you can usually see what one sensor is reporting while looking at another instead of having to flip through various tabs that have specific groupings, plus, it is extremely rare for HWinfo to not report the correct sensor values under the correct sensor listings, or misreport other information. Utilities like HWmonitor, Openhardware monitor and Speccy, tend to COMMONLY misreport sensor data, or not report it at all.
After installation, run the utility and when asked, choose "sensors only". The other window options have some use but in most cases everything you need will be located in the sensors window. If you're taking screenshots to post for troubleshooting, it will most likely require taking three screenshots and scrolling down the sensors window between screenshots in order to capture them all.
It is most helpful if you can take a series of HWinfo screenshots at idle, after a cold boot to the desktop. Open HWinfo and wait for all of the Windows startup processes to complete. Usually about four or five minutes should be plenty. Take screenshots of all the HWinfo sensors.
Next, run something demanding like Prime95 (With AVX and AVX2 disabled) or Heaven benchmark. Take another set of screenshots while either of those is running so we can see what the hardware is doing while under a load.
*Download HWinfo
For temperature monitoring only, I feel Core Temp is the most accurate and also offers a quick visual reference for core speed, load and CPU voltage:
*Download Core Temp
As far as thermal testing is concerned, there is basically one acceptable way to test thermal compliance and that is using a steady state workload. Using fluctuation workloads like most benchmark utilities, or Realbench, or other "stability" tests, or games, is really not acceptable for thermal testing.
Testing thermal compliance
Once you get to the Windows desktop, the first thing you will want to do is open HWinfo (Sensors only option), Core Temp or Ryzen Master and take a look at what your core and package temperatures are doing. At idle your core temps should be somewhere below 40°C in the majority of cases. Preferably somewhere in the mid to low 30’s. On some newer very high core count models, or if you are using the stock cooler (In which case you shouldn't be overclocking anyhow), then it might not be below the 40°C threshold.
If you are not overclocking and are ONLY testing the thermal compliance of the stock configuration, then don't be TOO concerned by a high idle temperature UNLESS you also have a high load temperature that is outside of spec. This WILL be affected by whatever the ambient temperature is in the room where you are, so if your are in a very warm region and have no air conditioning going you may have an idle temp that is a bit closer to 40. For cooler ambient rooms or regions it will likely show low 30’s-ish. Be aware that unless you have excessively high idle temps, say, above 40°C, then what your actual idle temps are is practically irrelevant. Cooler idle temps are not indicative of much of anything specific.
Very HIGH idle temps however DO indicate that there is likely a problem with an incorrectly installed CPU cooler heatsink, too high of CPU core voltage or some other cooling or voltage related issue. If you are using one of those other utilities I warned about in the beginning of this tutorial, it may also be that the utility is reporting falsely. In that case, go get HWinfo or CoreTemp and check again.
If idle temps seem fine, then leave your monitoring application open and run Prime95 (Either version 26.6 or the latest version with AVX/AVX2 disabled).
Choose the Small FFT option (NOT "Smallest FFT") and allow it to run for fifteen minutes. If you are using the latest version of Prime95 (Version 29.8 or newer) then you NEED to be sure to disable the AVX and AVX2 options in the main options window. When you disable AVX2 the option to disable AVX will become available. If at any point your core or package temperatures exceed 80°C for Intel or AMD Ryzen platforms, then click the “Test” menu at the top of the Prime95 window and select “stop” or “exit”. Do not simply click the "X" in the top right corner as that will NOT stop the stress test, it will only minimize it to the tray.
You MUST click Stop or Exit from the drop down TEST menu at the top left of the window to stop the stress test.
If you have an older AMD system that is pre-Ryzen, then measuring thermals is going to be a little different. If your AMD system IS a Ryzen based system, then testing will be the same as for Intel based systems.
On pre-Ryzen AMD systems they did not make, by any definition, measuring core temps accurate or reliable. On the low end of the scale their thermal sensor readings have long been laughable, sometimes showing temps that are well below what the ambient temperature is, which of course is not possible without some kind of Peltier cooler or active refrigeration. At the other end of the thermal range it’s not much better.
This is because AMD does not actually implement their sensor designs to be determined in the same way that Intel does. AMD uses a method known as distance to Tjmax. Tjmax being, in this case, the temperature at which AMD has determined bad stuff will start happening such as thermal throttling, shut downs and damage.
For this reason when you are testing thermal compliance, or just monitoring for general purposes, you need to be aware of this difference and purposely either use applications designed for use with AMD processors or make some settings changes in other utilities that will allow you to see distance to Tjmax rather than estimated core temps.
There are a couple of ways you can do this. First off, HWinfo generally has the appropriate fields which are labeled as Distance to Tjmax. I feel like the better choice though is either CoreTemp or AMD overdrive for monitoring Distance to Tjmax on AMD platforms. In CoreTemp you will need to go into the Options tab, click on Settings and on the Advanced tab check the box next to the setting for “Show distance to Tjmax in temperature fields” in order to change from the default and likely inaccurate core temperature display.
AMD overdrive shows Distance to Tjmax by default, and I don’t think there is any other way to monitor CPU thermals in that utility anyhow. Either of these is probably a good choice, but it’s also likely worth checking either CoreTemp or AMD overdrive against what you see for Distance to Tjmax in HWinfo and if the readings are pretty close to the same, just use HWinfo as there is a lot of other information available in the sensors display that is not available with these other two.
Regarding the actual Distance to Tjmax sensor readings, what you do NOT want to see is anything closer than 10°C Distance to Tjmax, ESPECIALLY if you are only in the first phase of your overclock configuration and have only made minor changes to the CPU multiplier and voltage at this point. If it drops below ten degrees to Tjmax you are getting very close to your thermal ceiling and need to revisit either your cooling solution or voltage settings.
If you can run the Prime95 version 26.6 or 29.8 (With AVX/AVX2 disabled) Small FFT (NOT "Smallest FFT". ONLY use the "Small FFT" for our purposes.) torture test for 15 minutes without exceeding 80°C for Intel/AMD Ryzen or dropping below 10°C thermal margin (AKA Distance to Tjmax) for AMD, then you are to some degree or other within specification for thermal tolerance.
It's important to note that when stopping or attempting to exit Prime95 that you MUST use the drop down file menu and choose either "Stop" or "Exit". Simply clicking the X in the top right corner like you would for most programs will not stop the test, and will leave it running in the system tray.
If you are very close to the edge however, this may be a warning sign that you don’t have much overclocking headroom since we’ve only barely set our multiplier to what is basically the all core equivalent of the default single core Turbo frequency (Speed). IF that is the case, you will want to either be very careful going forward or stop and think about upgrading your CPU cooler and perhaps looking at whether your case and case fan situation is really sufficient for what you are trying to do.
Once you get to the Windows desktop, the first thing you will want to do is open HWinfo (Sensors only option), Core Temp or Ryzen Master and take a look at what your core and package temperatures are doing. At idle your core temps should be somewhere below 40°C in the majority of cases. Preferably somewhere in the mid to low 30’s. On some newer very high core count models, or if you are using the stock cooler (In which case you shouldn't be overclocking anyhow), then it might not be below the 40°C threshold.
If you are not overclocking and are ONLY testing the thermal compliance of the stock configuration, then don't be TOO concerned by a high idle temperature UNLESS you also have a high load temperature that is outside of spec. This WILL be affected by whatever the ambient temperature is in the room where you are, so if your are in a very warm region and have no air conditioning going you may have an idle temp that is a bit closer to 40. For cooler ambient rooms or regions it will likely show low 30’s-ish. Be aware that unless you have excessively high idle temps, say, above 40°C, then what your actual idle temps are is practically irrelevant. Cooler idle temps are not indicative of much of anything specific.
Very HIGH idle temps however DO indicate that there is likely a problem with an incorrectly installed CPU cooler heatsink, too high of CPU core voltage or some other cooling or voltage related issue. If you are using one of those other utilities I warned about in the beginning of this tutorial, it may also be that the utility is reporting falsely. In that case, go get HWinfo or CoreTemp and check again.
If idle temps seem fine, then leave your monitoring application open and run Prime95 (Either version 26.6 or the latest version with AVX/AVX2 disabled).
Choose the Small FFT option (NOT "Smallest FFT") and allow it to run for fifteen minutes. If you are using the latest version of Prime95 (Version 29.8 or newer) then you NEED to be sure to disable the AVX and AVX2 options in the main options window. When you disable AVX2 the option to disable AVX will become available. If at any point your core or package temperatures exceed 80°C for Intel or AMD Ryzen platforms, then click the “Test” menu at the top of the Prime95 window and select “stop” or “exit”. Do not simply click the "X" in the top right corner as that will NOT stop the stress test, it will only minimize it to the tray.
You MUST click Stop or Exit from the drop down TEST menu at the top left of the window to stop the stress test.
If you have an older AMD system that is pre-Ryzen, then measuring thermals is going to be a little different. If your AMD system IS a Ryzen based system, then testing will be the same as for Intel based systems.
On pre-Ryzen AMD systems they did not make, by any definition, measuring core temps accurate or reliable. On the low end of the scale their thermal sensor readings have long been laughable, sometimes showing temps that are well below what the ambient temperature is, which of course is not possible without some kind of Peltier cooler or active refrigeration. At the other end of the thermal range it’s not much better.
This is because AMD does not actually implement their sensor designs to be determined in the same way that Intel does. AMD uses a method known as distance to Tjmax. Tjmax being, in this case, the temperature at which AMD has determined bad stuff will start happening such as thermal throttling, shut downs and damage.
For this reason when you are testing thermal compliance, or just monitoring for general purposes, you need to be aware of this difference and purposely either use applications designed for use with AMD processors or make some settings changes in other utilities that will allow you to see distance to Tjmax rather than estimated core temps.
There are a couple of ways you can do this. First off, HWinfo generally has the appropriate fields which are labeled as Distance to Tjmax. I feel like the better choice though is either CoreTemp or AMD overdrive for monitoring Distance to Tjmax on AMD platforms. In CoreTemp you will need to go into the Options tab, click on Settings and on the Advanced tab check the box next to the setting for “Show distance to Tjmax in temperature fields” in order to change from the default and likely inaccurate core temperature display.
AMD overdrive shows Distance to Tjmax by default, and I don’t think there is any other way to monitor CPU thermals in that utility anyhow. Either of these is probably a good choice, but it’s also likely worth checking either CoreTemp or AMD overdrive against what you see for Distance to Tjmax in HWinfo and if the readings are pretty close to the same, just use HWinfo as there is a lot of other information available in the sensors display that is not available with these other two.
Regarding the actual Distance to Tjmax sensor readings, what you do NOT want to see is anything closer than 10°C Distance to Tjmax, ESPECIALLY if you are only in the first phase of your overclock configuration and have only made minor changes to the CPU multiplier and voltage at this point. If it drops below ten degrees to Tjmax you are getting very close to your thermal ceiling and need to revisit either your cooling solution or voltage settings.
If you can run the Prime95 version 26.6 or 29.8 (With AVX/AVX2 disabled) Small FFT (NOT "Smallest FFT". ONLY use the "Small FFT" for our purposes.) torture test for 15 minutes without exceeding 80°C for Intel/AMD Ryzen or dropping below 10°C thermal margin (AKA Distance to Tjmax) for AMD, then you are to some degree or other within specification for thermal tolerance.
It's important to note that when stopping or attempting to exit Prime95 that you MUST use the drop down file menu and choose either "Stop" or "Exit". Simply clicking the X in the top right corner like you would for most programs will not stop the test, and will leave it running in the system tray.
If you are very close to the edge however, this may be a warning sign that you don’t have much overclocking headroom since we’ve only barely set our multiplier to what is basically the all core equivalent of the default single core Turbo frequency (Speed). IF that is the case, you will want to either be very careful going forward or stop and think about upgrading your CPU cooler and perhaps looking at whether your case and case fan situation is really sufficient for what you are trying to do.
TRENDING THREADS
-
-
-
-
Discussion What's your favourite video game you've been playing?- Started by amdfangirl
- Replies: 4K
Facebook
Twitter
Instagram