Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    11738

  • Joined

  • Last visited

  • Days Won

    503

 Content Type 

Everything posted by Fiery

  1. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    Please contact our Sales Department and ask for a refund: https://www.aida64.com/support/contactform
  2. Fiery
    Please note that in order to detect the missing details, the camera ID information had to be previously encoded into the Android profile of the device. When the manufacturer of the device (in your case Samsung) didn't encode the info there, then sysinfo apps cannot read or detect it.
  3. Fiery
    Awesome, thank you!
  4. Fiery
    Thank you, but the language module was already updated in the latest beta. It's maintained by another AIDA64 fan.
  5. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    That's fair. Thank you for giving our software a chance though.
  6. Fiery
    Can you please explain the steps you perform to import the .sensorpanel file of your choosing?
  7. Fiery
    Please let us know how to implement touch support for your new generation displays. For Matrix Orbital EVE displays we use touch facility to scroll between LCD pages. When the user touches the left 25% of the screen, AIDA64 switches to the previous LCD page; and when he/she touches the right 25% of the screen, AIDA64 switches to the next LCD page. It would be great to implement similar functionality for BeadaPanels too.
  8. Fiery

    Access Violation

    Fiery replied to IndyMX's topic in Bug reports

    I'm afraid the issue you're experiencing is too generic, so it would take a lot of efforts on your part to dig down deeper, e.g. disable various modules of AIDA64 to try to pinpoint the reason of the error message. If you're up for it, we can go down that path, but I still cannot guarantee that we could find the bug that way So in case you have a sour taste in your mouth about the $$ investment, then perhaps the best way for you is to get a refund and find another solution.
  9. Fiery
    Thank you for your kind words.
  10. Fiery
    I'd do at least a few hours. Even better if you could let it run through the night.
  11. Fiery
    We're working on it. Please note that what seems like a single display is actually a large family of displays with at least 5 different communication protocols. So in order to support all Turing/Turzx displays, we need to do a lot of research and development.
  12. Fiery
    Yes, it is. You may want to try it with factory default settings. It should work properly then, without hardware issues.
  13. Fiery
    With some unstable configurations AIDA64 can detect a glitch in the form of a calculation error. While in the vast majority of cases when the CPU makes a calculation error, it goes completely haywire and either Windows throws a BSoD, or the computer locks up, or the computer suddenly restarts.
  14. Fiery
    Thank you for checking it out
  15. Fiery
    In that process have you updated to the latest Adrenalin driver version of 24.12.1 WHQL?
  16. Fiery
    What do you mean by "stuck" ? Please explain it with more details.
  17. Fiery
    Please try the following: 1) Upgrade to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta 2) When the issue of the SensorPanel appearing on the wrong monitor occurs, in AIDA64 please press Ctrl+D --> System Debug --> Devices Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  18. Fiery
    @TheRealGD2X Both of you, please try the following: 1) Upgrade to the latest AIDA64 beta update: https://www.aida64.com/downloads/latesta64xebeta 2) When the issue of the SensorPanel appearing on the wrong monitor occurs, in AIDA64 please press Ctrl+D --> System Debug --> Devices Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
  19. Fiery
    The issue is fixed in the latest AIDA64 beta update available at: https://www.aida64.com/downloads/latesta64xebeta
  20. Fiery
    In AIDA64 please press Ctrl+D --> 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
  21. Fiery
    I've sent you your product key in email.
  22. Fiery
    The next beta build will be out later today.
  23. Fiery
    Yes, it's because the AIDA64 GPU stress test keeps issuing OpenCL kernels to the video driver in a constant manner. Between two kernels there's a slight pause due to OpenCL layer latency.
  24. Fiery
    Actually both happens in the same time. First the clock is reduced, and in case the overheating situation persists, the pipeline gets stalled.
  25. Fiery
    Your video driver doesn't expose the necessary interface that AIDA64 would require to interface with your video card. In most cases it's because the video driver needs to be reinstalled.
×
×
  • Create New...