Fiery

The issue will be fixed in the next AIDA64 beta release that will go online later today.

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

No, I'm afraid it's not possible on the Sensor page. But the System Stability Test has a Statistics tab where you can see those values. Also, the Logging feature can create a HTML statistics file where it lists min/max/average values. Regards, Fiery

1) In your first post you said AIDA64 is supposed to open up on the primary monitor, but it opens up on the secondary monitor. In the second post you said it always opens up on the primary monitor. Which one is the case? 2) Do you configure or adjust anything about the multi-monitor setup in ForceWare, or you simply connected both monitors and use default settings? I'm just asking because we've set up a 2-display configuration with a LCD connected to DSub, and another LCD connected to DVI, but weren't able to reproduce the bug of "closing on the primary display but opening on the secondary display". Our hw config was: GT520 + Win7 64-bit SP1. Thanks, Fiery

Thank you for the feedback

Yes, you can do that. AIDA64.INI file is fully portable between version upgrades or downgrades. Regards, Fiery

Previously you wrote Aux temperature doesn't associate with any reference temperatures, that's why we've removed it. Can you please post a screen shot that shows AIDA64 Sensor page and MSI Afterburner temperature readings side-by-side, so we can directly compare the values against each other? As for GPU1 vs GPU2, the difference in GPU ordering may be the explanation. AIDA64 orders GPUs based on their position on the PCI bus. So e.g. the GPU appearing on PCI bus#3 will come first, and the other GPU appearing on PCI bus#5 will be labelled GPU2. Other software may follow a different logic ordering GPUs.

Thanks for the feedback

Thank you for the feedback

Fixed it, please try it now.

We've fixed the lockup under Win8 on Intel Nehalem+ processors. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've fixed the SensorPanel Battery Voltage issue in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...17wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Our test systems are chosen mostly based on multiple criterias. For example, one motherboard has a specific feature or a certain integrated RAID controller that is useful for development or quality assurance purposes. Also, we usually get only one processor for each CPU core family, so e.g. we get one Conroe based Core 2 Duo, one Sandy Bridge based Core i3/i5/i7, one Gulftown based Core i7, etc. I'm not sure how well do our test systems represent real-world systems, but if you find the list useful, then feel free to use it Regards, Fiery

Thank you. We've been able to reproduce the bug, and it will be fixed in the next AIDA64 beta release. I'll post the download link into this topic once the new beta is available

We haven't put such new feature on our roadmap yet. But yes, we probably will develop something for the Metro UI. It will depend on the eventual user reception of Metro. BTW, in the next AIDA64 beta we'll roll out a bug fix for the lockup issue under Win8, so stay tuned

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 4) If it's possible, please also note down all temperature, fan speed, and voltage values you can see in the BIOS Setup, on the PC Health Status or HW Monitor page. Such data would provide an accurate reference for us. Using those dump and data we can correct the sensor readings to make sure they provide accurate values on your motherboard. Thanks, Fiery

1) 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. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 3) If it's possible, please let us know what temperature, fan speed, and voltage values you can see in the BIOS Setup, under the PC Health Status or HW Monitor page. Such data would provide an accurate reference for us. Using those dumps and data we can correct the sensor readings to make sure they provide accurate values on your motherboard. Thanks, Fiery

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 4) If it's possible, please also post a screen shot that shows what temperature, fan speed and voltage values MSI Control Center measures. Alternatively, you can also note down all values you can see in the BIOS Setup, on the PC Health Status or HW Monitor page. Such data would provide an accurate reference for us. Using those dumps and data we can correct the sensor readings to make sure they provide accurate values on your motherboard. Thanks, Fiery

Thanks for the feedback

It's supposed to be there, and more entries too. Please copy-paste the full content of the following pages of AIDA64 into this topic: - Computer / Power Management - Computer / Sensor Also, right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery Dump. Copy-paste the full results into this topic. Please use Beta 1812. Thanks, Fiery

"Aux" temperature can be a lot of things, on your motherboard I think it is a bogus reading that should be ignored. You can verify that theory by comparing AIDA64 sensor readings against MSI's own monitoring software (MSI Control Center). Regards, Fiery

AIDA64 has an Alerting feature that can be used to warn you when an overvoltage, fan stopping or thermal issue occurs. The Logging feature doesn't indicate such issues in the logs. In the logs red process colour means the mentioned process is stopped (closed), while green process colour means the process has started. Regards, Fiery

Core temperatures (measured via Intel DTS core diode sensors) are known to be inaccurate on Core 2-family processors, and the inaccuracy gets worse as your CPU cools down. Under 50 Celsius it gets quite inaccurate. As for the CPU temperature, some Gigabyte motherboards are known to provide unrealistically low temperature readings. Make sure to verify the CPU temperature against Gigabyte EasyTune. If the CPU temperature measured by EasyTune doesn't match AIDA64, then please create an ISA Sensor Dump, and copy-paste the results into this topic. Thanks, Fiery