Fiery

Thank you for the data! 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 how it works.

No, it's not. We just have too many things on our table right now Please give us a few more weeks to implement that.

We're working on that. There are multiple ways to do that, but none is easy I'm afraid

Yes, it'd worth trying to disable Secure Boot and check it again.

I've never used Python, so I can only make suggestions that will apply to any programming languages. You can either use the Shared Memory feature, in case you can use Win32 API calls... Or use the Registry feature if you have access to the Windows Registry from your script or program. Another solution might be to expose an interface in your microcontroller that can be used by 3rd party applications (like AIDA64) to push data onto the display directly. Either by sending textual information (like "CPU Clock = 32 C") or bitmap images in case the LCD display you use is a graphical one. Either way, if you would let AIDA64 talk directly to the display, we would be happy to implement your protocol as a new LCD device. Just keep us posted through this topic.

We've never tried to use that value to detect bus type. What we do is simply go by the GPU type, by using its PCI device ID. We then have a backend database that indicates whether a certain GPU is integrated or bus-connected (like PCI, AGP, or PCI Express).

No, that was designed for older Asus motherboards, and will not work properly for Asus motherboards released in the past few years up to today.

Please let us know more about your system configuration. Motherboard model, CPU type, video card(s) model, Windows version/build, AIDA64 version/build?

I'm afraid I have no idea what might cause the booting issues. Other than something about the USB device enumeration in the BIOS. But it's hard to dig deeper than that

We haven't taken it apart, so I don't have what LCD driver IC is used in this device.

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.

There're a few compromises in the Turing uarch compared to Pascal/Volta that could explain the performance drop. We however had no chance to dig deeper into Turing just yet. Once we can get a test sample, we'll analyze the issue. There may not be room for further optimizations though (on our side), since our OpenCL benchmarks rely heavily on the OpenCL compiler, and the fractal benchmarks are quite simply "too simple" to leave room for any tweakings on our part. nVIDIA may find some tricks on their side that they can implement in their OpenCL compiler, but I'm not sure how much attention they have about OpenCL benchmarks and optimizing their compiler to better work with such benchmarks

Thank you, we've added this display to AIDA64.

It's because your displays are not included in the AIDA64 monitor database yet. We've added this one, but if you have more where it shows "[NoDB]" in the monitor name, please post them as well, and we'll add them too.

Make sure to enable nVIDIA GPU SMBus access through nVIDIA ForceWare, which is the default setting.

Thank you for your feedback!

Are you sure the issues you're facing are directly related to AIDA64?

Thank you for your feedback

We need to reproduce the problem on our own Win10 test systems with a 4K display. Please let us know what tool/trick you use to be able to use the Vista Desktop Gadgets under Win10.

I've sent you a private message about this issue.

Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI 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

I meant if you request us to add support for a currently unsupported display, it is best if you already own (or plan to own in the near future) the display It's not a huge problem if you don't, for example if you only want to purchase a display when it's already supported by AIDA64. Fortunately implementing support for RoboPeak wasn't too difficult, but there are a lot more challenging devices. Multiple displays of the same kind is only supported for a few displays out there right now. You can use: two Razer LCDs two AlphaCool LCDs three picoLCDs three Saitek LCDs three Trefon LCDs three Cwlinux LCDs three YoctoPuce OLEDs three Crystalfontz LCDs three Aquaero LCDs three LCDInfo LCDs three Phidget LCDs We only enable more than one LCD support (of the same kind) per request, since most users only have one display from a particular vendor. You can however mix any number of displays when they're different kind. For example, you can use one LCD2USB, one Samsung SPF, one Matrix Orbital GX, one RoboPeak, and one EastRising (so 5 displays total, but it can be even more) simultaneously with AIDA64. The only difficulty you will experience with such a setup is the delays in poll rate due to the enermous USB traffic BTW, just as with multiple devices support, hot-plug support and rotation support are also only enabled for a few devices. But they can be enabled for other devices per user request.

I'm not sure what RAM modules you've got. If they're for example DDR4-3000 rated modules, you may want to try lowering the DRAM frequency to 2933 or 2667 MHz, and check fi it helps to stabilize their operation. You can also try to change Command Rate (Tcmd or tCR) to 2T in the UEFI Setup (BIOS Setup). Of course, make sure to have all Windows patches applied, and have the latest BIOS update flashed into your motherboard.

Thank you. Although, it would be best if you owned those displays and really wanted to use AIDA64 on them

We've opened a separate topic for RoboPeak: