Fiery

Yes, it should still be there. However, you may need to unblock access to the file by navigating to the installation folder of AIDA64, finding the AIDA64.CHM help file --> right-click context menu --> Properties --> Unblock (checkbox) --> OK.

Thank you for your feedback

Thank you for the feedback

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

We've fixed the reported issues in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta

We've added the requested hardware monitoring item in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Regards, Fiery

Steam is not our software, so I have no idea how it works. It may use an internal module to measure FPS.

Thank you for the feedback. Try to enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. If it still doesn't work, then your memory modules are not DIMM TS capable.

It depends on what kind of operating system you're running. You can check the assignment of real and virtual cores on the bottom of the Motherboard / CPU page. CPU utilization means the average CPU utilization. CPU temperature is measured by the motherboard sensor chip, and it is usually an external CPU package temperature. Regards, Fiery

Thank you for the feedback

We will implement support for 360 TS in the next AIDA64 beta update due next week. Regards, Fiery

Thank you. It's puzzling. I think we have to leave it as is now. If the issue returns, please check the DIMM temperatures and SPD memory details for all DIMMs using AIDA64 + CPU-Z + HWMonitor + HWiNFO64 as well, to check if this is a hardware collision that affects any software polling DIMMs, or a bug in AIDA64. And then please let us know about the results in this topic

AI Suite collides with AIDA64, and it is especially dangerous on ROG motherboards like yours. Such collisions could well cause system instability, so it would be best if you completely uninstalled AI Suite.

Do you have Asus AI Suite installed?

Thank you. Do you happen to have any other software or service running in the background that you reckon might also monitor DIMM thermal state? Or are there any kind of monitoring, tweaking or overclocking software, or remains of such software installed? Like AI Suite background service?

Are you running your CPU at the same settings (clock-wise) than before? Is it similarly overclocked? Is the memory running at the same clock and uses the same timings as before?

Thank you!

Thank you. That still seems to be a mysterious issue. It does affect multiple users, not just you, so it should be a bug in AIDA64. Can you please check if HWiNFO64 can read all DIMM temperatures reliably, over a few minutes period of time?

Thank you. The register output seems fine. Are you sure you don't have a custom TJMax value configured in AIDA64 / main menu / File / Preferences / Hardware Monitoring? The TJMax setting there should be set to Automatic, since your CPU can provide the right TJMax value via a CPU register.

That option no longer works, and we'll remove it soon. We're now using a single set of icons. Regards, Fiery

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

Yes, it does. It doesn't utilize the middle steps at all. Of course if a certain software doesn't measure the CPU clock the right way, it could show something that your CPU doesn't do at all. If during the CPU clock measurement the CPU switches its multiplier up or down, and the measuring software is not aware of that, the measured CPU clock will not reflect the actual state of the CPU, but something in between the old state (before the software started to measure the clock speed) and the new state (after the software is done with the measurement). The measured MHz value will be in between the old clock and the new clock, so it will reflect a multiplier that the CPU may not switch to, at all, ever. Not to mention the issue that I've mentioned before, ie. when the CPU clock measurement code itself causes the CPU to switch its multiplier up or down (most likely up).

As I've explained above, clearly AIDA64 + CPU-Z + HWMonitor measure CPU clock using a different method than what Task Manager and MSI Command Center use. I still have no other choice but to stick to my stance about AIDA64 (+ CPU-Z + HWMonitor) measuring CPU clock using the right (proper) method. I don't know what exactly the other 2 software do, and frankly I don't care, since I'm 100% sure they do not use a superior CPU clock measurement method than our software. Why do you need your CPU to run at e.g. 3500 MHz when you overclock it? I thought you want it to be quick. It is quick even when it is running at a fixed clock all the time -- as long as that single clock speed level is high enough, of course.

We've just rolled out the first AIDA64 beta with proper handling of DPI scaling, as well as fix for the screen resolution detection issue: https://www.aida64.com/downloads/latesta64xebeta A few icons are left to be updated, and we also have to fix a few issues in the Monitor Diagnostics module. Let me know how it works on your system

We've just rolled out the first AIDA64 beta with proper handling of DPI scaling. In other words, it is fully DPI aware now: https://www.aida64.com/downloads/latesta64xebeta A few icons are left to be updated, and we also have to fix a few issues in the Monitor Diagnostics module. Let me know how it works on your system