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
    Are you using the latest video driver for your GPU?
  2. Fiery
    Can you see any readings (on the Computer / Sensor page of AIDA64) related to your Z63 device? 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
  3. Fiery
    Please try the above linked latest AIDA64 beta build.
  4. Fiery
    Thank you for letting us know about how you managed to resolve it. I'm glad it works fine now with your system.
  5. Fiery
    ICX3 is not supported by AIDA64 yet, but we'll work on it
  6. Fiery
    A 5-inch BeadaPanel may fit your requirements: https://www.ebay.com/itm/BeadaPanel-5-LCD-Display-for-AIDA64-USB-Single-Cable-Monitor-WinUSB-SDK/113907827722?hash=item1a856f840a:g:YJQAAOSwwKpdkcxK It is fully supported by AIDA64 and IMHO it's a great value for the money.
  7. Fiery
    AIDA64 only supports the optional buttons of GLCD2USB. You can use the Hot Keys facility of AIDA64 to switch between LCD pages (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Hot Keys).
  8. Fiery
    AFAIK it's due to a BIOS issue related to Asus ROG Strix B450-F Gaming motherboard that Asus has to fix.
  9. Fiery
    Yes, but latest version could either be the latest stable version (v6.25.5400) or the latest beta build. 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
  10. Fiery

    Sharp Aquos

    Fiery replied to Гуля's topic in Android Forum

    I'm afraid we have no information on how could you solve this codec issue Maybe someone else can chime in who's more experienced in solving such matters.
  11. Fiery
    Please 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. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery
  12. Fiery
    We're rolling out a new AIDA64 update in 48 hours that will fix GPU support for RTX 3000 Series.
  13. Fiery
    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. Let me know if it helps.
  14. Fiery
    Thank you! Based on your report I suspect your device is trying to pretend having 8 cores in its CPU while actually it has only 4 cores. So the actual SoC model is MT6732 as correctly shown on the CPU page of AIDA64.
  15. Fiery
    Do you have both RAID related options enabled (checked) in AIDA64 / main menu / File / Preferences / Stability? RAID member enumeration RAID SMART support If yes, then please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Attach the results as a TXT file to your post. And also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Attach the results as a TXT file to your post. Thanks, Fiery
  16. Fiery
    Is this issue related to how our app (AIDA64 for Android) works on your device?
  17. Fiery
    Have you tried it with the latest AIDA64 beta build? https://www.aida64.com/downloads/latesta64xebeta
  18. Fiery
    How do you turn off your primary monitor? Powering it off by its power button?
  19. Fiery
    You can use the Logging facility to record the system values and sensor readings through multiple stress test sessions. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging to activate and configure it.
  20. Fiery
    AIDA64 should still work.
  21. Fiery
    Meanwhile we've managed to fix it in the latest AIDA64 beta build: https://www.aida64.com/downloads/latesta64xebeta
  22. Fiery
    MediaTek can be confusing about what values they encode to various places of the Android profile about their SoC's. I wouldn't mind about how it's called but rather focus on how many cores it's specified to have at what clock frequency, and whether those values can be seen properly on the CPU page in AIDA64. As for RAM size, indeed there could be a portion reserved for other purposes, although 1/3 of the RAM size reserved sounds a bit excessive. As for internal storage, sadly a lot of space is reserved on many devices for the Linux kernel and its files, for Android system files and system apps (built-in apps), and also for the recovery partition. That's why modern Android installations wouldn't really fit on anything less than a 10GB storage
  23. Fiery
    Some motherboards may wire the DIMM slots incorrectly to the SMBus. That's not a problem, since it's only a matter of how you call a certain DIMM slot. As for GPU fans, first is the GPU RPM (fan rotational speed), and the second one is the fan duty cycle setting (a percentage value). Duty cycle dictates how fast the fan is supposed to be spinning, but it's not a measured or observed value. Even with a 100% duty cycle the fan could be stopped if it's e.g. clogged up or there's a fan malfunction.
  24. Fiery
    No, since it's only an informational value. Its value doesn't affect how our benchmarks behave or how the result is being calculated or shown.
  25. Fiery
    Thank you, but please avoid posting a single issue into multiple topics.
×
×
  • Create New...