Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11334

  • Joined

  • Last visited

  • Days Won

    476

 Content Type 

Everything posted by Fiery

  1. 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
  2. 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.
  3. Fiery
    Thank you for the feedback
  4. 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
  5. 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.
  6. Fiery
    It says "Bus Type: Integrated" on your picture
  7. 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
  8. Fiery
    Full support will be implemented in the next AIDA64 stable update. We're planning to roll that out in March.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. Fiery
    Please let us know the full model name and/or part number of your graphics card. Thanks, Fiery
  14. Fiery
    Maybe there's an intermittent communication issue on the SPD bus that sometimes prevents detection of one of your memory modules.
  15. 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.
  16. Fiery
    We'd love to, but as far as we can tell, the latest Chroma SDK release doesn't support Core yet.
  17. Fiery
    Yes, they look fine.
  18. Fiery
    AIDA64 should provide that information on the Display / GPU page, as Bus Type.
  19. 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.
  20. Fiery
    Are any of those issues related to our app, AIDA64 for Android?
  21. Fiery
    We're planning to roll out the next AIDA64 stable update sometime during the upcoming 4 weeks.
  22. Fiery
    Try to scan eBay using "7-inch TFT LCD" and "8-inch TFT LCD" as search queries. Some of those may fit your needs as well as fit into your case
  23. Fiery
    Linux kernel will allocate cache buffers during the bootup process. So it's normal that most of the RAM is already taken (allocated) when the Sailfish OS boots up. The two battery temperature readouts are because AIDA64 reads temperature measurements using 2 interfaces. The first one is the thermal zones method, which provides a bunch of readings. The list of readouts via that interface may or may not include the battery temperature. So in order to assure that AIDA64 can measure the battery temperature specifically, it will use a second interface to read the battery temperature. When the battery temperature is provided by both interfaces, "Battery" is listed twice on the Thermal page.
  24. Fiery
    The documentation (https://open.uappexplorer.com/submit) on the OpenStore website clearly states that: Since our app would require a manual review (due to the special permissions it has to request), the last point applies to it. And since it's not open source, it cannot be submitted to manual review. So effectively, it cannot be published in the OpenStore.
  25. Fiery
    It's not easy to pick a screen that you've described. When it comes to large colorful LCD displays, we generally recommend to simply pick up a second-hand 15-inch or 17-inch classic TFT LCD monitor that you can connect via DSub, DVI or HDMI to your computer, and simply use the SensorPanel module of AIDA64 (instead of the External LCD module). Such a solution is cheap as chips these days, and gives you a lot of flexibility, since the monitor simply extends your Windows Desktop. And that means you can put any window or any software's user interface on the secondary screen. So you're not tied to AIDA64 and you can use the display for multiple purposes at the same time as well, ie. to share the display area between the AIDA64 SensorPanel and another window. Of course a classic TFT LCD monitor would require an external power source, so it may not be ideal for your purposes. There are USB-connected displays these days that don't require a separate power input, but they may be too expensive. 2 examples of such a display: https://www.asus.com/Commercial-Monitors/MB168BPlus/ https://www.asus.com/Monitors/MB169C-plus/
×
×
  • Create New...