Fiery

AIDA64 has a different way of managing sensor readings. It has a predefined set of sensor item slots where everything needs to fit into. By going with a per-device management, the whole current system would need to be replaced, and over 120,000 lines of code would need to be rewritten. And the advantages of that effort would be very limited: basically it would just be beneficial in very rare cases where multiple complex sensor devices (like Aquaero) is installed. As I've mentioned above, in most cases (over 99%) the current way of managing sensor readings and labelling them is completely fine. As for your comments on whether AIDA64 can really manage two Aquaero devices and one Aquastream device separately, without mixing USB requests and stuff: yes, it can. Even though the list of sensor items are pooled into one long list, and I gotta admit, it's not easy to sort them out with your setup, the readings come from the right device and AIDA64 uses the right USB commands for each device you've got installed.

Can you please export your current LCD settings (from AIDA64 Preferences) and attach it to your forum post, or upload it to somewhere on the web? Thanks, Fiery

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 update is available for download.

When the window color is at its default setting (white) and the window text color is also at its default (black), then AIDA64 will use blue color to indicate URLs that you can click on. However, when you use a custom color scheme, AIDA64 will use the system default hightlight color. On your system that seeems to be configured to light green which is hard to read over your background color setting. Make sure to pick a different, darker highlight color on the Windows system color configuration panel. Regards, Fiery

Sensors aren't necesserily chips. Sometimes they're integrated in a HDD, SSD, CPU or GPU. We believe the current sensor icon is more suitable to represent a generic sensor type than the chip icon would be. Regards, Fiery

Such difference is usually due to the different TJMax temperature value used by AIDA64 and the other software (HWiNFO32). If you believe the values measured by HWiNFO32 is closer to the real values, then you can adjust the TJMax value in AIDA64 / main menu / File / Preferences / Hardware Monitoring. Regards, Fiery

I've just sent you your product key in private message Regards, Fiery

Today FinalWire released a new stable update to the desktop editions of its popular system information software. As a new feature, it now allows users to define global hotkeys with which they can enable or disable the AIDA64 hardware monitoring panels or switch between multiple hardware information pages on external displays, even when AIDA64 is running in the background. The developers have made AIDA64 v5.80 DPI aware so that all elements of its graphical user interface scale properly when the DPI zoom is active in Windows. It supports the latest Windows 10 builds and the most recent hardware components, including the AMD RX 400 series and NVIDIA’s GTX 1050 GPUs. New features & improvements - AVX and FMA accelerated 64-bit benchmarks for AMD A-Series Bristol Ridge APUs - Global hotkeys to switch between LCD pages, start/stop logging, show/hide the SensorPanel - Proper DPI scaling to better support high-resolution LCD and OLED displays - Corsair and Razer RGB LED mousepad support - Microsoft Windows 10 Redstone RS2 Insider Preview support - Improved support for AMD Zen Summit Ridge CPUs - Improved support for Intel Apollo Lake SoCs - Support for Samsung PM851 and SanDisk X400 SSDs - Improved support for Intel NVMe SSDs - CUDA 8.0 support - GPU details for AMD Radeon RX 400 Series - GPU details for nVIDIA GeForce GTX 1050, GeForce GTX 1050 Ti and GeForce GTX 1060 What's new since AIDA64 v5.00 - AVX and FMA accelerated FP32 and FP64 ray tracing benchmarks - Vulkan graphics accelerator diagnostics - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - Microsoft Windows 10 RS1 (Anniversary Update) support - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell, Kaby Lake, Skylake CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APU - Optimized 64-bit benchmarks for AMD Carrizo APU - Optimized 64-bit benchmarks for Intel Braswell and Cherry Trail processors - Preliminary support for AMD Raven Ridge APU - Preliminary support for Intel Apollo Lake, Broxton, Kaby Lake CPUs - Preliminary support for Intel Cannonlake, Skylake-E/EN/EP/EX processors - Advanced SMART disk health monitoring - Corsair K65, Corsair K70, Corsair K95, Corsair Strafe, Logitech G13, Logitech G19, Logitech G19s, Logitech G910, Razer Chroma RGB LED keyboard support - Corsair, Logitech, Razer RGB LED mouse support - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream Ultimate, AquaStream XT, Farbwerk, MPS, NZXT GRID+ V2, PowerAdjust 2, PowerAdjust 3 sensor devices support - Improved Corsair Link sensor support - NZXT Kraken water cooling sensor support - Corsair AXi, Corsair HXi, Corsair RMi, Enermax Digifanless, Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Modding-FAQ, Noteu, Odospace, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - Portrait mode support for AlphaCool and Samsung SPF LCDs - SensorPanel and LCD: right-to-left bars, static label control strings - 0.01 Celsius temperature measurement resolution for select sensor items - System certificates information - Support for LGA-1151 motherboards - Support for USB 3.1 peripherals - Extended ACPI table decoding - Advanced support for Adaptec and Marvell RAID controllers - Autodetect information and SMART drive health monitoring for Intel and Samsung NVMe SSDs - ACPI 6.1, CUDA 7.0, OpenCL 2.1, OpenGL ES 3.2, SMBIOS 3.0, VirtualBox v5.0 support - Corsair Neutron XT, Crucial BX100, Crucial BX200, Crucial MX200, Kingston HyperX Predator, Kingston HyperX Savage, Kingston SSDNow UV300, Kingston SSDNow UV400, Lite-On MU II, OCZ Trion 100, OCZ Vector 180, Plextor M6V, Samsung CM871, Samsung PM871, SanDisk Ultra II, SanDisk Z400s, SK Hynix SC300 SSD support - GPU details for AMD Radeon Rx 300 and R9 Fury Series - GPU details for nVIDIA GeForce 900 Series, GeForce GTX 1070, GeForce GTX 1080, GeForce GTX Titan X, Quadro M3000M, Quadro M5000M, Tesla M60, Tesla P100 [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.80 ] [ Download ]

Thank you for your feedback

There's nothing wrong with your CPU or its current operating temperature. AIDA64 simply uses the wrong thermal rail to measure CPU temperature. The right CPU temperature while you were making the sensor dump was actually 48 Celsius. The issue will be fixed in the next AIDA64 update due in 2 days from now Regards, Fiery

That was only a temporary solution. Sadly it didn't look all that great on anything else but a very bright background (e.g. white or yellow). On regular and dark shades, like the default background color of the OSD Panel and SensorPanel, it looked too dark, so we had to come up with something that looks equally good over light and dark backgrounds. Regards, Fiery

How about Rivatuner (RTSS) ? Regards, Fiery

The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

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