Fiery

Once NetUpdate downloaded all files and asks you to let it restart itself, please do not let it do so just yet. Instead, go to the AIDA64 installation folder, and check whether there's a file called AIDA64.EXE.NEW in there. If not, then I guess AIDA64 has no permissions to write its installation folder. In which case it may be best if you could try moving the AIDA64 installation folder to e.g. C:\ That may help about the auto-update issues. Alternatively, you can try backing up the AIDA64 configuration file (AIDA64.INI) and license file (PKEY.TXT), both from the AIDA64 installation folder, then uninstall AIDA64, then reinstall it to C:\AIDA64 folder.

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

Thank you 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 how it works

Thank you. It's quite puzzling at this point We've tweaked a bit on it, but we're not 100% sure whether it makes it better or worse. Please check it out, and let us know how it works now. https://www.aida64.com/downloads/latesta64xebeta

Those measurements are obtained via the NVML API, which is difficult to utilize from our software. We will need to work more on it, and implement special tricks to use NVML, and so you can have the same GPU power draw measurements in AIDA64 as well.

Thank you. We've done a number of test runs with different display configurations, all in horizontal arrangement, and couldn't reproduce the issue We may need to build a more similar setup to yours, in terms of operating system type, and the same display resolution as well. Please let me know those parameters, and also the approx. placement of the SensorPanel on your Windows Desktop. Alternatively, try to place the SensorPanel where you prefer it to be, close AIDA64, open Registry Editor (Windows key + R --> regedit), navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 And let me know the value of these entries there: SensorPanelPosX SensorPanelPosY Having those coordinates, along with the exact resolution of both your displays, and the approx. coordinates you wish to have the SensorPanel placed should give us a bit more idea on where things may go south about the SensorPanel position restoring on your configuration.

As I've mentioned above, any "lite" or cut-down version of AIDA64 would cost the same as the current AIDA64 Extreme edition. We simply cannot lower the base price, since it wouldn't be a sustainable business model for us.

Thank you for the data. The measurements comes via the NVML API, which is difficult to utilize from our software. We will need to work more on it, and implement special tricks to use NVML.

Thank you for your feedback

Thank you for your feedback. PCH Diode temperature comes directly from the PCH, using its on-die thermal diode. PCH temperature comes from the Embedded Controller chip of your motherboard, and may or may not match the PCH Diode temperature readout, depending on the thermal diode solution used by your motherboard.

Yes, it's the same issue about EC bank switching

The problem with that is the same old issue about Windows: some system parameters/status can be detected for only logical drives, like free drive space. While some other parameters can only be detected for physical drives, like disk activity, disk temperature, SMART attributes, etc.

Is the Vcore value always 50% of the real value?

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.

Try to uninstall and then reinstall ForceWare, using the latest WHQL release. It should help to fix up the seemingly broken OpenCL stack. Regards, Fiery