Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. Our iCUE Nexus device hasn't arrived yet. As soon as it hits our lab, we start researching how can we support it. I have high hopes of fully supporting it as long as you close iCUE (software) since it notoriously collides with any other hardware monitoring software that is trying to access Corsair hardware. As for El Gato, the support is quite basic. You can place a single image on the last key and that's it. We're hoping that someone can develop a plugin for it that would allow more flexibility and greater interaction with other plugins. Currently we cannot allocate more development time on that project. I cannot recommend either, since El Gato support is too basic, and without a test device I cannot confirm that iCUE Nexus would work with AIDA64.
  2. Less issues and also usually you can obtain a cheaper _and_ larger screen that way.
  3. Are you using the latest beta build of AIDA64?
  4. 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. Make sure to also have both EC related options enabled in AIDA64 / main menu / File / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching
  5. Freezing, in case it's not due to a system lockup (system crash) is normal when you have the memory stress test enabled and you've got 32 or more GigaBytes of RAM installed. Windows can get quite busy and unresponsive when a certain running program is allocating almost the entire system memory for itself. As soon as the memory is fully allocated, the freezing should go away though.
  6. Temperature #2 is odd, since you're supposed to have Temperature #1 (which is also called T_Sensor1) on your motherboard. PCH Diode is the internal temperature of the chipset (PCH), measured by the PCH's own thermal sensing logic.
  7. Thank you. I have no idea why it doesn't work, so we've ordered a Kraken X-3 device to check it out more thoroughly. Please give us 2 weeks to solve this, because most of our team is currently on vacation.
  8. It's odd, since AIDA64 doesn't write/alter BAR5, but only reads it. We're in contact with AMD about this issue, which seems to be due to a collision between AMD video drivers and the part of AIDA64 that detects unified shader count on AMD GCN and RDNA GPUs. I hope AMD can come up with a solution to this issue that was never a problem before. They must have changed something in one of the recent video driver updates that made the collision happen.
  9. 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
  10. What motherboard, CPU and video card(s) do you have in your system? Do you have Valorant Vanguard installed?
  11. Check what happens if you only enable the CPU subtest of the AIDA64 System Stability Test, and then what happens when you only enable the FPU subtest. The first one (CPU) will put less thermal stress on your system than the second one (FPU). Watch how the CPU temperature reacts to each of the tests. In case it crashes much quicker with the FPU subtest, then my conclusion would be that it is an overheating issue.
  12. Thank you for your feedback and kind words! Yes, we're already working on supporting the upcoming RTX 3000 Series "Ampere" GPUs As for the Statistics tab, the readings that you have on the Voltages tab should also appear on the Statistics tab. If that's not the case, then please send me a screenshot of both the Voltages and Statistics tab. Maximize the System Stability Test window before making the screenshots please.
  13. I'm certain the new CPU temperature reflects the right measurement for the CPU temperature. Here's a fix for the voltages: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works
  14. The above mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  15. Then the issue may be related to the AMD PMLog interface that AIDA64 uses to monitor Vega and Navi GPU based video cards. Please try to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability and restart AIDA64 to apply the changes.
  16. Thank you, we'll implement those tricks in the next AIDA64 app update.
  17. Thank you! We'll make sure the next AIDA64 app update will detect Bluetooth version as 5.0 on your TV.
  18. Do you get proper results for the benchmarks that you can access from the left tree menu of AIDA64 main window, like CPU Queen or FPU Julia?
  19. Please post into this forum in English if possible.
  20. Thank you, those seem to be normal. Can you please post a screenshot of the Computer / Sensor page of AIDA64, showing all sensor readings ideally on a single picture? Or, you can use the right-click context menu on the Sensor page to copy the data to the Clipboard and paste it here, into the topic.
  21. Thank you! The issue may be related to your video card then. Do you have an nVIDIA video card in your computer?
  22. It's coming soon. Please don't mix support for that screen into this topic though.
  23. Try to ask Matrix Orbital about those issues. To me it seems to be a hardware failure or hardware configuration issue.
  24. These are respectful numbers indeed. Can they be better? I don't know, since we're not skilled in OC here at FinalWire Others may be able to chime in and give you more meaningful feedback on the OC achievements.
×
×
  • Create New...