Fiery

Please try this link: http://users.aida64.com/alphacool_lcd_driver_2_1.zip

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Thank you for the feedback, your panel looks great

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

Then I'm afraid the issue must be due to a CPU pecularity that is currently unknown to us. So I'm unable to help you

We've seen such anomaly before, but we haven't yet found the root cause of it So right now there's no fix for it. You can however apply a formula (e.g. a multiplier of 10x or 20x or 100x, etc) on the measured values in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction, if you deem it would help to fix them up. Edit: One possible cause could be that you've disabled SVID in the BIOS Setup. If that's the case, then try to enable it again, and check if it helps about the power measurements. Regards, Fiery

The difference between #2 and #3 is basically the protocol that a software has to use to push a bitmap image (a LCD/SensorPanel frame) to the display. With #2 it's trivial, since Windows does everything for you. All you need to do is open a new window and draw something on it. The user can move the window from the main monitor to the secondary monitor. No hassle at all. With #3 however, AIDA64 has to push the bitmap image data to the display, usually via a USB connection, using the protocol the device dictates. That's where things get quite complicated, since most devices have a proprietary protocol that only that device uses. That's why AIDA64 supports over 50 different LCD devices, in most cases with a separate protocol. Also, several external displays (like picture frames) simply do not have a protocol that could be used to pass image data from a Windows PC. They may support copying files over a USB connection, but that involves updating the internal flash memory of the device, which is not a good idea to perform too frequently. As for the tablet idea, yes, you're right, mounting a tablet permanently into your PC case is probably not a good idea. If you want to mount the display into your PC case, then I guess the best solution may be to try to find a relatively small old TFT LCD screen, and hook it up to your DSub or DVI output, and use it as a secondary monitor with AIDA64 SensorPanel. Of course there are some other alternatives, certain dedicated LCD screens that are case mountable, but usually they cost an arm and a leg, despite the fact that they're not that large Like USBD480 from LCDInfo: http://www.lcdinfo.com/products/usbd480-lq043.html USBD480 is fully supported by AIDA64, thanks to the fact that it features a very fast and efficient USB protocol. It's not that large though. I suppose you're looking for something considerably bigger than that...

1) Tough issue. These days what you can get easily is usually too expensive and also too small for your needs. When it comes to large colour LCD screens, we generally recommend getting an old Android tablet or iPad and use RemoteSensor or Odospace, or to simply go for an old TFT LCD monitor that you can hook up to an unused DSub or DVI connector. The monitor solution would enable you to extend your Windows Desktop to that display, and use AIDA64 SensorPanel instead of the LCD module. It enables more flexibility too, since you can move any window to that screen. And no, not any LCD displays would work. Most of those that support bitmap transfer through the USB connection should work. 2) The following special temperature readouts of Maximus VIII Extreme and Formula boards are supported by AIDA64: T_Sensor1 EXT_Sensor1 EXT_Sensor2 EXT_Sensor3 The rest (T_Sensor2 and T_Sensor3) cannot be measured via AIDA64 right now. 3) I'm afraid we're not experienced that much in water cooling setups, so you have to ask that question on a different forum. But, as long as you can connect the flow meter to a fan header, and it reports the flow rate just as a fan would report its RPM measurement, then you can handle the device in AIDA64. The reported value would still be RPM though. You can use the Correction feature of AIDA64 (main menu / File / Preferences / Hardware Monitoring / Correction) to apply an offset or multiplier on the RPM readout. Regards, 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!