Fiery

Thank you, we will fix the listed issues in the next AIDA64 beta update.

Thank you, we will fix the listed issues in the next AIDA64 beta update.

Unless developers of The Finals could let us know why they detect AIDA64 as a debugger, we cannot do much on our end. Please report the issue to them, and ask them to fix the issue in their detection method, or contact us directly in email to find a resolution involving both them and us.

Thank you! According to that dump, you should have GPU fan RPM reading on the Computer / Sensor page of AIDA64. If you cannot see it there, maybe it's because the fan is not spinning right now.

I cannot promise anything about this matter.

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

It doesn't work that way. Each GPU generation has its own interfaces and own measured values that they expose via either an official API or via undocumented/unofficial methods.

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

There's no offical, AMD-approved method to read that temperature on your video card. HWiNFO uses proprietary methods to go deeper, but we deem that quite risky since it may cause collision with the video driver.

Somehow your video driver thinks your video card has three 8-pin connectors. I'm not sure why, but my first guess is that there's a small glitch about this in your video BIOS. We can remove the 3rd entry if you could send us a necessary dump: in AIDA64 please press Ctrl+Alt+D --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

We've implemented the requested new option in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta

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

Try to update your AMD Adrenalin video driver. I assume you've got an AMD GPU.

2560 pixels is just one part of the equation. In case your laptop uses a higher DPI setting (which I assume it does, since it has a physically smaller screen despite the same resolution), it will scale the SensorPanel up so it would look wider and taller than on a similar resolution but physically bigger classic monitor screen.

We'll lower the minimum height of the SensorPanel to 10 pixels in the next AIDA64 beta update. I'm not sure how to achieve click-through since SensorPanel is simply another window, it's not opaque to user input

I know it costs $$ , but why don't you get a cheap external LCD or monitor that you can use to place your SensorPanel onto? Any old 15" or 17" LCD monitor would do, that costs $10 or so these days.

In AIDA64 please press Ctrl+Alt+D --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Please do it with both AIDA64 v6.92 and v7.20. Thanks, Fiery

Thank you for your feedback!

We cannot add such a sensor that your motherboard doesn't support or implement

I've just sent you an email about this.

What motherboard and CPU do you have? If you have any USB devices connected (that aren't a keyboard or mouse), try to disconnect them and check if it makes a difference.

You can alter the scale of each graph by that way easier and more dynamically than going to the System Stability Test Preferences and changing the graph minimum/maximum values there.

Yes, we had to remove the trackbars there to support both light and dark mode properly. There's still a hidden trackbar there, just try to move the mouse while you have the left mouse button pressed An Easter Egg of sorts to provide the same functionality than with the visible trackbar before.

A frozen window will not consume any real-time resources. However, hiding and then showing the SensorPanel may cause other issues when the system transitions between screen resolutions for example.

We've checked, and it's best to keep the SensorPanel visible but frozen.