Fiery

What version of AIDA64 are you using?

Thank you for your bug report. Please submit a report from the About page, and we will fix the reported issue in the next AIDA64 app update.

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

It's usually because the display DPI setting keeps changing (for whatever reason). You need to make sure the DPI is constant since SensorPanel needs to follow DPI scaling setting to look properly awesome on all displays.

That is caused by the always-on-top SensorPanel setting. When you press a right-click on Windows Desktop, Windows 10 (for whatever reason) take away the always-on-top state of the SensorPanel window. AIDA64 will then regularly have to check if the always-on-top setting is still enabled for the SensorPanel; and when it's no longer enabled, it will reclaim it. That's when Windows 10 (again, for some mysterious reason) hides the right-click context menu. Other than making the check for always-on-top setting less frequent, we couldn't find a workaround for this issue so far

Ryzen Master uses averaging and post-processing of thermal readings while AIDA64 reports the direct and immediate temperature readouts. We believe it makes no sense to process the thermal readings and make them artifically "feel" or look different to the immediate readings. AFAIK throttling in the sense we're used to that term on Intel processors is not implemented in AMD processors. I suppose what you refer to is the way Ryzen processors alter their own CPU core clock frequency depending on the actual thermal state. If you mean that, then it'd useful to try the AIDA64 System Stability

AIDA64 can measure the thermal readings coming from Farbwerk 360.

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

We don't use locking for our shared memory, but we also haven't got any complaints about it working incorrectly. When we use OpenFileMapping / MapViewOfFile, no such anomaly occurs at all.

We're working on it. Meanwhile, please avoid posting a single issue into multiple topics. I've removed your other topic.

It's quite complicated, since the order is determined by the type of device first and then the order (index) inside a particular device group. Usually external drives appear in the last group to avoid the issues you've described. Maybe your drive appears as an internal drive even though it's an external one? We'd need to have a better understanding of what's going on about that in order to fix this. Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your p

Maybe the issue is the ANSI (non-Unicode) codepage you have selected in the Windows Regional settings?

Thanks a lot, got it! We'll fix the issue in the next AIDA64 for Android app update.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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

Can you please submit a report from the About page? That way we could check the CPU identification strings as well. Thank you in advance!