Fiery

AIDA64 doesn't support special characters or custom characters for alphanumerical displays. Hence a "big date" that you've shown on your photo cannot be achieved with AIDA64 I'm afraid.

Try to re-arrange your displays in a way that the smaller screen is positioned to the left of the main monitor. Let me know if it helps.

Thank you for your feedback. We will fix the reported issue in the next AIDA64 app update.

What motherboard do you have?

1) We have no control over the firmware and its behavior of those panels, so we cannot fix any such issues 2) I'm not sure what exactly do you expect by "similar", but make sure to check BeadaPanel: http://www.nxelec.com/products/hmi/beadapanel-media-display It has a 5-inch version by now.

You can use that screen as an external monitor, and you can use the SensorPanel on it.

SensorPanel is only suitable for such external screens that appear as monitors under Windows. Typically such devices are connected via DSub, DVI, HDMI, or DisplayPort interface. However, for a few years now there're also USB Type-C connected monitors as well, so I cannot state specifically that any USB screens are non-monitors anymore As for the AIDA64 LCD module: the devices supported there are non-monitor devices. So when you connect those to your PC (typically via USB), they don't appear as a secondary monitor, and you cannot extend the Windows Desktop to those screens.

What kind of crash is it? Does AIDA64 throw an exception? Does Windows throw a BSoD? Does your computer lock up? Does your computer restart suddenly?

CAM tends to open NZXT hardware devices using exclusive access that blocks other software from accessing the same device.

Make sure to upgrade to the latest beta version of AIDA64 Engineer available at: https://www.aida64.com/downloads/latesta64eebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've implemented the requested feature in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.

Please close CAM and check if it makes it work with AIDA64. If not, then 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

AIDA64 v5.95 has full Russian localization. You don't need to install anything other than the default installation package. You can switch language in AIDA64 / main menu / File / Preferences / Language.

Thank you for your feedback

It's most likely a bogus reading that you should ignore.

AIDA64 v6.50 adds Leakshield support: https://www.aida64.com/downloads/latesta64xe

That's perfect, thank you! We'll disable PCH Diode temperature measurement for your motherboard in the next AIDA64 beta update.

We can disable PCH Diode temperature measurement specifically for your motherboard if you could kindly let us know what motherboard do you have, as it is shown by AIDA64 on the Motherboard / Motherboard page.

Please 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. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

AIDA64 detects the GPU device ID using low-level PCI device register readout and then interprets the ID to the GPU codename using its built-in GPU database.

What video card do you have?

It's normal, since we cannot add IPMI sensor readings to the regular sensor module of AIDA64 due to the slow IPMI protocol. It would make updates sluggish and cause a bad user experience.

How do you know the system freeze is caused by AIDA64 accessing the PCH?

AIDA64 currently doesn't support such monitoring sources.

I'm afraid not