Fiery

1) IMHO increasing the number of states would make it very tedious to come up with that many of individual state images. That's why we prefer to keep it at a managable level. 2) PNG images cannot be altered by AIDA64, so it's not possible to add shadow, gradient or other tricks to them. Bars are rendered by AIDA64 itself, which gives us a lot more freedom in manipulating them.

I'm not sure what you mean by that. Please explain your issue in English and use more details.

If you have an Asus motherboard, you can try disabling the two Embedded Controller (EC) related options in AIDA64 / main menu / File / Preferences / Stability, and see if it makes a difference. In case your motherboard is made by another vendor, or disabling those options fails to help, please let me know.

Actually, if you change the unit label (of NIC download rate and NIC upload rate sensor items) to MB/s (means: MegaBytes/sec), Mbps (Megabits/sec), GB/s (GigaBytes/sec), or Gbps (Gigabits/sec), it will change the value itself accordingly. We've implemented that somewhat secret feature in order to avoid having to use conversion or special expressions. Your screenshot looks perfect, but the problem with the current LCD layout / SensorPanel editor is that it's already too complex for average users. We're trying to avoid adding more layers or more hoops to avoid alienating not-so-super-experienced users from using it.

Thank you! Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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 --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Have you tried it with the latest AIDA64 version of 6.30? If yes, then my guess would be that perhaps your Corsair H100i causes the headaches by on its own, or due to a collision between AIDA64 and its manufacturer supplied software (Corsair Link or iCUE). In which case it would be great if you could try disabling both Asetek LC sensor support and Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability. In order to test for the collision, you can also try to close Corsair's own applications. Please let me know what can you experience about the issue that way.

Do you have a NVMe RAID array that this SSD is a member of?

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. Thanks, Fiery

You can limit the number of items in that list in AIDA64 / main menu / File / Preferences / Content Filtering. You can avoid flickering by waiting for the list to be populated before clicking on any of the column captions to use sorting.

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. Thanks, Fiery

That's a great idea, we will do just that in the next AIDA64 beta update. Thank you!

For NIC items we generally recommend using the Auto-scale graph option. If you want to specify your own scale, then you need to enter the data in KiloBytes/sec, so for a 1Gbps (1 Gigabit/sec or 1 billion bit/sec) connection maximum should be 122070.

We don't manage a collection of themes and there're no official themes simply because due to the different set of available sensors, every computer needs a different, customized layout. Your best bet is to start here:

We will fix the issue in the next AIDA64 beta update. I will post a message into this topic once the new beta build becomes available for download.

It's not yet possible, but we're planning to work on it in the first half of 2021.

FPS measurement works via external tools, either Fraps or RTSS.

AFAIK those displays are supposed to be connected via HDMI and act as a secondary screen under Windows. You can use the SensorPanel module of AIDA64 to build and display layouts on either your primary or secondary screen, depending on where you move the SensorPanel window.

I'm not sure if there's any actual hardware out there that can do what you're looking for. Usually PSUs and UPS'es have such feature that they measure power draw of the system that AIDA64 can pick up.

Please try to disable GPU monitoring by unchecking the option called GPU sensor support in AIDA64 / main menu / File / Preferences / Stability. You will lose the readings for your RTX 3090, but it'd be crucial to narrow this down to something related to your motherboard sensors or the video card. BTW, please also let us know the motherboard model and Windows 10 build you're using. Thank you in advance!

It sounds like a hardware malfunction or hardware compatibility issue. You definitely need to look into it, although I'm not sure if it qualifies for RMA or other warranty claim. Are 3D games work properly?

Try to uninstall it from Windows Settings, restart Windows, and install it from a fresh installation package: https://www.aida64.com/downloads/latesta64xe Before doing so, make sure to backup your AIDA64 settings by backing up your AIDA64.INI file from the existing AIDA64 installation folder.

You can set it to 1 second in case your computer only has SSD's and has no HDD. Certain older HDDs had issues when they were polled too frequently, that's why we set the default polling frequency to 20 seconds.

No, it's actually normal. We've had to increase the block size and cache invalidation scope in order to avoid the influence of the large L3 cache of Zen 2 and Zen 3 processors. The longer execution time of the benchmark is caused by the more thorough cache invalidation, so that's normal too. We do have plans to improve on that, but the combination of high amount of logical processors (32 in your case, incl. the SMT virtual CPU cores) and large L3 cache makes it very difficult to perform the cache invalidation properly without it taking loooong.

Thank you! We've checked and memory clock should be reported properly. Can you please post a screen shot of the Display / GPU page when the memory is running at its highest frequency?

The FPU subtest of the AIDA64 System Stability Test tends to cause throttling on several mobile computers which are not designed to handle such extremely demanding tasks without throttling.