Fiery

What motherboard and CPU do you have? Thanks, Fiery

We've dropped the original MHTML report format, because it was too slow to open and navigate in those browsers that supported it; and because it wasn't supported by all browsers. The new format is more modern, supported by all modern browsers, and much faster to open and navigate the MHTML files. Why do you want to open or copy-paste the MHTML report in a Word document? Do you need to do some kind of post-processing? Regards, Fiery

v4.30.2959 is not the latest version. Earlier today we've rolled out v4.50.3000. Please upgrade to that version, since as I've mentioned above, that will enhance the sensor readings on your motherboard.

Thank you for the data. We've extended the sensor information for ASRock H97 and Z97 boards in the latest version of AIDA64 Extreme available at: http://www.aida64.com/downloads/a64xe After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that several voltage readings shown by ASRock A-Tuning Utility are not measured, but read from BIOS voltage settings and ICC. Those readings are not available in AIDA64.

The new AIDA64 release introduces a multi-threaded OpenCL GPGPU AES-256 benchmark to measure cryptographic processing performance of modern graphics processors and APUs. It also provides extended Mantle API diagnostics for the latest AMD Radeon graphics accelerators, and supports the latest video adapters and storage devices. New features & improvements - OpenCL GPGPU AES-256 cryptography benchmark - Extended AMD Mantle graphics accelerator diagnostics - Intel H97 and Z97 chipset based motherboards support - Improved support for Intel “Haswell-E” CPU and DDR4 memory modules - Support for DDR4 XMP 2.0 memory profiles - A-Data SP920 SSD support - GPU details for AMD Radeon R9 295X2, FirePro W9100 - GPU details for nVIDIA GeForce GT 740, GeForce GTX Titan Z What's new since AIDA64 v4.00 - Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1 support - OpenCL GPGPU Benchmark Suite - Multi-threaded memory stress test with SSE, SSE2, AVX, AVX2, FMA, BMI and BMI2 acceleration - Optimized 64-bit benchmarks for AMD “Kaveri”, “Bald Eagle”, “Mullins”, “Beema” APUs - Optimized 64-bit benchmarks for Intel Atom C2000 “Avoton” and “Rangeley” SoC - Optimized 64-bit benchmarks for Intel “Bay Trail” desktop, mobile and tablet SoC - Full support for the upcoming Intel “Haswell Refresh” platform with Intel “Wildcat Point” PCH - Razer SwitchBlade LCD support - Improved support for Intel "Broadwell" CPU - Preliminary support for AMD "Carrizo” and "Toronto" APUs - Preliminary support for Intel Quark X1000 “Clanton” SoC - Preliminary support for Intel "Skylake", "Cherry Trail", "Denverton" CPUs - Socket AM1 motherboards support - CUDA 6.0 support - Improved support for OpenCL 2.0 - Support for VirtualBox v4.3 and VMware Workstation v10 - Crucial M550, Intel 730, OCZ Vector 150, OCZ Vertex 460, Samsung XP941 SSD support - GPU details for AMD Radeon R5, R7, R9 Series - GPU details for nVIDIA GeForce 700 and 800 Series [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v4.50 ] [ Download ]

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2959jb7mpx9kzfzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Thank you for the feedback. AFAIK Maximus VII Gene, Hero and Ranger boards are not capable of measuring PCH temperature.

Histograms and area graphs are already implemented since AIDA64 v3.20.

Yep, or by using G**gle Image Search

Thank you for the data, we've implemented sensor adjustments for Asus Maximus VII Gene, Hero and Ranger motherboards. Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2959jb7mpx9kzfzip Let me know how it works Thanks, Fiery

Indeed there is a SDK available now, which is a good news, of course. The bad news is: the current SDK seems to be a very compact one, with many details, explanations and tools missing, like C++ headers, hw emulator, 64-bit DLLs, etc. We may or may not be able to work with that. First, we have to order a STRIKE7 keyboard, and when it arrives, we'll see how far can we get with the current SDK. In case we get stuck somewhere, we'll contact Mad Catz support for assistance. I'll let you know in this topic once we have an update. If everything goes well, we should be able to roll out a stable STRIKE7 LCD support for AIDA64 around September.

It all depends on what exactly would you like to achieve. AIDA64 has a pretty solid support for 3rd party (external) applications. It supports shared memory, WMI and Registry to export the sensor readings for other applications to display or process. So if you would like to collect sensor readings from AIDA64 and display it on the AlphaCool LCD with your own implementation of LCD handling software, then the existing AIDA64 solution should work properly. However, if you would like to build a full graphical LCD screen layout in AIDA64 (just like with Logitech and Razer LCDs), and put the rendered bitmap straight onto your AlphaCool LCD, without any post-processing, then AIDA64 isn't capable of doing that. Regards, Fiery

On the Devices / PCI Devices page the PCIe information is provided for the cards and integrated devices using PCIe links to connect to the system. So it refers to the device capabilities, and not necesserily the port capabilities. For a PCIe 2.0 capable device plugged into a PCIe 3.0 capable PCIe port the version will be reported as PCIe 2.0.

We've added WDDM version detection to the Display / GPU page in the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild2954r6nxj2dscmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

That's a tough one, actually You can check the Computer / DMI page for such information, but many BIOSes program the DMI block up inaccurately, so the information there may not be 100% trustable. You can also check the Motherboard / Chipset page, but there only those PCIe ports are listed that are enabled by the BIOS, and the supported link rate and PCIe version are also programmed by the BIOS, and such things are also done inaccurately in many cases. It's easier to go by the motherboard model, and check the manufacturer's website for the most accurate specifications. Regards, Fiery

Thank you for reporting this issue, we've fixed the corresponding bug on our update server. Regards, Fiery

CPU core temperature is measured by the CPU itself, using its on-die thermal diode. So it cannot be swapped by any other temperatures. As for CPU vs. motherboard temperature, can you please post a screen shot that shows the CPU and motherboard temperature graphs while running the AIDA64 System Stability Test? Make sure to use only the FPU subtest, since it puts the highest thermal stress on the CPU.

That issue has already been fixed in AIDA64 v4.30. Make sure to upgrade to the latest stable version (v4.30) or the latest beta release: http://www.aida64.com/downloads/aida64extremebuild2943h3myxfzgrlzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. BTW, the 100 MHz BCLK (base clock) is the right value.

Please let me know what version of AIDA64 are you using, and what motherboard + CPU combo do you have. Thanks, Fiery

How many pages would you like to use? Regards, Fiery

1) Does your Windows user have the necessary permissions to access the Event Logs facility? 2) Have you tried it with the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild2932t6rgsj2cxhzip Regards, Fiery

AIDA64 is not affected by the Heartbleed bug. Regards, Fiery

We've fixed the +5V and +12V issue in the following new AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild2932t6rgsj2cxhzip

We've got a few reports of rare threading and OSD or Logitech LCD crash issues lately. It seems the only common part of such configurations is the security software: BitDefender. It seems, somehow BitDefender may collide with the hardware monitoring layer of AIDA64. We've tried to reproduce the issue on our own test systems, using various BitDefender versions, but without luck so far. Obviously I cannot recommend or request you to uninstall BitDefender and expose your system to other risks, so please provide us a bit more time to dig deeper and hopefully find the root cause of this issue. Meanwhile, please try to remove a few items from your OSD Panel that may be related to network traffic (like External IP Address and NIC download/upload rates), and see if it helps. Thank you for your understanding about this issue. Regards, Fiery

TJMax shows the maximum temperature the CPU can operate at. Once the CPU gets a few degrees Celsius close to TJMax, it starts throttling (slowing) itself down to prevent physical damage. Regards, Fiery