Fiery

Please try to apply an offset of -17 Celsius on the CPU temperature in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

No, and it's not necessary. The sensor dumps are there because AIDA64 supports over 400 different sensor devices, via a dozen of access methods. While memory status detection is done in a single way, without any quirks or different code paths.

Thank you. The only idea we've left with is that maybe the BIOS Setup uses an offset on the temperature reading to compensate a weak temperature diode. But the only way to verify that theory would be for you to install Gigabyte EasyTune application (that comes with your motherboard), and check temperatures both at idle and under heavy load, while having the AIDA64 Sensor page and EasyTune temperature monitoring page open side-by-side. If you could do that, then please let us know about your findings.

I meant do you have the External IP Address item enabled (used) on your LCD? Meanwhile, we've done a few test runs using Bitdefender 2014 on various systems of ours, but haven't been able to reproduce the issue so far

Please upgrade to the latest stable or beta version of AIDA64 Business v4.30. We've done a few tweakings to the Windows Devices enumeration module that may also fix the issues you're experiencing.

The values are reported by the standard Windows API call GlobalMemoryStatusEx. You may debate those values or question their integrity, but those are the values Windows reports to other software. Regards, Fiery

We've checked, and it seems MSI Command Center reports the CPU core temperature as CPU temperature. So you can simply ignore the "CPU" temperature in AIDA64, and use the CPU Package or one of the core temperatures when stressing your system.

Thank you for the data. I agree with your observation, however, we've checked, and everything seems to be alright with how AIDA64 handles your sensor chip. Please check both Motherboard and CPU temperatures before restarting your PC, then go straight to the BIOS Setup, and check those temperatures there. Let me know if there's any match between those. Please also let me know how many temperature readings you can see in the BIOS Setup. Maybe your motherboard only measures a single temperature, but it's labelled "CPU" in the BIOS Setup and "Motherboard" in AIDA64?

AIDA64 v4.30 follows the sensor registers layout specification provided by MSI for their LGA1150 boards. In case it doesn't match MSI's own software, then either their software works incorrectly, or they failed to provide accurate information with us BTW, does the CPU temperature seen in MSI's software happen to match any of the CPU-related temperature readings you can see on the Sensor page in AIDA64? Like CPU Package, or any of the CPU cores?

What version of AIDA64 are you using, and which MSI motherboard do you have? Thanks, Fiery

Ah, yes, my bad, it's an SMBus based sensor Then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results here. Thanks, Fiery

Thank you, but I'm afraid that dump didn't include any information for your onboard sensor chip. Are you sure everything was okay with AIDA64 when you made the dump? Or maybe you've stripped some parts of the dump output?

We'll remove the GPU TDP percentage decimal digits in the next AIDA64 beta release due next week. Regards, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

Engineering Sample is not meant to be localized. Regards, Fiery

The latest AIDA64 update introduces a multi-threaded OpenCL GPGPU Hash benchmark to measure SHA-1 hashing performance of modern graphics processors and APUs. It also implements support for Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1, and supports the latest graphics and GPGPU computing technologies. New features & improvements Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1 support OpenCL GPGPU SHA-1 hash benchmark CUDA 6.0 support Socket AM1 motherboards support Improved support for Intel “Broadwell” CPU Preliminary support for AMD “Carrizo” and “Toronto” APUs Preliminary support for Intel “Skylake”, “Cherry Trail”, “Denverton” CPUs Crucial M550 and Intel 730 SSD support GPU details for AMD Radeon R7 265 GPU details for nVIDIA GeForce GTX 745, GeForce 800 Series What's new since AIDA64 v4.00 OpenCL GPGPU Benchmark Suite AMD Mantle graphics accelerator diagnostics Multi-threaded memory stress test with SSE, SSE2, AVX, AVX2, FMA, BMI and BMI2 acceleration Optimized 64-bit benchmarks for AMD “Kaveri”, “Bald Eagle”, “Mullins”, “Beema” APUs Optimized 64-bit benchmarks for Intel Atom C2000 “Avoton” and “Rangeley” SoC Optimized 64-bit benchmarks for Intel “Bay Trail” desktop, mobile and tablet SoC Full support for the upcoming Intel “Haswell Refresh” platform with Intel “Wildcat Point” PCH Razer SwitchBlade LCD support Preliminary support for Intel Quark X1000 “Clanton” SoC Improved support for OpenCL 2.0 Support for VirtualBox v4.3 and VMware Workstation v10 OCZ Vector 150, OCZ Vertex 460, Samsung XP941 SSD support GPU details for AMD Radeon R5, R7, R9 Series GPU details for nVIDIA GeForce 700 Series [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v4.30 ] [ Download ]

1) The lack of BCLK and SPD information is because AIDA64 is unable to use its kernel driver on your system. It's either because AIDA64 is not properly installed on your system, or because your Windows user has no administrator privileges. 2) The diode temperatures well under ambient (room) temperature is a common issue of modern AMD processors. AMD says the diode temperatures in such cases are only meaningful when the CPU is under load. At idle you should simply ignore the diode temperature readings. Regards, Fiery

AFAIK Mantle currently has no interface to measure FPS or draw an image layer via hooks (what RTSS does). AMD may implement those later this year, but I suppose such features aren't their top priority right now.

The difference is that AIDA64 v2.80 didn't support AMD Mullins/Beema APUs at all. It also didn't support the SMBus protocol of the integrated FCH of those processors, so SMBus readouts couldn't cause a lockup there

I'm afraid only MSI can tell you the truth and specifics about the Aux temperature reading. All I can tell is that it can be a bogus reading, and invalid reading, or a meaningful reading. If the latter, then it can be for the CPU, iGPU or some motherboard component. Try to ask MSI Support, maybe they will be able to provide you with the information you're looking for.

Currently AIDA64 can only monitor the video memory usage of the primary (first) nVIDIA video adapter. We'll make sure to improve on that soon Regards, Fiery

Please refer to question #18 at: http://www.aida64.com/support/knowledge-base In case the two CPU core temperatures remain normal while you're gaming, then you can simply ignore the Aux value, and focus on the Motherboard, CPU and CPU core temperatures only. Regards, Fiery

Thank you for your help. I've just sent you a private message about this.

Thank you for the info. Then maybe some other SMBus addresses cause the issue, but it's not easy to debug that remotely. Would it be okay with you if we made a special debug build of AIDA64 that would let us find out exactly at which SMBus address does the Discovery board crash?

I'm not sure how could replacing the PSU make the onboard sensor chip to report incorrect values. Quite frankly, I've never heard of such issue. The sensor chip used on your motherboard is Nuvoton NCT6776F. The base voltage (voltage resolution) of the sensor chip is 0.008V, but AFAIK that has nothing to do with the temperature measurement module of the sensor chip.