Fiery

We need to narrow this down a bit, so please try to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability, and let us know if it makes a difference. Thank you in advance!

Try to check whether you have any left-over main executable for AIDA64 (AIDA64.EXE file). Remove all remaining instances of that file and restart Windows. After doing that, the kernel driver file (KERNELD.X64) should be free to be removed also.

Thank you for letting us know about your way around the issue. What we've found out recently is that indeed when AIDA64 SensorPanel is running on a secondary display and the primary display resolution changes, the SensorPanel position will change since it's tied to a relative position counting from the top-left corner of the primary display. One workaround for such issues we've found is to move the secondary display to the left of the primary display in the multi-monitor configuration panel of the WIndows 10 Settings. So when the small (secondary) display is on the left and the large (primary) display is on the right, the position of the SensorPanel will be retained even when the primary display resolution changes.

We've checked, and I'm pretty sure our CPU Package temperature measurement works fine. I'm not sure if HWMonitor's correct since it's not our software, so I don't have an oversight on the validity of those readings. However, if you're in doubt about the CPU Package temperature, just ignore it and focus on the other CPU related thermal readings that your motherboard and processor provides.

Both of you, please let us know exactly what model of Corsair AIO cooler do you have. Thanks, Fiery

PCI devices and their registers, including PCIe root port descriptors are configured by the BIOS at system bootup. Apparently on your system the motherboard fails to put the right PCIe speed information into the PCI devices. It's a minor cosmetical issue that you can freely ignore, especially that as you've proven using our benchmarks, the devices are indeed working in 3.0 mode.

Your Z63 device presents as a USB device in your system, but the default HID driver isn't seem to be installed for it. Can you please check (using e.g. the Windows Device Manager) what driver do you have installed for your Z63?

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

AFAIK it's not possible to detect such details for memory cards under Android.

You can only convert an Android platform to 64-bit by installing a new Android firmware update that is 64-bit. You need to consult with the manufacturer of your device and inquire them whether they have such an update for your device.

It's not supported by AIDA64 yet. In order to let us have a better understanding on the USB layer of it, 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

Make sure to disable (uncheck) the option called SMBus access through ACPI (Asus motherboards) in AIDA64 / main menu / File / Preferences / Stability, and on the same page enable (check) the option called DIMM thermal sensor support. Let me know if it helps.

We're waiting for a chance to acquire an iCUE Nexus sample that we could use to develop support for it. It was briefly available at its launch, but AFAIK it was pulled back from the market due to unknown reasons. Corsair hasn't put it back to market yet, but hopefully will do soon.

It's actually normal. Our i9-10900K (stock settings) exhibits throttling even with a big-*ss cooler that's rated for 250W TDP. So you have nothing to worry about.

Please post a screenshot of the Cache & Memory Benchmark panel of AIDA64 so we can check all scores. Also make sure to use the latest AIDA64 version of 6.30.5500.

If you could explain the protocol in details, and provide us with either sample hardware or a way to acquire such a hardware, then we could implement support for your LCD device in AIDA64.

Please avoid posting a single issue into multiple topics. I've replied you in your other topic.

I'm not sure if I understand your inquiry. Can you please explain with more details, and in English?

Our best guess is that it's because 144Hz is only used when you're playing a game or watching a movie. In regular apps the device may lower the refresh rate in order to save power.

Please note that ever since Android 7.0 (for whatever reason) Google decided to block apps from accessing several system files that were previously readable. That includes the files apps would need to show thermal sensor readings. Battery temperature reading is still available fortunately.

soc is basically the CPU of your mobile device.

Do you mean it's not indicated on the Devices page of AIDA64 for Android?

Please note that on many devices the standard Android Battery API is inadequately implemented, and fails to provide proper charge counter information for the battery. If you want, you can hide the incorrect charge counter information from the Battery page by unchecking the charge counter option in the AIDA64 Settings.

Yes, it's a known issue that is caused by new architectural tricks of Ampere. We're working on fixing it as well as a few other minor issues related to Ampere GPUs.

Yes, it's a very secret feature due to our negligence of not documenting it anywhere You're right, by average users I meant average power users, or average AIDA64 users. Even those folks tend to get deterred by the complex configuration possibilities that SensorPanel/LCD already offers. They're looking for ready-made solutions or half-baked layouts that they could modify. Starting from scratch and learning how to "drive" this thing does indeed require a learning curve and a lot of time invested. I hear you about the collapsible section, but until this Covid issue blows over I cannot and would prefer not to make promises about future developments. We're trying to focus on what we can do right now, since noone knows what tomorrow brings...