Fiery

It looks absolutely normal. That list shows the installed video adapters, as they're managed by Windows. Windows installs one video adapter for every display outputs, so if you have a dual-output (e.g. DVI + HDMI) video card, then you will have 2 adapters listed there. Regards, Fiery

Thank you. It seems your motherboard has a few tricks up its sleeves The CPU Vcore seems to be influenced by the onboard CHL8326 VRM controller. 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. 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. Thanks, Fiery

I'm sorry to hear about your issues and see that you're getting frustrated Please try to give it a bit more tries, it really should work. If there's no AIDA64.INI file in the AIDA64 installation folder, then a default layout of AIDA64.INI file is created when you perform step #3. If the file isn't created, then AIDA64 may not have the necessary rights to write a file in your AIDA64 installation folder. Make sure to have administrator privileges, you need that to use AIDA64 low-level hardware features like sensors monitoring. Also, you can try moving AIDA64 files to C:\AIDA64 folder, it could make it easier to handle file permissions.

Please post a screen shot that shows AIDA64 Vcore reading against ASRock Formula Drive. It should be the definitive reference tool for sensor readings.

Thank you for posting this, it looks like a very useful tool

Thank you, the bug will be fixed in the next AIDA64 beta release.

Thank you, the bug will be fixed in the next AIDA64 beta release.

Thank you for the info. We'll add both formats for the PCI-E temperature readings to make sure AIDA64 can handle both old and new BIOSes.

In other Sabertooth Z87 logs the PCI-E #1 and PCI-E #2 temperatures are listed as "PCIE-1" and "PCIE-2". Are you sure you haven't renamed those? Or maybe between two BIOS updates Asus changed those labels? BTW, when it comes to sensor-related issues, AI Suite II = AI Suite III

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2522cfs6y7mpqjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't help, then please send us your SensorPanel configuration file.

Please note that Vcore measurement is done by the onboard sensor chip, so in case you find the measured values slightly inaccurate, it could well be because of the voltage level measurement inaccuracy of the sensor chip BTW, what motherboard do you have?

Thank you. We've fixed the Chassis Fan #4 reading. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2522cfs6y7mpqjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. As for the temperatures, on your system AIDA64 gets confused, because you've got Asus AI Suite II installed, and -- I suppose -- you've renamed the temperature labels in it. When AI Suite II is installed, AIDA64 doesn't use its low-level EC sensor functions, and relies on AI Suite II calls to gather sensor information. And that only works properly as long as you use the default labels. You can revert back to the default labels, or uninstall AI Suite II to make all temperatures appear properly in AIDA64.

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

Do you mean the local IP address of the computer, or the external IP address? Regards, Fiery

1) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery Dump. Copy-paste the full results into this topic. 2) Then go to the Computer / Sensor page of AIDA64, and copy-paste the full page into this topic, using either the right-click menu on the Sensor page, or post a screen shot of the page. Make sure to have the battery charging (so connected to A/C power, and the battery being not fully charged) when you make those tests. 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) Finally, right-click on the bottom status bar of AIDA64 main window --> System Debug --> Asus SPD Dump. Copy-paste the full results into this topic. Before running the 3rd test, please make sure to save your documents and close any applications you may have open, because there's a slim chance that it might cause a system lockup or BSoD. Thanks, Fiery

That's because even when AI Suite II is installed, AIDA64 can still read the sensor values that are measured by the onboard Nuvoton sensor chip, but not the ones measured by the Embedded Controller. When AIDA64 (or any other software for that matter) reads Embedded Controller registers while AI Suite II is also installed, a collision may occur that could cause system lockup or BSoD. We -- and a few AIDA64 users as well -- have already contacted Asus and asked them to fix AI Suite II to make it synchronized with other monitoring software (like AIDA64, HWMonitor, HWiNFO, SpeedFan, SIV, etc), but they refuse to cooperate with anybody Hence we had to implement the workaround to go through AI Suite II driver calls to get sensor readings -- but as you can see, it only works when the sensor labels aren't renamed.

We've checked the Multi-Media Commands - 6 (MMC-6) specifications, but it seems M-Disc support cannot be detected using MMC or any other methods. So what we've done is extended the optical drives database to cover M-Disc support as well. We've added the drives listed on mdisc.com, and also a few other LG models. The improved optical drives database will be rolled out in the next AIDA64 beta release due in a few days. Regards, 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 --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

1) On your system AIDA64 gets confused, because you've got Asus AI Suite II installed, and -- I suppose -- you've renamed the fan labels in it. When AI Suite II is installed, AIDA64 doesn't use its low-level EC sensor functions, and relies on AI Suite II calls to gather sensor information. And that only works properly as long as you use the default labels. You can revert back to the default labels, or uninstall AI Suite II to make the fans appear properly in AIDA64. 2) Minimum, maximum and average sensor readings are available in the System Stability Test (main menu / AIDA64 / Tools / System Stability Test). You can use the Clear button there to reset the values. Regards, Fiery

That's bad news, but thank you for letting us know about their decision.

Thank you for the feedback. As I wrote above... "But please note that the core temperatures are measured via the on-die temperature diode of your processor. And most FM1, FM2 and AM3+ socket based AMD processors feature a hardware issue in their temperature diodes that yields to very low temperature readouts at idle -- usually way below ambient (room) temperature. The measured core temperatures only make sense when the CPU is under load" ... core temperatures are independent from motherboard sensor calibration, and the issue you experience cannot be fixed from software, since it's a hardware issue.

You're right, I'm sorry, I've mixed it up The correct statement would be: "Hi-Speed USB Device Plugged into non-HI-Speed USB Hub" It means you've connected a USB 2.0 device into a USB 1.x port. That however alone wouldn't mean the device doesn't function properly, since USB 2.x and USB 1.x devices and ports can be mixed in any combinations.

Thank you for the feedback

Thank you for the feedback