Fiery

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

1) @ x16 means it's working at x16 link width. 2) BIOS fills in the PCI-E controller registers at bootup, so in case they're incorrectly filled, it's sadly a BIOS bug that we cannot fix from our end 3) Bus / Device / Function = 1 / 0 / 1 means Bus #1, Device #0, Function #1.

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. Let me know if it helps.

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

It looks great!

Thank you!

You can use the Hot Keys feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys) to switch between LCD pages. In that sense LCD includes RemoteSensor but not SensorPanel which is strictly a one-page layout. However, with RemoteSensor it's best to use a 2x or 4x resolution than the recommended one, and then you can use touch navigation on your smartphone to move to a different area of the page.

Here's the fix for this issue: https://www.aida64.com/downloads/latesta64xebeta

We've implemented rotation support (to enable portrait orientation) for BeadaPanel LCDs in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta

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

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

AIDA64 implements support for Thermaltake Riing Plus fan controller, but you seem to have a different fan controller by Thermaltake. I'm wondering whether these controllers share the device ID and compatible with each other on some levels. In order to let us check that, 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

We haven't found a solution yet.

We can only monitor those that can be monitored by the motherboard itself. Many UEFI BIOS'es implement more voltage rails to control than to monitor. Sometimes the ratio is 2x or more

The requested feature (of supporting up to 3 independent EastRising ER-OLEDM032 displays) will be implemented in the next AIDA64 beta update. I will post a message into this topic once the new beta is available for download.

The requested feature will be implemented in the next AIDA64 beta update. I will post a message into this topic once the new beta is available for download.

Only you can tell whether the picture quality and resolution of the display is a priority for you or not. If you want to build a beautiful external screen, then quality is important. If you just want to glance on some sensor readings while you're playing games on your main monitor, then probably quality is less of importance. AIDA64 SensorPanel supports clickable images and static labels to open a pre-defined URL, but for most users it's not a huge deal. Therefore I don't think touch capability is really beneficial for SensorPanel. For those who're looking for a large colour screen, we usually recommend SensorPanel + any display that can be used as an extension of Windows Desktop. USB connected monitors and regular monitors (connected via DSub, DVI, HDMI or DisplayPort) both work fine for such purpose. An old 15-inch or 17-inch DSub-connected LCD monitor is a great start due to the low costs. USB-connected external displays that aren't monitors can sometimes be a challenge (e.g. Samsung SPF digital frames) and can cost a lot as well, but one great example of those that AIDA64 fully supports and is relatively affordable is BeadaPanel: https://elinux.org/BeadaPanel http://www.nxelec.com/products/hmi/beadapanel-media-display https://www.ebay.com/itm/BeadaPanel-7-LCD-Display-for-AIDA64-USB-Single-Cable-Gadget-Monitor-w-Touch-/113404121186 It is supported since AIDA64 v6.00, but you need to use the AIDA64 LCD module for that, and not the SensorPanel that only supports monitors. The last option is using an Android tablet and the RemoteSensor or OdoSpace LCD module of AIDA64. It's the least flexible option, since you gotta make sure to charge the tablet. But, if you already have a tablet in your drawer that is otherwise not in daily use, it could be a great start to get used to the LCD layout editor of AIDA64 -- which is shared between the SensorPanel and LCD modules of AIDA64.

Yes, it is, thank you!