Fiery

Your particular video card most likely requires additional tricks over regular RTX 3080 cards to make all fans to be measured. First of all, make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. 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. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

You can download other users' SensorPanel layout files in the following forum topic here:

Thank you for the test. We're still investigating this. Most likely this is a collision between AIDA64 GPU detection module and the latest Windows 10 updates... Not easy to figure it out...

Thank you for your suggestion, we'll look those APIs up and do some research on various Android devices about them.

Thank you for your feedback. It's actually absolutely normal. On many 4K devices and 4K displays, Android itself uses 1080p resolution for apps, and will only switch up to the full 4K resolution mode when you're watching a movie or looking at photos.

That's the LCDsysinfo for GOverlay device that is not supported by AIDA64 (as stated above).

Stunning!

I apologize for not being able to resolve this issue for you to date. I'll do my best to take care of you from now on. Please let me know at which page do you have AIDA64 open at where you experience that issue. Or whether you get this when you have SensorPanel, LCD or OSD Panel activated. If you've already provided a certain amount of such details to our Tech Support, please refer to your ticket number and I'll look it up.

That's quite odd then. Well... I suppose it would be best to consult overclocking enthusiasts on XtremeSystems or other similar forums about your liquid cooler setup and whether it's normal to have such high thermals with your particular setup.

AIDA64 currently does not support NZXT Smart Device v2. Do you know where can it be purchased?

I've sent you a private message about this.

The issue must be one of the Catalyst video driver interfaces that we started using between v5.99 and v6.00 at one point. Please let me know the operating system you use (and whether it's 32-bit or 64-bit OS) and we'll build a similar configuration and check the Catalyst 12.4 + HD4670 combo to find out what exact video driver call we should avoid there.

Are you using PNG or JPEG images? Are there any particular pecularity about those images? Maybe they're too large files or have special embedded data in them?

What about the other CPU related temperatures like CPU Package, CPU GT Cores, CPU IA Cores? Do all of them reflect a high temperature? Please note that laptops tend to work at much higher CPU temperatures as desktop computers, so it's not uncommon to see 70+ Celsius for laptop CPUs. I don't think you have anything to worry about. As for the "CPU" temperature vs. other thermal readings: there's a chance that in your case the laptop provides a CPU thermal reading that is more the temperature of a system component (like motherboard) than the actual thermal state of the CPU. With laptops the ACPI interface that we use to measure CPU temperature can be dodgy sometimes, so it's best to focus on the other CPU temperatures that the CPU itself measures using its on-die thermal sensing logic. Those direct CPU temperatures are the core temperatures, CPU Package, CPU GT Cores, and CPU IA Cores.

If it's possible, please send us your AIDA64.INI file in order to let us try to replicate the issue by having the same OSD configuration as yours. If you cannot attach it to a post here or you would rather send the file in email to us, please let me know in private message.

Some portion of that system load is due to Odospace. Try to turn it off and as aszc suggested, check RemoteSensor instead. Let me know if it helps to put the CPU load down considerably.

As far as we know, RTSS support is properly implemented on our end. So in case RTSS fails to provide the FPS values using the standardized method, then I'd try contacting RTSS author to find out what could be wrong on his end.

I'm afraid wireless mice and keyboards do not feature such a standardized smart battery interface that UPS'es and notebook batteries feature. Hence it's not possible to measure their battery charge level using a unified method.

Please let us know what exact sensor do you have in HWiNFO that you miss from AIDA64. We'll try to add those readings into AIDA64 too.

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

Under heavy load such small amount of throttling is considered acceptable for a high-performance + overclocked system like yours. I suppose the only way to avoid it in your case would be to switch to liquid cooling.

Is your issue related to our app AIDA64?

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the first 20 lines of the results (up to the end of the last line starting with DMI) into this topic. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

We will fix the sensors issue in the next AIDA64 beta update. I will post a message into this topic once the new beta is available for download.

Thank you for the data. I'm afraid we cannot find the root cause of the issue. We'll need to order a 980 Pro SSD unit and try to replicate the issue using it.