Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. Fiery
    Mice007 meant the send/receive files feature of the Remote Control module. Try to initiate a Remote Control session, and you'll see a separate Tools menu on the Remote Control client window.
  2. Fiery
    Since LCD Smartie is not our software, nor did we develop the plugin for it, I cannot assist you regarding that issue. As for the direct support for Crystalfontz in AIDA64, 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
  3. Fiery
    Thank you for your feedback. It will take a few more weeks for us to get to rolling out a new stable update
  4. Fiery
    Thank you for your feedback
  5. Fiery
    You don't need to disable SMBus support, since that particular module shouldn't cause any issues on your motherboard. As for crashes, that can still be because of a collision between your motherboard performing various tasks around the sensor chip and EC. Hard to tell where the issue might be exactly, but without further assistance from Asus (Jon), we cannot tweak the current sensor access solution any further BTW, the crashes might also indicate generic stability issues, like due to excessive overclocking, memory configuration issue, etc.
  6. Fiery
    The way it works on your motherboard is that at idle the Vcore voltage provided by the onboard sensor chip gets too low. In which case we've been told to use the CPU VID value instead of the measured Vcore voltage value. As far as I can tell, the voltage rails you miss aren't monitored by the onboard sensor chip on your motherboard. You may be able to adjust those rails in the BIOS Setup, but readback is not provided.
  7. Fiery
    It could mean that the memory frequency is too high, the memory timings are too tight, or the memory modules aren't compatible with your motherboard. Try to run other memory tests as well, to confirm that the memory modules aren't working properly across different tests.
  8. Fiery
    Thank you. This can happen if SVID is disabled in BIOS - in such case CPU Package power monitoring cannot work. Please check the BIOS settings.
  9. Fiery
    Previous Asus motherboards may have had issues about EC sensors, but now you can disable handling EC sensors in AIDA64. So if that fix (well... more like a silly workaround) doesn't help about Crosshair VI Hero, then it's an unrelated issue to the old 990FX era issues As for Jon's guidelines: on Asus AM4 motherboards we read sensor registers using an unconventional method (MMIO) as opposed to how it works on all other motherboards where we use classic port I/O. We also disable SMBus before reading the sensor registers, and re-enable it when we're done. We're not keen on doing that, but that's what Jon suggested to fix the hardware collision issues. Based on our email correspondance with Jon, those two fixes should be adequate to make AIDA64 sensor polling stable on Crosshair VI Hero and other Asus AM4 motherboards.
  10. 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.
  11. 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.
  12. Fiery
    Thank you. We've tweaked it a bit more, although we're not sure if it makes any difference... Please check it out: https://www.aida64.com/downloads/latesta64xebeta
  13. Fiery
    The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  14. Fiery
    The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  15. Fiery
    Thank you. You own the infamous Crosshair VI Hero That explains a lot. On this motherboard, as The Stilt correctly stated, even Asus has issues when it comes to 3rd party software polling the motherboard sensor registers. AIDA64 follows Jon's (who works for Asus) guidelines on how to handle the IT8655E sensor chip of Crosshair VI Hero. If it still doesn't work 100% reliably, it's not really our fault. We've already tweaked around it a lot, but in case Asus has further ideas on how to make it better, we can put more efforts into this. However, we haven't heard from Jon since July, so we assumed that all issues are gone now around Crosshair VI Hero.
  16. Fiery
    What sort of device are you talking about? Windows PCs or Android based mobile devices?
  17. Fiery
    I don't think so. And even if it was possible, it would require separate support for each motherboard model out there That's also why AIDA64 cannot read BIOS settings: it would be a hell of a job to implement support for every single motherboard out there, one by one
  18. Fiery
    You can also use the Operating System / Services page of AIDA64 to capture a state right after system restart, when the potential Stream service is not running. And then check the same page after you suspect the service has started. Comparing the state for each service could reveal the service installed, used and started by Steam
  19. Fiery
    Thank you. Do you use DPI scaling? (font zooming)
  20. Fiery
    Yes, it could be an invalid reading. 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. Thanks, Fiery
  21. Fiery
    Since there's a workaround for this issue (that I've mentioned above), we're not considering getting back to working on it. It would require us to come up with a new rendering solution, so it's not a few days work. And performance of rendering may also suffer because of transparency.
  22. Fiery
    We haven't got any further assistance from AMD to step further about that issue. There may not be a technical solution afterall
  23. Fiery
    The memory bus properties on the Motherboard / Motherboard page may refer to only the primary CPU of the system, or only the primary IMC (Integrated Memory Controller) of the system. You can check all IMCs for all installed processors on the Motherboard / Chipset page. The AIDA64 CPUID Panel however uses a trick to aggregate all available IMCs to show the total number of memory channels across all CPU sockets. We'll add the missing motherboard physical information in the next AIDA64 beta update due later this week
  24. Fiery
    You can only get rid of throttling by improving the cooling of the CPU. Since you already have a powerful solution, I'm not sure if there's more room for you to push the OC further. As for microstuttering, that can be caused by a few issues, and one of those is when the CPU momentarily throttles to mitigate overheating.
  25. Fiery
    The recently added new command-line option is: /STAY This option can be used to keep AIDA64 running in the background after report creation. It is useful when Network Alerting is used together with /R, /E or /FTPUPLOAD options. The default behavior is that after the report creation process is finished, AIDA64 quits. One can override this by using the new /STAY command-line option.
×
×
  • Create New...