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
    Thank you. We've fixed the issue in 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 how it works.
  2. Fiery
    Thank you for the dumps. We've fixed the issue in 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 how it works.
  3. Fiery
    No, it's not. But here's the one that is https://www.aida64.com/downloads/latesta64xebeta
  4. Fiery
    We haven't noticed it yet, and no other US based AIDA64 users complained yet. We've asked our ISP, but they also haven't found any issues. So it could have been (it could be) something under the ocean or such
  5. Fiery
    "Waiting for Sync" is not displayed by AIDA64, so the issue must be in either the Android platform (about email submittal), or in the email app you use to send the report out.
  6. Fiery
    On the SensorPanel make sure to use a more frequent update rate. 500 milliseconds should be safe, but you can even go down to 100 millisec.
  7. Fiery
    We haven't changed anything about that particular sensor item between 4321 and 4329 beta builds. If it still works incorrectly, please create a screen shot of he issue and post it.
  8. Fiery
    Thank you, the issue will be fixed in the next AIDA64 beta update due in a few hours from now
  9. Fiery
    If you want to focus on the real cores and ignore the secondary (virtual) cores of SMT/HyperThreading, you simply need to skip every second logical processor.
  10. Fiery
    Since the RAM acts up not only with AIDA64, but also with another stress testing software, I suspect it may just be some kind of compatibility issue between your RAM modules and your motherboard. You may want to ask Gigabyte to resolve the issue in the next BIOS update.
  11. Fiery
    Does it get stuck after the report creation process is complete, or somewhere in the middle?
  12. Fiery
    We've checked, and we couldn't reproduce the issue on our 5820K based test system (with HTT disabled). The next time it occurs on your system, please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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
  13. Fiery
    Anytime
  14. Fiery
    1.8V is not VID at all, but some bogus value
  15. Fiery
    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
  16. Fiery
    That happens when the sensor item is no longer available. Do you still have the UPS connected to your computer?
  17. Fiery
    We've done some experiments on that, but it wasn't successful. If the BIOS fails to properly initialize the thermal controller, PCH Diode temperature cannot be measured by Windows software or any other method
  18. Fiery
    The video driver reset takes a second or two, and after it is done everything should go back to normal. Except for the GPU subtest of the AIDA64 System Stability Test which will be stopped after the video driver reset. So in case a permanent blackscreen is exhibited, it may be due to a video driver reset issue in the first place, but then the video driver cannot recover due to -- in most cases -- a hardware stability issue. In other words: if you cannot get the display output working after the video driver reset, it's a hardware malfunction. Such malfunction can be due to a number of reasons, including excessive overclocking (and/or overvoltage), overheating, video memory stability issues (or overheating), PCI Express communication breakdown, etc.
  19. Fiery
    And we've done that in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  20. Fiery
    The mentioned new AIDA64 beta update is available for download at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade.
  21. Fiery
    We've added the requested new hot key in 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.
  22. Fiery
    1) If you're a power user, then I suppose shifting the indexes by one shouldn't be a problem 2) Please make a screen shot (or report, or copy-paste) of the Storage / Physical Drives page of AIDA64 at both states (when it's OK; and when the anomaly occurs).
  23. Fiery
    Thank you, that's great to hear
  24. Fiery
    Power out is calculated using the same formula as power efficiency. Efficiency = power out / power in. And out of those 3 values only the power out value can be directly measured or detected on most PSUs.
  25. Fiery
    I'd still say: I don't think it would qualify your motherboard for a RMA, but it may worth a try to call the store where you bought it.
×
×
  • Create New...