Fiery

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.

We rarely have a chance to test systems with over 100 GigaBytes of RAM installed, and no, we never had a chance to have a Xeon Gold system at our HQ to test it thoroughly. As I've mentioned above, we're working on the next-generation AIDA64 System Stability Test that will allocate RAM via a smarter way to get rid of the freezing issues. We're currently considering backporting the new RAM allocation scheme into the currenty AIDA64 System Stability Test to help you about that issue quickly...

Thank you for your feedback

Maybe the values disappear when your video card switches down to a low-power mode? Can you see a pattern in the behavior?

I'm afraid Samsung SPF devices are not 100% stable. Overheating and firmware getting mixed up seem to plague them quite frequently These days we'd recommend using Beadapanel instead of Samsung SPF.

Thank you for letting us know about the resolution. We'll contact the authors of CoreTemp to make sure they implement the necessary synchronizing mutexes to avoid such issues in the future.

Make sure to upgrade to the latest version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Yes, scanning for DIMM thermal sensors can cause issues, that's why it's there on the Stability page. You can disable Aquaero sensor module temporarily by right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules --> Aquaero. You may need to enable status bar in AIDA64 / main menu / View first.

It means your motherboard cannot handle your RAM modules at 3200 MHz setting. It could be because of incorrect settings used for the memory module by the motherboard BIOS, or due to a faulty memory module.

Stability settings are there to let you disable certain modules that have a potential of causing problems. It's not there to let you disable otherwise perfectly working parts of AIDA64.