Fiery

The missing sensor will be added to the next AIDA64 beta update. I will post a message into this topic once the new beta build becomes available for download.

Thank you, we'll fix it up in the next AIDA64 beta update.

What motherboard, CPU and video card do you have in your system?

No need to turn them off, since those low-level calls are only done once (or not even once if they don't suit your system) to detect the presence of a certain hardware or interface.

Please avoid posting a single issue into multiple topics.

It's a good idea, but it also seems quite complicated, and in the current situation I'd rather not promise anything about complex development tasks

1) Not really. With AIDA64 you can put shortcuts on labels and images, but I don't think it's really all that useful when it comes to hardware monitoring. 2) Win10 does support handling multiple displays independently, in terms of resolution and dpi, but I never tried to deal with colour space or HDR, so don't really know a definitive answer for this. 3) It should be able to, but I never tried it. 3/b) (Mouse) AFAIK it's not possible to avoid that. 4) No, there's only a single page supported by the SensorPanel, and you cannot use multiple SensorPanels. 5) See my answer for #1 6) Quite frankly, we don't really want to overcomplicate the already quite complicated LCD and SensorPanel modules. There're several ways you can monitor your system parameters using AIDA64, and it's possible to combine multiple features in the same time. E.g. you can use the SensorPanel and the External LCD module to have basically 2 or 3 (or even more) pages of information displayed. With the LCD module you can use multiple devices too, so for example if you pick up a HDMI monitor, you can put SensorPanel on it. If you pick up a cheap as chips Android tablet, it could be your second device with page #2 using RemoteSensor. If you then pick up a BeadaPanel or another sorts of external LCD device, it could be your page #3 or even page #4 (since AIDA64 can handle two BeadaPanels in the same time).

AIDA64 doesn't measure DirectX GPU utilization, but hardware GPU utilization as reported by the GPU itself. So it doesn't depend on the actual DirectX, OpenGL or Vulkan layer used.

Try to push the power button of your system once. It should trigger Windows to shut down your system. If it doesn't work, try to disconnect the PC from A/C power by e.g. switching the power button on the PSU (power supply unit).

AIDA64 doesn't detect that system setting.

That I think is rather a hiccup of the sensor chip, providing incorrect values for one or more readings for just a brief moment. Or, another monitoring software collided with AIDA64 about the low-level hardware (sensor) access.

What sort of RAID controller do you have in your system, and what RAID array do you have defined?

IMHO the current solution is already way more useful than having no support for Stream Deck

No problem with our servers. The internet in general however is quite overloaded due to CoVID-19 quarantine/lockdown.

Make sure to 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.

1) We will fix it in the next AIDA64 beta update. 2) Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> IPMI Access 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 --> System Debug --> IPMI Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. BTW, if you have a chance to install a Windows IPMI driver, that alone should solve this issue since then AIDA64 won't need to use low-level IPMI access. 3) 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. 4) Your motherboad may use a SPD mux that is very difficult to handle without having the necessary technical details on the mux (provided by ASRock). Let's check this first though: 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.

Thank you for your quick response and awareness about this issue!

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

Thank you for your feedback!

No, only one, via the RemoteSensor module. For a more advanced solution you need to develop your own HTTP server and process the readings exported by the External Application module of AIDA64.

Running more than one instance would be possible, but you wouldn't be able to use the kernel driver (and so all the low-level features of AIDA64) in the secondary, tertiary (etc) instances since AIDA64 kernel driver can only be used by the process that loaded it first. So even if we enabled the use of multiple instances, it wouldn't be useful for your purposes I'm afraid. I know it's not the best advice, and also it would cost you money, but picking one (or even more than one) external LCD screen would enable you to use the LCD facility of AIDA64 and effectively double or triple the amount of "SensorPanels" you can use at any given time. For example, if you picked up a BeadaPanel, you could place your secondary readings on it using the same layout editor that you use for SensorPanel.

You can check if AIDA64 has the necessary privileges to load its kernel driver (which is necessary to detect SPD information) if you check whether the CPU multiplier and FSB (BCLK) are properly measured on the Motherboard / CPU page or on the CPUID Panel (main menu / Tools / CPUID Panel).

I'm afraid that monitor device has no identification strings in the EDID block, so we cannot add it to our monitor database.

Try to enable the option called Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps.

That's a known limitation of Android 8+ platforms which became more secure, more sensitive about SSID and BSSID information. Now it would require requestign an additional permission to access SSID and BSSID information. We're considering doing that, but on the other hand, lot of users are sensitive about apps requiring and asking for too many permissions. So it's a difficult issue, but we're on it.