Fiery

The issue is because AIDA64 requires to allocate a huge continuous memory blocks to properly measure memory bandwidth utilizing all available PC resources (mostly all available CPU cores). In some cases -- for example when the computer has a lot of CPU cores paired up with inadequate amount of physical memory -- Windows simply refuses to allocate the continuous memory blocks AIDA64 would require to test the memory properly. In that case AIDA64 pops up a message box about memory allocation error. True, in some cases it is adequate to simply restart AIDA64 to make it work, but in many cases it's best to restart Windows completely. That would free up resources and Windows could allocate more memory then. So while my reply ("Try to restart Windows, and try it again") may have seemed like a short one, that is actually the best recommendation when you get the error message. I could have said "Consider adding more RAM to your PC" too, but that would have been borderline obnoxious, wouldn't it?

I'm afraid no, you gotta take care of removing old log files once you find them unnecessary.

Do you want to disable auto-start of AIDA64 at Windows boot?

Please post a screenshot of your settings for the AIO Pump sensor item (as part of your SensorPanel layout I assume).

Does your computer go to sleep during the night?

That's a great idea, but currently we focus more on the mainline product, AIDA64 Extreme, and how to enhance its existing functionality to cater for existing demands.

Please let us know in what part of AIDA64 do you get this error? For example, do you click on a particular page of AIDA64?

Thank you, the issue will be fixed in the next AIDA64 beta update.

Thank you! I'm afraid we haven't found a reliable method to measure fan speeds on your system. We've contacted Minisforum about this issue, but they refused to provide the necessary technical information on the fan measurement

Did you manage to fix all images so now it won't crash with the latest beta build as well?

Thank you for your feedback. For some reason not all devices can provide that information via the standard Android Battery API.

You can adjust the number of decimal digits in AIDA64 / Preferences / Hardware Monitoring.

Does it crash during the time when you're not editing it too? So when e.g. you're viewing the SensorPanel?

In AIDA64 please press Ctrl+D --> 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

I've sent you an email about this.

Thank you!

I've sent you a private message about this.

Thank you for your feedback! We will try to shave off some more of that 2 seconds delay in the upcoming builds.

Those layouts were designed for 100% DPI (zoom) setting. In case your monitor uses a non-100% DPI setting, you need to adjust the layouts to fit your DPI setting.

@BHSY @Surjeet Both of you, please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

I've sent you an email about this issue.

That string (рЕЯРНБНЕ ЯННАЫЕМХЕ) is not written to the email subject by AIDA64.

I've sent you a private message.

We believe the issue is about the firmware of your display, so please report the issue to VoCore.

No worries