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
    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.
  2. 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.
  3. 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.
  4. 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.
  5. Fiery
    Please let us know the full model name and/or part number of your graphics card. Thanks, Fiery
  6. Fiery
    Maybe there's an intermittent communication issue on the SPD bus that sometimes prevents detection of one of your memory modules.
  7. 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.
  8. Fiery
    We'd love to, but as far as we can tell, the latest Chroma SDK release doesn't support Core yet.
  9. Fiery
    Yes, they look fine.
  10. Fiery
    AIDA64 should provide that information on the Display / GPU page, as Bus Type.
  11. 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.
  12. Fiery
    Are any of those issues related to our app, AIDA64 for Android?
  13. Fiery
    We're planning to roll out the next AIDA64 stable update sometime during the upcoming 4 weeks.
  14. 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
  15. 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.
  16. 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.
  17. 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/
  18. Fiery
    Please 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. You may need to enable status bar in AIDA64 / main menu / View first. BTW, has the total system memory amount increased after you've installed the new memory module? Thanks, Fiery
  19. Fiery
    In theory, any PCIe M.2 SSD should work, as long as it physically fits there. But notebooks can be challenging systems when it comes to hardware upgrades. So there's absolutely no guarantee that 960 Evo would work there.
  20. Fiery
    We'll do our best This is a really new and strange issue to us. We basically needed to come up with a virtual SMBus layout to emulate the 4 memory channels that your motherboard offers. That's because the Skylake-X memory controller manages the SPD channels as if the CPU had only 2 memory controllers. Very odd...
  21. Fiery
    Perhaps Asus removed VRM temperature reading from the BIOS Setup on all versions of your motherboard. AIDA64 fortunately doesn't care about the BIOS version nor the motherboard version. It simply tries to read the corresponding register from the sensor chip, and when it holds a meaningful value, it shows it.
  22. Fiery
    Your notebook features an Intel Sandy Bridge class iGPU that doesn't support OpenCL. AIDA64 GPU stress test and GPGPU benchmarks require a GPU that supports OpenCL.
  23. Fiery
    The Ubuntu Touch OS has been discontinued, and no new devices are rolling out to feature the last release. We will only resume further developing our Ubuntu Touch app in case the OS itself gets further developed and enhanced.
  24. Fiery
    AFAIK OpenStore doesn't accept app submittals that require special permissions and that are not open-source. Due to its nature of being a sysinfo/diagnostic tool, our app requires special permissions, and we're not planning to publish its source code. Hence I don't think our app can ever get to the OpenStore.
  25. Fiery
    Thank you for your feedback.
×
×
  • Create New...