Fiery

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?

Thanks for the feedback

Please let us know more about your system configuration: 1) Motherboard model? 2) CPU type? 3) Video adapter(s) model? Single card, or CrossFire/SLI? 4) Windows variant? Windows kernel type? (32-bit or 64-bit) Thanks, Fiery

Some UPS report those values (e.g. Full Battery Lifetime), some don't. Some UPS will report more values when they're offline (not plugged into A/C power). Try to disconnect the UPS from A/C power, wait for 10 seconds, and see how the values on AIDA64 Power Management page change.

Please copy-paste the full content of the Computer / Power Management page of AIDA64 into this topic. Thanks, Fiery

Can you please post a download link to the acEverest.dll file?

It will be fixed in the next AIDA64 beta. I'll post a note into this topic when the new beta is published.

We would love to add that, but so far we couldn't find a proper method to measure current and aggregated network bandwidth, with minimum performance hit (so WMI wouldn't work) We have a very old method on the Network / Windows Network page in AIDA64, but that counter overlaps at 4GB, and these days it's too easy to reach 4GB -- hence it's not really suitable for modern applications.

We currently have no plans about a native AlphaCool LCD support. Do you know who made the Everest.dll module?

Do you mean the advanced Intel RAID SMART support works fine for you? Or you wanted to report a bug? Thanks, Fiery

Did the latest beta fix it for you too?

Yorkfield uses 2 dies in the CPU package, each with 6MB L2 cache. AIDA64 shows the cache size associated with the actual core selected. Regards, Fiery

Thank you for the feedback