Fiery

Please try to uninstall it temporarily, and let us know if it makes a difference.

On Asus ROG motherboards, when you've got AI Suite II installed, it's best activating Asus ATKEX sensor support in AIDA64 / main menu / File / Preferences / Stability. It may help in your case If you decide to give it a try, then first please make sure to have the latest AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild2571jfzsxrb3qdzip

One of the drivers (maybe ForceWare) or one of the installed and background running software or services may be sensitive to the heavy stress AIDA64 puts on the system. Do you have AI Suite II installed?

AIDA64 also supports RAID members enumeration, but it doesn't support Adaptec RAID controllers. It may change in the future, but not in the near future I'm afraid Regards, Fiery

AIDA64 reads CPU temperature from the 3rd temperature register of the sensor chip of the X79-UD5 motherboard. What you wrote to me sounds like a BIOS issue, or a collision between AIDA64 and another monitoring software. Try to upgrade the BIOS to the latest one, and temporarily uninstall other monitoring software that you may have installed.

Yes, that's how it works. By having no AIDA64 tray icon and main window hidden, but sensor icons enabled, that would in theory enable you to show and hide the main window by double-clicking on one of the sensor icons. But if you had the main window hidden, right-clicked on any of the sensor icons and choose to hide sensor icons, then you would block yourself out of using AIDA64. Hence it would require a complicated rule if we'd involved sensor icons in that logic.

We'll rename PLX to a generic temperature label on your motherboard, and will also check if it's possible to read VRM temperatures.

Thank you for the feedback. In case the "PLX" temperature reading looks valid (not stuck, not showing anything unreal), then it must be another temperature reading. Although we currently have no information on which temperature would it be.

The mentioned new AIDA64 beta release is available for download at: http://www.aida64.com/downloads/aida64extremebuild2571jfzsxrb3qdzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Thank you for letting us know, I'm glad you managed to make it work.

At this time it looks like it's a driver issue that cannot be fixed from AIDA64, HWiNFO or GPU-Z

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.