Fiery

Thank you for the dumps. Currently we have no plans to decouple the slow sensor modules from the main sensor module due to it being already very complex. AFAIK it's not possible to talk to HXi/RMi Series PSUs through Corsair's software. We do not have plans to add more power readings for your PSU, especially about the power efficiency which is a calculated value and IMHO it's not something that is accurate or has much foundation.

AFAIK there's no software based method to adjust the brightness of Samsung photo frames

That's a notice that's displayed only on Windows 10 systems -- since AIDA64 Build 5006 -- on the AIDA64 Cache & Memory Benchmark panel after obtaining a memory bandwidth score to explain the relevance of each score. When you hover the mouse over those "i" icons, it will display: (for Memory Read) Read performance measurements offer insight into CPU architecture, but do not reflect typical application workloads. (for Memory Write) Write performance measurements offer insight into CPU architecture, but do not reflect typical application workloads. (for Memory Copy) Copy performance measurements offer the best insight into the effect of the CPU architecture and memory subsystem on typical memory-bound application workloads.

We will fix the issue by disabling SMBus support for your notebook in the next AIDA64 beta update.

I suppose it's more because of the slow gathering of sensor readings rather than because of a slow rendering of SensorPanel or RemoteSensor layout. 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. Thanks, Fiery

I suspect the issue is either CrossFire or the improper implementation of AMD's own PMLog API in their recent video drivers. Try to disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. If it doesn't help, try to disable GPU sensor support on the same page of the Preferences as well, and restart AIDA64.

That 200+ Celsius reading for DIMM temperature is an invalid reading and should be ignored. At such a high temperature your memory modules would get irreversibly damaged. The invalid reading could be because of a collision between AIDA64 and another monitoring software trying to access the sensor chip concurrently.

Please check the temperatures with the following new beta build of AIDA64: https://www.aida64.com/downloads/latesta64xebeta

Please check if the memory stress test gets more responsive with the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta

Thank you! Please check the following beta about the IPMI issue: https://www.aida64.com/downloads/latesta64eebeta

Thank you. Quite frankly, I wish we had the time and resources to develop a Stream Deck plugin for AIDA64 from scratch. But in the current situation I cannot make any promises about it. So it's either the current solution or taking over the whole device -- but none of those seems to be 100% suitable for your requirements.

Yes, you can create your custom gauge states and assign them if you select the gauge type as "Custom". Then click on the "..." button next to "States" to select your custom gauge state images (e.g. PNG files).

To avoid issues, multi-bank EC support has to be enabled on a per-motherboard basis. Are you sure there are multiple banks for the EC of your motherboard?

We've checked it, and for us everything works properly. Please export your Arx LCD items (layout) using the Export button on the page AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / LCD Items. Attach the file to your post here.

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

Are you sure the Vcore is correct in CPU-Z and incorrect in AIDA64? Try to compare the value measured by AIDA64 against ASRock's own monitoring software.

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).