Fiery

In AIDA64 please press Ctrl+D --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for your feedback!

Thank you for your help in diagnosing this issue. The issue occurs when you use resizing on your image but the desired dimensions of the image matches the actual dimensions of your image, and so there's no actual need to resize it. So in your particular case you use a PNG file with 515x1920 pixels resolution, and you have a resize setting to 515x1920 configured. Once you disable resizing, the SensorPanel will start working for you again. In the next AIDA64 beta update we will implement a proper bug fix for this issue of course.

In the latest AIDA64 beta update we've added Ctrl+M keyboard shortcut on the SensorPanel to let you open the SensorPanel Manager without using the right-click context menu. https://www.aida64.com/downloads/latesta64xebeta

In the latest AIDA64 beta update we've added Ctrl+M keyboard shortcut on the SensorPanel to let you open the SensorPanel Manager without using the right-click context menu. https://www.aida64.com/downloads/latesta64xebeta

We've fixed the issue in the latest AIDA64 beta update 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.

We've implemented support for HX1200i 2023 PSU in the latest AIDA64 beta update 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 how it works.

Yes, you can use my explanation of the issue.

They came back and informed us that the project was put on hold. I suppose they have to focus on other matters that are more pressing than dealing with AIDA64

No, 1% throttling means that 1% of the time the CPU execution pipeline gets stalled due to overheating. So in a period of one second (which equals to 1000 milliseconds) the CPU only operated for 990 milliseconds and stood idle for 10 milliseconds.

No, it won't damage your CPU, you're safe.

I'm not quite sure the issue is with the motherboard. As long as it's consistently the same memory module (the 3rd one out of four), it looks like more of an issue with the SPD chip that's on that single memory module that fails to switch the SPD bank.

Thank you. Somehow SPD bank switching fails to work properly in your 3rd memory module. Without proper bank switching it's not possible to detect DDR5 memory module details.

Usage is for a lifetime, but you only get updates and technical support for 1 or 2 years, depending on the license you purchase. https://www.aida64.com/licensing

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

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.

Sadly most laptops use Embedded Controller based proprietary interfaces (to measure fan speeds and temperatures) that are not published and so cannot be supported by 3rd party hardware monitoring software like AIDA64.

Thank you, we'll add that to the next AIDA64 beta build.

Can you please send me your layout (in email) including the .png files that may cause the issues with AIDA64 v7.50?

You can use it on both your PC and your boyfriend's (or spouse, child, parent, etc) PC as well, as long as you're a single user. If your boyfriend gets to like AIDA64, and he wants to use it for his own purposes, then he needs to purchase a license for himself as well.

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?