Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    It sounds like a sophisticated and also quite complicated idea One immediate issue about it: how to decide which is the best setting? Because sometimes a higher memory clock combined with worse timings could yield to a higher bandwidth but also higher (worse) latency. One would have to gear the overclocking towards maximizing bandwidth _or_ minimizing latency. The 2 together may or may not work out. A loop that would cycle through 10 or even more tests of each benchmark may work out well, but then one would have to digest the results in a CSV or XML output, and that also would not be ideal for your imagined kind of usage I suppose.
  2. Fiery
    We've fixed the issue in 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.
  3. Fiery
    We've fixed the issue in 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.
  4. Fiery
    We've fixed the issue in 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.
  5. Fiery
    Please find the Strike7 API files in: http://users.aida64.com/strike7_api_1_1.zip
  6. Fiery
    Thank you. The issue is due to the fact that Corsair stopped using the necessary synchronization mutexes that they defined to let 3rd party applications work with their hardware. Now the old hardware may still work, but the new hardware, e.g. Corsair Commander Pro will not work. The issue will only be fixed once Corsair gets around and enable the old mutex on their new hardware as well.
  7. Fiery
    It should work with the latest AIDA64 beta build of 4510. If not, please post a nVIDIA SMBus Dump, and we'll check it out.
  8. Fiery
    I'm afraid we have zero experience about Tensor Core benchmarks or even accessing those cores. I suppose the only way to do that right now is via CUDA, but we don't have any actual experience in CUDA. First we would need to port the existing GPGPU benchmarks from OpenCL to CUDA, and after then we could deal with adding new "juice" to the existing set of GPGPU benchmarks. We may do that next year, but I cannot promise an actual release date for those CUDA benchmarks right now…
  9. Fiery
    When it comes to processing an AIDA64 XML report file, it's much easier and quicker to go by the ID fields, and not trying to process the groups or field labels. And when you get multiple matches for a certain ID (for example, that ID for USB devices is 537), you need to cycle through them in order to process the list of similar kind of hardware or software component. That's just the way it is, that's how you process a XML file We do have unique IDs assigned for unique kind of components, but when there are multiple components of the same kind, you cannot avoid going through a loop/cycle to enumerate them and process them in a way you need.
  10. Fiery
    Thank you. Please let me know the version of ForceWare drivers that you have installed on your first 2 systems.
  11. Fiery
    Do you overclock your memory, or use special tuning settings for your RAM?
  12. Fiery
    Thank you. 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.
  13. Fiery
    If you need to iterate through a list of USB devices anyway, I'm not sure why you need to have an index number included in the description, or how would it help. Maybe you can elaborate on what you're doing? It may be possible to alter the XML report layout in a way to make it more useful for you.
  14. Fiery
    The problem with such devices is that it's not possible to pinpoint them based on a certain hardware type or property. There's no such device that has "camera" type or "Bluetooth" type There's a list of USB devices, and one of them may happen to be a camera -- but even its model ID may not have the word "camera" anywhere in it.
  15. Fiery
    On your particular motherboard we've already used EC bank switching (before AIDA64 v5.95), but it wasn't safe to do it by default, without any precautions. That's why we've implemented the new EC bank switching option, and made it disabled by default. While EC bank switching is enabled, and you have AI Suite running in the background, things could well go south when AI Suite and AIDA64 collides due to non-synchronized bank switching activity. Of course it would be a whole lot easier if Asus made AI Suite work together with 3rd party monitoring applications, but it doesn't seem to happen anytime soon
  16. Fiery
    It seems on some configurations reading EC (Embedded Controller) registers cause high DPC latency. The only "solution" we've found so far is to disable EC readout by disabling the following options on the page AIDA64 / main menu / File / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes. However, by disabling those, you will lose a set of sensor readings, e.g. PCH temperature, T_Sensor1 temperature, WATER_IN temperature, WATER_OUT temperature, Water Pump fan, Water Flow fan, VCC Sustain voltage, CPU PLL voltage, VCCMP voltage.
  17. Fiery
    That explains it, thank you Meanwhile we've been informed that the situation is a bit more complex than on other Asus ROG motherboards. We'll add the relevant register readout in the next AIDA64 beta build, but it will only work when the reading is available in the BIOS.
  18. Fiery
    You need to use the Correction feature with a ratio of 0.333. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction to configure it.
  19. Fiery
    Thank you! The dump shows no issues. I'm glad you've managed to resolve it
  20. Fiery
    Just as always, we're open to any further discusson on how to fix any remaining issues about Asus motherboards.
  21. Fiery
    Thank you! It's quite weird, since the register that should hold the VRM temperature readout is zero on your motherboard. Can you please take a photo of the BIOS page where it shows the VRM temperature readout?
  22. Fiery
    Go to AIDA64 / main menu / File / Preferences / Stability, and enable both the following options: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes.
  23. Fiery
    Both of you, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller 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
  24. Fiery
    The AIDA64 external LCD display module is for USB and serial port connected displays. The AIDA64 SensorPanel module is not designed for external displays specifically, but for Windows Desktop monitoring. But since HDMI, DSub, DVI and DisplayPort displays all extend the Windows Desktop to a certain degree, you can use SensorPanel on all of them.
  25. Fiery
    Go to AIDA64 / main menu / File / Preferences / Stability, and enable both the following options: Embedded Controller (EC) support Embedded Controller (EC) bank switching After altering those options, make sure to restart AIDA64 to apply the changes.
×
×
  • Create New...