Fiery

It depends on the video card. If you have an iCX2 video card, then you shouldn't have both GPU and GPU Diode, but only GPU Diode. If you see something else on the Computer / Sensor page of AIDA64, then please copy-paste the full content of that page into this topic or make a screenshot showing the entire page and attach it to your post, so we can check it out.

Thank you for your feedback. I'm afraid so far we haven't found a way to report the 3rd fan on Gigabyte RTX 3080/3090 video cards as well as on Asus Strix RTX 3080/3090 cards. In your dumps I cannot see a 3rd fan, so these new Aorus cards must use a new, proprietary interface to report the RPM for the 3rd fan. BTW, can you see all 3 fans reporting individual RPM readings in Gigabyte's own monitoring utility?

Thank you for your feedback!

Make sure to check if the fans are really stopped when AIDA64 stops reporting them (or reports them at zero RPM).

Make sure to have the option Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability enabled (checked). That should make it work with your Commander Pro unit.

Please let us know what exactly are you doing and what happens. Also, where do you download the SensorPanel layouts from?

Try to update your motherboard BIOS to the latest version, and enable the option called Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability. That should help to avoid crashes on sensor access on your particular motherboard.

Thank you for your feedback

Thank you for your feedback!

We haven't touched iCX2 support or diode measurement for Turing based GPUs, so it's quite puzzling...

We've ordered a NZXT RGB & Fan Controller device that should be the retail version of the Smart Device V2 in your PC. Until it arrives, please help us out a little bit by right-clicking on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. That dump will let us verify if your device really compatible with our upcoming NZXT RGB & Fan Controller device. Thank you in advance!

AIDA64 doesn't have a built-in facility that would let you monitor System Stability Test sessions remotely. However, I think that could be achieved using simple remote desktop or VNC too as long as your admin system has a large display (or multiple displays) and you use a low resolution on the remote computers.

What temperatures are you missing from AIDA64? If it's related to your motherboard, then please let us know what motherboard you've got and what version of AIDA64 are you using.

1) What are the model ID of those M.2 SSD's? 2) Is your NIC5 a simple wired Ethernet network connection? Can you see it on the Network / Windows Network page of AIDA64?

I'm afraid AIDA64 doesn't support such sensor source.

You need to perform the upgrade this way: close AIDA64, download the new beta ZIP package, and extract the ZIP contents into the existing installation folder of AIDA64. Let it overwrite any existing files. It will retain your Preferences settings and your license as well.

They look normal to me.

We've done several test runs and tried to fix it from our end, but it seems LGS and Arx sometimes simply act up and stop working through the Logitech Arx SDK that AIDA64 relies on What we've found out is that the only way to fix it is to start AIDA64, and when it fails to work with Arx, restart LGS. That seems to be an annoying but working fix.

Thank you! Maybe what HWiNFO64 measures is the CPU VID instead of the Vcore? In AIDA64 you can see both readings right next to each other.

Thank you for your feedback! About the ext.fan, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller 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

Thank you, it's always great to bump into and work together with other developers

In the next AIDA64 beta we will add the drive serial numbers to the Physical Drives page in order to help you out about this issue. I will post a message into this topic once the new beta build becomes available for download.

Please give us a few weeks to complete that task though, since even acquiring the device will take at least a week due to low supplies/stock at local dealers on such specific products.

Driver details and hardware ID look correct. Maybe it's because the manufacturer of your device updated the USBD480 firmware to one that's incompatible with the old firmware that we designed our USBD480 support around. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. If it's possible, please also post a screenshot of the AIDA64 / main menu / File / Prerefences / Hardware Monitoring / LCD / LCDInfo page. Thanks, Fiery

The FPU subtest puts the most demanding task on the processor which could make it hit TDP, TDC or other power limits or simply overheat, and that will effectively disable automatic overclocking, or prevent any kind of overclocking without potentially damaging the CPU. In other words, in your particular case what happens is that 4.6GHz is only possible with 90-95% of the tasks (workloads), but the most demanding few of such tasks will only enable a lower CPU clock frequency to be used.