Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. Yes, but first you need to enable DIMM thermal sensor support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option.
  2. Ubuntu Touch OS development has been discontinued by Canonical. We're not planning to add more architectures to our Ubuntu Touch app, or develop it any further for a ceased platform.
  3. What issues can you see about the sensor readings? The latest AIDA64 beta is supposed to provide 100% accurate readings for your motherboard.
  4. We've sent a request to Asus to investigate this issue, but they haven't completed their efforts to replicate the anomaly and dig down deeper to find out what exactly causes the slowdowns. I'll let you know once we know more about this issue. I'm afraid at this point we have no tools to get around the problem or to fix it on our end.
  5. System availability indicates the percentage of time when your system was turned on (was "up"), as opposed to being in sleep mode or completely shut down. A system availability of 33% means that your computer was turned on for 8 hours a day.
  6. The issue doesn't seem to be related to AIDA64 itself. You need to find a different SMTP server, one that accepts your outgoing messages.
  7. Does your Windows user have administrator privileges? Did you install AIDA64 properly, or just launched the main executable (AIDA64.EXE) file from the ZIP package?
  8. Thank you for your feedback. The memory stress test is designed to "eat up" all the RAM in order to put all of the system memory under scrutiny. You're not really supposed to launch any other software while the test is running.
  9. Awesome, thank you! We'll update the stress test module in the next AIDA64 beta in order to provide AVX stress test on AVX-512 capable processors when you disable the use of AVX-512.
  10. Yes, you can switch the onboard SATA controller to AHCI or IDE mode, but it most likely will cause WinXP to fail to boot up completely So I wouldn't touch that option in the BIOS Setup, unless you're ready to perform a complete OS re-installation.
  11. Thank you. Do you have any RAID arrays configured -- or just have the standalone drives connected to the SATA controller which happens to be working in RAID mode right now?
  12. Yes, that's the limitation right now.
  13. We've found a few parts in the code where we could improve threading. It seems the issue is very complicated, but we may have stumbled upon the root cause of the user interface freezing. The allocated memory amount % cannot be configured right now, and perhaps it wouldn't be as useful as we previously thought.
  14. Thank you for the data. Please check the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  15. In the latest AIDA64 beta build we've added 2 new options to the AIDA64 System Stability Test Preferences / General page, to let you disable AVX and AVX-512 stress testing. https://www.aida64.com/downloads/latesta64xebeta Let me know how it works. Please note that right now disabling AVX-512 will make AIDA64 stop using AVX as well, since we haven't defined any AVX stesst testing codepaths for AVX-512 capable processors yet. We'll fix that soon.
  16. 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 how it works.
  17. I'm afraid we still haven't been able to reproduce the issue on our own test system, nor we could find an error in your disk activity measurement code
  18. Arx could be a bit tricky when you need to init and de-init it in a quick succession by checking or unchecking the option Enable Logitech Arx LCD support in the AIDA64 Preferences. Usually it gets back to normal after you've set the right resolution, checked the checkbox, and restarted AIDA64. I know it's tricky, but we haven't been able to figure out how to avoid Arx getting stuck in those init/de-init cycles
  19. Thank you. Something fishy is going on around the RAID detection. It would be important to find out what kind of RAID controller do you have in your system, so we can install a similar one. Meanwhile, if you have an AIDA64.INI file present in the AIDA64 installation folder, you can use Notepad to disable RAID detection by altering the following lines in there: LowLevelRAIDEnum=1 LowLevelRAIDSMART=1 Change them to: LowLevelRAIDEnum=0 LowLevelRAIDSMART=0 And let me know if it makes AIDA64 working on your system. It's not an actual solution to the issue, but rather a workaround to at least get AIDA64 to start properly. Thanks, Fiery
  20. No, it's not possible directly. But, you can override the LPH unit label with your own preference of text, and you can also adjust the flow rate values using the Correction feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction). A ratio of 60 should work to convert the value from LPH to LPM.
  21. Try to go to AIDA64 installation folder, find the manual file (AIDA64.CHM), right-click on it --> Properties --> Unlock button --> OK button. That should solve it.
  22. Just install the latest (beta) Crimson ReLive video driver from e.g.: https://www.techpowerup.com/download/amd-radeon-graphics-drivers/
  23. You can use the FLOPS benchmarks of the AIDA64 GPGPU Benchmark suite. Go to AIDA64 / main menu / Tools / GPGPU Benchmark to check it out. The first column will reflect the performance of the integrated Vega GPU, and the second column will reflect the raw computing power of the four Zen cores. Sample output of a Ryzen 5 2400G APU:
×
×
  • Create New...