Fiery

AIDA64 currently only supports reading strings and DWORD values from the Registry, and put them on external displays (or SensorPanel, OSD Panel, etc). You need to find a way to write the Registry values into the following path: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\ImportValues And name them as: Str1 Str2 ... Str10 for string values, or: DW1 DW2 ... DW10 for DWORD values. As you keep updating those values in the Registry, the values get updated on your external display.

Thank you for your feedback. Please submit a report from the About page, and we will fix the reported issue in the next AIDA64 app update of v1.55.

Probably you have started AIDA64 once in the past, and its kernel driver got cached by the Windows kernel. If you want to make sure you have all files related to AIDA64 removed from your system, then scan your system for the following files: AIDA64.* KERNELD.X32 KERNELD.X64 And if you find any of those files on your system, make sure to remove them all.

Thank you for your feedback. When the liquid temperature reading becomes unstable, do the other readings (fan RPM, pump RPM) also become unstable? Or it's only the liquid temperature that has that issue?

Those are generic temperature readings that we cannot properly label due to lack of information for the motherboard in question. Do you have temperature readings in your BIOS Setup? If yes, then you may be able to figure out the proper labels for the thermal readings. In which case we can adjust the readings to make the temperature readouts more meaningful.

That one looks incredible Great job!

Thank you! Voltages still do not look correct though. If you would be so kind to help us fix them, then 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. Thanks, Fiery

Start the AIDA64 stress test (AIDA64 / main menu / Tools / System Stability Test), make sure to have only the FPU subtest enabled, press Start, and leave it running for a few hours. In case your computer keeps working properly with such demanding task, the PSU as well as other components work fine.

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

Thank you. Please check the latest AIDA64 beta: 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. I think the issue is that you don't have the necessary SiUSBXp.dll library installed on your system, or AIDA64 is unable to locate it. Can you please try to find that file on your system, and let us know the full path name for the file?

Edge is fully supported. We've just checked under Win10 1809 using AIDA64 latest version, and it performs the auto-polling just fine in IE, Edge, Firefox, Safari and Chrome as well.

I don't know much about the LED. You may want to ask around in MSI motherboard related forums about that. I would make sure to have the latest BIOS and latest Windows 10 updates installed, and use the system with factory settings. With those settings everything should work fine. Don't worry about the temperatures as long as the system is running fine and never slows down due to overheating.

Thank you!

Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic, or create a screen shot of that page.

Yes.

Exporting and importing settings is easy: just backup the file called AIDA64.INI that you can find in the AIDA64 installation folder.

I'm afraid there's no debug log that could work about this particular issue. Please try to disable all External Applications features (like Shared Memory), enable SensorPanel or OSD Panel, and add those items there that you've added to your shared memory. Let it run for a few minutes, and let us know if it behaves similarly to shared memory.

Please avoid posting a single issue into multiple topics. This topic is closed.

As it is stated on the Display / GPU page, the 366.0 GFLOPS @ 953 MHz figure is the theoretical peak performance of your GPU. The actual performance is lower in most cases.

Thank you for your feedback

Great news, thank you!

Well... It's not quite as easy as I've expected As long as you move the items inside the same group -- e.g. you move CPU temperature inside the Termpeatures group one line up or down -- it works great. But, when you move an item into another group, things could get messy. Not to mention a potential scenario when you would like to rename a group to e.g. CPU, and move all CPU related items into that group. Also, it would complicate things even more if you wanted to remove (or hide) an item, and especially when you want to remove (or hide) a group or add a new group. The potential need to change the grouping logic is the most challenging task to accomplish by simple drag&drop and context menu actions... What do you think?

Thank you! Have you tried to make a report using AIDA64 v5.98?

Awesome, thank you for you feedback!