Fiery

It should not be necessary to do that. In the file called aida64.exe.manifest AIDA64 specifically requests administrator privileges. In case that file is missing from the AIDA64 installation folder, then using the trick you explained becomes necessary.

AIDA64 cannot load its kernel driver. And without its kernel driver it cannot perform most low-level hardware access. Check if you properly installed AIDA64, and check if your Windows user has administrative privileges.

Those aren't duplicates, they reflect the number of hardware or other entries in the system perfectly fine.

That issue is already fixed in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

We believe the issue is at Asus' end, so please contact their tech support and ask them to try and reproduce the issue and then investigate it.

Thank you, we will fix the reported issue in the next AIDA64 beta update.

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

That socd entry probably means something else. On some devices, it's not even a thermal reading (even when it's listed among all the usual thermal readings), but the battery level in %.

Make sure to enable both EC related options in AIDA64 / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching Let me know if it helps.

Thank you! Everything seems to be fine there. I suppose your CPU fan was not shown in the list of the available sensor items because the CPU fan wasn't spinning at that time.

In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

What version of AIDA64 are you using?

Try to use the POS module of the AIDA64 LCD feature on the virtual COM port that the device allocates. Set protocol to Epson. Let us know how it works out.

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta

By powering off, do you mean you press the power button on your primary monitor? Please note that pinning only works in case the number of monitors are constant. If you pin your SensorPanel to display #2, and display #1 (primary monitor) vanishes from the list of monitors as managed by Windows, the whole concept stops working. We've designed the pinning feature to mitigate issues rising from changing primary monitor resolution as well as relations between the primary and secondary displays (e.g. when displays are moved around). It's not been prepared to be aware of display #2 (secondary display) becoming display #1 (primary display) because of the main (primary) display suddenly disappearing from the system...

Unfortunately sensor icons can do whatever they can in a very constrained 16x16 pixel space. By making the text bold, it may not fit into the 16x16 pixel space reserved for System Tray icons If you need more flexibility, you may want to check out the OSD Panel, SensorPanel and RemoteSensor LCD modules of AIDA64.

@Surjeet Thank you for the dumps, for both of you. The issue will be fixed in the next AIDA64 beta update.

Try to restart Windows, and try it again. It may have come up because of a temporary lack of physical memory that AIDA64 could allocate in order to execute its memory benchmarks.

In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Pinning works in that case too.

We've implemented support for Razer PWM PC Fan Controller in the latest AIDA64 beta version available at: https://www.aida64.com/downloads/latesta64xebeta Let us know how it works.

No, since AIDA64 memory benchmarks consume a lot of memory, and in most cases when you start an app, it's not "as memory hungry" by allocating so much memory in a very short timeframe as AIDA64

I think it could have come up because of a temporary shortage of available physical memory.

Try to restart Windows and try it again.

It's enabled by default, so you must have unchecked at some point