Fiery

Do you have an Asus motherboard?

We're not planning to implement such a feature in our Android app. But since the current report layout is quite clear and easy to post-process, it's quite possible to write a script that would convert it to a HTML file with the layout of your choosing.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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're not that skilled in using PowerShell, but maybe someone else can help you out reading this.

Are you using the latest AIDA64 version of v6.00?

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

Please upgrade to AIDA64 v6.00 first. If the issue persists, 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 need to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability to enable CLC support.

I guess the issue is due to lack of permissions. In other words, the update process (AIDA_UPDATE.DLL) has no rights to overwrite the old AIDA64 main binary file (AIDA64.EXE) and replace it with the new one. What you can do is either dig down deeper and find out why the update process has no rights to do that, or download the AIDA64 v6.00 portable ZIP package, and extract it to the existing AIDA64 installation folder (C:\Program Files (x86)\FinalWire\AIDA64 Extreme). Let it overwrite any existing files. Your settings and your license will both be retained that way. If you're concious about keeping your settings, I recommend you to periodically backup the AIDA64.INI and PKEY.TXT files that you can find in the AIDA64 installation folder.

What kind of POS device are you using, and what protocol did you select in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / POS?

No, it's not possible, especially on iOS.

All measured voltages are listed on the Computer / Sensor page. But please note that not all motherboards are capable of measuring DIMM voltage or QPI voltage.

I guess your SMTP settings are incorrect.

The above mentioned beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta

We've fixed the issue in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

We've contacted Asus and asked them whether it's possible to access the OLED screen of their device directly. We'll see what they have to say about this... I'll let you know in this topic once we have an update.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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. I can give you a proper answer after studying that dump. It's because the delay occurs either somewhere in the sensor code, or inside the Odospace API. Thanks, Fiery

State #0 should display the state where the range is zero, so it shows for example 0 RPM or 0 degrees Celsius. State #15 should display the state where the range is at its maximum. So it shows like 5000 RPM (if your cooler can spin up to 5000 RPM) or 100 degrees Celsius (if you deem your thermal readings will never exceed that value). All the other states should show an intermediate step. Since State #0 = 0%, and State #15 = 100%, for example State #5 should show the range as if it was 33%.

Please let us know more about the issue you're facing with AIDA64. Please also note that this is an English language forum, so please post your questions in English.

AIDA64 has never implemented a SHA2 benchmark...

Thank you. I guess the issue is due to the number of fans your card has got. Based on the product photo we assumed it has only got a single fan. Maybe Fan 2 in your card's case reflects the pump RPM for the onboard liquid cooling?

Can you please check if the device is overheating after 4 minutes?

The Windows scheduler explanation still applies: Windows deems it's best to run AIDA64 on the last core and probably puts more threads/processes on that core as well. It results in the core running at a higher core ratio than the other cores, which then means it has to use a higher VID step to operate properly.

Thank you for your feedback and for your kind words

As a hashing algorithm, SHA1 is obsolete. It's also redundant when you have a more modern implementation of SHA. But, to make sure not to leave it behind completely, you can still run the SHA1 benchmark from the GPGPU Benchmark panel (AIDA64 / main menu / Tools / GPGPU Benchmark / double-click on the box in the x64 column, third line from the bottom).