Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12437

  • Joined

  • Last visited

  • Days Won

    554

 Content Type 

Everything posted by Fiery

  1. Fiery
    I've replied you in your separate topic.
  2. Fiery
    As for the missing 3rd GPU fan, please right-click on the bottom status bar of AIDA64 main window --> Video Debug -->nVIDIA 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. Also 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. We're kinda lost about the memory/resource error, since we cannot find the place in AIDA64 where that occurs, and it's extremely difficult to find it when you don't have the system on hand (here in our labs). Let's deal with the missing 3rd GPU fan issue first, and we'll see where we can go from there. BTW, please confirm that in either EVGA's Precision software or GPU-Z you can see the 3rd GPU fan measured properly. Thanks, Fiery
  3. Fiery
    Can you please check how RPM and duty cycle (%) values look like when the video card is under load? I'm wondering if you can achieve a 100% duty cycle for the first two fans and then it would be very interesting to know what the GPU3 fan duty cycle indicates then. We may use an incorrect conversion formula for GPU3 fan duty cycle, but not sure if it's a matter of wrong ratio or something else.
  4. Fiery

    Image png error

    Fiery replied to FoX's topic in Bug reports

    It's not quite clear to us what causes the PNG issues. Our best guess is that certain image editors place some big data into the PNG file that causes the crash in our code. BTW, I've managed to place the image you've attached to your post on a SensorPanel. Probably it's because the image got converted by our forum engine. Try to load the PNG file into another image editor, maybe PAINT.EXE or a free image editor of your choice, and save it to a new PNG file to convert it and get rid of the problem in the file.
  5. 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
  6. Fiery
    That's a difficult issue, since other software and tools would stick to using a dot for decimal separator, regardless of the current regional setting. Probably a new option in the Preferences is the way to go, although when it's possible, we prefer to avoid that. A dropdown list of "Windows Default / Dot / Comma" would be suitable, what do you think?
  7. Fiery
    When we came up with the AES benchmark, hardware acceleration wasn't available for it yet. Same thing with the SHA1: hardware acceleration was introduced after we designed and introduced that benchmark method too. Now it's the same story with SHA3: currently there's no hardware acceleration (at least not in x86 CPUs), but it's coming soon. As for the longevity and relevance of the AES benchmark, we're watching the market and will make a decision on its fate when the right time comes.
  8. Fiery
    1) No, such frame stats cannot be measured or displayed by AIDA64. 2) Fraps and RTSS are supported by AIDA64, albeit recently RTSS seems to have gone incompatible with AIDA64 -- we're investigating that part.
  9. Fiery
    You can adjust the SensorPanel resolution in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel. Please note that SensorPanel layouts are designed for a specific resolution, and when you import it and want to use a different resolution, you need to adjust the layout accordingly.
  10. Fiery
    We've picked SHA3 over SHA2 exactly because it has no specific CPU acceleration.
  11. Fiery
    That one uses HDMI connector and so it can be plugged into your PC and will become a secondary monitor. In which case you can use the AIDA64 SensorPanel module and move the SensorPanel to your secondary monitor.
  12. Fiery
    Most picture frames do not feature a facility to pass a bitmap image via the USB connection. Let me know if you're sure that your device supports such a facility.
  13. Fiery
    It's a difficult question. Are you looking for an alphanumeric (character) display or a fancier, graphical screen?
  14. Fiery
    Thank you, we'll check LCD Smartie. For us driver download wasn't done automatically under Win10, but the Windows Update facility offered an optional driver update "wch.cn" for the device and that worked out. Where did you get USB_LCD.DLL (LCD Smartie plugin) from?
  15. Fiery
    AFAIK fake device manufacturers use such tricks that are deeply embedded into the firmware of the device, including not just proofed files but also patched Android API calls. I wouldn't spend too much time on trying to reverse this activity.
  16. Fiery
    What output of AIDA64 do you find difficult to be post-processed? Are you trying to load e.g. a CSV log file generated by AIDA64 into Excel perhaps?
  17. Fiery
    Thank you! I'm afraid we cannot find the relevant register that would correspond to the 3rd fan of your video card
  18. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA 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. Also 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. Make sure to use AIDA64 v6.32 (latest version). Thanks, Fiery
  19. Fiery
    I'm afraid for most PC's it's not possible to meausure overall system power consumption in a reliable and accurate way.
  20. Fiery
    That's a very interesting and peculiar anomaly. My best guess is that the whole process takes more time to complete than what's expected from the average throughput because of the overhead of the graph drawing, time measurement, etc. If you push a right mouse click on the Save button, you can save all datapoints to a CSV or TSV file
  21. Fiery
    It's very difficult to find out the protocol details (if there's a proper protocol) without help from the person who's responsible for developing the firmware of the device. Have you tried to use your display with other software like LCDSmartie?
  22. Fiery
    You can only convert an Android platform to 64-bit by installing a new Android firmware update that is 64-bit. You need to consult with the manufacturer of your device and inquire them whether they have such an update for your device.
  23. Fiery
    I suppose a 3rd party software keeps opening AIDA64 for monitoring purposes. We've seen Logitech Gaming Software to behave like that, but I'm not sure what other software may do that. Does the issue come back after a Windows restart?
  24. Fiery
    We don't design and distribute custom gauge images, but maybe someone else reading this may be able to help you out.
  25. Fiery
    1) Reference results are strictly obtained and managed by us. Those systems are our reference systems that are kept unchanged if possible, both hardware- and software-wise. 2) We update the benchmark results for each reference system when they need to be updated. If you meant to ask about the selection of systems, then we keep adding new ones as new platforms get introduced, and only rarely we remove (retire) a reference system. At one point in the next few years we're going to retire all 32-bit only hardware, and probably some of the early 64-bit capable systems too. 3) You can submit reports, but we only add entries to the reference list that are obtained by us, under fully controlled circumstances. That's to avoid overclocking, special tuning, cheating, and user errors or other anomalies. By cheating and user error I don't mean you personally, of course
×
×
  • Create New...