Fiery

You need to have Asetek LC sensor support enabled in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. If it still doesn't work, then try to close CAM Software. We've already asked NZXT to implement the necessary synchronization mutexes to avoid collisions between CAM Software and AIDA64 (as well as other monitoring software like HWiNFO, HWMonitor, SIV, etc), but I'm not sure whether they're done with the implementation yet. Regards, Fiery

Let me know if you settled on a single interface and a single display protocol, and then we can start working on the implementation

Custom gauges would dramatically increase the amount of data that AIDA64 has to send over the network multiple times a second. Also, due to resolution and dpi differences, custom gauges scale badly across various devices, just like static images.

Thank you. We've checked, but found no information on how to detect OCP state with RMi PSUs

What interface will you use to connect your OLED display to your PC?

What kind of Corsair PSU do you have? Corsair uses multiple protocols for their PSUs

Thank you for the feedback

It works the same way for temperatures than for other readings.

In theory both memory module variants should work. But, in many cases BIOS support is also necessary. Only Toshiba can give you a definitive answer to that dilemma. Regards, Fiery

There are a lot of folks out there who can exploit the 3 PC license since they own a desktop computer as well as a notebook or an x86 tablet. We used to offer the 1 PC license for the same starting price of $39.95. So we haven't raised the price, but raised the number of licenses you get for the same price. Personal use license (AIDA64 Extreme) starts from $39.95, while professional use license (AIDA64 Engineer) starts from $199.90. There's quite a gap there already However, I agree that the price tag of AIDA64 Extreme may be up for debate. But if you compare it against other venerable Windows utilities, it's in the same ballpark as those. Just a few examples: - Total Commander: $42 - WinRAR: EUR 29.95+VAT - Sandra Personal: $49.99 - GetRight: $39.95 - Axialis IconWorkShop: EUR 69.95 - Kaspersky Anti-Virus: $39.99 - etc... But based on the price of other Windows utilities, IMHO the price of AIDA64 Extreme shouldn't be $10 but more like $49 or $59. Charging $10 for an AIDA64 Extreme license wouldn't be sufficient for us to sustain our efforts on the development side. Regards, Fiery

We've added support for Asus Fan Extension Card for a bunch of Asus motherboards -- including Z170-A -- in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Please let us know how it works

The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Please let us know how it works

Thank you. Please let us know when Asus comes up with a fixed BIOS update and/or fixed AI Suite, since we need a 100% reliable reference to compare the readings against. We cannot fine-tune the sensor readings when even the reference readings are incorrect

When you have those options disabled, AIDA64 won't be able to enumerate member drives of RAID arrays. If you have no RAID array defined in your system, you won't lose any functionality. In fact, by disabling those options, the time it takes for AIDA64 to perform its startup initialization gets shorter.

Make sure to watch both the core temperatures and CPU Package temperature. Whichever is the highest, that one should matter the most.

It means that under very heavy stress your CPU is overheating and throttles to prevent permanent damage. It's normal for mobile computers equipped with Haswell, Broadwell, Skylake and Kaby Lake processors. As long as the notebook works fine under everyday load, you're fine. Regards, Fiery

Thank you, we'll fix that issue in the next AIDA64 beta update due in a few days from now. Regards, Fiery

I'm afraid we're not experts on such matters. But maybe someone else who reads this could chime in and give you some guidelines. As for the Mali-T720 GPU, it's sadly an integral part of the the SoC, so you cannot replace it or reuse it in any ways. Regards, Fiery

Please note that it's not possible to diagnose such issues remotely. You may want to take your phone to a local specialist and have it checked out.

Your memory modules do not seem to support DIMM TS thermal state reporting.

That process belongs to a software installer. Try to kill that process, restart Windows, and check if it gets running again. If it does, then you need to find out what causes that process being launched automatically, without starting any new software installations. Keeping dozens of web browser pages open may put a toll on system memory allocation, but it shouldn't cause any significant CPU or GPU load.

Please give us a few more days to dig down deeper. So far we've concluded that Intel changed something in their RST drivers between Version 13 and Version 15, that caused our existing RAID member enumeration code to stop working. We need to find out what we have to change to continue supporting the latest Intel RST driver generation. I'll post a message into this topic once we have a fixed AIDA64 build that you can try

Please try to disable the two RAID related options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. If it doesn't help, then please let me know what hardware do you have that fails to work with uniata driver and AIDA64. We need to get one example of such hardware to try and replicate the issue on our own test systems. Thanks, Fiery

Thank you. It's quite tough to follow that, but please let me know if the latest AIDA64 beta (Build 4028) is fine now or still not correct https://www.aida64.com/downloads/latesta64xebeta

1) We do not really compete with Geekbench or other similar benchmark software, mainly because AIDA64 has no online database where users could submit their scores. Until we have that, we don't really see the type of benchmarks we've got an issue. 2) We haven't added the OpenCL benchmarks to the regular page tree simply because those scores can vary greatly across not only different hardware, but different drivers with the same hardware too. So for example, by simply upgrading your video drivers may cause the scores to jump up or down 20 or 50 percent. Such inconsistency would never happen with native (x86/x64) CPU or FPU benchmarks. OpenCL is a very different beast, and so we have to treat it as a different beast too 3) As for producing a single benchmark score, from time to time we reconsider that idea, but then we always get to the point of dropping the idea. It's because even though producing a single score may sound quite convenient, but it would represent basically nothing about the actual performance of the system or CPU. It's also very difficult to come up with reasonable weighting of scores. If you take all our existing benchmarks, add all the scores up as a percentage to a certain hardware (let's take Core 2 Extreme X6800 as a rererence of 100% performance for example), then it may sound a great solution ... as long as hardware accelerated AES, AVX and FMA don't distort the picture Not to mention what AVX-512 and hardware accelerated SHA would mean for next-generation processors...