Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12009

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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
  6. Fiery
    The above mentioned new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  7. 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
  8. 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.
  9. Fiery
    What sort of device are you talking about? Windows PCs or Android based mobile devices?
  10. 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
  11. 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
  12. Fiery
    Thank you. Do you use DPI scaling? (font zooming)
  13. 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
  14. 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.
  15. Fiery
    We haven't got any further assistance from AMD to step further about that issue. There may not be a technical solution afterall
  16. 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
  17. 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.
  18. 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.
  19. Fiery
    We've checked, and we haven't been able to reproduce this issue with either Crimson 17.5.2 or 17.9.3 WHQL. Maybe because we use a RX 560 test card, and the issue affects only RX 570 and RX 580? Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. 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. BTW, have you tried to install the recently released Crimson 17.9.3. WHQL driver? I wonder if that makes this issue go away or not. Thanks, Fiery
  20. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
    I apologize for the late response (in your other topic). Let's continue investigating this issue here. If you disabled EC support already, then I don't think merely reading a SIO (Super I/O) register like at index 43h could cause such issues. You can try dumping all SIO registers (all 256 of them) by issuing an ISA Sensor Dump, and see if any of those register readouts make the fan spin up to 100%. Right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. If you make such a dump, then please also 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. The dump may help us understand more about your system, and may provide us tips on where to look next. I really thought disabling EC support would cure the issues you're having on your system. Thanks, Fiery
  22. Fiery
    I'm sorry for the late reply. Let's continue this discussion in your other topic
  23. Fiery
    On your particular video card those 2 values are measured using different methods, so you definitely shouldn't add those numbers up or combine them in any ways. AMD GPUs use quite a few secret tricks that are not documented well enough -- but AIDA64 uses those tricks to provide every possible measurements. Due to the lack of documentation though, it's hard for us to provide you with guidelines on how to interpret the readings.
  24. Fiery
    We've only recently managed to acquire a Vega test card that we can use to improve the GPU diagnostic capabilities of AIDA64. We're already working on the issues you've mentioned, as well as a few other Vega related matters. I'll post a message into this topic once a new beta build of AIDA64 becomes available for download
  25. Fiery
    My guess would be the same: Steam must start a background process or service that constantly consumes a few CPU cycles. It would then leave that background process and service running after you closed the Steam Client.
×
×
  • Create New...