Fiery

If you have the OSD Panel enabled, it is displayed quicker than if you first had to navigate to Computer, then Sensor... If you don't have it enabled, then right-clicking on the AIDA64 System Tray icon --> Show OSD Panel will display the OSD Panel quickly. And you can still use the hot-keys as well. If you mean quickly glancing on sensor readings on a new system, then I agree, the Sensor page is great and superior to deep-customizing the OSD Panel or SensorPanel. Then again, you seem to bring up conflicting issues and situations. On one hand you're advocating for a deeper customization of the Sensor page -- but on the other hand you find it quicker to go to the Sensor page for a quick glancing on sensor readings. If you need something quickly, customizing Sensor page, OSD Panel or SensorPanel are equally time consuming in my book. If you have time to customize the Sensor page, then -- at least the way I see it -- you can spend that time on customizing the OSD Panel or SensorPanel instead. Maybe I miss something, but I still cannot see the real use scenario where customizing the Sensor page is superior to making your own layout for OSD Panel or SensorPanel.

You can either manually launch AIDA64, minimize it to the System Tray, and then you can use the hot-keys to show/hide OSD Panel or SensorPanel -- or you can configure AIDA64 to be automatically launched at Windows startup, as well as you can configure it to be started with its main window automatically minimized to the System Tray. Either way, if you want to use the Sensor page, OSD Panel or SensorPanel features, AIDA64 first needs to be started somehow.

It's still not clear to me why you cannot use the OSD Panel or SensorPanel instead of the Sensor page. You can configure a hot-key to show/hide them anytime you want, so it wouldn't occupy any desktop space...

That's not an option, since new versions bring other fixes, improvements and new features. We need to make sure everyone is satisfied somehow. Which is not easy when you have a popular software like AIDA64

Noone but a few enthusiasts read the changelog. And the change will be included in the next stable release as well, and its changelog doesn't cover all minor changes. We'll see how users will cope with the new way the Sensor page would work.

The problem is that when we display the 2 readings in the same line, it looks very crowded with both the Celsius and Fahrenheit readings. So we need to apply the Fahrenheit option (in Preferences / Hardware Monitoring) to the Sensor page as well. But then the problem is that existing AIDA64 users are used to having both Celsius and Fahrenheit readings on the Sensor page, and they may not be able to quickly find the option to switch between Celsius and Fahrenheit readings. So we may need to add a new button to the toolbar to make that setting more visible to users.

Okay, then I misunderstood your post. No problem, no need to merge posts or topics. We will however need to rethink some of the thermal measurement methods to make sure everyone is satisfied with the secondary NVMe temperature measurement and indication.

You've proposed in the following other topic that the 2 lines should be joined together: And above you've proposed the same idea.

Yes, but it's not a fault, but a peculiarity.

Please avoid posting a single issue into multiple topics.

You're the first one to bring that up in 19 years So I don't think it's that confusing to users.

That setting doesn't apply to the Computer / Sensor page, but only for the hardware monitoring modules (Sensor Icons, OSD, Desktop Gadget, LCD, SensorPanel).

Thanks for the feedback

Thank you for your feedback. Yes, certain NVMe SSDs are capable of measuring 2 different temperatures. The second temperature is most likely indicates the SSD controller's die temperature.

Both thermal readings are valid for certain NVMe SSDs. It makes no point to hide any of the valid readings.

Only now Here it is: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works for you.

We've fixed the issue in the latest AIDA64 beta build available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

CPU current is read from the EC (Embedded Controller) on your motherboard, using an undocumented register. The method is proven to be properly working on previous Asus motherboards with LGA115x socket, but maybe it's not 100% reliable on your motherboard. Have you noticed any pattern in why causing the CPU current value to disappear, or what may cause it to appear again? Maybe under heavy load it disappears and then reappears once the heavy load is gone?

Thank you! If possible, please send us a photo that shows all temperature, voltage and fan speed readings in the UEFI Setup (BIOS Setup). Thanks in advance!

Thank you. 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

I'm not sure how to talk to that mouse, but we've ordered one and we'll try to figure it out I'll let you know in this topic once we have a new AIDA64 beta build for you to check out.

No, since only the AX1600i is available in stores so far. We're still waiting for the AX850i to become available.

We've tried to find out where those values come from, but no luck. If someone could chime in with some technical information, we would be glad to implement it.

What subtest(s) do you have enabled in the AIDA64 System Stability Test when it indicates overheating?

It may be because of overheating of the CPU and/or GPU in your PC.