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!

1) Yes, correct. 2) iCUE and 3rd party monitoring software don't work together, but it depends on the actual situation and devices in question whether the issue is minor or major. You need to exploit the 30-day trial period that we provide for AIDA64 in order to find out that on your particular configuration how deep the synchronization issue is. We'd be happy to work on it, but as I've explained in other forum threads, the ball is now rolling at Corsair's and they don't seem to want to play the game with anyone 3) Without iCUE AIDA64 can read up to 4 thermal measurements from Com

In the latest AIDA64 version of 6.33, there's a Reset Position button in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel. When you press it, AIDA64 will move the SensorPanel to the center of its Preferences window.

When it's an EVGA video card, I'd trust Precision X1 over 3rd party software. So it'd be important to verify what PWM setting is indicated by Precision X1.

It's hard to tell since we have no technical information on how CPU temperature is measured by Afterburner or iCUE. Modern processors implement several methods to measure CPU temperature, and you need to decide which one you take into account. The highest temp, lowest temp, the average of them, it's up to you. BTW, even on top of the ones you've listed there are the CPU core temperature readings too -- just to make it even more complicated I'd personally trust HWMonitor in this case, but it may be worth checking HWiNFO64 too.

That's how Windows reacts to AIDA64 forcing the SensorPanel (and OSD Panel) windows to always on top. A behavior that was recently appeared in one of the Windows 10 updates. All we could do to mitigate it is to make it less frequent that AIDA64 reclaims the always on top setting for SensorPanel and OSD Panel. It seems everytime you press a right-click on the Desktop, Windows disables (takes away) the always on top setting from SensorPanel and OSD Panel. AIDA64 will then detects that and tries to claim back the setting.

Maybe a full graphical remote control solution could do that for you? Remote Desktop, TeamViewer or VNC?

That's odd then. Do you think you have another software running in the background that may collide with AIDA64 about sensors polling? Something like AI Suite or a 3rd party monitoring application?

Thank you, we've added those devices to our PCI device database.

Make sure to have the option called SMBus access through ACPI disabled (unchecked) in AIDA64 / main menu / File / Preferences / Stability.

I'm not sure if it's possible, since I don't think Windows provides a method to control screensaver activity per-monitor.