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
    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.
  2. 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
  3. 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.
  4. 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.
  5. 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.
  6. Fiery
    Thank you! The dump shows no issues. I'm glad you've managed to resolve it
  7. Fiery
    Just as always, we're open to any further discusson on how to fix any remaining issues about Asus motherboards.
  8. 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?
  9. 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.
  10. 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
  11. 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.
  12. 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.
  13. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling 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
  14. Fiery
    I've sent you a private message about this issue.
  15. Fiery
    You've got a private message
  16. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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
  17. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus 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
  18. Fiery
    We've never tried that, so would love to hear some feedbacks on such a configuration.
  19. Fiery
    Intel uses VCCIN for the Skylake-X voltage rail in question, so that's the correct term to use by monitoring software as well.
  20. Fiery
    If you don't have Asus AI Suite installed, try to enable the 2 options about EC in 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.
  21. Fiery
    Please navigate to the installation folder of AIDA64, and create the following 2 new files there: ENABLE_SMBUS_LOG.TXT ENABLE_HWMONINIT_LOG.TXT They can be simply 0 byte long (empty) files. Then start AIDA64, go the Computer / Sensor page, wait for your computer to lock up, restart it, and check the 2 files that you've previously created. If they have a content, please attach the files to a forum post, so we can check where the lockup occurs inside the AIDA64 sensor module. After finding the culprit, we can work on fixing the issue or implementing a workaround. Thanks, Fiery
  22. Fiery
    HDMI, DSub, DVI and DisplayPort connected displays are handled as regular monitors by Windows, so you can use the SensorPanel module of AIDA64 to display sensor readings on your secondary monitor. If the display is always connected, the SensorPanel window will be placed at the right monitor at the right coordinates once you start AIDA64. Of course you can make AIDA64 launch automatically at Windows startup by enabling the option AIDA64 / main menu / File / Preferences / General / Load AIDA64 at Windows startup As for configuring your SensorPanel layout, make sure to check this guide: https://www.aida64.co.uk/knowledge-base/how-create-fully-customized-sensorpanel-aida64
  23. Fiery
    Not yet. We're planning to roll that out early next year.
  24. Fiery
    1) Reviewers do not rely on our reference results, but they use their own test results. And apart from reviewers, not many folks are interested in single-core benchmarks. Why to have 4, 6, 8 or 18 cores in your CPU and only use just one to check how great your CPU is? 2) No, we have no plans on that.
  25. Fiery
    I'm afraid we have no specific idea on what to do about that. Try to ask the same question in a forum that's geared towards Asus ROG users and products, or specifically Maximus VI motherboards and their owners.
×
×
  • Create New...