Fiery

Using ForceWare 320.18 driver, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Hopefully that data will help us to find out what happened to the CHiL chip detection between the last two ForceWare releases. Thanks, Fiery

We've tried to replicate the issue on our test systems, but with no luck. Can you please post a RAID Dump and a SMART Dump using the latest AIDA64 beta? http://www.aida64.com/downloads/aida64extremebuild2460x8f2dmshtbzip Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. Thanks, Fiery

Thank you, I'm glad you've managed to work it out. We've tested AIDA64 latest beta with Windows Server 2003 SBS, and could not replicate the issue here. So it must have been a temporary mixup in AIDA64 on your system

We're slowly introducing the new features of the upcoming AIDA64 release that is due in a week from now You can also notice the L4 cache benchmark fields on the new Cache & Memory Benchmark Panel Regards, Fiery

Most likely it doesn't crash, it's just a bit slow. You have to wait at least 90 seconds to have the benchmark finished on X79 chipset based systems. The slowness will be fixed in the next AIDA64 stable release due 1 week from now. Regards, Fiery

Switching the mux is slow and readings tend to be unreliable. For example, you switch to CPU Fan2, then you have to wait 3 or 4 seconds (which is unacceptably long), and even after then sometimes the reading comes from CPU Fan1 -- and in such case there's no way to know which fan do you get the readings from.

On several ASRock boards 2 fans are muxed a single fan connector (fan header). Since the mux is implemented improperly, AIDA64 cannot switch them. Try to connect the fan to another fan header, and it will then show up in AIDA64 BTW, on your particular motherboard CPU Fan1 and CPU Fan2 are muxed together, so you have to use the other connector to make sure it appears in AIDA64. Regards, Fiery

Such 0-byte long tables are usually there because of either a BIOS bug, or because of a disabled ACPI table (e.g. HPET). The memory address matching with other tables could just be a coincidence.

AFAIK the VRM chip on your video card is only responsible for providing voltage for the GPU itself, and not for other components of your video card, e.g. the memory chips. Plus, as you mentioned, it may only account for the power flowing through the +12V PCIe power connector(s), and not include the power drawn from the PCIe slot. But all those things heavily depend on the actual video card design, and the type of VRM used. Regards, Fiery

Your temperature look just fine in the System Stability Test. We'll fix the temperature labels and also the voltage ratios in the next AIDA64 beta release. Regards, Fiery

BTW, what version of Windows do you have installed?

First, try to do the following: 1) Close AIDA64 2) Go to AIDA64 installation folder, and delete the following files: AIDA_CPUID.DLL AIDA_ICONS7.DLL AIDA_ICONSXP.DLL AIDA_UIRES.DLL 3) Manually download the latest beta ZIP package from: http://www.aida64.com/downloads/aida64extremebuild2454wptb6zhg9nzip Extract the ZIP into the AIDA64 installation folder. Let it overwrite any existing files. 4) Restart Windows, and start AIDA64 ------- If the above steps do not resolve the icons issue, then do the following to revert back to AIDA64 v2.85 stable: 1) Close AIDA64 2) Manually download the v2.85 stable ZIP package from: http://www.aida64.com/downloads/aida64extreme285zip Extract the ZIP into the AIDA64 installation folder. Let it overwrite any existing files. 3) Restart Windows, and start AIDA64 Please note that by extracting the ZIP package and overwriting existing files will keep your Preferences settings. If you want to specifically backup AIDA64 settings, just backup the AIDA64.INI file from the AIDA64 installation folder. Regards, Fiery

AIDA64 follows power measurement specifications that AMD provided. If you believe the power measurement is inaccurate, then you need to ask AMD about it On our FX processors we can see similarly low wattage values, but higher (more realistic) values on FM2 processors. Regards, Fiery

Thank you for the feedback

I'm sorry for the late reply. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2454wptb6zhg9nzip 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 fixed the RST 12.6 related issues in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2454wptb6zhg9nzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

We've fixed the RST 12.6 related issues in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2454wptb6zhg9nzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Here it is http://www.aida64.com/downloads/aida64businessbuild2454hgfqm7t5swzip

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2447jx5ym0bnwgzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

AFAIK your motherboard is unable to measure CPU/NB voltage, so we cannot add that to AIDA64. Regards, Fiery

Your processor has 4 cores and 2 threads per core (via HyperThreading), so a total of 8 CPU threads. Other places may refer to your CPU as "4C/8T", meaning 4 cores and 8 threads total.

Core i7-920 is a processor that has 4 cores. "QuadCore" means "has 4 cores" Regards, Fiery

Thank you, I'm glad meanwhile the fixed AIDA64 build resolved the issues on your system too

You can try disabling the following options on the Stability page in AIDA64 / main menu / File / Preferences, although I don't think it would accelerate startup considerably. Apple SMC sensor support Dell SMI sensor support Koolance TMS-200 sensor support T-Balancer sensor support Toshiba TVALZ sensor support The delays are most definitely caused by the RAID scanning, but since you have a RAID array in your system, disabling that feature may not be the best idea Regards, Fiery

No, I don't think you should be so drastic First try to contact EVGA and ask them about the E-LEET CPU temperature reading discrepancy vs. BIOS Setup readings. If they supply you with a fixed EVGA E-LEET, then the CPU reading may come from the same wrong place in E-LEET and AIDA64, and the BIOS Setup provides the best values. In such case we'll also fix AIDA64