Fiery

Thank you. Quite puzzling, since we've used SMART device emulation to verify the whole thing, but it works properly on our -- albeit emulated -- system. Would it be possible to record a video of the issue and upload it to Youtube or send us directly, so we could see what exactly are you clicking through (how exactly you navigate on the AIDA64 user interface), and what exactly is shown? In our efforts of trying to replicate the issue, maybe we're not doing what you're doing...

Thank you for your feedback. Your virtual machine has no USB device that would correspond to your Kraken X52 device. It's best to avoid running AIDA64 -- especially for hardware monitoring and benchmarking purposes -- in a virtualized environment. We cannot guarantee that any of the low-level hardware features of AIDA64 would work properly in virtual machines.

Thank you for your feedback. AIDA64 names the first temperature reading coming from F71809U as "Motherboard" temperature. The second temperature reading is named "CPU", and the last one is named "Aux". If you reckon we should use different labelling scheme on Jetway NC98, please let me know how to change the labels. And no, AIDA64 doesn't support fan control, but only fan monitoring.

Thank you for your feedback!

Please use the following form to contact our enterprise support staff directly: https://www.aida64.co.uk/support-request

You need Network Alerting to be notified by certain actions accomplished by your users, like installing a software or connecting a USB flash drive. You can configure Network Alerting in AIDA64 / main menu / File / Preferences / Network Alerting. Also, make sure to read the AIDA64 Business Setup Guide: https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf And the AIDA64 Business User's Manual: https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-manual.pdf Regards, Fiery

Both of you: Thank you for the data! Please 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 Thanks, Fiery

Thank you. Please 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.

We've implemented support for Kraken X52 in 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

Thank you. Please 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 how it works

I'm afraid I'm not experienced in that field, so I'm unable to give you recommendations about such dilemmas.

1) Yes, it is allowed. 2) Yes, it's the perfect edition for such usage. Regards, Fiery

Thank you. Please let me know if you have the full combo assembled and tested to be working.

I've never seen such a device with a USB connection Regards, Fiery

Thank you. It looks quite odd. Can you see any useful info reported on the Computer / Sensor page on that system? Can you please post a copy-paste of the Sensor page, or a screen shot?

Thank you for the feedback

The SensorPanel currently cannot detect whether it's shown or hidden on the Windows Desktop, so it cannot stop refreshing itself when it's not necessary. Regards, Fiery

We'll check the registration process on smaller screens. It may not be properly optimized for such devices. Our mobile apps have no documentation. You can however use Google to find out more about the technical terms used in our apps. Regards, Fiery

Okay, then let's just agree to disagree, and move on. Thread locked.

Sandra performs Stream benchmark, which is essentially a variant of a memory copy bandwidth benchmark, spiced with some simple CPU instructions performed on the copied data.

Thank you, but we'd like to stick with our formula -- which is used by other benchmark software (like Sandra) as well BTW.

Please also post an Embedded Controller Dump that you can find in the same Sensor Debug right-click menu.

It depends on how the video driver handles that situation. Maybe it doesn't throttle the GPU itself, but stops the video card fan (or throttles it down) to make the system work quieter.

In our memory read benchmark, we read a 64 MegaByte sized block from the RAM, and measure the time it takes to complete. Score = 64MB / time_it_took_in_seconds. In our memory write benchmark, we write a 64 MegaByte sized block into the RAM, and measure the time it takes to complete. Score = 64MB / time_it_took_in_seconds. In our memory copy benchmark, we copy a 32 MegaByte sized block by reading small chunks (into CPU registers) in each cycle and writing it back to a different RAM location (from the CPU registers). We measure the time it takes to complete the whole operation. Score = 64MB / time_it_took_in_seconds --> that's what can be debated, ie. whether it should rather be "Score = 32MB / time_it_took_in_seconds". Whether you consider copying 32MB as moving 32MB of data, or moving 64MB of data. From the memory interface perspective, reading 32MB and writing 32MB is considered transferring a total of 64MB data, that's why we use the formula "Score = 64MB / time_it_took_in_seconds".

Thank you for the feedback