Fiery

Due to product segmentation it's not really possible to build a database for such features. And most companies tend to keep information on detecting such features private

"FPU" subtest uses AVX acceleration on certain AVX capable processors. It's not possible to disable AVX acceleration, unless of course you switch to Windows 7 SP0 or Windows XP -- where AVX is not available due to Windows kernel restrictions.

We currently have no information on how to measure such GPU load on either architectures. Do you know of a software that can do that? Thanks, Fiery

If you use only the "FPU" subtest in AIDA64 System Stability Test, then you can try the worst case scenario for your processor: an AVX accelerated heavy stress test that will put the most demanding load on the CPU. With the "FPU" subtest your CPU will reach the highest power draw and the highest temperatures as well. If you don't want to put so much stress on the CPU, to test the "without AVX" scenario, then in the AIDA64 System Stability Test just enable all tests except for the "FPU" subtest. Regards, Fiery

I'm afraid I don't understand your question. Can you please explain it more detailed, or maybe post it in your native language and we can use Google Translate to figure it out. Thanks, Fiery

Please let us know more detailed what the issue is.

Thank you for the dumps. Please check it with GPU-Z 0.7.2 as well, and let us know if it shows similar value to AIDA64 or not. Thanks, Fiery

1) Custom PNG images can only be used for gauges. 2) The seconds issue is due to the fact that the update frequency of the panel is 1 second, but it could be more when detecting certain items take a long time. We'll try to come up with a workaround soon. 3) You can use the auto-scaling option for your graph to avoid the clipping issues. The auto-scaling feature is implemented specifically for the network traffic items

Thank you for the feedback

We've asked the local Razer distributor again about availability on the DeathStalker Ultimate. If they cannot deliver the hardware soon, then we'll order one from A**zon. AIDA64 fully supports Logitech gaming keyboards with built-in LCD screen, including G19s.

Thank you for the data. The battery charge rate information should work properly on your system. But please note that it cannot be placed on the Sensor Icons, but only on the rest of the hardware monitoring modules, like OSD Panel or SensorPanel.

Tcase is the maximum ambient (case) temperature specified for your processor. In case the case temperature (labelled as "Motherboard" temperature in AIDA64) crosses that limit, your processor may be permanently damaged. Regards, Fiery

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

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it doesn't help, then please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Also, 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

Thank you for the feeedback

Thank you for the feedback! I'm afraid the Antec Chill Control issue cannot be fixed. It is due to the fact that the underlying Asetek LC interface doesn't allow multiple Windows software to access the liquid-cooling hardware simultaneously

We've removed the invalid CPU fan reading. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've just extended the 32 threads benchmarking capabilities of AIDA64 to 640 threads, and added processor groups support as well. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Using this release you can use all CPU, FPU and memory benchmarks of AIDA64 to measure the full 48-core performance of your configuration.

I'm sorry for the difficulties. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

The mentioned AIDA64 beta release is available for download at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

We've implemented the External IP Address hardware monitoring item. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2546y3mbp1kvdjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that AIDA64 only updates the External IP Address info once per 15 minutes, since it has to go to the internet to query for your external IP address.

Do you have the slowdown on the splash screen? If yes, then what's the status message displayed while the long wait is occuring? Or do you experience the slowdown only when going to the Sensor page?

Single-threaded memory benchmarking is obsolete, and retaining them next to the multi-threaded ones would just cause more confusion. You can still compare i7-4770K against Core 2 using the new multi-threaded benchmarks. You can still use the old single-threaded AIDA64 cache & memory benchmarks if you keep a copy of AIDA64 v2.85.

Thank you for the feedback

1) Even if you divide the L1 cache bandwidth scores by the number of cores, it's not really possible to compare Haswell AIDA64 v3.00 L1 cache results against results obtained by previous releases, mostly because only AIDA64 v3.00 utilizes AVX instructions. Without AVX it's not possible to properly measure Haswell L1 cache bandwidth. 2) 5400 vs. 4699 MB/s: you need to use XMM or YMM registers to properly utilize the cache and memory subsystem capabilities of modern Intel processors. 3) According to Intel's optimization guide, the bank conflict issue of Sandy Bridge and Ivy Bridge has been eliminated in Haswell. 4) "I hate the fact that cannot play with new toys myself" -- In order to develop kick-ass benchmark methods, you simply need to get the hardware you optimize for Without letting you to try every combinations on an actual CPU, it's very tough to come up with extreme optimizations. Hope this helps to let you dig deeper into Haswell