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
    On some (but not all) systems AIDA64 reports the CMOS battery voltage as VBAT Battery voltage on the Computer / Sensor page. If it's not there, you need to try to find it in the BIOS Setup. In there it's usually shown on the PC Health Status page or H/W Monitor page. Replacing it requires a full power-down of the PC. Disconnect the power cord as well. You can remove the battery without any tools and virtually any CR2032 battery can be used as a replacement. Make sure to check the old battery though after removing it, that it's really a CR2032 part.
  2. Fiery
    I think I know what you mean, so no need to hassle with making and uploading a video of the anomaly. I'm thinking about a proper way to get around this issue. The problem is that the OSD Panel is top-left anchored, so when the width changes its top-left corner stays in place and the width increases (or shrinks). It's great when you use left alignment, but can produce jerkiness when the OSD content is right-aligned. We can either let you specify a minimum width for the panel, but then you need to tweak around the find the right width to accomodate all possible text widths as the values keep changing; or make the OSD Panel top-right anchored so its width would increase and shrink on the left border of the panel. Since the latter would require less of a hassle and tweaking on your part, IMHO that should be the way to go. Let us think about it and make a few test runs before coming up with a proper fix.
  3. Fiery
    Most likely WD's software kept the drives locked and other software (like AIDA64) couldn't gain proper access to them.
  4. Fiery
    Try to update the motherboard BIOS to the latest version, and check if your PSU is powerful enough. Also check if it gets stable if you lower the memory frequency or if you use slightly more relaxed timings, like changing Command Rate (tCMD / tCR) from 1T to 2T.
  5. Fiery
    What GPU do you have, and what version of AIDA64 are you using?
  6. Fiery
    We reckon there're different methodologies to measure the core temperature of Matisse processors, and both Ryzen Master and AIDA64 are right about the temperatures. They just indicate a different value because Ryzen Master computes an average reading during a short timeframe, while AIDA64 shows the immediate reading at any given time point.
  7. Fiery
    Using the FPU subtest alone is important too, since it's vital to see whether the system can work at peak power draw and highest thermal state regardless of whether it is overclocked or not. GPU subtest is a strange beast, since it uses OpenCL and so it consumes quite a few CPU cycles as well. It can also behave differently with integrated GPUs than with discrete GPUs (video cards). It's definitely worth a try to enable the GPU subtest besides all the others, but it may cause troubles when the OpenCL stack has some installation issues. So we generally wouldn't recommend using it automatically, but only with cautions. If it works fine and produces the right system load (as per your expectations), then use it.
  8. Fiery
    No, it cannot filter down that way, since the sensor module is called everytime there's any sensor reading requested. I'm glad you've solved it using the EC options, that would have been my suggestion too We've seen a few Asus motherboards where polling EC registers can cause high DPC latencies.
  9. Fiery
    Is it because the width of the OSD panel keeps changing? It should change with left alignment too, BTW.
  10. Fiery
    The FPU subtest alone is perfect to drive the power draw and thermal state of the system to the maximum. You should run it for several hours, and then switch to a mixed workload, like CPU+FPU+Cache+RAM+Disks order to verify how the system handles a more mixed scenario.
  11. Fiery
    Here's the fix for the rotation bug: https://www.aida64.com/downloads/latesta64xebeta
  12. Fiery
    The new AIDA64 beta build is available for download at: https://www.aida64.com/downloads/latesta64xebeta
  13. Fiery
    We've implemented a new option called Alignment on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD page. You'll know what to do https://www.aida64.com/downloads/latesta64xebeta
  14. Fiery
    Thank you for the dump. I'm afraid we have no information on noise detection sensors, but we'll try to ask someone at Gigabyte about it. As for the fan labels, we've checked, and they should be labelled properly already. Can you please post a screenshot of the Computer / Sensor page of AIDA64 showing all measured values (incl. temperatures, fan speeds, voltages)
  15. Fiery
    Does it crash if you disable Include debug information in the report in AIDA64 / main menu / File / Preferences / Report?
  16. Fiery
    No need to install it.
  17. Fiery
    Yes, I'm afraid AMD's PMLog API is not 100% stable
  18. Fiery
    I'm not entitled to publish any of the Corsair contact emails I've got. Especially since they're proven to be great folks -- except for this single issue. So I don't want to unleash a s* storm of angry emails flying into their individual mailboxes
  19. Fiery
    Does it work if you make a custom HTML report and exclude the Config / Event Logs page? Maybe that page is very long in your case?
  20. Fiery
    AIDA64 still supports the LCD screen of the Strike7 keyboard.
  21. Fiery
    You don't need an Aquaero device to issue the Aquaero Dump. We'll rename that dump to Aquacomputer Dump to avoid further confusion.
  22. Fiery
    Thank you, we'll add flow rate reading for D5 Next in the next AIDA64 beta update due in a few days from now.
  23. Fiery
    Yes, you need to disable ULPS to enable monitoring both your GPUs. Scan the Registry (using REGEDIT.EXE) for EnableUlps and set all occurences of that to 0 (zero). When you're done, restart Windows to apply the changes.
  24. Fiery
    Ask the great folks at Matrix Orbital about EVE3-39 It should fit your needs. If not, they should be able to provide you with a solution. Worse case anything can be 3D-printed these days
  25. Fiery
    I'm afraid we cannot find a solution
×
×
  • Create New...