Fiery

We're rolling out a new major update to AIDA64 on June 03, 2013. It will feature the usual improvements to support the latest and greatest hardware technologies, such as GPU details for AMD Radeon HD 7990 "Malta" and nVIDIA GeForce 700 Series, and optimized benchmarks for AMD Kabini/Temash and Intel Haswell. On Haswell AIDA64 v3.00 will utilize all new instruction set extensions, so the benchmarks and the System Stability Test will also use the appropriate AVX2, FMA and BMI2 instructions. But more importantly, we've replaced the outdated set of memory benchmarks with brand new ones. The new bandwidth (read, write copy) benchmarks now use multiple threads to squeeze out every last bit of performance from the caches and the memory modules. On modern multi-core processors, using the old single-threaded benchmarks you couldn't see the actual memory bandwidth, but only the memory bandwidth available for single-threaded applications. With the new benchmarks you will however get considerably higher scores, much closer to the theoretical memory bandwidth available. It is especially true for 3-channel and 4-channel memory configurations, such as Intel X58 and X79 based high-end desktop systems; and also for NUMA-enabled multi-socket systems, such as 2- and 4-way AMD Opteron and Intel Xeon based servers and workstations. For example: Core i7-3960X with X79 chipset and 4-channel DDR3-1600: - AIDA64 v2.85 Memory Read: 16825 MB/s [ old ] - AIDA64 v3.00 Memory Read: 45640 MB/s [ new ] We've also implemented multi-threaded cache benchmarks, that now include support for the latest AVX and AVX2 instruction set extensions. Thanks to using all CPU cores for the cache benchmarks, you will get dramatically different cache bandwidth scores than with the old benchmarks. For example: Core i7-3960X with X79 chipset and 4-channel DDR3-1600: - AIDA64 v2.85 L1 Cache Read: 121.8 GB/s [ old ] - AIDA64 v3.00 L1 Cache Read: 674.7 GB/s [ new ] And thanks to the 2x widened L1 cache bandwidth of Intel Haswell, on these new processors using the new cache benchmarks of AIDA64 v3.00 you will get unusually high scores. Using Haswell, with a hint of overclock it's quite easy to cross the 1 TB/s mark for the L1 cache We've also replaced the old cache and memory latency benchmark with a brand new one that uses a different approach, recommended by processor architecture engineers. The old memory latency benchmark used the classic forward-linear solution, so it "walked" the memory continuously, in forward direction. Unfortunately that classic approach was sometimes over-optimized by "too smart" memory controllers, that led to unrealistically low latency scores. It was a constant fight for us to get around those over-optimizations, to make sure AIDA64 provides stable and reliable latency results. With the new latency benchmark we've switched to a block-random solution, that keeps "jumping" to random addresses inside a memory block for a period of time, and then skips to a new block and continues "jumping" to random places inside there as well. With this new solution memory controllers cannot find a pattern anymore in the latency measurement, and so they cannot over-optimize the benchmark. The block-random approach however means that latency results will be higher, and since the scores are in nanosec, it means the results will be worse than what you got used to. For example: Core i7-3960X with X79 chipset and 4-channel DDR3-1600: - AIDA64 v2.85 Memory Latency: 55.9 ns [ old ] - AIDA64 v3.00 Memory Latency: 67.5 ns [ new ] AIDA64 v3.00 also supports benchmarking the eDRAM L4 cache of the upcoming Intel Crystal Well processors. An interesting article about Crystal Well: http://www.anandtech.com/show/6993/intel-iris-pro-5200-graphics-review-core-i74950hq-tested Less radical change, but still deserves a note: we've also revamped the framework around the CPU ZLib benchmark, so you can see a few percent gain in performance using AIDA64 v3.00. For example: Core i7-3960X with X79 chipset and 4-channel DDR3-1600: - AIDA64 v2.85 CPU ZLib: 418.3 MB/s [ old ] - AIDA64 v3.00 CPU ZLib: 444.5 MB/s [ new ] We hope you'll find the new AIDA64 release useful. Feel free to ask any technical or not-so-technical questions about AIDA64 v3.00 benchmarks in this topic. Regards, Fiery

Since the exception seems to be related to NTDLL.DLL, we've added stronger exception handling for every calls in AIDA64 that uses NTDLL.DLL. It will be implemented in the next AIDA64 stable release due tomorrow

Please note that when you install an IPMI driver, the sensor readings should appear on the Computer / IPMI page in AIDA64. If you ask a technical person at Asus, please try to find out what methods are necessary to perform to read fan speeds (RPM) on your motherboard from a 3rd party software. As far as we can tell, none of the known methods apply to your motherboard, so it's quite a special piece of kit Usually there are 5 different ways to acquire sensor readings: 1) ISA port I/O 2) SMBus 3) Embedded Controller 4) IPMI Sensor 5) ACPI query Some motherboards use just a single method, while on others one needs to combine multiple methods to read all sensor readings. If Asus tech.support could tell us which method to use, and which registers belong to the fan speeds, then we can implement that in AIDA64 to let you measure fan speeds in AIDA64. However, based on our previous experiences with Asus, I doubt they would reveal their "cards" about this or any other Asus motherboards Asus tends to use proprietary methods about sensors, and they almost never publish any technical details on what they do and how they do it.

That issue is already fixed, so make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2460x8f2dmshtbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

That's normal, and it is due to the lag of the video driver.

That's great, thank you for letting us know!

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