Fiery

Thank you for your feedback

Thank you. That's rather weird then. Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post.

Since they both will be displayed on the Sensor page, I don't think we need to replace anything Whichever you don't like, just ignore it

What version of BSPlayer are you using? BTW, we've checked it with BSPlayer 2.70 Free, and it displays the media title properly in AIDA64.

That look odd. Do you happen to have Low-level PCI bus operations or Low-level SMBus operations or Low-level sensor operations disabled in AIDA64 / main menu / File / Preferences / Stability?

Processes: We of course have the code to enumerate running processes. I just find it quite complicated to configure it that way. E.g. if you want to configure it for a particular game, you need to launch the game, go back to AIDA64, find the process in the list of processes, etc. To do that with all the games and applications you use on your computer is quite a task. Not to mention you need to do that in the future with newly installed games/applications. Let's just say it's not a feature we would see implemented in AIDA64, unless there's a very easy way of detecting the computer state. Duty cycle: Fan duty cycle is quite misleading, since when the duty cycle is configured and then detected at e.g. 30%, it doesn't mean the fan is actually spinning. Focusing on the RPM is a lot better, since that way you can be aware of a stopped or clogged fan. VLC: I'm sorry, but both HTTP and Telnet protocol is way too overkill to be used in the AIDA64 hardware monitoring module. And DBus is not supported by Windows.

Thank you

It seems on your particular motherboard model the Vcore reading has to be multiplied by 1.2. We'll implement that in the next AIDA64 beta update

Thank you for your feedback, I'm glad you like the way we steer the development of AIDA64

Those temperatures are reported by AIDA64 too.

There seems to be no classic sensor chips in your system, or they're connected to an IPMI BMC. Have you tried to check the Computer / IPMI page? Maybe sensor values are reported via IPMI on your system. Regards, Fiery

Thank you for the feedback. The limit has to be fixed, so it will be increased from 10 to 25 in the next AIDA64 beta update

1) Smooth transitions and animations are not supported because of the limitations of the LCD rendering engine. It's really not designed to handle such effects and it doesn't support complex associations between slides/pages. 2) It'd be quite difficult to automatically detect which type of usage is currently going on on the computer And due to multi-tasking, detecting the starting or stopping of certain processes could be misleading too. 2) VLC is not supported at this time. Do you have a sample code that can take such details from a running VLC process? BTW, Winamp should be able to play movies too -- although it's not the ideal tool for the job 3) It's because fan duty cycle is a misleading value that shall be ignored. You should rather focus on the fan RPM readings. The GPU duty cycle was implemented only because certain video cards only support duty cycle detection, and doesn't support fan RPM measurement. For most motherboard fans both are always supported, so we only deal with the RPM measurement for motherboards. 4) Please send me your updated French language module in email, and I'll take a look into those changes Thank you!

Thank you, we'll fix that issue in the next AIDA64 beta update

We've contacted MSI to find out what causes the discrepancies between the information they've provided us, and the way their own monitoring software works. Meanwhile, we've added the missing +3.3V reading 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.

The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

The above mentioned new AIDA64 beta build is available for download 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.

The above mentioned new AIDA64 beta build is now available for download 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.

The mentioned new AIDA64 beta build is available for download 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.

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 if it helps.

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 fixed the 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. Regards, Fiery

Thank you for your help! It's always great to work with guys skilled in both electronics and C++

Please use MSI's own software as a reference on MSI motherboards, and Asus' own software as a reference on Asus motherboards. We'll add CPU VID voltage below the CPU Vcore reading to the Sensor page as well, so you can see both values listed.

We follow MSI's recommendations on how to handle the sensor registers on MSI Z270 motherboards. What exactly is the issue about the Vcore? Does MSI's own monitoring software measure a different value or the same value?