Jump to content

Fiery

Administrators
 View Profile  See their activity

  • Posts

    12004

  • Joined

  • Last visited

  • Days Won

    525

 Content Type 

Everything posted by Fiery

  1. Fiery
    The requested feature has been implemented in the latest AIDA64 update of v6.00: https://www.aida64.com/downloads/latesta64xe
  2. Fiery
    After the "Cannot find DLL" message, try to open Device Manager, find the device for the Samsung frame, and try to install the Samsung SPF LibUSB driver manually.
  3. Fiery
    CPU Package is a single thermal measurement provided by the CPU itself, using its on-die thermal diodes. It's not an issue at all, unless either of the CPU temperatures get above 100 Celsius.
  4. Fiery
    Thank you. We're finally getting a Radeon VII video card on Monday that will allow us to dig down deeper and fix the remaining issues in the next AIDA64 update.
  5. Fiery
    CPU VID on Sandy Bridge and later processors are read from a CPU register. AIDA64 doesn't specifically forces the thread that reads that register onto any cores, so it's the job of the Windows scheduler to decide which core it executes the register readout task on. Most likely Windows works the way it is because it deems AIDA64 is a performance oriented application and so whatever it does is executed on the highest performing core (also known as preferred core) which can use the highest Turbo Boost ratio. In your processor's case it seems to be the last core.
  6. Fiery
    Please create and send us the following dumps: - SMART Dump - RAID Dump - Disk Controllers Dump Thank you in advance!
  7. Fiery
    The content of the Apps page, Codecs page and System Files page are only included in the report when you do not submit it to us. So when you click on "Send Report In E-mail" those pages are included. However, when you click on "Send Report To Author", those pages are not included in the report.
  8. Fiery
    Your system seems to have an unknown Nuvoton super I/O (sensor chip). Is there any chance you can get a peek into the chassis and find the Nuvoton chip on the motherboard PCB? It should have markings like NCT67xx (where "xx" is unkonwn to us) or NCT67xxD or such.
  9. Fiery
    CPU Package is the total consumption of the whole CPU package, including the x86 CPU cores ("IA Cores") and -- if available -- the iGPU shaders/cores ("GT Cores") as well.
  10. Fiery
    1) Only the first 4 cores are automatically assigned as temperature slots in the AIDA64 System Stability Test. You can use the Preferences button to change the temperature slot assignments to display the rest of the cores on the Temperature graph as well as among the thermal readings in the Statistics list. 2) TSX is not listed on any processors as part of the Instruction Set list on the AIDA64 CPUID Panel.
  11. Fiery
    I know, it's a complicated issue, since the frame still works well under Windows XP... And probably under Windows Vista as well.
  12. Fiery
    You can use the right-click context menu on the Computer / Sensor page --> Extended Labels to help you understand where one or more of the generic sensor readings (like Temperature #1, Fan #21, etc) comes from.
  13. Fiery
    Are you sure the device cannot switch to Mini Monitor Mode? I'm just asking because when AIDA64 says it cannot find libusb0.dll, it usually means the device is ready (in Mini Monitor Mode), and the issue is on the DLL side. You can then download and install the Samsung SPF LibUSB driver from the following link: http://download.aida64.com/resources/lcd/samsung_spf_lcd_driver.zip
  14. 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.
  15. Fiery
    1) The GPU stress test relies on the OpenCL subsystem that seems to be broken on your system. Try to uninstall your video driver and install the latest WHQL one to fix that up. 2) Saving the stress test history or statistics to text file is not supported. You can however use the Logging facility to save your selection of sensor readings into a CSV or HTML file. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging to configure that feature.
  16. Fiery
    I'm afraid we cannot find the reason why AIDA64 holds lock on such folders. We've implemented a more modern save file dialog to the debug dump window, but it works the same about holding the lock.
  17. Fiery
    Does TACH(0) always provide the correct RPM when your fan is spinning at various non-zero RPMs?
  18. Fiery
    We've tried it with the default 20 seconds poll rate as well as with 1 second.
  19. Fiery
    AFAIK with Asetek-compliant liquid coolers the issue is that the fan controlling logic could get reset when AIDA64 and iCUE collides while reading the liquid cooler measurements. It results in the fans spinning up to 100% speed, which could be quite annoying. If you can live with that limitation, then it's safe to leave the Asetek liquid cooler module enabled in AIDA64.
  20. Fiery
    It will be implemented in the next AIDA64 beta update.
  21. Fiery
    Awesome, thank you for your feedback. Can you please post a screenshot or report or copy-paste of the Display / GPU page?
  22. Fiery
    I don't think it's our responsibility to be frugal on network requests when the traffic is initiated by the user by clicking on a link in our software. We'll alter the most clicked links, but the sheer number of URLs (over 1100) makes it a difficult task to leaf through all of them using manual review.
  23. Fiery
    Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it works better than the previous builds
  24. Fiery
    Yes, but we're unable to reproduce the issue on our own Z10 keyboard Are you using the latest firmware on your keyboard?
  25. Fiery
    After VHD creation 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. Also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. Thanks, Fiery
×
×
  • Create New...