Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12376

  • Joined

  • Last visited

  • Days Won

    549

 Content Type 

Everything posted by Fiery

  1. Fiery
    We do 1/a, so we read something and then write it. It's not full duplex. And the read and write block sizes are added up together, so it's not 1/2 of read/write speed, but 1/1. There's no consensus in the benchmark industry about how to calculate the memory/cache copy scores, some software does it the "AIDA64 way", some others use your approach of 1/2. 2) No, we have no plans to go back to providing single-threaded memory bandwidth benchmarks. You can still use AIDA64 v2.85 to have that.
  2. 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 AIDA64 beta build is available for download. Regards, Fiery
  3. Fiery
    Thank you. 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 AIDA64 beta build is available for download.
  4. Fiery
    What version of Aquasuite are you using? And what AquaComputer hardware do you have?
  5. Fiery
    Nice video Let us know if the issue comes back. Maybe it's related to another Windows software that you sometimes are running, but many times not.
  6. Fiery
    1) Memory Copy means writing a memory block and then reading it back. If there are no separate (dedicated) paths for writing and reading, then the copy scores will be close to the read and write scores. 2) AIDA64 uses multiple threads to perform memory bandwidth benchmarks. Modern applications are multi-threaded, so a single-threaded memory bandwidth benchmark (that we used in AIDA64 1.xx and 2.xx) is considered obsolete in 2017. Regards, Fiery
  7. Fiery
    No, AIDA64 doesn't behave differently in different power management states. It executes the same stress testing code no matter the screen is powered or sleeping. Radeon video cards however work differently in those states, so it must be due to a video driver (Catalyst) pecularity. Regards, Fiery
  8. 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 AIDA64 beta build is available for download. Regards, Fiery
  9. Fiery
    Throttling detection only works on Intel processors. Regards, Fiery
  10. Fiery
    No sensors require an internet connection. Regards, Fiery
  11. Fiery
    We've tried but wasn't able to reproduce the issue on our own Windows 10 test systems. Are you running Windows 10 Anniversary Update? (Build 14393)
  12. Fiery
    Using our benchmarks under virtual machines is not supported. Regards, Fiery
  13. Fiery
    One possible explanation is that AIDA64 displays a message box that is not displayed anywhere, since you have AIDA64 running as the SYSTEM account. Can you please try to replace /CUSTOM \\server\aida\aida64.rpf with /SUM ? Maybe one of the pages that you have in your report profile causes the issue. In which case (when /SUM works fine) you need to remove some of the pages from your report profile.
  14. Fiery
    We've already seen such issues on Haswell-E and Broadwell-E systems, but couldn't reproduce it on our own test systems using the same processors It must be due to SMBus timing pecularities, but when we've tried to adjust the timing to a more relaxed value, surprisingly things (ie. SPD detection) got even worse. As for Aquasuite, you can try to close that software, but I'm pretty sure it's not the culprit.
  15. Fiery
    Thank you. We'll implement advanced support for MX300 SSDs in the next AIDA64 beta update due next week
  16. Fiery
    Yes, using a microcontroller would probably be the ultimate solution -- although not the easiest or most cost effective one We will keep things on hold until you have the final hardware assembled and tested to be working.
  17. Fiery
    Thank you. I think I misunderstood you then All looks fine in the dump, so no issues
  18. Fiery
    Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART 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. Thanks, Fiery
  19. Fiery
    You seem to know your stuff, so let me ask you a few further deep technical questions, to make sure we initialize your device in a way it's expected. 1) What baud rate shall we use when calling FT_SetBaudRate? 2) What argument values shall we use when calling FT_SetDataCharacteristics, FT_SetFlowControl and FT_SetTimeouts? 3) Can you please provide the exact command bytes we need to issue at the OLED init, and the command bytes we need to use at each frame update?
  20. Fiery
    As for the GTX1080 fan issue, 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. Make sure to have the video card fan spinning at a non-zero RPM when you're issuing the dump. Thanks, Fiery
  21. Fiery
    It works the way it's supposed to be. It's due to the fact that it's not possible to tell the difference between a stopped fan and an unconnected fan AIDA64 shows the 0 RPM reading only in the SensorPanel and LCD modules. But first you need a spinning fan to place the items on your panel, and then when it stops, 0 RPM will be shown. On the Sensor page the stopped fans will not be displayed.
  22. Fiery
    NVMe doesn't support thresholds/value/worst fields as ATA/SATA drives do.
  23. Fiery
    You've got the OnePlus 3T device. The small glitches about detection will be corrected in the next AIDA64 app update. Regards, Fiery
  24. Fiery
    Thank you. It seems the USB communication protocol used by your Kraken X52 device is completely different to the one used by previous Kraken coolers that are supported by AIDA64. So it's normal that AIDA64 doesn't support Kraken X52 We will need to do more research -- and possibly get a Kraken X52 -- to find out how to handle the new Kraken protocol. I'll let you know in this topic once we have an update to this issue.
  25. Fiery
    Then please close CAM Software, start AIDA64, and right-click on the bottom status bar of AIDA64 main window --> System Debug --> USB 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. Thanks, Fiery
×
×
  • Create New...