Fiery

Can you please post a picture of how HWiNFO displays GPU power draw in Watts?

No problem, and thank you! I'm afraid we cannot find the missing readings in those dumps. Maybe your motherboard has a 3rd sensor chip that we didn't look for before. If it's possible, please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta And post an updated ISA Sensor Dump. We've added a deeper scanning for sensor chips for Gigabyte X299 motherboards in this new AIDA64 build. Maybe this time it will pick up a "ghost" chip

Meanwhile, we've rolled out a new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta In this build we've added a new option to the Preferences / Stability page to let you disable EC (Embedded Controller) polling. That way you would lose a few sensor readings, but maybe it helps to get around the latency issues. Also, in this build we've added GPU clocks as Correction items

Please 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. Let me know if it helps

We've implemented a workaround for this issue in 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. Let me know how it works

Thank you for your feedback

It's easy to check whether the sensor module or the LCD module causes the high latency: simply just try turning off all LCD modules, and try to enable the SensorPanel. Please let me know how it changes the latency. Note that we've seen latency issues caused by the Logitech LCD API in the past. There's a chance the whole thing isn't rooted in AIDA64 at all. As for the missing features, we'll work on them GPU clock correction should come first, it's relatively easy. GPU Watts usage, I'm not sure about, since it should be supported by AIDA64 already. What video card do you have? As for sensors individual enabling/disabling: we haven't really dealt with that on the basis that the Computer / Sensor page was designed to provide just a quick glance on all the readings. If you want to further customize it, then you can go OSD Panel, where you can pick the items you want to have displayed. And, if you want to go one more step further, then there's SensorPanel and LCD, where you can not only pick which item to show, but also the visual representation of those items. About sensors AIDA64 Engineer will behave similarly to AIDA64 Extreme, so it doesn't make much sense to deal with it.

Try to do a complete uninstall again. Uninstall AIDA64, remove all the files belonging to it, restart Windows (this is an important part to get rid of the old kernel driver). After system restart check if there're any files left over. Then install the latest beta, restart Windows again, and check if it works.

On your motheboard, VRM temperature reading should be there, as long as you're using the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta The rest of the readings in HWiNFO (Auxiliary and AUXTIN2) both look bogus readings to me, and so they shall not be displayed at all.

Power efficiency is calculated using a special formula that's specific to not only the PSU manufacturer, but also PSU model/SKU. And we don't consider those formulas scientific at all. So we've decided to stay away from dealing with that. The formula of course involves the power input value, so AIDA64 will not measure or detect either of them. But, it should still show the power out (both Wattages and Ampers) for the voltage rails of Corsair PSUs using Corsair Link interface.

Thank you for your feedback

What video adapter do you have, and what version of Windows do you have installed?

We wanted to wait to tell final judgement on this issue until we have more info and more input. It's a Windows 10 bug indeed that plagues Windows 10 Insider Build 16273 and 16275, but only the 64-bit editions. It prevents certain software to install and use its otherwise perfectly fine kernel driver. The issue affects several software, not just AIDA64. We're already working on a workaround, but we also expect Microsoft to fix this up soon. I'll post a message into this topic once we have an update.

What motherboard do you have?

A couple of possible explanations: 1) Your Windows user no longer has administrator privileges. 2) AIDA64 cannot load its kernel driver for some reason. Due to lack of permissions or missing files (KERNELD.X64 should present in AIDA64 installation folder). 3) Something got mixed up after you've performed an AIDA64 upgrade. In most cases simply restarting Windows resolves this. Please start with #3, and then go backwards up to #1

We've added the mentioned new right-click menu option in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

The mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

If you mean that about the SensorPanel, then the first two are already supported. Hold down the Ctrl key and you can select multiple items to move or edit (modify), straight on the panel. Or, you can use the SensorPanel Manager, where selecting and altering/removing/reordering/hiding multiple items is also supported. An intuitive way of altering Z-order is quite a challenge. But you can already do that using the SensorPanel Manager (Move Up and Move Down buttons). As for the 4th idea, I'm not sure what you mean. Do you mean like a magnifier to zoom in into a certain spot on the panel? Or to e.g. click and hold a certain item to push it down, in order to reveal another item that was previously hidden under it, due to incorrect Z-order?

It's a good idea indeed. The problem is that the current Alerting module can only check for changes against a pre-defined value. So you could set an IP (if there was such an alerting item defined), and when the current one differs from it, then an alert could be fired. But, the current solution wouldn't be able to recognize the new IP then and check for changes against it from then on. So first we need to make the whole thing more sophisticated by implementing a simple "change" alert trigger, besides the current "above X" and "below Y" triggers. Although that one wouldn't be suitable for the rare case when the IP changes while AIDA64 is not running...

We'll check how to do that. We haven't really dealt with such a bar style yet on the basis that in our opinion it would make the visual impact of the SensorPanel a bit "too much", a bit like a parrot

The basic issue is that even with EC traffic, such high latency is not supposed to occur. Other users with Asus motherboards having an EC chip do not see such anomalies. So it must be something about your computer IMHO. Maybe you've got another software running in the background that collides with the EC register readout activity of AIDA64?

When you offer tons of flexibility in designing a visual layout, it's a great challenge to come up with a UI that is both easy-to-use and easy-to-navigate. It's a bit like sitting in a Boeing 737 cockpit and complaining about the unfriendly layout of the dashboard

I'm pretty sure that activity is not related to the clean AIDA64 build that you can download from our website. Your AIDA64 copy may be infected or otherwise altered (cracked, hijacked, etc). Basically there are 2 distinct internet activities that AIDA64 performs between the user's computer and our servers. The first one is related to the auto-update feature, and should happen in the frequency you choose in AIDA64 / main menu / File / Preferences / General / NetUpdate. You can completely disable the auto-update check there, if you wish. The other activity only happens if you have the External IP Address sensor item placed on your OSD Panel, SensorPanel, LCD, log file, or used as an External Applications item. That activity is repeated every 15 minutes while you keep AIDA64 running. It simply pings our servers to obtain the external IP address of the user's computer. The repeat frequency is set to 15 minutes in order to avoid putting too much pressure on our servers.

Without EC (Embedded Controller) support, you'd lose some of the sensor readings you may have places on your LCD layout. So it's not a good idea to disable EC support as long as you'd prefer to have all sensor readings.

Thank you! It seems the issue is that the HDD serial number fields aren't properly populated, and AIDA64 filters out 2 drives you've got due to similar serial numbers. We'll fix the issue in the next AIDA64 beta update due in cca. a week from now. I'll drop a message into this topic once the new build is available for download.