Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11546

  • Joined

  • Last visited

  • Days Won

    489

 Content Type 

Everything posted by Fiery

  1. Fiery
    HD Graphics 530 is the marketing name for the GT2 iGPU of Skylake-H CPUs.
  2. Fiery
    Yes, it's only a cosmetic issue that doesn't actually effect the capabilities of the WiFi controller.
  3. 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.
  4. 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.
  5. 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.
  6. 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
  7. 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.
  8. Fiery
    Thank you for the feedback
  9. 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
  10. 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.
  11. Fiery
    It says "Bus Type: Integrated" on your picture
  12. 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
  13. Fiery
    Full support will be implemented in the next AIDA64 stable update. We're planning to roll that out in March.
  14. Fiery
    Thank you for the dump. Please try to disable GPU sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart Windows. Let me know if it helps.
  15. Fiery
    On your particular motherboard, if you have Asus AI Suite installed, AIDA64 will take the sensor readings using the ATKEX API. But that will only work correctly with AIDA64 as long as you avoid renaming the sensor item labels in AI Suite.
  16. Fiery
    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.
  17. Fiery
    Do you think your monitor notifies Windows of the refresh rate change when it's initiated via the monitor's physical button? Because if not, then I have no idea how to get that information from the monitor itself Unless of course the current refresh rate property is included in the EDID block.
  18. Fiery
    Please let us know the full model name and/or part number of your graphics card. Thanks, Fiery
  19. Fiery
    Maybe there's an intermittent communication issue on the SPD bus that sometimes prevents detection of one of your memory modules.
  20. Fiery
    That's normal, since it shows the real frequency that your memory is operating at. The other values show the DDR (double data rate) and QDR (quad data rate) effective frequencies of GDDR5/GDDR5X memory.
  21. Fiery
    We'd love to, but as far as we can tell, the latest Chroma SDK release doesn't support Core yet.
  22. Fiery
    Yes, they look fine.
  23. Fiery
    AIDA64 should provide that information on the Display / GPU page, as Bus Type.
  24. Fiery
    The dedicated GPU is most likely asleep (de-activated) when AIDA64 starts up, and that causes AIDA64 to miss detecting it. Try to activate the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64.
  25. Fiery
    Are any of those issues related to our app, AIDA64 for Android?
×
×
  • Create New...