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, now I see what's going on there. What we've done is consolidated the core temperature readings on AMD processors by removing the core temperature readings and adding a single "CPU Diode" reading. Those processors have only a single temperature diode, so displaying that single reading as 4 (or 6 or 8) separate core temperatures was redundant and unnecessary. If you check the readings via AIDA64 v5.80, you will see that the 4 separate core temperatures were actually always the same
  2. Fiery
    Please reinstall AIDA64 v5.92, restart Windows, and check if it helps. If not, then 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. Please keep posting in English. This is an English language forum, and also we cannot speak Chinese I'm afraid. Thanks, Fiery
  3. Fiery
    Of course! And thank you for your feedback, I'm glad it worked.
  4. Fiery
    It seems to be a firmware issue of the hard disk drive in question. We may need to completely disable SMART readout for your HDD using the current firmware version. What is the full model ID and revision (firmware) ID of your HDD? Do you experience similar issues while running HWMonitor? Are you using a HDD monitoring software like HD Sentinel?
  5. Fiery
    I'm afraid it's not possible with AIDA64 for Android. That app of ours only supports exporting the collected sysinfo via email submit.
  6. Fiery
    Because only recently we could manage to acquire a system with AVX-512 support. The CPU you're referring to (Knights Landing) is a niche product, has no official Windows support, and virtually no AIDA64 users own such a machine. BTW, due to the enermous complexity of AVX-512 (over 1000 new x86 instructions) it takes over a year to fully optimize all AIDA64 benchmarks to AVX-512. We've started working on it cca. a year ago, but we couldn't finish it up before the Skylake-X launch. It's at 95% now, and we're going well, but it will still take 2 to 4 months to finish everything.
  7. Fiery
    Such issues are usually due to intermittent voltage measurement issues. In most cases it is caused by a collision between AIDA64 and another monitoring software. Do you happen to have AI Suite installed?
  8. Fiery
    AVX-512 is not yet supported. We'll add HW SHA information to the CPU Hash page of the Benchmark guide. Thanks, Fiery
  9. Fiery
    You use quite an old AIDA64 version. Can you please check 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.
  10. Fiery
    Thank you, but that's not what I've requested above. Please post an ISA Sensor Dump, because only that one contains the necessary details for us to fix this bug.
  11. Fiery
    Thank you for your feedback
  12. Fiery
    Thank you! We'll add CPU Mesh and VCCIO voltage readings in the next AIDA64 beta update due next week. I'll post a message into this topic once the new beta becomes available for download.
  13. 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
  14. Fiery
    We've implemented preliminary EVGA iCX sensor support 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 how it works. Note that the iCX related readings will only appear on the Computer / Sensor page at this time. As the new sensor module gets more mature, we'll add the readings to the LCD, SensorPanel, OSD Panel (etc) modules as well. Please note that currently it supports a single video card model: EVGA GTX 1080 Ti FTW3 iCX. If it doesn't work on your video card, or in case you have a different video card that features iCX sensor, 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.
  15. Fiery
    We've implemented preliminary EVGA iCX sensor support 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 how it works. Note that the iCX related readings will only appear on the Computer / Sensor page at this time. As the new sensor module gets more mature, we'll add the readings to the LCD, SensorPanel, OSD Panel (etc) modules as well. Please note that currently it supports a single video card model: EVGA GTX 1080 Ti FTW3 iCX. If it doesn't work on your video card, or in case you have a different video card that features iCX sensor, 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.
  16. Fiery
    We've implemented preliminary EVGA iCX sensor support 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 how it works. Note that the iCX related readings will only appear on the Computer / Sensor page at this time. As the new sensor module gets more mature, we'll add the readings to the LCD, SensorPanel, OSD Panel (etc) modules as well. Please note that currently it supports a single video card model: EVGA GTX 1080 Ti FTW3 iCX. If it doesn't work on your video card, or in case you have a different video card that features iCX sensor, please submit a fresh nVIDIA SMBus Dump.
  17. Fiery
    We've implemented the requested feature 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 how it works
  18. Fiery
    What video card and ForceWare version do you have? We'll try to reproduce the issue and then fix it up if possible.
  19. Fiery
    Yes, that could happen when the polarity of charge rate reporting is reversed in the Android platform. We need to implement a workaround for each those devices -- very time consuming task But, if you can send a report of your Android devices from the About page, we can do it of course
  20. Fiery
    It's not supported yet. We've just ordered a unit, and we'll implement support for the Commander Pro protocol as soon as it arrives. I'll let you know in this topic once a new AIDA64 beta -- with the protocol implemented -- becomes available for download. It shouldn't take more than 2 weeks approx.
  21. 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
  22. Fiery
    I know The problem with such approach is that AIDA64 supports over 50 LCD protocols, and it's not the best idea to cherry-pick from them. And we don't want to implement 100 more separate hot-key options either, to cover enabling+disabling the 50 different LCD protocols
  23. Fiery
    ULPS has little to do with the current sleep or awake state of a certain GPU. Even when ULPS is enabled, and AIDA64 wakes the GPUs, it will still not query the non-primary GPU (or GPUs) for video BIOS readout. And that's because ULPS is very agressive: it can put the non-primary GPU to sleep anytime, even half-way reading the flash BIOS for example. And when that happens, a system lockup is likely to happen AIDA64 detects the marked information using ADL (AMD proprietary API) calls. http://developer.amd.com/display-library-adl-sdk/
  24. Fiery
    What motherboard do you have? Can you see the MESH voltage in the BIOS Setup among the other measured voltage readings? (e.g. PC Health Status or H/W Monitor page in the BIOS Setup)
  25. Fiery
    Thank you for the dump. Yes, we'll add it, but first, we need to find a way to detect the presence of the iCX MCU. So far we haven't found a reliable way of doing that, but we keep looking for a proper solution. Please give us a few more days to investigate this.
×
×
  • Create New...