Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12273

  • Joined

  • Last visited

  • Days Won

    541

 Content Type 

Everything posted by Fiery

  1. Fiery
    We will look into it after the rollout of the next AIDA64 stable update, which is due next week
  2. Fiery
    You can purchase a license renewal at: https://www.aida64.com/support/renewal Let me know (preferably in private message) if you run into any issues during the renewal process, or in case you have any questions about it.
  3. Fiery
    Those temperatures are quite high, so I'd definitely try to do something more in order to improve the cooling of your CPU and/or your system case.
  4. Fiery
    Why don't you simply use the built-in auto-start facility of AIDA64?
  5. Fiery
    As far as we know, SPF-83V uses a separate protocol that we know absolutely nothing about So we cannot support that, unless someone can provide us with the necessary programming guidelines for its protocol. We don't have the USB device ID for SPF-85M. Try to enable Samsung SPF LCD support on it, and after then try to issue an USB Dump by right-clicking 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
  6. Fiery
    Heatmaster II is already supported by AIDA64. Just go to AIDA64 / main menu / File / Preferences / Stability, and enable the option called Heatmaster II sensor support. Make sure to restart AIDA64 after altering that option. Regards, Fiery
  7. Fiery
    That information comes from the PCI device of the PCI-E controller. The information is encoded there by the BIOS. Hence, if you see an incorrect value there, it's because of a BIOS bug or BIOS limitation. Regards, Fiery
  8. Fiery
    Thank you for your help, and the report you've submitted!
  9. Fiery
    We seem to have difficulties receiving emails with attachment from certain SMTP servers Thank you, we'll filter D21 out as well. I'll send you a new email Please reply in this topic, to make sure I receive it
  10. Fiery
    We don't have plans for a sub-$30 license. I've sent you a private message about this.
  11. Fiery
    AIDA64 Extreme supports both Logitech Arx LCD and RemoteSensor LCD.
  12. Fiery
    No, there's only one, the 3 PC license.
  13. Fiery
    Thank you for the feedback
  14. Fiery
    I've sent you an email about the SMBus issue. As for the benchmark reference results setting, that's exactly how it should work.
  15. Fiery
    Make sure to 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. Regards, Fiery
  16. 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.
  17. 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 if it helps.
  18. Fiery
    We've fixed the CPU utilization measurement issues in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  19. Fiery
    The mentioned new AIDA64 beta update is now available for download at: https://www.aida64.com/downloads/latesta64xebeta
  20. Fiery
    Thanks a lot! Please try the latest AIDA64 beta available at: https://www.aida64.com/downloads/latesta64xebeta If it still crashes while scanning the SMBus, please let me know the new device index where it stops.
  21. Fiery
    If you could check what's the device that's scanned when the system turns off, we can filter that device out. Previous MSI boards with Z170 and X99 chipset are sensitive for scanning at device 21h, 22h and 23h, so we skip those devices there. We haven't received any guidelines from MSI about Z270 boards, so we somehow have to discover if there are sensitive devices there too
  22. Fiery
    I suppose the BIOS is doing some magic on your MSI motherboard
  23. Fiery
    The difference between how NB clock is measured on the Overclock page vs. on the Cache & Memory Benchmark panel, is that the latter will disable the power management facilities (namely EIST a.k.a. SpeedStep and C1E a.k.a. Enhanced Halt State) of the CPU before measuring the clock speeds. Maybe MSI motherboards alter the behavior of the NB, ie. adjust its operating frequency in a proprietary way when those power management features are disabled? As for the SPD bank switching issue, it looks a lot like a BIOS issue.
  24. Fiery
    I'm afraid we have no idea what could work incorrectly about the NB clock measurement. How do you know it's an issue limited to MSI motherboards? As for the SPD issue, for some reason your memory modules cannot perform SPD bank switching. Bank switching is necessary to read the full 512-byte SPD block of DDR4 memory modules. Can you please check if CPU-Z is also affected?
  25. Fiery
    Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the devcie (in your case Sony) didn't encode the info there, then sysinfo apps cannot read or detect it.
×
×
  • Create New...