Jump to content

Fiery

Administrators
  • Posts

    11334
  • Joined

  • Last visited

  • Days Won

    476

Everything posted by Fiery

  1. Thank you for your post, it's very useful. We'll add those new Mantle extensions to the next AIDA64 beta update.
  2. Not quite well, since coming up with a plugin from scratch is quite the work. And we wouldn't want to copy the existing plugin for HWiNFO to not violate the IP of its developer. We did try to contact him on GitHub, but no response yet. It would be much easier to go with option #2, but I understand that you would prefer to use multiple applications in the same time for your Stream Deck instead of AIDA64 taking over the whole device.
  3. It's a complicated issue, since the Asus WMI ACPI interface heavily depends on the implementation in the motherboard BIOS you currently have flashed into your motherboard. So it's best to download the latest AIDA64 version, and check if it works as you'd expect. Just use it in trial mode, and exploit the 30-day evaluation period before you go for a license renewal or a new license purchase. Once you have a conclusion on how the Asus WMI ACPI interface works on your particular motherboard with the current BIOS version, please open a new topic and share your experiences with other users as well as us, the developers of AIDA64. Thank you in advance!
  4. Thank you. We've tried to replicate the issue on various test systems of ours, but with no luck so far. It would be very helpful if you could help us investigating this issue by disabling GPU sensor support in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 after altering that option, and check if it eliminates the issues after resuming from sleep/hibernation. Please let us know how it goes.
  5. Does AIDA64 turn your display green as soon as its splash screen is displayed? Or when its main window is displayed? Or only when you check the GPU parameters on the Display / GPU page? Or only when you check the sensor readings on the Computer / Sensor page?
  6. Can you please try to catch what's the last message displayed on the bottom of the AIDA64 splash screen? Perhaps it's Scanning RAID Devices ? Also, please let us know more about your laptop. Full model name/part number, CPU type, storage devices installed, any external (USB or Thunderbolt) devices connected?
  7. I'm confused. AIDA64 was never able to detect whether a certain application or game is using DX9, DX10, DX11 or DX12.
  8. We'll remove the bogus CPU thermal reading in the next AIDA64 beta update.
  9. Thank you for the dumps. Everything looks correct there. When you activate the LCD function for Aquaero (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / Aquaero), what's displayed by AIDA64? Is there a red error message shown?
  10. 64 Celsius doesn't seem to be excessive for your CPU (or any CPU for that matter). Are you sure the CSGO lagging is due to this thermal state?
  11. Please try this one: http://users.aida64.com/SDC-USBDriver_v2411.zip
  12. Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR 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
  13. Nope: https://forums.evga.com/Z10-Keyboard-Code-to-write-text-to-the-LCD-display-m3012492.aspx
  14. 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.. Thanks, Fiery
  15. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aqua Computer 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. Please also let us know the approx. expected values for the readings at (or around) the time you've issued the dump. Thanks, Fiery
  16. We've come up with an idea about that. It will be implemented in the next AIDA64 beta update. I will post a message into this topic once the new beta becomes available for download.
  17. Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor 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
  18. Thank you for your feedback. When it comes to Intel processors, CPU power draw can only be measured on Sandy Bridge and later processors.
  19. Martin's explanation there specifically talks about effective clock being an average, while the classic clock frequency measurement being instant (discrete). IMHO it should be the responsibility of the CPU maker to make sure that by simply detecting the core multiplier the core shouldn't wake up or change its power state. In fact, we've been requesting a more user-friendly and more accurate way of measuring CPU core clock frequency at both AMD and Intel for years, one that wouldn't require elevation (administrator privileges) as well. We're hoping that eventually it will be implemented in all x86 processors in a proper way. Till then, I still reckon AIDA64 is correct, simply because it reports the CPU multiplier and resulting core clock frequency as it is, without any tricks, conversions or averaging.
  20. We will add support for your motherboard in the next AIDA64 beta update. I will post a message into this topic once the new beta is available for download.
  21. We will alter the GLCD2USB module to support 8 pages in the next AIDA64 beta update. I'll post a message into this topic once the new beta build is available for download.
  22. Then it must have been a timer mixup. If you see the same issue to happen, just restart Windows and it should fix itself again
×
×
  • Create New...