Fiery

It should work just fine. The new readings should appear on the Computer / Sensor page. They may overwrite other values, like +5V and +12V that are read via other sensor devices.

Please send me your AIDA64 Business product key in private message, and I'll send you a download link to a new AIDA64 Business beta update that implements Corsair Link support.

Companies can simply rename or rebadge their products, without altering the actual hardware. I wouldn't worry about that much, as long as the device works as advertised. E.g. if it was sold as a quad-core SoC with 2 GHz CPU clock, and you get that, then it's fine.

Okay. Then please let me know what's wrong with the latest beta. Does it make Windows pop up the same message as in your opening post?

You're right, AIDA64 does not try to create a VkDevice. It uses vkEnumeratePhysicalDevices, vkGetPhysicalDeviceProperties and vkGetPhysicalDeviceFeatures. In case a driver reports meaningful information through those API calls, I don't think it's wrong to assume there's a physical device there that supports Vulkan. In case the video driver mistakenly provides physical device information for such devices that are not really supported by Vulkan, it's the bug of the video driver and not the fault of AIDA64 or VK-Z.

Maybe, in the future. So far the only limitation of using 32-bit interface is the remote heap size detection issue.

Thank you for the feedback. AIDA64 uses 32-bit interface to acquire Vulkan information. So the remote heap size -- as you've pointed out -- will be somewhat limited. But that value is still relevant to indicate how 32-bit applications are handled by Vulkan.

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. Make sure to use the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Thanks, Fiery

Are you sure you're running the latest AIDA64 beta? Have you restarted Windows after upgrading to it? If you have 2 instances of AIDA64 installed, and you configured the old one to auto-load at Windows startup, then maybe after restart Windows the old version got started automatically, and not the new beta?

I'm not fluent in Russian, but I suppose the latest AIDA64 Extreme beta should fix it up: http://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

In the latest AIDA64 beta update we've add a new page (Display / Vulkan) to display Vulkan device information: http://www.aida64.com/downloads/latesta64xebeta

Video BIOS Dump and any other debug dumps are not features. They are only there to help finding and fixing bugs. The debug dumps may or may not produce a meaningful result. Regards, Fiery

What kind of additional features do you mean?

Have you tried the latest AIDA64 beta as well? http://www.aida64.com/downloads/latesta64xebeta Let me know if it is affected too.

Thank you. We're already working on it

We will definitely implement a new page to show Vulkan video adapter information. We just need to wait for the first official Vulkan-ready drivers to be rolled out by both AMD and nVIDIA. We may also phase out the existing Mantle page at one point. But for legacy systems it makes sense to keep it for a while. Regards, Fiery

Thank you for the data. We currently have no information on how to handle Aquastream Ultimate. We've contacted Aquacomputer to ask for assistance. I'll post a message into this topic when I have an update on this matter.

How does this issue relate to AIDA64? Regards, Fiery

Thank you for the feedback

In general, as long as the computer is not sleeping, AIDA64 should be able to communicate with non-Logitech LCD devices while the computer is locked. LCDsysinfo devices are not supported directly by AIDA64. Those devices come with a software that can communicate with AIDA64 and put the values provided by AIDA64 to the LCD screens. However, it means you have to rely on their software and its capabilities to support system locking.

AIDA64 works via the Logitech LCD API. In case Logitech Gaming Software blanks the LCD in locked mode, it may also prevent AIDA64 from communicating with the LCD. But, you can try AIDA64 for 30 days in trial mode, so make sure to download it, and check it out thoroughly before acquiring a license Regards, Fiery

Try to set your configured fan duty cycle (%) in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Set Asetek fan speed to avoid AIDA64 altering the fan duty cycle to maximum (100%).

In single or dual channel mode it would say "Single Channel DDR4-2800" or "Dual Channel DDR4-2800". Your memory configuration uses quad channel mode, we can confirm that based on your screen shot.

We currently have no technical details on how to access sensor readings of GRID devices (ie. how to talk to them via the USB connection). We'll need to get one and try it out, to see if we can communicate with it from AIDA64.

It wouldn't make a difference, since your PSU is not connected via a Link Commander unit.