Fiery

We do have plans about a GPGPU benchmark based on OpenCL. However, our efforts on the benchmarks development are slowed down and somehow blocked as well by the improper quality of OpenCL compilers. Therefore, we have to delay the release of the existing benchmarks until the compilers get more mature. Not mentioning names, but 2 out of the 3 major GPU manufacturers have really poor OpenCL compilers, not being able to properly compile our benchmark code. We've notified both companies in question, so they know about the issues, and they promised things will slowly improve in the upcoming months. So we expect to roll out our OpenCL GPGPU benchmarks before the end of the year. Regards, Fiery

In that case then I guess it would be better if you could create a TXT report of the Devices / USB Devices page of AIDA64, and copy-paste into this topic. We'll then find the ID in there I understand that the issue may not be directly in connection with the RAID member enumeration (due to the fact that you mentioned about stick behavior), but it may still be useful to exclude the stick from the RAID member enumeration. Maybe it helps, maybe not, but sticks shouldn't be scanned anyway for RAID members

Thank you

Currently it's not possible to adjust those.

My only guess would be that the RAID and external drives scanning module of AIDA64 makes the stick's firmware go crazy for some reason. The solution would be to exclude the drive from the scanning. In order for us to add your drive to the exclusion list, we need to have its USB hardware ID. Please go to the Device Manager, find the drive in the list, right-click on it --> Properties --> Details --> Parent. The USB hardware ID should be in the format of "USB\VEN_xxxx&PID_yyyy". If you could send us the ID, we can add it to the exclusion list, and send you a new AIDA64 beta to try it on your system. Thanks, Fiery

Thank you. We'll implement sensor tweakings for your motherboard in the next AIDA64 beta release due in a few days. I'll post a message into this topic once the new AIDA64 beta is available for download.

"CPU Package" is one of the temperatures that Intel processors measure using their integrated on-die temperature diode. Only Intel knows what exactly does it measure and how. Regards, Fiery

Please refer to the following forum topic: http://forums.aida64.com/topic/1326-new-cache-and-memory-benchmarks-in-aida64-v300/ Regards, Fiery

Thank you for the feedback! It looks cooool

I'm afraid due to the way AIDA64 detects, manages and orders physical drives, it's not possible to revamp the HDD slots in a way that would be suitable for your special case Regards, Fiery

I understand you need AI Suite II for your system. What I think would worth trying is temporarily removing AI Suite II, restart the computer, then checking whether it makes a difference in the way AIDA64 blocks your system's shutdown process. Whatever the outcome is, you can then install AI Suite II back again. An alternative solution may be activating the option Asus ATKEX sensor support (Asus ROG) in AIDA64 / main menu / File / Preferences / Stability, and restarting AIDA64 to apply the changes. However, that solution may or may not be effective. It worth a try though.

We've fixed that bug in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2566j5wh1ysmcqzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2566j5wh1ysmcqzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't help, then 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. Also 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

I'm glad you managed to make it work. Please do let us know if you have any further questions or run into any other issues.

The main temperature is the GPU Diode, which is measured by the GPU itself, using its on-die temperature sensing logic. GPU VRM1 and GPU VRM2 are the two rails of the onboard power regulator chip (e.g. CHL8328). Catalyst Control Center should display the same temperature that AIDA64 shows as GPU Diode.

That shouldn't make any difference. The self-installing EXE package contains the very same files as the ZIP (portable) package.

Thank you, we've added Oland and Kalindi from the 2nd source. I wouldn't consider the 1st one 100% reliable, especially since the Kaveri codenames do not match

Thank you for the list. In order to verify the list, could you please provide the source you got it from? I'm just asking, because I'm not entirely sure about the accuracy of your list. For example, the APUs of Kaveri should rather be codenamed Spectre and Spooky. Regards, Fiery

Then please copy-paste the full content of the following pages of AIDA64 into this topic, so we can check out what's wrong. - Display / Monitor - Display / Desktop - Display / Multi-Monitor Thanks, Fiery

AIDA64 reports the current desktop resolution setting, which may or may not match the native resolution of the display. You can adjust the desktop resolution by right-clicking on the Windows desktop --> Screen Resolution. Regards, Fiery

We'll add your storage device to the filter list to make sure AIDA64 can get through the SMART scanning. But in order to do that, we need to have the USB device ID for your device. In the Device Properties window please select "Parent" as Property, and send us a new screen shot. It should show the USB device ID in a format of e.g. "USB\VID_xxxx&PID_yyyy". Thanks, Fiery

First, please try to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2559vf5d6rhmlkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't solve the issue, then try to completely uninstall Asus AI Suite II. If that doesn't help, then please let us know, and we'll investigate the issue further. In most cases however, it's the improper synchronization (or better said, the complete lack of synchronization) of AI Suite II that causes such issues

We've tried it on a Win7 64-bit SP1 configuration, and it worked flawlessly for us. Are you sure your Windows user have permissions to write to C:\ folder? Try to change C:\ to a folder where you definitely have write permissions. If it doesn't help, then AIDA64 may crash at one of the report pages, so try to limit the report profile to e.g. Audit-related pages, using the following command-line: aida64 /R C:\Report.html /HTML /SHOWPCANCEL /AUDIT Regards, Fiery

Looks quite cool, good job

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2559vf5d6rhmlkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Please note that when the GT Cores are not utilized, their power measurement indicates 0 (zero) Watts, and then AIDA64 may hide the value from the Sensor page. Regards, Fiery