Fiery

Thank you, we've added that info bit to the AIDA64 SSD database.

You need to right-click on the incorrect temperature units on the SensorPanel --> Modify, and alter the Unit for each such item.

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> Battery 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. As for the SensorPanel issue, that could happen when you upgrade from an older AIDA64 version to AIDA64 v5.80. In v5.80 we've enabled DPI scaling, and that includes the SensorPanel too. Text, bars and graphs are automatically scaled, so they don't need any adjustment because of this change. However, gauges and images are not scaled up, so you may need to change them or update them to make sure the SensorPanel layout looks great when it's scaled with DPI.

Thank you for the feedback

UV400 cache size is already reported for the 480GB and 960GB variants on the Storage / ATA page (you need the latest version of AIDA64). Kingston didn't specify the cache size for the 120GB and 240GB variants, so that's why AIDA64 doesn't report it for those SKUs. If you however have got reliable information on the cache sizes for those parts, we would be happy to add it to the AIDA64 SSD database. Regards, Fiery

You can switch the temperature measurement unit in AIDA64 / main menu / File / Preferences / Hardware Monitoring. However, if you already use a fixed label for temperature units (e.g. "C") on your SensorPanel, then you will need to change that to "F" manually.

Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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. Thanks, Fiery

We usually don't implement such temperature readings that neither the BIOS Setup or the manufacturer's own software measure and display. Regards, Fiery

We haven't changed the defaults. The default font has always been Tahoma for the LCD module and SensorPanel. Try to set the fonts to Lucida Sans, it looks quite good at size 6.

Thank you for the feedback

The only thing that might cause that is the Dell SMI sensor support, that may interfere with other, non-sensor related SMI calls used by the BIOS. You can disable Dell SMI sensor support in AIDA64 / main menu / File / Preferences / Stability. Let me know if it makes a difference. Thanks, Fiery

Thank you. After upgrading to the latest AIDA64 version of 5.80, did you change anything about your LCD configuration in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items? Did you change anything else about your Windows setup that may have removed the original font used before? I'm pretty sure it wasn't Tahoma before, since that font doesn't support font size 6. Do you happen to have a previous backup of your AIDA64 settings that may reveal the font used before? BTW, the update wasn't supposed to change any of your existing settings, including your LCD layout. However, in case the font previously configured was removed from your Windows installation (due to e.g. upgrading from Win7 to WIn10), AIDA64 may have reverted back to the default font of Tahoma. And if you change your LCD layout settings after that automatic font change, then AIDA64 would save Tahoma as the font into your LCD layout, effectively removing the name of the font that you used previously

Thank you for checking it out. Do you experience the same stuttering issue (or latency spikes in DPC Latency Checker) when you disable G15/G19 LCD support and you keep AIDA64 opened while its Computer / Sensor page is showing?

Thank you for the feedback!

Thank you for the feedback

Thank you for the feedback

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 BTW, when you disable the CPU Diode module, AIDA64 will still use ACPI and motherboard sensor to try and measure CPU temperature.

The above mentioned AIDA64 beta update is available for download 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 how it works

The above mentioned AIDA64 beta update is available for download 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 how it works

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.