Fiery

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.

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

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

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.

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

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.

SiI 3114 is already supported. Regards, Fiery

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.

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

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?

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?

GPU utilization values are displayed on the Display / GPU page instead of the Computer / Sensor page.

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

Thank you for the feedback

Yes, both applications (AIDA64, GPU-Z) measures the 3 separate GPU utilizations the same way (via ForceWare driver calls).

MC = Memory Controller VE = Video Engine Modern nVIDIA GPUs are capable of monitoring 3 separate GPU utilization parameters.

Thank you for the feedback

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

We've further improved negative temperature 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

Thank you for the feedback

Thanks BTW, having the mentioned option checked is the safer setting. It's weird that unchecking it helped, but I'm glad it did.

AIDA = Advanced Identification of Devices & Adapters It's an old thing

Thanks for the dumps. This one seems to be a completely different issue to the P5Q fan problem. Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

EVEREST Ultimate Edition and EVEREST Ultimate Edition Engineer shares the same functionality and features set, and only the licensing differs. Same applies to AIDA64 Extreme Edition vs. AIDA64 Extreme Engineer. EVEREST Corporate Edition has features geared towards corporate use (network monitoring, remote control, remote reporting, SQL database support), and it doesn't have several features that the Ultimate Edition has (e.g. benchmarks, overclock information, hardware monitoring modules). Same applies to AIDA64 Business Edition. The most accurate description of the features set of various AIDA64 editions is shown at: http://www.aida64.com/product/aida64-extreme-edition/features Regards, Fiery

Thank you. However, it doesn't seem to work even with EVEREST v5.50 (latest version). I'm not sure what's the trick there, but this plugin seems to be a bit crude. Is there any AlphaCool SDK or programming documentation, so we could make an AIDA64 plugin from scratch?