Fiery

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...

Auto-starting at Windows bootup may not work due to the security software you've got installed. Certain such software may prevent any software from being automatically launched at Windows bootup due to security concerns.

You need to enable Multi-GPU support in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Stability, and restart AIDA64 to apply the changes. However, if you have ULPS enabled, monitoring the non-primary GPU may cause a system lockup. So you need to make sure to disable ULPS first, and only after then enable Multi-GPU support. Regards, Fiery

Using the Task Manager, try to check if you have a software, process or service running in the background that loads the CPU "under the hood" when you have an active network connection. Regards, Fiery

Thank you. That looks odd: somehow the Areca RAID driver reports 5 connected drives, and they're all 3 TB Seagate HDDs. There seems to be no SSDs connected to the Areca RAID controller. Maybe you've got more than one RAID arrays defined for the single Areca RAID controller?

There are a few issues with that: 1) Too many lines make the graph very crowded 2) We don't really have more colours to assign to new lines 3) Core temperatures aren't that far from each other, so it's usually fine to use the temperature of a few cores only. Core #1 and Core #2 should be enough to monitor, along with CPU Package temperature

Yes, using the new Hot Keys feature that you can activate and configure in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys.

Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID 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 --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery

Also, as I've mentioned above, so far we haven't been able to replicate (reproduce) the issue on our own test systems.

Maybe I have misunderstood your post above. Do you mean that you cannot see any latency spikes in DPC Latency Checker, but you still have stuttering issues in the games you've mentioned?

Do you have the two RAID related options in AIDA64 / main menu / File / Preferences / Stability both enabled?

I'm afraid so far we haven't found a way to replicate the issue on our own i7-6850K test system using an Asus X99 motherboard. We've tried to get a hardware as close to yours as possible, so we're perplexed that we cannot see the same issues here. There may be a hardware component or software installed on your system that is behind these issues -- or maybe Turbo Boost 3.0 works differently on your system than on ours...