Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12179

  • Joined

  • Last visited

  • Days Won

    536

 Content Type 

Everything posted by Fiery

  1. Fiery
    Maybe these URLs would help? They always point to the latest stable and beta build, respectively. https://www.aida64.com/downloads/latesta64xe https://www.aida64.com/downloads/latesta64xebeta
  2. Fiery
    Thank you for your feedback. We'll complete the iCX support in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta build becomes available for download.
  3. Fiery
    Thank you for your feedback. We will add the RGB LED keyboard background color configuration option to the AIDA64 Preferences in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  4. Fiery
    Without proper evaluation/test hardware we couldn't do more than what we have accomplished. BTW, since virtually no software has AVX-512 optimizations right now, those benchmarks that only have up to AVX2/FMA optimizations are actually more representative about the performance you can extract from the new Skylake-X/Skylake-SP processors currently And by the time AVX-512 accelerated encoding and rendering software hit the market, we will already have an AVX-512 optimized AIDA64 out too
  5. Fiery
    Thank you. We will disable SMART readout for your HDD in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  6. Fiery
    Please let us know more about your display setup, and from what position does SensorPanel shits from and into?
  7. Fiery
    Update: Support for the Command Pro protocol will be implemented in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  8. Fiery
    Thank you. The issue will be fixed in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  9. Fiery
    Thank you. The issue will be fixed in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  10. Fiery
    Thank you. The issue will be fixed in the next AIDA64 beta update due later this week. I'll drop a message into this topic once the new beta build is available for download.
  11. Fiery
    Please try to disable the SensorPanel, close AIDA64, remove those two Registry entries again, start AIDA64, enable SensorPanel, wait 10 seconds, close AIDA64, and examine the two Registry entries again. Let me know if they are reverted to zero or they indicate some odd value.
  12. Fiery
    I think the Memory Write performance is limited by the uncore frequency. In other words: the memory controller simply cannot churn out more data using non-temporal write, even at higher memory frequencies.
  13. Fiery
    Okay, but I think we need to apply such a fix for the particular BIOS version you've got installed right now. Going back and forth about updating temperature register indexes is a messy process. Please post an up-to-date ISA Sensor Dump, and we'll revert the CPU temperature register index to the one we've used in AIDA64 v5.80. Let me know if the motherboard temperature is wrong too.
  14. Fiery
    Please check if the sensor readings properly appear and are updated regularly on the Computer / Sensor page in AIDA64. If they do, then please try to enable SensorPanel again, close AIDA64, and examine the following values in the Registry: HKEY_CURRENT_USER\Software\FinalWire\AIDA64\SensorPanelPosX HKEY_CURRENT_USER\Software\FinalWire\AIDA64\SensorPanelPosY Let me know the values of those entries. Maybe the SensorPanel is shown and updated properly, but it's outside the visible Windows Desktop area.
  15. Fiery
    Your particular system may not be able to provide motherboard and GPU temperature measurements. If you can't see those readings on the Computer / Sensor page, then it's normal that those readings are missing from the SensorPanel.
  16. Fiery
    When it comes to sensor items about network traffic, there's a neat trick. If you specify the unit as "MB/s", AIDA64 will convert the value to MegaBytes/sec. If you specify the unit as "Mbps", AIDA64 will convert the value to MegaBits/sec.
  17. Fiery
    Thank you, now I see what's going on there. What we've done is consolidated the core temperature readings on AMD processors by removing the core temperature readings and adding a single "CPU Diode" reading. Those processors have only a single temperature diode, so displaying that single reading as 4 (or 6 or 8) separate core temperatures was redundant and unnecessary. If you check the readings via AIDA64 v5.80, you will see that the 4 separate core temperatures were actually always the same
  18. Fiery
    Please reinstall AIDA64 v5.92, restart Windows, and check if it helps. If not, then please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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. Please keep posting in English. This is an English language forum, and also we cannot speak Chinese I'm afraid. Thanks, Fiery
  19. Fiery
    Of course! And thank you for your feedback, I'm glad it worked.
  20. Fiery
    It seems to be a firmware issue of the hard disk drive in question. We may need to completely disable SMART readout for your HDD using the current firmware version. What is the full model ID and revision (firmware) ID of your HDD? Do you experience similar issues while running HWMonitor? Are you using a HDD monitoring software like HD Sentinel?
  21. Fiery
    I'm afraid it's not possible with AIDA64 for Android. That app of ours only supports exporting the collected sysinfo via email submit.
  22. Fiery
    Because only recently we could manage to acquire a system with AVX-512 support. The CPU you're referring to (Knights Landing) is a niche product, has no official Windows support, and virtually no AIDA64 users own such a machine. BTW, due to the enermous complexity of AVX-512 (over 1000 new x86 instructions) it takes over a year to fully optimize all AIDA64 benchmarks to AVX-512. We've started working on it cca. a year ago, but we couldn't finish it up before the Skylake-X launch. It's at 95% now, and we're going well, but it will still take 2 to 4 months to finish everything.
  23. Fiery
    Such issues are usually due to intermittent voltage measurement issues. In most cases it is caused by a collision between AIDA64 and another monitoring software. Do you happen to have AI Suite installed?
  24. Fiery
    AVX-512 is not yet supported. We'll add HW SHA information to the CPU Hash page of the Benchmark guide. Thanks, Fiery
  25. Fiery
    You use quite an old AIDA64 version. Can you please check 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.
×
×
  • Create New...