Fiery

Thank you for the test. The issue will (hopefully) be fixed in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta is available for download. Thank you for your patience

Thank you for the data. The issue will be fixed in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta is available for download. Thank you for your patience

Do you have another monitoring software running in the background? Like ASRock's own A-Tuning Utility perhaps?

Try to make the AIDA64 window as tall as possible, and try to find the item that keeps disappearing and then reappearing again. If you cannot find it, then try to make a report of the Sensor page (using Quick Report from the right-click context menu) multiple times, and compare the Sensor page content in the report. If you can pinpoint the culprit, we can start digging deeper

Is the page super small or the text that you've put on your preview looks too small? If the latter, then you simply need to use a bigger font The LCD preview in AIDA64 Preferences should reflect the actual layout that will appear on the device. It should be accurate, although you may need to imagine it in a bit smaller physical size if eventually display the layout on a small screen phone.

Aquaero 5 and 6 devices actually have a lot more than 8 temperature sensor slots. There are 16 misc temperature sensors, 8 internal and 8 external (Aquabus) of those. Then there're 8 soft sensors, 4 virtual sensors and 16 "other" sensors. AIDA64 will try to measure all those temperatures, but it (AIDA64) doesn't have an insight on how the Aquaero device actually manages those readings. That's why AIDA64 will call those readings "Temperature #n". Since you have two of such complex Aquaero devices, it's quite difficult to sort the readings out, since AIDA64 doesn't (and cannot) indicate which reading comes from which device. In normal situations where the sensor device layout isn't that crazy (sorry, but it's really very non-typical to install 2 full-blown Aquaero devices in the same computer), that limitation isn't a big deal. Normally it's quite easy to figure out what reading comes from where, and you can then alter the sensor labels when you put the readings on a LCD device or SensorPanel or OSD Panel, etc. Right now the only solution is to try and match them against the readings in Aquasuite. AIDA64 doesn't process, interpret or convert the temperature readings, so that 50 Celius is what comes from the Aquaero device. Aquasuite may have an internal logic to filter out non-connected thermal rails, but AIDA64 is a 3rd party software that may not be all that smart about knowing all the internal tricks of such complex sensor devices We do our best to show only those readings that make sense, but when the device provides a 50 Celsius reading, that looks quite sensible, so AIDA64 will show it. Water temperature is a special reading that comes from an AquaStream device, and not from the Aquaero device. Fan VRM temperature slots are named slots, and not just generic slots named like "soft temperature" or "virtual temperature". They're different slots than the regular "Temperature #n" slots of Aquaero devices. The sensor data that Aquaero 5 and 6 returns have the same layout, so both devices support fan VRM temperature slots. It's a whole different issue whether the actual device that you've got is capable of returning proper thermal readings in those slots or not. You need to refer to the spec sheet of your devices to figure out what they are capable of, what fields in the returned sensor data block is undefined for a certain device due to hardware limitations. The sensor data block returned by Aquaero 5 and 6 devices have 14 flow sensor slots defined. Out those 14 slots apparently your device returns 9 readings that look sensible. AIDA64 reports the data as it comes from the Aquaero device. It's the responsibility of the Aquaero firmware to properly populate the flow rate slots with meaningful measurements. From our standpoint, being a 3rd party software, it would be very difficult to sort those readings out. In other words, we cannot decide which readings should be ignored, which ones may be duplicates of other ones, etc. So given the complexity of Aquaero devices, we rather report every sensible readings as they come from the device, and not try to process the data to sort out the unnecessary bits. There are actually 4 liquid level slots supported by Aquaero 5 and 6 And I'm afraid we have no idea why 3 of those show the same value. Aquasuite may have a trick to sort them out, but we don't have specific information on the nature of the trick behind this issue. Same as #10 They're not wrong about that Regards, Fiery

No, it's not because of the length of the sensors list. It is because one of the items in the list keeps disappearing and then reappearing again. The list can only keep the listview state intact when the number of items in the list doesn't change. Once a new item is added or removed, the listview will be refreshed, and the vertical scrollbar will revert back to the top-most position.

If you want to use your own method of loading AIDA64 at system startup, or use any custom scheduling solution to launch AIDA64, then you need to: 1) Disable the option called Load AIDA64 at Windows startup in AIDA64 / main menu / File / General. Please note that by doing so, AIDA64 will remove its own scheduled task from Task Scheduler. So you may want to do step#2 first by renaming the existing task called AIDA64 AutoStart to something else of your choice. 2) You need to use a different name in Task Scheduler for your task. It can be anything else than AIDA64 AutoStart. AIDA64 will not alter any other scheduled task but its own. Regards, Fiery

I'm not sure what you would like to achieve. If you enable the option called Remember main window position and Remember main window size in AIDA64 / main menu / File / Preferences / Layout, then the last position and size of the AIDA64 main window will be restored the next time you open AIDA64. If you however disable the remember position option, then AIDA64 will always open in the center of your main monitor.

The first battery capacity value (labelled as "Capacity (Reported by Android)") comes from the Android profile of your device. It was encoded to the profile by the manufacturer of your device, and may or may not reflect an accurate value. The second value (labelled as "Capacity (From Database)") comes from the built-in AIDA64 hardware database, and should reflect the correct value. Regards, Fiery

Please note that Notification Area and System Tray are the same thing. So if you hide the AIDA64 icon from that area, and then you want to minimize AIDA64 to the hidden icon, it wouldn't work out well You then wouldn't be able to restore AIDA64 in any ways. That's why AIDA64 has a protection against such issues: it will simply not let you lose the main window if you enable both mentioned options in the same time. Regards, Fiery

Yes, it seems to be a popular subject lately I know I've said repeatedly that we're not interested, but we may need to give it a second thought next year -- which is quite close now

Please try this link: http://users.aida64.com/alphacool_lcd_driver_2_1.zip

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. 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, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for the feedback, your panel looks great

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps

Then I'm afraid the issue must be due to a CPU pecularity that is currently unknown to us. So I'm unable to help you

We've seen such anomaly before, but we haven't yet found the root cause of it So right now there's no fix for it. You can however apply a formula (e.g. a multiplier of 10x or 20x or 100x, etc) on the measured values in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction, if you deem it would help to fix them up. Edit: One possible cause could be that you've disabled SVID in the BIOS Setup. If that's the case, then try to enable it again, and check if it helps about the power measurements. Regards, Fiery

The difference between #2 and #3 is basically the protocol that a software has to use to push a bitmap image (a LCD/SensorPanel frame) to the display. With #2 it's trivial, since Windows does everything for you. All you need to do is open a new window and draw something on it. The user can move the window from the main monitor to the secondary monitor. No hassle at all. With #3 however, AIDA64 has to push the bitmap image data to the display, usually via a USB connection, using the protocol the device dictates. That's where things get quite complicated, since most devices have a proprietary protocol that only that device uses. That's why AIDA64 supports over 50 different LCD devices, in most cases with a separate protocol. Also, several external displays (like picture frames) simply do not have a protocol that could be used to pass image data from a Windows PC. They may support copying files over a USB connection, but that involves updating the internal flash memory of the device, which is not a good idea to perform too frequently. As for the tablet idea, yes, you're right, mounting a tablet permanently into your PC case is probably not a good idea. If you want to mount the display into your PC case, then I guess the best solution may be to try to find a relatively small old TFT LCD screen, and hook it up to your DSub or DVI output, and use it as a secondary monitor with AIDA64 SensorPanel. Of course there are some other alternatives, certain dedicated LCD screens that are case mountable, but usually they cost an arm and a leg, despite the fact that they're not that large Like USBD480 from LCDInfo: http://www.lcdinfo.com/products/usbd480-lq043.html USBD480 is fully supported by AIDA64, thanks to the fact that it features a very fast and efficient USB protocol. It's not that large though. I suppose you're looking for something considerably bigger than that...

1) Tough issue. These days what you can get easily is usually too expensive and also too small for your needs. When it comes to large colour LCD screens, we generally recommend getting an old Android tablet or iPad and use RemoteSensor or Odospace, or to simply go for an old TFT LCD monitor that you can hook up to an unused DSub or DVI connector. The monitor solution would enable you to extend your Windows Desktop to that display, and use AIDA64 SensorPanel instead of the LCD module. It enables more flexibility too, since you can move any window to that screen. And no, not any LCD displays would work. Most of those that support bitmap transfer through the USB connection should work. 2) The following special temperature readouts of Maximus VIII Extreme and Formula boards are supported by AIDA64: T_Sensor1 EXT_Sensor1 EXT_Sensor2 EXT_Sensor3 The rest (T_Sensor2 and T_Sensor3) cannot be measured via AIDA64 right now. 3) I'm afraid we're not experienced that much in water cooling setups, so you have to ask that question on a different forum. But, as long as you can connect the flow meter to a fan header, and it reports the flow rate just as a fan would report its RPM measurement, then you can handle the device in AIDA64. The reported value would still be RPM though. You can use the Correction feature of AIDA64 (main menu / File / Preferences / Hardware Monitoring / Correction) to apply an offset or multiplier on the RPM readout. Regards, Fiery

Yes, it should still be there. However, you may need to unblock access to the file by navigating to the installation folder of AIDA64, finding the AIDA64.CHM help file --> right-click context menu --> Properties --> Unblock (checkbox) --> OK.

Thank you for your feedback

Thank you for the feedback

The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta

We've fixed the reported issues in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta