Fiery

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.

1) With both virtualization settings, please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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. 2) With BIOS 5216 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. You may need to enable status bar in AIDA64 / main menu / View first. Then 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.

NZXT GRID+ V2 and GRID+ V3 are two other well-known modern fan controllers that AIDA64 supports. Those don't have a collision-free interface either, but V3 is slightly better about it than V2. Other than those there's Aquacomputer Quadro which is well supported by AIDA64. AFAIK it's possible to use more than one of those in the same computer. Corsair Commander Pro is a sophisticated solution, but we're still struggling with Corsair's thick head of not allowing proper synchronization between their software (iCUE) and 3rd party monitoring software like AIDA64. There're also some old stuff that AIDA64 supports for ages, like AlphaCool Heatmaster II and T-Balancer bigNG, but I think they are no longer available for purchase.

Thank you for checking it out, and also thank you for the dump. Your Pure Plus controller seems to be compatible with the already supported Riing Plus. You cannot disable the Riing Plus module right now, but as you've checked it, it seems without it the collision is still there. Can you please check what happens when the collision occurs? Like an incorrect temperature is measured by Thermaltake's own software? BTW, what is the exact issue that happens? The fans spin up to 100% or stop?

Thank you for letting us know about it. I suppose something went south about the motherboard database of AIDA64, and that caused the incorrect use of sensor adjustments.

The voltage sensors are as follows (this is specifically and only for EVGA Z390 Dark): - VSA (BIOS) = VCCSA (AIDA64) - +12V CPU = +12V CPU1 - VGT = iGPU - PCH = PCH Core - VCCST = VCC Sustain - VCCPLL = CPU PLL - VCCPLL_OC = CPU PLL OC - DMI PLL = DMI - USB/PCIe PLL = PCI-E - BCLK PLL = CPU PLL2 - DIMM CA CPU VrefA = DIMM CA - DIMM DQ CPU VrefB = DIMM DB The rest uses the same label. As for the gauges, you can simply specify the range as 0-2 to have a better "red line effect".

Thank you. This is a laptop, and most laptops do not need motherboard specific sensor adjustments. Other than that, your system is well supported already. We'll add your Micron 2200S SSD to the SSD database of AIDA64 though

First, try to disabled Embedded Controller (EC) support[ in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. You will lose a few sensor readings due to that, but it may help about the lags. If it doesn't help, try to 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. As for the Windows startup lag, that's caused by the Windows kernel which is sensitive to the auto-start of certain applications that use a dynamically loaded kernel driver. On some systems this issue comes up, but on most systems the delay is not unbearable. We cannot do much about this, since we prefer the dynamic kernel driver scheme over the static (installed) one in order to fully support portability for AIDA64.

Please 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. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery