Fiery

I'm sorry for the delays, and thank you for the dumps. I'm afraid neither of the RAID codepaths AIDA64 currently features supports your RAID controller. We'll try to find out how to handle it.

Thank you. Sadly, Aquaero uses a slow USB protocol, and there's nothing we can do to get around that limitation

Sadly, not all Adaptec controllers are handled properly by AIDA64 at this time. So it's best not to pretend it supports all Adaptec RAID controllers

Multi-GPU support can be dangerous with ULPS-enabled CrossFire setups, but it is fine to have enabled with SLI

That indeed looks very weird. We'll need to see the before & after dumps to find out more about the root cause of the issue.

We don't use an offset for the "CPU" value. AIDA64 should show the same value that Gigabyte's own monitoring software displays as "CPU" temperature.

Thank you. We will fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download.

Are you sure Afterburner has no background task that would keep monitoring your sensor readouts, even after you've closed its main window?

The CRC for the ZIP package is downloaded (acquired) from our update server, so it's not possible to manipulate the ZIP package. The CRC is not part of the ZIP package at all, and it doesn't necesserily come from the same download server either. We don't see a vulnerability there.

It is rooted in It is rooted in the limitation of the chipset, since it can only handle up to 8 DIMM slots by default. So the SMBus mux is necessary to make sure it can handle up to 16 DIMMs slots (using a 2-way / binary mux). The SMBus mux of Intel S5500BC, S5520HC, S5520SC and S5520UR motherboards are handled by AIDA64. Rare exception, but it's there. The mux of a few Asus and Supermicro motherboards are also handled.

We can implement any mux, as long as we get the technical guidelines on it. In case Lenovo is willing to help us out about that, we'd be happy to add a mux for your motherboard. It's a discontinued product, so if you ping the right person at Lenovo, there's a chance they figure there's nothing wrong handing out such details on an old-ish product...

Sadly, most 2-way and 4-way server motherboards use a SMBus mux to handle the SPD for more than 8 DIMM slots. Such muxes are proprietary and not documented at all, so we can only support a few of them where we somehow could obtain the technical guidelines on handling the mux. I'm afraid we have absolutely no such information on any Lenovo server motherboards though, so we can only support them without handling the SMBus mux. It usually manifests as AIDA64 being able to detect half or 2/3 of the installed memory modules -- exactly as it is in your case.

Yes, our automatic update system verifies the CRC for the downloaded ZIP package before extracting it and moving the files to replace the old files. Regards, Fiery

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. Thanks, Fiery

Great minds read each other

I've sent you my email address in private message

They seem to be helpful on this, which is indeed a rarity these days. Let's see if they could replicate the issue on their own test systems. If they ask you about it, feel free to let them know that we are more then happy to work with them to resolve this issue, as long as they're fine with communicating us directly (in email, preferably).

The problem with us reporting the bug is 2-fold: 1) We're not an actual customer to them, even though we own a few Razer test devices. 2) The sort of automatic response would be that it's the fault of AIDA64, and that we're using the protocol incorrectly. And since it's no way to downgrade Synapse (AFAIK) to an older release to check if it works, and then gradually upgrade to newer and newer releases in "baby steps", we alone cannot test this whole issue in the classic way. The classic way of bug-hunting is to go back in time until we can find a point where the protocol works fine on both ends -- but with the silly cloud and fully automated manner of Synapse, this isn't possible.

In the state where you've disabled all the unnecesary modules (in Preferences / Stability), please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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. We need to see that to find out which sensor module causes the delays on your particular configuration. Thanks, Fiery

Make sure to enable Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability. You need to restart AIDA64 to apply the changes. Let me know if it helps. Thanks, Fiery

Yes, there are many Hash algorithms out there, and we've picked the one back in the day that was the most popular by the time. We can debate on whether it's outdated or not by today's standards, but picking just one of the many hashing algorithms would equally be as questionable There's no universal standard, so we have to pick one. We may relieve the current SHA1 based benchmark sometime in the future, but it won't happen this year for sure, since we're already pretty much booked up about improvements and new features until Santa comes

We've tested it on our Windows 10 x64 (Version 1703, Build 15063, latest patches applied) based system with the latest Synapse updates and also fully updated keyboard firmware. Keyboard was of course the DeathStalker Ultimate. We can confirm to see the same phenomenon that you've brought up, and our conclusion is that it's due to a bug in the Synapse framework. Please report the issue to Razer, it's their responsibility to fix this up.

Unfortunately AIDA64 (and other Windows software as well) has no control over the order of System Tray icons. You cannot rearrange them in any ways from software. You can show them or hide them, that's all. Everything else is taken care of by Windows itself.

We've already got a Hash benchmark for CPUs that also can harness hardware acceleration (IA SHA x86 instruction set extension) if available. We've also got OpenCL based GPGPU Hash benchmark in the AIDA64 GPGPU Benchmark Suite that you can launch from AIDA64 / main menu / Tools / GPGPU Benchmarks. IMHO we're pretty much covered on hash benchmarks without specifically targeting any certain cryptocurrencies individually.

Thank you for letting us know about the root cause