Jump to content

Fiery

Administrators
  • Posts

    11544
  • Joined

  • Last visited

  • Days Won

    489

Everything posted by Fiery

  1. We've checked our code, and it seems to do things right. We follow the "book" (MSDN Library) precisely. It looks to be a Windows bug. Maybe Windows reports the wrong information via the interface (API call) we use, but Windows may use a different interface (API) in the Control Panel.
  2. Displaying the AIDA64 OSD Panel in full-screen 3D applications is not supported at this time. Regards, Fiery
  3. Thank you. If you wait 30 seconds after returning from hibernation, do the HDD temperatures get back to normal?
  4. Thank you. We've just checked it with a Win7 64-bit system + nForce RAID controller + a RAID array, and found no slowdowns at all. Are you using the standard Win7 driver for the nForce RAID controller, or you've installed a new driver downloaded from e.g. nVIDIA's webpage? If you don't use the standard Win7 driver, then please let us know the version of the nForce RAID controller driver you're using. Thanks, Fiery
  5. In order to let us come up with our own AIDA64 plugin for AlphaCool, we would need either: 1) The source code or the uncompressed DLL image for acEverest.dll, or 2) Guidelines (SDK, programming documentation) on how to develop a new AlphaCool plugin from scratch
  6. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1170ws0dcy6mjxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery
  7. Unfortunately the LCD screen of the MX5500 is not available for 3rd party applications. So AIDA64 cannot support it Regards, Fiery
  8. Please try to disable Multi-GPU support in AIDA64 / main menu / File / Preferences / Stability. That way AIDA64 can only monitor the primary GPU, but at least no lockups should occur.
  9. WMI definitely works in AIDA64. I'm not sure why WMI Managment Console wouldn't show the class, but if you use WMI Explorer or WBEMTEST.EXE, it should be accessible. We've just tested it with both Win7 32-bit and Win7 64-bit, and both cases it worked flawlessly. Regards, Fiery
  10. The problem is with Koolance's software. It's not designed properly to allow 3rd party software to access the TMS-200 controller while it is running. In other words, you have to close Koolance's software to let AIDA64 open the TMS-200 controller. We've already contacted Koolance, and they seem to be ready to change their software to allow AIDA64 (and other 3rd party software as well) to work while Koolance's own software is running. They couldn't provide a timeframe though, so I'm not sure when can we expect the new software You may also want to refer to the previous thread on the same topic: Regards, Fiery
  11. Thank you for the dumps. However, they don't include any sensor chips or voltage regulator chips Quite frankly, I have no idea how to access the EPU chip on your video card Do you have any 3rd-party utilities that can do that? As for fan controller, AFAIK the GPU itself controls and monitors the fan on your video card.
  12. In order to let us check what sensor chips or power regulator chips does your video card feature, please use the latest beta version of AIDA64 Extreme Edition to create the following 2 dumps for us: Latest beta: http://www.aida64.com/downloads/aida64extremebuild1170ws0dcy6mjxzip Dump #1: Right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Dump #2: Right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery
  13. No. Enumeration means AIDA64 can find the devices "hiding" in a RAID array. SMART readout is another question, but AIDA64 cannot read that for any SiI RAID arrays.
  14. SiI 3114 is already supported. Regards, Fiery
  15. VIA KM266Pro, KM400 and KM400A chipsets are quite weird. Even their datasheets are inaccurate about registers layout and memory timings detection So that's why we cannot detect such details for those chipsets.
  16. 1) Besides the integrated nForce RAID controller, do you have any other RAID controllers, SATA controllers or AHCI controllers in your system? 2) Do you have any USB or eSATA or FireWire storage devices connected to your system? 3) Have you tried it with the latest AIDA64 beta release? http://www.aida64.com/downloads/aida64extremebuild1170ws0dcy6mjxzip Thanks, Fiery
  17. Video won't be necessary, thanks. 1) Are you running any Asus monitoring software next to AIDA64? E.g. Asus PC Probe, Asus TurboV? 2) Do you have the option "SMBus access through ACPI (Asus motherboards)" in AIDA64 / main menu / File / Preferences / Stability checked or unchecked?
  18. We can continue this thread. Thanks for the dump, but I cannot see any problem there. What's wrong with the Chassis #1 fan reading?
  19. GPU utilization values are displayed on the Display / GPU page instead of the Computer / Sensor page.
  20. You need to have the Intel Management Engine (ME) Driver installed. It is also known as HECI driver. Download link: http://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=16953&lang=eng Regards, Fiery
  21. Thank you for the feedback
  22. Yes, both applications (AIDA64, GPU-Z) measures the 3 separate GPU utilizations the same way (via ForceWare driver calls).
  23. MC = Memory Controller VE = Video Engine Modern nVIDIA GPUs are capable of monitoring 3 separate GPU utilization parameters.
  24. Thank you for the feedback
  25. We've implemented hot-plug HDD support in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1170ws0dcy6mjxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery
×
×
  • Create New...