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 your feedback!
  2. Fiery
    CPU utilization is measured by the operating system. The CPU itself cannot measure that.
  3. Fiery
    The 2 fan speed settings are used by the older Asetek VI protocol only. They refer to the fan speed (fan duty cycle) setting of up to two Asetek VI based devices. As long as you don't experience any issues with the default settings, you don't need to alter those options in the AIDA64 Preferences.
  4. Fiery
    When they can be detected, the PCI and AGP clocks are shown on the Motherboard / Motherboard page. As for how the PCI and AGP clocks are driven, it depends on the FSB logic (FSB strap) the motherboard uses. If it has a different strap for 266 MHz FSB than for 200 MHz FSB, then no overclocking of the PCI and AGP clocks should be used when you switch from 200 MHz FSB to 266 MHz FSB. In other words, at 200 MHz FSB the PCI clock should FSB/6 (FSB clock divided by 6), and the AGP clock should be double the PCI clock. If the right FSB strap is used by the motherboard, at 266 MHz FSB the PCI clock should be FSB/8, and the AGP clock should still be double the PCI clock. To rule out the possibility of AIDA64 detecting the wrong clock frequencies, try to check the same information using other software like CPU-Z, HWiNFO and SIV as well.
  5. Fiery
    They should be there, on the AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD / OSD Items page. Try to scroll down a bit to find them
  6. Fiery
    AMD processors have only a single thermal diode, so per-core thermal measurement is not possible. When a software shows per-core thermal readings for AMD CPUs, the temperature values will be identical across all cores. As for the DIMM voltage and perhaps other measurements missing, try to switch the option Asus WMI sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes.
  7. Fiery
    I'm afraid we're not skilled in overclocking and fine-tuning, but hopefully someone else can chime in and help you out.
  8. Fiery
    Thank you. Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. 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
  9. Fiery
    The above mentioned new AIDA64 beta build is now available for download: https://www.aida64.com/downloads/latesta64xebeta Let me know how it works.
  10. Fiery
    Thank you!
  11. 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. Also 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
  12. Fiery
    Thank you for your feedback. Yes, we're aware of those pecularities. AIDA64 simply pushes the image onto the device to the pre-defined key, without taking into account any interference or any other processes simultaneously accessing the device. As long as the other process (Stream Deck Software) doesn't alter the key that AIDA64 updates, they should work well together.
  13. Fiery
    It shouldn't have any of those, but you can check it out to make sure by opening the .RSLCD file in a text editor like Notepad, WordPad or Word.
  14. Fiery
    Not yet.
  15. Fiery
    We will fix the issue in the next AIDA64 beta update. I'll post a message into this topic once the new build is available for download. I'm afraid it's not possible to decouple any of the sensor modules or to use a different polling frequency for them. When a certain sensor device is slow to provide the readings, it will stall the rest as well. There was no checkbox for disabling Aqua Computer devices support on the Preferences / Stability page. Let me know if you need one.
  16. Fiery
    Try to wait a minute or two in case you have the RAM (System memory) subtest enabled in the AIDA64 System Stability Test. When you have that subtest enabled, AIDA64 will allocate almost the entire physical memory using standard Windows API memory manegement calls. However, those calls could stall Windows when there's a large amount of system memory to allocate (over 64 GigaBytes).
  17. Fiery
    What clock speeds can you see in AIDA64 which you reckon are double the actual ones?
  18. Fiery
    Please avoid posting a single issue or question into multiple topics. This topic locked.
  19. Fiery
    AIDA64 Engineer has certain command-line options that can be used to automate report creation and writing the results into XML files. Refer to the AIDA64 Engineer User's Manual / Command-line options / Benchmarks.
  20. Fiery
    If you mean AIDA64 and the software of Optimus Popularis, then I suppose no, unless Optimus Popularis software can ignore to handle the wide strip of LCD of your keyboard and just deal with the smaller screens of it. Meanwhile we've rolled out the fix for Optimus Popularis keyboard: https://www.aida64.com/downloads/latesta64xebeta
  21. Fiery
    Yes, we've managed to add support for all 4 versions (Original v1, Original v2, Mini, XL) of the Elgato Stream Deck device in the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta Please note that it's only the first step (hopefully in the right direction). It will only use the bottom-right (last) button as a LCD screen. But the good news is that it should work fine even when you're using the other buttons for other purposes via the Stream Deck software. Let me know how it works for you.
  22. Fiery
    Please contact our international distributor ABSEIRA Ltd at the following email address for more information on that: info AT abseira.com
  23. Fiery
    It's not wrong, since 4+ means "4 or later version". Please submit a report from the About page, and if possible, we will fix the reported issue in the next AIDA64 app update. Alternatively, you can post a screenshot or photo of the System page of our app here.
  24. Fiery
    So far we haven't found a way to read the pump RPM from the Ryujin 360 using its USB connection. Is there any software that can show you that reading?
  25. Fiery

    2 problems

    Fiery replied to FoX's topic in Hardware monitoring

    RTSS is not our software, so in case it doesn't work properly, you need to contact its author and file a bug report to him.
×
×
  • Create New...