Fiery

As I've mentioned above, we've expanded the number of misc temperature slots from 30 to 99. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta I hope it will work better than the previous builds. Please let me know how it works out on your setup.

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know if it helps

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

AIDA64 doesn't officially support running without an associated user session. If you want to configure AIDA64 the way you launch it, you will need to kill the process from Task Manager and start it as a logged on user.

None of those is normal. Have you tried to restart your computer after upgrading to AIDA64 v5.80? It seems as if the kernel driver of AIDA64 cannot be loaded right now. That can easily cause a sluggish update rate and missing sensor readings. Usually a Windows restart fixes such issues.

1) No, I haven't said anything about a reappearing device. I've said it's because of a reappearing item in the list of sensor items. It may or may not be due to a device communication issue. And since we don't know what causes the issue, whether it's a bug in AIDA64 or due to a limitation that we may be able to fix easily, a warning message or notice in the documentation is not necessary. BTW, potential customers of AIDA64 have 30 days of trial period, plus 30 days no-questions money-back guarantee after their order. That's 60 days total, which is plenty of time to discover whether AIDA64 suits their needs and their hardware configuration. It's plenty of time to discover the limitations (if any of them impacts them). And even so, when someone bumps into a limitation, in most cases we are here to fix AIDA64, by e.g. expanding the number of sensor slots. It's already happened a few times before, and AFAIK noone left this forum with a bad taste in their mouth due to such limitations. 2) There are several limitation in various features of AIDA64, just like there are many limitations in other software or even operating systems as well. In most cases the limitations are set to a certain value that would mean 99.9% of the users wouldn't ever discover the limitation. In other words, a limitation on temperature sensor slots or fan slots (etc) are set quite high already, and 99.9% of the AIDA64 users never notice that there's a ceiling on the number of slots. 3) It's quite hard to discuss this issue when you have 2 separate topics on the same matter. I've already listed the temperature measurement slots that AIDA64 reads in your other topic. Since there are 30 misc temperature slots in AIDA64, with two Aquaero devices it's not that difficult to exhaust that -- otherwise not that tight -- limitation. We will increase the number of misc temperature slots in the next AIDA64 beta, to make sure not only every other user can fit in there, but your complex configuration too. The first 4 fan VRM temperatures use their own temperature slots, so they will not mix with the misc temperature readings. However, when you have more than one device providing fan VRM temperature readout, the last device will overwrite the readings coming from the previous device(s). Yes, it's a limitation in AIDA64, but since before you came along, noone installed more than one Aquaero in the same computer _and_ used AIDA64, this limitation never caused any issues for anyone. This is one example when the per-device sensor slot management would come in handy. 4) AIDA64 supports up to 16 Aquaero devices, in any kind of a mix. You can have 15 Aquaeros and 1 MPS, or 4 Aquaeros, 4 MPSes, 4 AquaStreams, 4 PowerAdjusts -- everything will be handled by AIDA64. But, due to the way AIDA64 pools the sensor readings (instead of managing them per device), certain overwriting of values may occur, and certain other limitations (like 30 misc temperature slots) may cause issues. 5) It's not easy to continue this discussion when your wording becomes that particular, but I'll try. You have no technical insight into how AIDA64 works, so please don't make any quick assumptions, and please don't think I'm lying to you. Why would I lie? AIDA64 doesn't manage sensor readings per device. Period. It has a pre-defined set of sensor slots. Among those slots there are "misc" ones where such values can be squeezed that do not have a dedicated sensor slot defined. For example, CPU OPT fan has a pre-defined slot, but EXT_Sensor1 temperature (of some Asus motherboards) hasn't got an own slot, so it's added to the pool of misc temperature readings. What you can see on the bottom of the Sensor page is such readings that are not covered by the hardware monitoring module of AIDA64. That module doesn't support pressure readings at all, but only temperatures, fan RPMs, fan duty cycle, voltages, currents, powers, liquid levels and flow sensors. But due to user demand, we had to add pressure readings too, but they are only available on the Sensor page, in separate blocks. And since only those devices (Aquastream and MPS) support pressure readings, we've decided to name those readings. It's a very few number of readings, so it's not a huge problem to manage them separately. But, they are still not covered by the hardware monitoring module, so you cannot put them e.g. on the OSD Panel or SensorPanel. And as you can see, only the pressure readings are there, the other readings coming from those devices are not listed per-device, but instead pooled with the other sensor readings coming from other sensor devices. We cannot put a prefix there since the readings are pooled, and the source of readings is not stored (managed) at all. It would be quite an overhead for the sensor module to manage the devices for every sensor slots too, but we may add it as an optional feature that you can activate from e.g. the right-click context menu on the Sensor page. It would still not be a true per-device management though, but more a clarification feature that you can use to better understand the readings -- when there are that many.

That issue will be fixed in the next AIDA64 beta update due in a few days from now.

No, it's still not supported.

Yes, of course it's included. Thank you for the feedback, I'm glad the bug fix worked out

We need to dig down a bit deeper, since the hardware monitoring module of AIDA64 is very long and complex, and involves several sub-modules. It's not easy to tell which one of those sub-modules cause the issue. Try to go to AIDA64 / main menu / View and enable status bar from there. Then right-click on the status bar (at the bottom of the main window of AIDA64) --> HWMon Modules, and enable the modules you can see in the list one by one. Probably it's easier and quicker to locate the culprit if you don't play a game, but use DPC Latency Checker: http://www.softpedia.com/dyn-postdownload.php/bea29454771dccab4156ec33079d5d02/58146715/1cf3a/4/1?tsf=0 (the direct download link from the vendor's site doesn't seem to work right now) Please let me know if you can find the one hwmon module that causes the latency issues on your computer.

Thank you. We'll fix the CPU OPT fan measurement issue in the next AIDA64 beta update. However, the T_Sensor temperature should already be there, named as Temperature #1 or so. If you cannot see it on the Sensor page, then please submit an Embedded Controller Dump as well. Thanks, 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