Overclock.net › Forums › AMD › AMD CPUs › Tcase of the FX line and AMD Non-Disclosure Agreement
New Posts  All Forums:Forum Nav:

Tcase of the FX line and AMD Non-Disclosure Agreement - Page 3

post #21 of 26
Thread Starter 
Quote:
Originally Posted by Undervolter View Post

In HWMonitor you should have 2 temperatures related to the CPU:
- The CPU temp (which is the same as CPU temp in BIOS and it's from the thermal diode i mentioned in post #11, linking to Stilt's post).
- The package temp, which is what HWmonitor calls the "core temp". So if you are at 33C, it means you have 37C thermal margin in Overdrive. The catch, is what i had written in earlier post. Because the tclt is translated into core temp in Celsius through an algorithm that AMD gave, the reading isn't accurate for temps below 40C (it's a limitation of the algorithm). This is why at idle, you can have the core temp (alias "package" in HWmonitor) inferior to your ambient temperature (which is impossible). Once your core temp exceeds 40C, then your reading is accurate. The core temp is usually lower than the CPU temp is pretty much all motherboards. Also, Gigabyte motherboards run quite cool in the CPU area (contrary to 970 models from Asrock and MSI). The core temp tends to become equal to the CPU temp, at least on my GIgabyte, at high clocks (at around 4.5 it's about the same).

So if you have 33C core temp in HWMonitor when you run OCCT, well, the reading is a bit lower than it should, but it's a limitation of the algorithm. The main point is that you have still ample thermal margin up to 70C. When you hit 40C, it becomes accurate. The CPU temp on the other hand, isn't calculated by algorithm, so what you see is what you get always.

So the rule of thumb is: As long as your core temp (or package) and your CPU temp are below 70C, you 're good. Many prefer to leave some safety margin.

I'll study that later, but mine has the same reading for both CPU and Package (HWinfo64). The AMD algorithm seems to be standardized. HWmontor has only Package. AIDA64 has only Cores and Processor also with the same value. The processor sometimes gets 1ºC difference in AIDA, but 99% of the time they show the same value. The cores also have the same values at all times. They could show just one Core value for all of them, because they never vary. Seems to be a very simple reading.
post #22 of 26
Quote:
Originally Posted by Contiusa View Post

I'll study that later, but mine has the same reading for both CPU and Package (HWinfo64). The AMD algorithm seems to be standardized. HWmontor has only Package. AIDA64 has only Cores and Processor also with the same value. The processor sometimes gets 1ºC difference in AIDA, but 99% of the time they show the same value. The cores also have the same values at all times. They could show just one Core value for all of them, because they never vary. Seems to be a very simple reading.

If you want, post 2 screenshots. One from HWMonitor at idle and one after 10 minutes of OCCT or Prime or IBT. Then we will be able to explain which sensor is what.
Main
(16 items)
 
Dedicated Encoder
(15 items)
 
 
CPUMotherboardGraphicsRAM
FX-8320@4Ghz Gigabyte 970 UD3P rev2.1 Gainward GTX 750Ti Corsair XMS3 1600Mhz 16GB (4x4GB) 
Hard DriveHard DriveOptical DriveOptical Drive
Crucial BX100 250GB Western Digital Green 2TB LiteOn Blu-Ray Burner IHBS 112-2 LG BH16NS55 Blu-Ray Burner 
CoolingOSMonitorKeyboard
Scythe Katana 3 Windows 7 Pro 64bit ASUS 22" VS228HR Microsoft Wired Keyboard 600 
PowerCaseMouseAudio
EVGA 430W Sharkoon VG4-V Logitech M90 Onboard 
CPUMotherboardGraphicsRAM
FX-8300 Asrock 970 Extreme3 HIS 6570 Silence Corsair XMS3 1600Mhz 8GB (2x4GB) CAS9 
Hard DriveHard DriveOptical DriveCooling
Plextor M6S 128GB Toshiba 2TB SATAIII LiteOn Blu Ray burner IHBS 112-2 Xigmatek Balder 
OSMonitorKeyboardPower
Windows 7 Pro 64bit Samsung S22B350H Microsoft Wired 600 Corsair VS350 
CaseMouseAudio
Lepa LPC 306 Logitech M90 Onboard 
  hide details  
Reply
Main
(16 items)
 
Dedicated Encoder
(15 items)
 
 
CPUMotherboardGraphicsRAM
FX-8320@4Ghz Gigabyte 970 UD3P rev2.1 Gainward GTX 750Ti Corsair XMS3 1600Mhz 16GB (4x4GB) 
Hard DriveHard DriveOptical DriveOptical Drive
Crucial BX100 250GB Western Digital Green 2TB LiteOn Blu-Ray Burner IHBS 112-2 LG BH16NS55 Blu-Ray Burner 
CoolingOSMonitorKeyboard
Scythe Katana 3 Windows 7 Pro 64bit ASUS 22" VS228HR Microsoft Wired Keyboard 600 
PowerCaseMouseAudio
EVGA 430W Sharkoon VG4-V Logitech M90 Onboard 
CPUMotherboardGraphicsRAM
FX-8300 Asrock 970 Extreme3 HIS 6570 Silence Corsair XMS3 1600Mhz 8GB (2x4GB) CAS9 
Hard DriveHard DriveOptical DriveCooling
Plextor M6S 128GB Toshiba 2TB SATAIII LiteOn Blu Ray burner IHBS 112-2 Xigmatek Balder 
OSMonitorKeyboardPower
Windows 7 Pro 64bit Samsung S22B350H Microsoft Wired 600 Corsair VS350 
CaseMouseAudio
Lepa LPC 306 Logitech M90 Onboard 
  hide details  
Reply
post #23 of 26
Quote:
Originally Posted by Undervolter View Post

If you want, post 2 screenshots. One from HWMonitor at idle and one after 10 minutes of OCCT or Prime or IBT. Then we will be able to explain which sensor is what.

+ Rep for all your efforts. Good job thumb.gif
Ryzen Build
(20 items)
 
 
Bruce
(14 items)
 
CPUMotherboardGraphicsRAM
R7 1800x Crosshair VI Hero Diamond 7970 GSkill FlareX F4-3200C14D-16GFX  
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO NVMe Samsung 840 SSD Corsair GT SSD WD 2TB Black 
Hard DriveCoolingCoolingCooling
WD 4TB Red EK-FB Asus C6H Monoblock XSPC GPU Razor WB XSPC RX 360 
CoolingCoolingCoolingCooling
XSPC RS 360 XSPC EX140 D5 Vario Gentle Typhoon AP-15 1850 rpm 
OSMonitorPowerCase
Win 10 Pro Asus VE248H x2 EVGA 850 G2 Xigmatek Elysium 
  hide details  
Reply
Ryzen Build
(20 items)
 
 
Bruce
(14 items)
 
CPUMotherboardGraphicsRAM
R7 1800x Crosshair VI Hero Diamond 7970 GSkill FlareX F4-3200C14D-16GFX  
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO NVMe Samsung 840 SSD Corsair GT SSD WD 2TB Black 
Hard DriveCoolingCoolingCooling
WD 4TB Red EK-FB Asus C6H Monoblock XSPC GPU Razor WB XSPC RX 360 
CoolingCoolingCoolingCooling
XSPC RS 360 XSPC EX140 D5 Vario Gentle Typhoon AP-15 1850 rpm 
OSMonitorPowerCase
Win 10 Pro Asus VE248H x2 EVGA 850 G2 Xigmatek Elysium 
  hide details  
Reply
post #24 of 26
Thread Starter 
Quote:
Originally Posted by Undervolter View Post

If you want, post 2 screenshots. One from HWMonitor at idle and one after 10 minutes of OCCT or Prime or IBT. Then we will be able to explain which sensor is what.

I rather took two photos, because then I could frame two thermometers in the scene. The image is a bit fuzzy, but then you can have an idea of room temperature. The one with humidity values has a good precision.

EDIT: the forum engine uploads smaller images. You could download these ones from MediaFire so that you can see better.

The motherboard value for tCTLMax with AIDA64 is 80ºC.

ovcrs_01 is at idle. This one in particular is at 11ºC, but all cores varies from 18-16-24-15ºC at the same time, but seldom goes above room temperature. I would say the average is 16-18ºC. Like I said before, all cores shows the same temperature all the time. It could show the value of one core and it would make no difference.



ovcrs_02 is after 10min of OCCT Linpack (produces more heat than OCCT CPU). It reached 33ºC. At one point it reached 34ºC, but then got back to 33ºC and was stable the whole time, more or less not changing from 33ºC in the last 5 minutes of the test. The CPU sensor has a 1ºC difference from the Cores with AIDA64 (trial version), but 99% of the time they have the same value, like I said before.



This is not particular to me in special. I know several other people with the same below room temperatures readings and unrealistic temperatures at stress test.
Edited by Contiusa - 6/4/16 at 10:14am
post #25 of 26
I am not very familiar with AIDA and don't know how well it supports your model. In HWMonitor the readings are quite clear.

TMPIN0 = motherboard
TMPIN1 = CPU temp (the one you see in BIOS)
TMPIN2 = core temp

The CPU temp you get is low, but depends on cooling and airflow too. 42C socket temp at 1.26v is not impossible if you have good cooling. I also see you have a max temp of 50C. What is concerning is that in OCCT it shows your CPU at 3Ghz. It should be 3.5Ghz. But it could be the minithrottling that AMD motherboards do when at high loads. Also your max wattage in HWMonitor shows as 59C, which can't be. So i suspect that your motherboard model isn't supported too well...

Your voltage lines also seem all too low, but again, this could be software problem. If you get the expected performance in benchmarks, there is nothing to worry.

If you want to get rid of the minithrottling (3.5-3-3.5), go to BIOS and disable APM and turbo. Your CPU temp will likely increase a bit during stress tests too. But i would suggest you simply overclock to 4Ghz at this point and be done with the turbo once and for all.
Edited by Undervolter - 6/4/16 at 10:57am
Main
(16 items)
 
Dedicated Encoder
(15 items)
 
 
CPUMotherboardGraphicsRAM
FX-8320@4Ghz Gigabyte 970 UD3P rev2.1 Gainward GTX 750Ti Corsair XMS3 1600Mhz 16GB (4x4GB) 
Hard DriveHard DriveOptical DriveOptical Drive
Crucial BX100 250GB Western Digital Green 2TB LiteOn Blu-Ray Burner IHBS 112-2 LG BH16NS55 Blu-Ray Burner 
CoolingOSMonitorKeyboard
Scythe Katana 3 Windows 7 Pro 64bit ASUS 22" VS228HR Microsoft Wired Keyboard 600 
PowerCaseMouseAudio
EVGA 430W Sharkoon VG4-V Logitech M90 Onboard 
CPUMotherboardGraphicsRAM
FX-8300 Asrock 970 Extreme3 HIS 6570 Silence Corsair XMS3 1600Mhz 8GB (2x4GB) CAS9 
Hard DriveHard DriveOptical DriveCooling
Plextor M6S 128GB Toshiba 2TB SATAIII LiteOn Blu Ray burner IHBS 112-2 Xigmatek Balder 
OSMonitorKeyboardPower
Windows 7 Pro 64bit Samsung S22B350H Microsoft Wired 600 Corsair VS350 
CaseMouseAudio
Lepa LPC 306 Logitech M90 Onboard 
  hide details  
Reply
Main
(16 items)
 
Dedicated Encoder
(15 items)
 
 
CPUMotherboardGraphicsRAM
FX-8320@4Ghz Gigabyte 970 UD3P rev2.1 Gainward GTX 750Ti Corsair XMS3 1600Mhz 16GB (4x4GB) 
Hard DriveHard DriveOptical DriveOptical Drive
Crucial BX100 250GB Western Digital Green 2TB LiteOn Blu-Ray Burner IHBS 112-2 LG BH16NS55 Blu-Ray Burner 
CoolingOSMonitorKeyboard
Scythe Katana 3 Windows 7 Pro 64bit ASUS 22" VS228HR Microsoft Wired Keyboard 600 
PowerCaseMouseAudio
EVGA 430W Sharkoon VG4-V Logitech M90 Onboard 
CPUMotherboardGraphicsRAM
FX-8300 Asrock 970 Extreme3 HIS 6570 Silence Corsair XMS3 1600Mhz 8GB (2x4GB) CAS9 
Hard DriveHard DriveOptical DriveCooling
Plextor M6S 128GB Toshiba 2TB SATAIII LiteOn Blu Ray burner IHBS 112-2 Xigmatek Balder 
OSMonitorKeyboardPower
Windows 7 Pro 64bit Samsung S22B350H Microsoft Wired 600 Corsair VS350 
CaseMouseAudio
Lepa LPC 306 Logitech M90 Onboard 
  hide details  
Reply
post #26 of 26
Thread Starter 
Quote:
Originally Posted by Undervolter View Post

I am not very familiar with AIDA and don't know how well it supports your model. In HWMonitor the readings are quite clear.

TMPIN0 = motherboard
TMPIN1 = CPU temp (the one you see in BIOS)
TMPIN2 = core temp

The CPU temp you get is low, but depends on cooling and airflow too. 42C socket temp at 1.26v is not impossible if you have good cooling. I also see you have a max temp of 50C. What is concerning is that in OCCT it shows your CPU at 3Ghz. It should be 3.5Ghz. But it could be the minithrottling that AMD motherboards do when at high loads. Also your max wattage in HWMonitor shows as 59C, which can't be. So i suspect that your motherboard model isn't supported too well...

Your voltage lines also seem all too low, but again, this could be software problem. If you get the expected performance in benchmarks, there is nothing to worry.

If you want to get rid of the minithrottling (3.5-3-3.5), go to BIOS and disable APM and turbo. Your CPU temp will likely increase a bit during stress tests too. But i would suggest you simply overclock to 4Ghz at this point and be done with the turbo once and for all.

I checked my BIOS and the clock was 3.5Ghz. I am running the rig at optimized defaults. I ran OCCT again and it varies the clock from 3 to above 3.8Ghz. I might have taken the photo when it was low. I won't tweak it further because this is my backup / family rig and it is better to leave at stock settings. The intention was never to run extensive tests anyway, I will probably never OC it.

The TMPINs values I would need to confirm with Gigabyte because the sensors position varies from motherboard as all I know, is it not? I am not used to TMPIN readings but from what I see it is not the same for everyone.

I would expect to see CPU values at the CPU, Package and Core readings, even to don't read the wrong values. And every person would need to check with their manufactor which TMPIN is the CPU / Core so we can compare values.

But thanks a lot for your time. I will try later on to find out about CPU and Core readings in these software and why they are off and how can I / and people who own FXs read them properly.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD CPUs
Overclock.net › Forums › AMD › AMD CPUs › Tcase of the FX line and AMD Non-Disclosure Agreement