Fiery

We do have plans, but not for the near future. We're watching the market, the evolution of the Windows PC ecosystem, and we'll make our move to 64-bit once it will become necessary or mandatory. The 32-bit main binary is there because that's the best compromise. Having a 64-bit main binary wouldn't be a major benefit, but on the other hand it would raise a lot of issues. One such issue would be a considerably bigger distribution package, more than twice the size of the current ZIP and EXE package. That's because when you have a 64-bit main binary, you need to have all DLLs compiled to 64-bit as well -- while retaining the existing 32-bit DLLs for compatibility reasons. Another issue is that many interfaces and APIs that AIDA64 relies on have no 64-bit support. And so when you want to use such an interface/API from AIDA64, it works now, but it would stop working if the user switched to the 64-bit main binary. As for the name itself: it's there to separate the software from its predecessors, namely AIDA32 and AIDA16. While it's true that the main binary is still 32-bit, but the critical parts (modules) that truly benefit from porting 64-bit are already available in both 64-bit and 32-bit flavours. Those modules are the benchmarks and the stress test (AIDA64 System Stability Test).

I've just sent you a private message about this

Using AIDA64 v5.90, 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. Thanks, Fiery

Such "stolen" section of RAM is usually occupied by the video buffer of an internal (iGPU) or external (VGA card) video adapter. Check if you've got any special BIOS options about memory mapping, and try to enable it if you find such an option in the BIOS Setup.

The next AIDA64 stable update is scheduled for May or June, although there are many factors that could delay that release, for example the recent changes in AMD and Intel CPU roadmaps. But please note that our beta builds are considered "quite stable", so you should give the latest one a chance

Thank you for the data. Reading all the registers from Aquaero devices is a slow process. You can lower the update frequency in AIDA64 to 100 milliseconds, but reading all registers from your Aquaero device would still take over 800 milliseconds. So the lowest update rate you can achieve would still be over 1 second. We cannot fix that from our side, we simply have to live with slow USB protocols.

It's not supported right now. You can however watch the minimum/maximum/average sensor readings on the Statistics tab of the AIDA64 System Stability Test. You can also use the Logging facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging) to record the minimum/maximum/average sensor readings in a CSV or HTML log file.

Thank you for applying. I've sent you the guidelines on AIDA64 localization in email.

We only add those computers to the list of reference results that we own. That's the only way to make sure all results are reproducable, accurate and authentic. We've only got a single Broadwell-E system based on 6800K CPU. As for Apollo Lake, you're right. It was due to a bug, but now it's fixed. It will be included in the next AIDA64 beta update due later today

We do have references to 4D Systems LCDs, but they are actually not supported. We'll fix that discrepancy to clear things up.

The readings look fine to me. I'm not sure why one core is colder than another one that's very close to it. It's probably due to inaccuracies in Intel's DTS (Digital Thermal Sensor) solution. DTS was not designed to allow temperature monitoring, but rather to prevent the CPU from overheating. So it doesn't have to be 100% precise, as long as it can detect the situation when the overall CPU state is considered "too hot for normal operation".

It is usually caused by one of the sensor modules taking too long to update the values. 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. Thanks, Fiery

The latest AIDA64 beta applies the -20 Celsius offset on the CPU Diode temperature reading for Ryzen 1600X, 1700X and 1800X processors. We merely follow AMD's recommendation on how to handle the Tctl based temperature readings. You can override that offset if you want, in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. On that page you can also override the "CPU" temperature reading as well, BTW. As for the "CPU" temperature reading, that one comes from the motherboard sensor chip. The reading coming from that source depends on how BIOS configures the sensor chip at bootup. Gigabyte never requested us to implement an offset for that reading, so we show the raw value as it comes from the sensor chip.

Thank you, but Asus Crosshair VI Hero is already supported in AIDA64 v5.90. What do you find incorrect about it?

Yes, it's correct.

Thank you for your feedback

The reference list is part of AIDA64, it's not downloaded or updated from the internet. You can already have the up-to-date reference list, including Ryzen 7 1800X and Kaby Lake i7-7700K results if you use the latest AIDA64 beta available at: https://www.aida64.com/downloads/latesta64xebeta We've also added a Broadwell-E i7-6850K result and an Apollo Lake reference set of scores as well.

Yes, it should still work. Just create that key if it doesn't exist, and put your values under there.

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

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.

Thank you. We've implemented support for Norton Security v22 in the latest AIDA64 Extreme beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works

Try to update everything in Play Store, and also install any available Android platform updates for your tablet. If it still doesn't work, then I'm afraid it's a platform limitation that prevents our app from using the standard Google services. In which case we cannot fix it from our end Regards, Fiery

No, it's not possible right now. You need to pick the images for each state individually, but then when you're done with one gauge, you can duplicate it on your LCD/SensorPanel layout to avoid having to go through that process again.

If you can send us a sample, we'd be happy to do that

Do you have an AMD processor? If yes, then please note that AMD processors do not support throttling activity detection/measurement.