Fiery

Did you keep your "old" DDR4 memory modules when you've upgraded your CPU? Did you only change the CPU or the motherboard too?

Thank you for the feedback

In case DIMM temperature readings fluctuate by showing a weird anomaly, then it is most likely due to a collision on the SPD SMBus. Are you running any other hardware monitoring, tweaking or overclocking software in the background?

Only the latest AIDA64 beta build implements full support for GeForce GTX 1080 and GTX 1070. Make sure to upgrade to it: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

GPU1 should be your primary GPU. Do you have more than one GPUs in the system? If yes, then make sure to enable the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability.

It should already be available as GPU Clock in the list of items you can place on your LCD.

Thank you for the feedback

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

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

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

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 --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Then 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. Also, please create a screen show of Asus' own hardware monitoring utility, of the page where it shows the temperature and voltages readings. That way we could have a reference list of readings that we could use to calibrate the temperatures and voltages in AIDA64. In case you cannot find such Asus utility, then please create a photo of the H/W Monitor page of the BIOS Setup (UEFI Setup) for the same purpose Thanks, Fiery

1) That's an issue of character set differences between Windows and the LCD device. We usually recommend against using the degree character simply because it takes precious space away from useful readings. If you have a 4x20 LCD, it's only 80 characters to display something useful. I wouldn't waste any characters on a degree character 2) Same issue as #1: alphanumeric LCDs should be used to display vital information, not just static labels.

You only need to worry -- slightly -- in case your CPU throttles under heavy load. You can check the throttling state (in %) in AIDA64 / main menu / Tools / System Stability Test.

CPU Package is not Tcase. It's what was explained on the other forum. Processur (or "CPU") is provided by the sensor chip integrated on your motherboard. I can't comment on Intel XTU, since it's not our software. It may use an offset value of minus 5 Celsius on the actual CPU Package reading though. But that's just a theory.

AIDA64 doesn't use a fixed COM port, but instead it detects which COM port is allocated by the Sure LCD. But maybe with your device it fails to work for some reason. Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. Thanks, Fiery

CPU Package is the temperature provided by the CPU itself. It has a built-in digital thermal diode that provides the temperature reading that AIDA64 then displays as "CPU Package".

Most digital picture frames cannot take images via a USB connection, hence they cannot be supported by AIDA64. The 2 exceptions are Samsung SPF and AX206 LCDs. In the range of 7-8 inches it's probably best to use the AIDA64 RemoteSensor feature with an old tablet running Android, iOS, Windows RT or another mobile operating system. Another solution might be to pick up a small USB-connected LCD, using DisplayLink, or one that is simply connected as a regular monitor via DSub, DVI or HDMI. The big advantage of such solution is that you can extend your Windows Desktop to it, since it would act as a secondary monitor to your system. You could then have any window displayed on the small monitor.

Renaming shouldn't be a problem about any sensor items. What you can do however, is to backup your AIDA64.INI settings before the issue, then when the issue happens and you go to AIDA64 Preferences to readjust the sensors, just push the OK button on the Preferences (not to rename the sensor item to your preference), and check what happens. Also backup the AIDA64.INI after doing that. Then rename the sensor item, and do another backup of the AIDA64.INI file. It would be very interesting to see those 3 states of the AIDA64.INI file, and it may just reveal the root cause of the issue.

We'll add PCH +1.8 V as a sensor item in the next AIDA64 beta update. As for the other voltages, you're right, not all of them can be monitored. Only those can be monitored for sure that E-LEET can monitor, since it's the reference software made by the same guys who made your motherboard The rest may or may not be monitored by the motherboard. Except for VSA which should be VCCSA, and it's already monitored by AIDA64.

Thank you for the dumps. It's odd, you cannot see anything strange in there. Can you please check if the information on the Computer / Sensor page changes too? Or the one displayed on the Storage / SMART page? Also, if you have space on your Windows Desktop, it may be a good experiment to check what happens if you put the AIDA64 OSD Panel there, with the SSD temperature as an OSD item.

Thank you, we'll remove Temperature #2..#4 in the next AIDA64 beta update

Please create an ATA Dump and also a SMART Dump before and after the issue happening. Maybe the issue is related to computer sleep state? E.g. when your computer comes back from sleep, the issue happens?

Yes, since we've extended the Dell SMI temperature slots from 5 to 8. Which of the temperature readings are stuck? Are you absolutely sure they mean nothing and should be removed?

Thank you guys for the feedback. We'll fix it up and roll it out as a new beta update in 2 or 3 days from now. I'll post a message into this topic once the new AIDA64 beta is available for download

Thank you for your feedback