Fiery

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

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

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2514g5l8npfkxbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. As for CPU Analog I/O and CPU Digital I/O voltages, they are unfortunately not measured via conventional methods, so we need to do a bit of research about them.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2514g5l8npfkxbzip 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, the bug will be fixed in the next AIDA64 beta release due in a few days.

In AIDA64: MByte = 1024 x 1024 byte, so 1048576 bytes. GByte = 1024 x 1024 x 1024 byte, so 1073741824 bytes. Regards, Fiery

AIDA64 Business Edition doesn't implement benchmarks. AIDA64 Extreme Edition does implement benchmarks, but doesn't support command-line driven automatization.

"Hi-Speed USB Device Plugged into non-HI-Speed USB Hub" It means you've connected a USB 1.x device into a USB 2.0 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. If you believe your issues may be related to having an outdated device (due to it being only USB 1.x), try to ask your internet provider to replace the device with a more modern one. Regards, Fiery

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

Thank you, we'll fix that in the next AIDA64 beta release due next week. Regards, Fiery

If you don't know what should appear in the AIDA64.INI file, then you should better go with the default settings

Please note that unlike 3DMark, Furmark or many other 3D benchmarks or 3D games, AIDA64 uses GPGPU compute tasks (via OpenCL) to put stress on the GPUs and APUs. It means, it has to call OpenCL to first copy a block of memory from system memory into the video memory, then start a program that performs the actual computation, and then when it's finished, it has to copy the memory back from the video memory to the system memory, in order to let it verify the results. And since all those tasks have to go through OpenCL driver, then the video driver (ForceWare in your case), the PCI Express link, and also the GPU itself, there's a lot of latency and bottlenecks involved in the process. It effectively means the GPU may not be driven 100% constantly, but sometimes a downward spike may appear when the OpenCL driver, the PCI Express link or the video driver lags a bit. That's normal, and can only be avoided by directly programming the GPU (which is impossible), or using a 3D scene instead of a GPGPU code. However, the advantage of GPGPU stress test over 3D scenes is that using GPGPU code it's much easier to stress all available GPUs simultaneously. Regards, Fiery

I'm glad you chimed in If it doesn't violate any protocols or NDAs, would you please share the pre-draft register locations and bit fields -- where the DevSleep capability and status can be detected -- with us? Or shall we wait for the first public ACS-4 drafts to become available for download? Thanks, Fiery

As I've explained above, such issues may happen when under heavy load the CPU intermittently provides invalid core temperature readings to AIDA64. Such readings should be ignored. As for GPU, I'm not sure what may cause that, but since the GPU TDP% reading is measured via nVIDIA driver calls, it depends on the driver whether it provides reliable and stable readings.