Fiery

We're looking into this... Should be possible to add it for us too.

I'm afraid in order to get rid of the collisions with Corsair's iCUE software, on your particular system you need to disable (uncheck) Corsair Hydro Platinum sensor support in AIDA64 / main menu / File / Preferences / Stability. There's no self-installing EXE package for our beta builds. You download the beta ZIP package and extract it into the existing installation folder of AIDA64. Let it overwrite any existing files. That upgrade process will still retain your entered license and your existing settings.

We'll add $CHIPSET to the next AIDA64 beta update. The rest is more complicated, and we'd need to narrow your ideas down to specific variables to add. And the list isn't supposed to be too long either, considering that users have to select them from a dropdown list.

They execute the same benchmark, so it's only the run-to-run variation that you experience. Try to run the benchmark 5 or 10 times, and either average the values or pick the best (lowest) result of them all.

Without knowing what panel you've got, it's difficult to provide you with valuable instructions or guidelines. The BPS Customs video specifically talks about the importance of connectivity. I love the video, so let's link it here too

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.

Does CPU-Z for Android report the same clock range for your SoC than AIDA64?

Maybe Hyper-V wasn't enabled before, but a certain (most likely major) Windows update may have activated it without your interference or choice.

1) Mixing different LCD displays is fully supported, with virtually no limit on how many displays can you connect and handle with AIDA64 as long as each display kind has only one device connected. So you can have one AlphaCool, one Matrix Orbital EVE2, one Crystalfontz, one POS (etc) and AIDA64 will be able to put sensor readings on them separately and independently. 2) There are several LCD modules in AIDA64 that support more than one device, but it's not a generic rule or generic property of the LCD modules. For example, with BeadaPanel you can have 2 devices handled by AIDA64. With Matrix Orbital EVE you can have 4 devices. With AlphaCool you can have 2 devices (etc). 3) I'm not sure what exact form factor and dimensions "bar style but 17-18 wide" would have to be. Can you please post the dimensions of the display you're looking for, both width and height, either in inches or mm's? Then I'd be able to recommend you a display.

What GPU (video card) do you have?

It's not that straightforward, unless you can connect your Pi as a HDMI screen (regular monitor). We currently have no ready-made solution to support Pi as an external LCD screen.

No, not with those apps. Corsair iCUE and NZXT CAM are notorious of collising with 3rd party monitoring software though...

We don't have a ready-made solution for that setup, but it is possible to construct a script to connect to one of the existing LCD interfaces that AIDA64 supports and interact with AIDA64 as if the Pi would be one of those displays (e.g. Matrix Orbital LK or POS).

Maybe the network activity is performed on a different NIC, not NIC1?

In many cases it's because of the influence of some sort of virtualization. If you can, try to deactivate Hyper-V on your system or completely disable CPU virtualization (from the BIOS Setup).

We never said single-core benchmarks are not included. You can use the Parameters button on the AIDA64 tool bar to limit the CPU and FPU benchmarks to use only one CPU. The argument was about including a list of reference benchmark scores for single-core performance. That's what we're not doing, but you can still use the benchmarks with limited number of cores.

You can use the Correction facility of AIDA64 in order to scale the memory clock to the effective clock value you're looking for. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

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. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aqua Comptuer Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

We currently have no plans to support such data input natively. You can however make a plugin that takes that data and writes them into the Registry to a pre-defined path where AIDA64 can pick the values up and import them into its hardware monitor module. Let me know if you want to go down that path and interested in the details on how to process Registry values.

Maybe it's too low in MB/s?

I'm afraid new AGESA releases discontinued to publish EDC and TDC information the way AIDA64 could read them out. Only TDP is available now for those processors.

Can you see network activity on any of the NIC's listed on the Network / Windows Network page of AIDA64.

We're still waiting for Corsair to unlock the possibility of 3rd party software accessing Corsair hardware concurrently with their own monitoring software (iCUE). It seems they're not so keen on going down that path though. Hence, Corsair hardware owners and customers to the brand have to put more pressure on Corsair to make a move in the right direction.

Please 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 makes a difference. Also let me know what motherboard, CPU and video card do you have.