Fiery

Atom N450 supports a maximum of 2 GB system memory, according to Intel's site: http://ark.intel.com/products/42503/Intel-Atom-Processor-N450-512K-Cache-1_66-GHz

You may have that information listed on the Motherboard / Chipset page in AIDA64. If not, then please let me know the notebook model and CPU type. Regards, Fiery

You can try Battery Eater for example

I think that's a bug of the smart logic of the battery itself. The Current Capacity is reported by the battery via a standard Windows API call. Regards, Fiery

Here's the mentioned new AIDA64 Extreme beta release that improves on the Logitech LCD support at Windows bootup: http://www.aida64.com/downloads/aida64extremebuild2914kf2mbs7dcqzip Please let me know how it works on your system.

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2914kf2mbs7dcqzip Let me know if it helps.

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. If possible, please list the fans you have connected when you made the dump, with their corresponding RPM value as well. That way we can have a reference list of readings and we can compare them with the sensor registers output.

Thank you for the feedback

You need to use the left and right arrow buttons to switch between pages.

Try to disable Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability. Also, make sure to have no AI Suite residuals on your system. Even after uninstallation AI Suite leaves behind a few services that are still active and prevents AIDA64 to access sensor devices directly.

AIDA64 only communicates with the Logitech LCD driver through the proprietary Logitech API, so the USB "pollution" must come from the Logitech drivers. Or, in case you can see the same issue without the Logitech LCD support enabled in AIDA64, like when you're just viewing the Computer / Sensor page, then there's a chance one of the AIDA64 sensor modules causes it. In that case try to disable the following features in AIDA64 / main menu / File / Preferences / Stability: HID UPS sensor support Koolance TMS-200 sensor support T-Balancer sensor support Regards, Fiery

Thank you, we'll improve on that in the next AIDA64 beta release due later this week. Regards, Fiery

It's possible, yes. Some Gigabyte motherboards use such offsets for voltages and temperatures, so it's not a very unique feature. Sadly, such quirks are usually not easy to have automatically applied in 3rd party software like AIDA64, so you have to find out the offset and use the Correction feature of AIDA64.

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?