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
    We're not sure why that happens. Our best guess is that there must be a bottleneck about memory write bandwidth in the IMC (Integrated Memory Controller) of Skylake-X processors. And that bottleneck may work differently in 12+ core versions (HCC) than 10-core and lower SKUs of Skylake-X (LCC).
  2. Fiery
    No, language should have no impact on that feature. Does your Windows user have administrator privileges?
  3. Fiery
    Thank you for your feedback
  4. Fiery
    No, it's not the same thing. The EC warning is due to EC bank switching, which is indeed a dangerous thing to perform when AI Suite is installed.
  5. Fiery
    Make sure to always use the latest AIDA64 beta build on Asus ROG products -- although in this particular case it wouldn't help much I'm afraid. As a temporary workaround you can try disabling EC (Embedded Controller) support in AIDA64 / main menu / File / Preferences / Stability, but that may still not get things 100% stable. We've discussed the issues and came up with a possible solution with Asus' engineers. So yes, they are absolutely committed now to fix the collision issue.
  6. Fiery
    Asus is working on the solution as we speak. We need to give them a few more weeks to come up with a BIOS update that would solve the collision issues.
  7. Fiery
    The difference may be because of the throttling activity. BTW, we've already seen reports of incorrect CPU utilization reported by Windows Task Manager...
  8. Fiery
    Yes, it should work with any Asus ROG motherboard. We haven't tested the OLED screen yet. You need to check if Live Dash requires any AI Suite components that may collide with the EC layer of AIDA64.
  9. Fiery
    We're not quite sure why the DIMM numbering is illogical.
  10. Fiery
    1) I'm not sure, since it's not a quick project 2) Already replied above
  11. Fiery
    As I've explained above, the Sensor page is not meant to be customized. Use one of the listed features if you need to have the layout customized.
  12. Fiery
    Only the labels, but not the grouping logic
  13. 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. In order to make it easier for you to configure the SMTP parameters, we've added a new Provider option to the Preferences / E-mail/ SMTP page. That way you can select your email provider (e.g. AOL, Gmail, GMX, Outlook, Yahoo, etc) to limit the number of options you need to properly adjust. We've of course fixed the issues related to how AIDA64 handles SSL and the way it explicitly issues the STARTTLS command. Let me know how it works with both your providers.
  14. 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.
  15. Fiery
    I know. But the Sensor page was not designed to be customizable. If you need to customize the readings, you can do that via multiple other methods So there's a solution for everyone.
  16. Fiery
    You can already do that if you use any of the OSD Panel, Desktop Gadget, SensorPanel, or External LCD modules
  17. Fiery
    We've tried to reproduce the issue under Windows Server 2008 R2, but for us it worked flawlessly. It must be due to a special configuration setting on your system that prevents AIDA64 from accessing the necessary counters to measure disk activity. Do you know what setting might cause that?
  18. Fiery
    Thank you. We've already come across the same issue about the EC register readout causing latency spikes. But sadly, so far we haven't found a solution to this We'll keep looking into this.
  19. Fiery
    Thank you. It seems to be due to a motherboard BIOS bug about handling the MMIO (memory-mapped I/O) portion of the motherboard sensor chip (IT8655E). Please report the issue to Asus, I'm sure they will know how to fix it in an upcoming BIOS update for your motherboard.
  20. Fiery
    Thank you for the feedback
  21. Fiery
    It's not that difficult to rename any of the readings, but it involves allocating newer and newer sensor slots. New sensor slots mean the whole monitoring module gets bigger and slower (by a tiny bit) everytime we add more, so we gotta be careful not to carelessly add everything that Asus comes up with Watercooling section doesn't make much sense, since that's not how the sensor readings are grouped on the Sensor page anyway. When you have a dedicated liquid flow meter (Aquaero, T-Balancer, etc), it will be slotted into the Flow Sensors group though.
  22. Fiery
    Since only the base frequency is guaranteed, indicating the turbo frequency would be less relevant IMHO. Not to mention the fact that modern processors have different turbo frequencies defined for different workloads (e.g. AVX-512 turbo is different to SSE turbo, etc). Only the base frequency is somewhat constant as a single MHz value. Our benchmarks do not enable or disable Turbo Boost, so the benchmarks are performed at whatever frequency the CPU chooses to operate on. Most of our benchmarks complete in 10 seconds, but we're planning to implement some sort of long-haul benchmarks in the future in order to better measure the long-term performance you can expect from such low-TDP parts that turbo like crazy in the short run Exactly as the graph from the TechSpot article shows.
  23. Fiery
    Probably the secondary temperature shows a diode that is placed close to the SSD controller chip, while the first diode is placed far from it. In which case the first temperature would be considered or better labelled as "enclosure temperature"; while the second temperature should rather be called "SSD controller chip temperature" for example.
  24. Fiery
    AIDA64 v1.50 is a very old version. Make sure to use the latest version of 5.95: https://www.aida64.com/downloads/latesta64xe Let me know if the problem persists.
  25. Fiery
    Please note that AIDA64 (for Windows PCs) is already localized to Spanish. Our Android mobile app (AIDA64 for Android) is also localized to Spanish. Regards, Fiery
×
×
  • Create New...