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. Please note that Vcache voltage readout is only supported from BIOS version 1201.
  2. Fiery
    How much system RAM you've got? 32GB? 64GB? A lot rides on that, since it takes quite some time for Win10 to allocate big chunks of RAM. Windows, going from WinXP through Win7 through Win8 to Win10 tends to get slower and slower when it comes to allocating huge memory blocks. But, you may have a point there: we may need to add a new option in the System Stability Test Preferences to let you lower the default 95% memory allocation to 90% or 80%.
  3. Fiery
    The BIOS (at least on Maximus X Formula) uses a formula of x 24 / 1000 to get to L/M, but I don't think that that formula is correct. Unless we can come up with a proper formula that yields to values that make sense, I'd be hesitant to convert the raw RPM reading to anything else...
  4. Fiery
    It's cool then Please let me know what subtests do you have enabled in the System Stability Test when the "jumping" occurs. If you have the memory stress test enabled, please check it without it, and let me know if it makes a difference. If it does, let me know how much system RAM do you have installed, and whether you're running the latest Windows 10 stable build (of 16299) or an Insider Preview build.
  5. Fiery
    Thank you. I think the issue occurs because you didn't enclose the report file name with quotes (" characters) in order to mitigate the potential space characters that appears in the filenames after %dirname% is resolved. Do you think that it may explain the issues?
  6. Fiery
    Based on your experiences with your Rampage VI Extreme motherboard, what do you reckon the proper conversion formula from RPM to LPH would be?
  7. Fiery
    Have you tried it with the latest AIDA64 beta as well? https://www.aida64.com/downloads/latesta64xebeta I'm just asking because we've recently applied a workaround to mitigate the issue you've described.
  8. Fiery
    Thank you for your feedback. I don't think that that formula applies to this particular case. Asus seems to use a simpler formula of x 24 / 1000 to convert the raw RPM readings into LPM (L/M). The AIDA64 sensor module uses a fixed measurement unit of LPH (L/H) on the flow sensor readings, so we need to come up with a proper formula to convert the RPM value of Water Flow on your motherboard into the LPH reading that can be squeezed into the AIDA64 sensor module as a secondary measurement for the same reading for your motherboard.
  9. Fiery
    The missing options means that you're not using the latest beta build of AIDA64. We're rolling out a new stable update next week, so make sure to upgrade to that then, and then the new options will be there on the Stability page. As for the GTX1050Ti, it doesn't seem to be able to monitor its TDP% measurement. It looks like a hardware limitation.
  10. Fiery
    Thank you for your feedback
  11. Fiery
    I'm confused. Are you talking about benchmarking or stress testing?
  12. Fiery
    To me it seems more like a collision on the sensor chip access, and not a hardware failure. Well, except for the case when AIDA64 reports a failure with that big red screen of course Make sure to check the voltages with Gigabyte's own monitoring software, with all other monitoring software not running in the background.
  13. Fiery
    No, since our benchmarks are designed to squeeze out the last bit of performance from actual processors. We use such extreme optimizations that take actual hardware architecture into account. If you distort the underlying architecture by e.g. removing a lot of CPU cores from a multi-core CPU in a virtualized environment, our optimizations may or may not work as great as on a non-virtual environment. That all doesn't mean that you cannot obtain valid benchmark results in a virtual machine. But the extreme optimizations will not work 100% in such an environment.
  14. Fiery
    It's most likely because Asus has implemented a temperature offset on the CPU temperature measurement. It may be because the previous values were inaccurate, and so the new values are more representative of the actual thermal status of the processor.
  15. Fiery
    It can be due to a few issues. One of which is that the new Android platform (Nougat) blocks access to the necessary Linux kernel files that AIDA64 uses to detect the list of connected USB devices.
  16. Fiery
    Please show us the line in your logon script that launches AIDA64. If it includes sensitive information, please send the line in private message to me.
  17. Fiery
    We haven't received bug reports about AIDA64 vs. Aorus Graphics Engine other than the posts in this forum topic. The issue may be wide spread, but we haven't heard of a massive number of users complaining yet. We'll do our best to find a resolution soon.
  18. Fiery
    We will fix the issue in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta build is available for download.
  19. Fiery
    What do you mean by "always bugs" ? Is it overheating? Does it keep locking up (freezing) ?
  20. Fiery
    Do you have EC bank switching enabled in AIDA64 / main menu / File / Preferences / Stability? If yes, then please create the following 2 dumps and post them as TXT file attachments to your post at both 1.00V Vcache setting and 1.10V Vcache setting. We have 2 registers that may hold Vcache, and cannot decide which one is the right one I'm afraid 1) Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. 2) Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Thanks, Fiery
  21. Fiery
    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
  22. Fiery
    I'm afraid we cannot find your license in our customer database. Please send me a private message with your full name and the email address that you've specified at your purchase. Thanks, Fiery
  23. Fiery
    As long as Mad Catz offers a similar SDK for RAT9 that it has for Strike7, we can implement that feature in AIDA64. But I haven't seen any such SDK offered by Mad Catz...
  24. Fiery
    It seems AIDA64 is unable to use its kernel driver. Make sure to install AIDA64 properly using its self-installer package from e.g.: https://www.aida64.com/downloads/latesta64xe Also make sure to have administrator privileges for the user that launches AIDA64.
  25. Fiery
    I'm afraid it's not possible to filter the reports for certain items. You need to come up with a script that identifies the sensitive lines and removes them. Regards, Fiery
×
×
  • Create New...