Fiery

AIDA64 Business uses a proprietary protocol with proprietary encryption. We do not publish the protocol details.

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. If the problem persists, please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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 --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Also 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. Thanks, Fiery

-10000 indicates a measurement issue. It could be due to excessive overclocking, but it can also be completely unrelated. Can you see such "hiccups" in current measurement when the CPU is not overclocked or less overclocked?

Task Manager shows an average CPU clock speed measured through a period of time, while AIDA64 shows the CPU clock speed as it is provided by the CPU, at any given time point.

Here's the proper fix for the Windows Explorer issue: https://www.aida64.com/downloads/latesta64xebeta

Meanwhile, we've made a change to AIDA64 to exclude Adafruit UF2 bootloader equipped USB devices from the external storage device scan. It may or may not help though. We'll only be able to check it out once our device arrives. If you or one of your customers can test the new build, and report us back whether it makes any difference, it would be appreciated. https://www.aida64.com/downloads/latesta64xebeta

Thank you

We've tested RemoteSensor with Bitdefender Total Security 2019, both under Windows 7 64-bit and Windows 10 64-bit, and couldn't reproduce the issue you've described. It must mean that the firewall configuration is to be blamed on your system. Make sure to browse through the firewall settings in Bitdefender configuration, and also check if Windows Firewall is enabled and how it is configured.

It comes from the battery, but not directly. AIDA64 measures that value using the standard Android Battery API, and applies no conversion on the raw value that is provided by the Android platform.

Yes, the next beta should be fine as long as you're on 4691 right now.

The latest 2 beta builds of AIDA64 have an issue about auto-update. It will be fixed in the next AIDA64 beta. Make sure to upgrade to it manually, and from then on everything will be fine again. I'm sorry for the troubles.

Thank you! We've ordered an ItsyBitsy M0 as well as an ItsyBitsy M4 to help us track down this issue. I'll let you know once we have the fix ready.

The latest beta update (Build 4691) messed up the automatic update facility. It will be fixed in the next AIDA64 beta. You will need to manually update to the new beta in case it fails.

What you're looking for is not supported by AIDA64 for Android at this time. We may implement that feature next year.

Thank you for contacting us. Please let me know what Adafruit product can we order to diagnose this issue in our own labs.

I'm glad you've managed to work it out. Thank you for letting us know about the resolution.

All NVMe SSDs (and most SATA SSDs, and most HDDs as well) have a primary thermal reading that is shown and monitored by basically all hardware monitoring software, and used as a basis of thermal throttling by SSD controllers. Certain NVMe SSDs (like Samsung 960 and 970 Series) have additional thermal readings (e.g. "Temperature Sensor 1" and "Temperature Sensor 2") that -- as some folks claim -- show the temperature of the memory and memory controller components of the SSD. Before Beta Build 4678 AIDA64 used the primary thermal reading as the temperature of the device. Following a user request, in Beta Build 4678 we've switched to using the highest thermal reading of them all as the device temperature. Then some users started to complain and argue about the validity of that solution, and expressed their concerns that all other software use the primary thermal reading. It's something that you can debate, of course. But since we've got one request (one vote basically) for the highest reading solution and many requests (votes) to switch back to the old solution, we've opted to go with the masses and put things back as they were in AIDA64 Beta Build 4681.

Most likely AIDA64 has issues communicating with your H110i device because of a collision between Corsair Link Software and AIDA64. Corsair used to have a synchronization mutex to make sure Corsair Link Software can be used simultaneously with 3rd party monitoring software like AIDA64, CPU-Z, HWiNFO, HWMonitor, SIV, etc. But due to unknown reason to us, Corsair decided to discontinue using those mutexes in recent releases of Corsair Link Software and iCUE. Since then all sorts of collisions could occur, and it's now difficult to use AIDA64 when Corsair Link Software or iCUE is running as well. The only solution is to use only one of those software until Corsair puts the mutexes back in their software again. We've already contacted Corsair and offered our help, but it seems the issue is internal, and so they have to do their homework to enable the mutexes in their software. What you can do as an owner and user of Corsair hardware is to express your dissatisfaction with the current state of Corsair Link Software and iCUE via their technical support system, and demand that they enable concurrent use of 3rd party monitoring software again.

AIDA64 doesn't overclock the CPU at all. The Computer / Overclock page of AIDA64 merely reports the most essential systems parameters that are worth watching when you do in fact overclock your system.

We've reverted back to using the primary thermal reading as opposed to the maximum reading of all thermal readings.

Yes, it is most likely caused by the system fan stopping.

Thank you for the test. What do you use CAM for? I suppose it's the NZXT CAM software, right?

Yes, we've rolled back that change, after getting a few feedbacks and also doing some research. It's best to keep the primary thermal reading as the relevant temperature reading for the SSD, and have the rest as alternative readings that may or may not reflect the thermal state of the memory chips or other components of the SSD.

I suspect your issue could be related to the problems about recent ForceWare releases. Try to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability, restart AIDA64, and check if it makes a difference. I know you would lose a lot of readings that way, but I'm afraid there's no better way to narrow it down to the suspected ForceWare issue.

Do you have the option Wake GPUs up at AIDA64 startup enabled in AIDA64 / main menu / File / Preferences / Stability?