Fiery

It's normal, since we cannot add IPMI sensor readings to the regular sensor module of AIDA64 due to the slow IPMI protocol. It would make updates sluggish and cause a bad user experience.

How do you know the system freeze is caused by AIDA64 accessing the PCH?

AIDA64 currently doesn't support such monitoring sources.

I'm afraid not

You can use any resolution monitor for SensorPanel, but you may need to adjust your existing SensorPanel layout to fit the new screen.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

You can configure the number of decimal digits to be displayed for each sensor reading in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

Do you have an AMD or nVIDIA video card?

I'm afraid all those wireless peripherals use a proprietary protocol to provide battery status. It would be a tremendous task to support them all, since it would require separate development efforts for all devices individually. That's one task that we currently have no resources to take on.

It could happen in case the AX206 protocol your device uses is slower than expected.

Thank you for your feedback! Such issues tend to occur after certain major firmware updates by Aqua Computer.

In progress. It seems to work on the 4-inch and 4.3-inch screen already, but doesn't work on the 5-inch screen yet. Which screen do you have?

You need to use Fraps or RTSS (Rivatuner Statistics Server) since AIDA64 cannot measure FPS on its own but rather relies on those software to perform the FPS measurement. TRIAL means you're running the trial (evaluation) version of AIDA64. Once you purchase a license and you unlock AIDA64 full capabilities by entering your product key, all those TRIAL limitations get eliminated.

I'm not sure if I understand your concern about CPU vs. GPU. You basically can place the SensorPanel to any monitor, no matter what the monitor is connected to a dGPU (video card) or iGPU (CPU integrated graphics controller).

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.

I probably should have stated that you need to have any virtualization and sandboxing disabled. So under Win11 you need to disable both Memory Integrity and Hyper-V. The high L3 latency issue should have been fixed already.

Please consider getting a refund in case you're not satisfied with AIDA64. We're not quite comfortable for you to "bite the loss". Alternative software may be HWiNFO, HWMonitor and SIV, give them a try to see if they suit your needs.

On certain Intel processors, before the Ice Lake and Rocket Lake era, suffer from this issue under Windows 11. You need to disable Memory Integrity to get proper BCLK and CPU core clock measurement, as well as accurate benchmark results. Even Intel's own tool (XTU) suffers from major issues under Windows 11, so it's definitely not a bug in AIDA64 but a serious limitation that Microsoft introduced in Windows 11. One that causes headaches to both Intel and us. AMD processors do not suffer such limitations under Windows 11, but there used to be other problems about them under Windows 11 that Microsoft resolved by now.

You need to have AIDA64 running to use the SensorPanel. You can however configure AIDA64 to minimize to the System Tray when you close its main window by enabling the option "Close button" minimizes main window to System Tray in AIDA64 / main menu / File / Preferences / General. Alternatively, you can make AIDA64 minimize to the System Tray when you minimize its main window by enabling the option "Minimize button" minimizes main window to System Tray in AIDA64 / main menu / File / Preferences / General.

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.

It could be because your CPU keeps altering the core clock based on thermal state and power draw. It could increase the CPU core clock for a short duration but then it his thermal limits and gotta decrease the core clock again.

Thank you for the info! Any kind of virtualized environment or sandboxing could affect AIDA64 to measure CPU core clock properly. So it's best to disable them all if you can.

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 check if you can recover it here: https://www.cleverbridge.com/750/?scope=cusecolp If not, then please contact us via: https://www.aida64.com/support/contactform

Thank you for your feedback!