Fiery

The current and power values could be misleading since they require scaling. The scaling constant are motherboard specific and not published at all, so AIDA64 uses a default value that may or may not be correct for your system. You can use the Correction facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction) to scale the CPU VDD and CPU VDDNB currents and powers in a way that you deem would make them report more meaningful and more realistic values. Sadly Ryzens implement such current/power telemetry logic that cannot provide an absolute Amper and Wattage measurement.

1) I'm really not sure what could be wrong, since the last time we've checked it worked fine. And it's difficult to verify the wiring remotely. Is there perhaps another software that supports the same wiring and protocol that you can check to find out whether it's a bug in AIDA64 or due to a hardware issue? 2) BSPlayer, Winamp and Windows Media Player are the 3 media players that are currently supported by AIDA64. 3) That's correct. Does SPF-07N support Mini Monitor Mode? Only those Samsung digital photo frames can be supported by AIDA64 that support Mini Monitor Mode.

Thank you! We will fix it in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download. BTW, not only the voltages but also the currents and powers are labelled incorrectly. VDD <--> VDDNB is reversed on all Zen 2 CPU based systems right now.

Minimum, maximum and average values are shown on the Statistics tab of AIDA64 System Stability Test. You can also use the Logging facility to track minimum, maximum and average values. As for 250W/300W vs. 125W, my point was that I don't think a single core (as shown by SIV64) can draw 250-300W on your CPU -- or any CPU for that matter. And when a reported value seems way off, I tend to completely ignore the values.

You need to update your SensorPanel in order to squeeze everything into the new panel's picture resolution and space. Usually it's not a quick and trivial job when it's a complex SensorPanel layout.

Please avoid posting a single issue into multiple topics.

I'm not sure what correctly means and why would AIDA64 show the highest measured value. I'm also not sure how one CPU core could possibly draw cca. 250-300 Watts (as shown by SIV64).

Are you using the latest AIDA64 beta build of v6.25.5434?

There's no generic rule or standard on that. You need to experiment a bit and watch how the values change when the SSD is under stress (e.g. doing a longer reading or writing session) and draw your own conclusion for your own drive.

We do not have such plans right now.

The first battery capacity value (labelled as "Capacity (Reported by Android)") comes from the Android profile of your device. It was encoded to the profile by the manufacturer of your device, and may or may not reflect an accurate value. The second value (labelled as "Capacity (From Database)") comes from the built-in AIDA64 hardware database, and should reflect the correct value.

In Photoshop try to do a quick export to PNG. That way the filesize will be less than 13 KiloBytes and will be easy to put on the SensorPanel. Let me know if it works out.

We've heard about such issues, related to PNG images exported from Gimp. If it's possible, please send me one or two of such PNG images that you cannot add to your SensorPanel in email to me. I'll send you my email address in private message. Thank you for your help!

GIF image format and any form of animations are not supported by the SensorPanel.

AIDA64 only supports a single Commander Pro unit.

Are you sure it's possible to 3rd party applications to put information on the LCD of the connector?

Please try to enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it makes DIMM temperatures appear properly.

What's the value reported by AIDA64, what do you reckon the accurate value should be, and what version+build of AIDA64 are you using?

What motherboard and CPU do you have, and which version of AIDA64 are you using?

You're right, it doesn't cause any issues, but of course we will fix this in the PCI database of AIDA64 in the next AIDA64 beta update.

The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta

It's implemented in the latest AIDA64 beta update available for download at: https://www.aida64.com/downloads/latesta64xebeta

We're not quite sure why it happens and at what point of Windows 10 development this was introduced, but when you right-click on the Windows Desktop or on a Desktop icon, Windows takes away the always on top setting from the SensorPanel window, and it wouldn't give it back after the right-click context menu gets hidden. The SensorPanel however detects that it no longer has the always on top setting (even though you have it configured in the AIDA64 Preferences for it), and it reconfigures its own window to have it back. It then causes the right-click context menu shown by Windows on the Desktop to vanish. Very weird, but so far we haven't found a perfect solution to get around this. Because if the SensorPanel window doesn't detect its own always on top state change, the always on top behavior will stop working after you press a right-click on the Windows Desktop or on a Desktop icon

Rendering the LCD layout could well cause power consumption spikes, since it consumes system resources to render the LCD layout.

Do you find a pattern across those different systems you've mentioned, like a common hardware component? Maybe they both have the same Radeon video card?