Fiery

Thank you for the info. We will fix the issue in the next AIDA64 beta update. Meanwhile, I've sent you a download link (in private message) for a special beta build that you can try now.

We don't have a list of compatible devices with the RGB LED features, mostly because it's so diverse and complicated that it's not really possible to compile a list. It's because e.g. with Corsair and Razer there's a SDK that potentially supports a wide range of devices and even future devices. With other modules it's still not in a final stage and the manufacturer doesn't guarantee that it would work for a wide range of RGB devices. So it's best if we go by a case by case basis. As for your system, ASRock motherboards in general are not supported by the RGB LED module, because only Asus motherboards are supported via the Aura LED SDK. Razer is easy, since the Razer Chroma SDK supports virtually any Razer device out there, and certainly all Razer keyboards and mice. Only Asus video cards are supported via the Aura LED SDK. RGB fans and controlling the RGB LED portion of liquid coolers are not supported right now. Since our RGB LED features are designed to reflect the state of a hardware component or a sensor reading, we do not push for implementing support for such devices that are not easily visible for most users. We believe peripherals are the best candidates to reflect e.g. high system temperature by changing their LED colour, so that's why -- in general -- the AIDA64 RGB LED module supports keyboards, mice, mousepads and headset stands.

It seems high, but in case your computer is stable, you have nothing to worry about.

We'll do our best. Does it work with 90 degrees and 180 degrees rotation?

The mentioned new AIDA64 update is now out, as the v6.10 stable update: https://forums.aida64.com/topic/5213-aida64-v610-is-out/

The mentioned new AIDA64 update is now out, as the v6.10 stable update:

The new AIDA64 release implements AVX optimized benchmarks for Zhaoxin processors, adds PCIe 4.0 and NVMe 1.4 devices support, monitoring of sensor values on Matrix Orbital EVE3 displays, and supports the latest AMD and Intel CPU platforms as well as the new graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - AVX accelerated 64-bit benchmarks for Zhaoxin ZX-C+ and Zhaoxin KaiXian KX-5000 processors - Full support for Hygon C86 “Mukti/Dhyana” CPU - Enhanced RGB LED monitoring module - Matrix Orbital EVE3 LCD display support - Improved support for Intel “Comet Lake” and “Ice Lake” CPUs - Support for PCI Express 4.0 controllers and devices - Preliminary support for Zhaoxin KaiXian KX-6000 CPU - Advanced support for LSI RAID controllers - NVMe 1.4 support - Improvements for AMD X570 chipset based motherboards - GPU details for AMD Radeon RX 5700 Series - GPU details for nVIDIA GeForce RTX 2000 Super Series What's new since AIDA64 v6.00 - SHA3-512 cryptographic hash benchmark utilizing AVX, AVX2 and AVX-512 - AVX2 and FMA accelerated 64-bit benchmarks for AMD Zen 2 “Matisse” processors - Microsoft Windows 10 May 2019 Update support - BeadaPanel LCD and SteelSeries Rival 710 OLED display support - Corsair H100i Platinum and H115i Platinum liquid cooler sensor support - Cooler Master MP750 RGB LED mousepad support - Corsair Obsidian 1000D, EVGA iCX2, Farbwerk 360, NZXT GRID+ V3 sensor support - Preliminary support for Intel “Comet Lake” CPU - GPU details for AMD Radeon VII - GPU details for nVIDIA GeForce GTX 1600 and GeForce RTX 2060 Series - Preliminary support for AMD “Navi” GPUs - Retired SHA1 and VP8 benchmarks [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (magyar) ] [ What's new in AIDA64 v6.10 ] [ Download ]

Thanks, we'll add that monitor too. The next AIDA64 update should be out tomorrow

It's not few minutes. At least not if you do it properly.

We'll add the requested new option to the Preferences / Stability page in the next AIDA64 update due in a few days from now.

Please give us a few days to implement that.

The first one lacks the necessary information to detect it properly, but we'll add the second one in the next AIDA64 update due in a day or two.

This is a collision between AIDA64 and iCUE. Please report this issue to Corsair. We've been in contact with them for over a decade now, but this is the only issue where we cannot convince them to fix their software. AIDA64 -- as well as many other 3rd party monitoring applications including CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, Rivatuner, SIV, SpeedFan, etc -- use industry standard synchronization mutexes in order to prevent such collisions when multiple monitoring software is trying to interact with the same hardware. This works great as long as you use two or more of the mentioned software concurrently. We've got to the point of convincing Corsair to implement a synchronization mechanism in their previous generation software (Corsair Link Software), but then at a certain point they simply removed the mutex and never implemented in iCUE. It means iCUE cannot be used concurrently with 3rd party monitoring applications which is simply unacceptable IMHO. No matter how much pressure us and the developers of the previously mentioned 3rd party monitoring software put on Corsair, they stick to their stance on this matter. Only you, the customers of Corsair and owners of Corsair hardware have a chance to convince Corsair to change their mind.

I've sent you a private message about this issue.

Thank you! It seems the HID protocol we use for Z10 cannot be used for Z10 RGB, since the protocol itself seems to have changed. We've contacted EVGA and asked them to provide us with he necessary technical information to implement support for the new Z10 RGB HID protocol and so let us put our own bitmaps on the LCD of Z10 RGB. I'll let you know once we could accomplish all of that.

We'll add that reading in the next AIDA64 beta update

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. Thanks, Fiery

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

Thank you. Everything looks fine there. I think with virtualization enabled, the APIC clock runs slower than the BCLK for some reason. Maybe because APIC is virtualized then as well. As for the missing sensor readings, in the case the rest of the readings are there, and AIDA64 uses the Asus WMI interface, it is then due to a BIOS bug.

I'm almost certain that if you disable GPU monitoring, the issue won't come up.

On Vega 56/64 and RX 5700 Series AIDA64 uses AMD's standard PMLog interface that was designed to avoid such collisions when both AMD's video driver and 3rd party applications try to poll sensor readings and they alter GPU registers in a concurrent way. Apparently PMLog is still not 100% stable, so using it causes different issues then previously when low-level register readout caused collisions I'm afraid we cannot fix that issue from our end, so you need to report this to AMD and ask them to fix PMLog in their drivers.

I have no idea what disabling a certian fan RPM reading is accomplished by the BIOS Setup, but most likely it just means that the BIOS Setup stops monitoring that fan. It still could mean that the fan RPM register indicates a reading, and actually no sensor register is altered to indicate that Chassis #2 fan RPM readout is disabled. I'm not sure what to do about such issues. Unless of course you use the SensorPanel, OSD Panel (etc) modules where you can select which items you want to hide or show

Thank you, it's clear now. I'm perplexed though, since you've mentioned above that the issue persists even with AIDA64 v5.97 that has no support for Thermaltake fan controllers at all. Maybe you've checked not the stable build of v5.97.4600, but a beta version that is v5.97.4628 or newer?

Thank you. Please repeat #1 with virtualization disabled, so we can compare the CPU registers output against the "virtualization = enabled" state. As for issue #2, try to enable Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability.

We'll add DIMM CA and DIMM DQ voltages in the next AIDA64 beta update. We'll also update the label "CPU PLL2" to "BCLK PLL" in order to clarify that voltage reading.