Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    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.
  2. Fiery
    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.
  3. Fiery
    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.
  4. Fiery
    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?
  5. Fiery
    Thank you for your feedback
  6. Fiery
    Yes, that's the limitation right now.
  7. Fiery
    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.
  8. Fiery
    Thank you for the data. Please check the following new AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  9. Fiery
    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.
  10. 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 how it works.
  11. Fiery
    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
  12. Fiery
    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
  13. Fiery
    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
  14. Fiery
    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.
  15. Fiery
    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.
  16. Fiery
    Just install the latest (beta) Crimson ReLive video driver from e.g.: https://www.techpowerup.com/download/amd-radeon-graphics-drivers/
  17. Fiery
    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:
  18. Fiery
    Thank you! With TB3 disabled we can still experience the same issue on our own Asus Prime X299-A motherboard based test system. In your dump you can see the anomaly as: Time #3 = 0.230 / 0.272 / 0.269 / 0.225 / 0.258 / 0.241 / 0.266 / 0.230 / 0.230 / 0.301 / 0.218 / 262.524 / 0.338 / 0.443 / 0.230 / 0.246 msec AIDA64 reads 16 registers from the EC there, and one case out of 16 it slows down tremendously. The chances of that happening seems to be similar on our Prime X299-A motherboard. So typically once per every 10 or 20 EC register accesses gets a penalty that way. We'll contact Asus to find out what can we do on our end to avoid the penalties.
  19. Fiery
    I'd second an3k's suggestion on trying to disable both EC options on the Stability page: Embedded Controller (EC) sensor support Embedded Controller (EC) bank switching Aquasuite is supposed to work well together with 3rd party applications about ISA based sensor chip access, but maybe it collides with AIDA64 if it also tries to read EC registers.
  20. Fiery
    The above mentioned new AIDA64 beta build is available at: https://www.aida64.com/downloads/latesta64xebeta
  21. Fiery
    The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta The 6 temperature readings come from the onboard sensor chip. The chip (IT8686E) supports 6 temperature readings, but only 4 is utilized by your motherboard.
  22. Fiery
    Thank you for the info. We'll do relevant test runs tonight as well. Meanwhile, we've added more debug information to the Embedded Controller dump. Please post an updated such dump using the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta Thank you in advance!
  23. Fiery
    There's no technical solution to the issue.
  24. Fiery
    Yes, we're planning to develop the GPGPU benchmarks further, but we currently have no definitive roadmap on your ideas I'm afraid.
  25. Fiery
    I'm not sure what Gigabyte G7 refers to. Is it a Gigabyte motherboard with Z370 chipset? If yes, then which one? Do you have any special sensor devices connected, like via USB? Do you have any RAID arrays defined? Please also let me know what version of ForceWare do you have installed.
×
×
  • Create New...