Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12008

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    I've sent you a private message about this.
  2. Fiery
    I'm afraid I don't understand that. Can you please explain (in details) how the issue has been affected by the new beta build of AIDA64?
  3. Fiery
    I'm not that experienced in Linux, but I don't think any of those motherboards would have any issues running Linux.
  4. Fiery
    Thank you for your feedback. Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update.
  5. Fiery
    AIDA64 memory stress test is supposed to allocate almost the entire free physical memory amount. You're not supposed to browse the web while the test is running, since the stress test will not leave enough free memory for other processes to work properly.
  6. Fiery
    AX1500i vs RM650i: Make sure to enable both Corsair AXi sensor support and Corsair HXi/RMi sensor support on both systems, in order for AIDA64 to properly handle both PSUs. They use very different protocols BTW, and the one used in the AXi PSU is prone to be less reliable than the more stable protocol of RMi. GPU TDP% should be available for both your GPUs. On your PC2 system (with GTX1050Ti) 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. Thanks, Fiery
  7. Fiery
    Thank you, it looks much better We'll fix the issue in the next AIDA64 beta update. I'll post a link into this topic once the new beta build is available for download.
  8. Fiery
    Thank you, we'll implement advanced sensor support for your system in the next AIDA64 beta update. I'll post a link into this topic once the new beta build is available for download.
  9. Fiery
    It shows how much your battery is charged up. When the battery is not worn out, charge counter should very closely match the capacity of the battery. Android devices and their batteries do not store any counters, so it's impossible to track the number of charge-discharge cycles through the lifetime of the battery.
  10. Fiery
    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.
  11. Fiery
    Thank you. Strangely we cannot see any valid readings in the W_FLOW register. One more odd thing is that the CPU OPT fan register seems to indicate a reading of 1395 RPM in your register dumps, but on the BIOS Setup photo above the CPU OPT fan didn't seem to be spinning at all.
  12. Fiery
    It's an issue that only comes up when you have SMT disabled on Ryzen processors. We will fix the issue in the next AIDA64 stable update due in a few weeks from now.
  13. Fiery
    HD Graphics 530 is the marketing name for the GT2 iGPU of Skylake-H CPUs.
  14. Fiery
    Yes, it's only a cosmetic issue that doesn't actually effect the capabilities of the WiFi controller.
  15. Fiery
    Such issues could happen when the platform designer (in your case Alfawise) fails to encode the proper information in the Android WiFi profile to indicate the true capabilities of the WiFi controller. We'll implement a workaround in the next AIDA64 for Android app update.
  16. Fiery
    1) Pump #1 shouldn't be available as a fan on your particular motherboard. Unless of course PC1 system also includes an additional sensor device that provides the Pump #1 reading. Also, make sure to have both systems running the same AIDA64 version, and that both systems have the following 2 options enabled in AIDA64 / main menu / File / Preferences / Stability: Embedded Controller (EC) support Embedded Controller (EC) bank switching 2) Temperature #1 through #4 may be available if T_Sensor1 and/or the EXT_Sensor1..3 sensors are currently connected. Maybe PC1 provides unreliable (bogus) readings for T_Sensor1 sometimes, but in most cases it's not available. 3) SPD chips are wired in a different way on Broadwell-E (i7-6950X) and Haswell-EP (Xeon E5-2680 v3) processors. Different SPD controllers are connected to the same DIMM slots, and that is why the DIMM thermal readings labels differ across those CPUs. 4) +3.3V Current, +3.3V Power and Power Supply (I suppose you mean PSU Power by that) are provided by the AX1500i PSU of your PC1. RM650i of your PC2 system is a less sophisticated PSU than the AX1500i of your PC1 system. 5) GPU TDP% is only available on modern nVIDIA video cards. Most likely your PC2 features an AMD video card, and only PC1 features a nVIDIA video card. 6) -12V voltage is once again provided by the AX1500i PSU of PC1. 7) On PC2 CPU OPT fan may provide an unreliable reading, or it's spinning too slow for the sensor chip to measure the fan RPM reilably. 8) There's no need and no way to reset the list of sensors that AIDA64 manages, simply because it is always refreshed (polled again) at every AIDA64 startup.
  17. Fiery
    The FPU subtest of the AIDA64 System Stability Test is a more demanding task than the CPU subtest. While the FPU subtest is running, your processor is hitting its pre-programmed power limits, and has to run at a lower clock speed in order to obey the power limits.
  18. Fiery
    Thank you for the photos. 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. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  19. Fiery
    Thank you. We've tried to reproduce the issue on our own Gigabyte video card, but for us it worked flawlessly, even with GPU sensor polling enabled in AIDA64. Please let me know what exactly happens, what functionality of Aorus Graphics Engine stops working when you have AIDA64 auto-started at Windows bootup.
  20. Fiery
    Thank you for the feedback
  21. Fiery
    Here's the above mentioned new AIDA64 beta build. Hopefully it will now work perfectly on all pages https://www.aida64.com/downloads/latesta64xebeta
  22. Fiery
    It looks like a memory leak or memory corruption issue -- due to a software bug in AIDA64 GPGPU benchmarks, not due to a hardware issue about your computer. Please give us a few days to try and reproduce the issue on our own test systems, find the bug, and fix it up. I'll let you know in this topic how it goes.
  23. Fiery
    It says "Bus Type: Integrated" on your picture
  24. Fiery
    W_FLOW header is shown as Water Flow fan in AIDA64. But you may need to enable the following 2 options in AIDA64 / main menu / File / Preferences / Stability to have the reading properly measured by AIDA64. Embedded Controller (EC) support Embedded Controller (EC) bank switching Regards, Fiery
  25. Fiery
    Full support will be implemented in the next AIDA64 stable update. We're planning to roll that out in March.
×
×
  • Create New...