Fiery

No worries, we've already ordered the keyboard. As soon as it arrives, we'll start working with the current SDK. We've also sent Mad Catz an inquiry about the potential issues and missing parts we've found analyzing the first SDK release. If they respond in a timely manner and the SDK is useful in its current form afterall, then the 3 months I've mentioned above for the stable implementation may be a lot shorter to get a beta stage Strike7 implementation in AIDA64

As I've stated above: "One thing that doesn't seem to work is putting images under the dynamic keys. We suspect it is due to a bug in the SwitchBlade SDK. We've asked Razer through their forum about this, and will push them to fix it up if it is indeed a SDK bug." So far we haven't been able to fix this on our end, since it indeed seems like a SDK bug that Razer has to fix on their end.

The message means the stess testing module of AIDA64 has found a small issue while running the test. When I say small issue, I mean a glitch that is small enough not to cause a catastrophic system halt, via a BSoD, system lockup or unexpected system restart. Of course a minor instability is still an instability, so you have to tweak your system settings to make sure your PC returns to being stable.

Thank you for the data. Your notebook definitely has a new kind of sensor solution that is unknown to AIDA64. Can you please check how many temperatures and fan speeds can you see in the laptop's diagnostics, and is there any voltages there as well? If it's easier, then please take a photo of how that app looks like, and attach it to a forum post. Thanks, Fiery

It's already available since AIDA64 v4.00 (November 2013).

It means one of your input devices (mouse or keyboard, typically) has a broken DirectX Input support in their Windows drivers. It's usually not a big deal these days, so you can ignore that issue. In case you want to stress your system to see how it copes with heavy load, you can use the AIDA64 System Stability Test (main menu / Tools / System Stability Test). http://www.aida64.com/solution/system-stability-test

Thank you for the feedback. So you mean now, after reinstalling AIDA64 v4.50, everything works fine, including the Sensor page? That would be great news

Thank you for your replies. Can you please check whether the lockup occurs if you click on the Motherboard / Chipset page?

Dedicated is supposed to be the on-board video memory, while dynamic should be the remote memory, allocated in the system memory. In case you've got a CF configuration, then there's a chance Direct3D reflects video memory usage by adding up the two 3GB memory regions.

Windows video drivers may use local (on-board video card) memory, or remote (portions of system RAM) memory, depending on what their requirements are. I suppose in your case the on-board memory has been exhausted, so the game started to allocate system RAM to store textures. That is normal these days, you don't have to worry about it -- unless of course the game slows down when it exhausts video card memory. Regards, Fiery

1) Do you have Asus AI Suite installed? 2) What was the previous version of AIDA64 that worked fine? 3) Have you tried AIDA64 v4.50 only once, or anytime you try to use it, it freezes when accessing sensors?

We have a lot of things on our long-term roadmap, including the idea of having multiple SensorPanels in AIDA64. I cannot provide a definitive schedule though, since we tend to prioritize such plans based on a rate of requests coming from our users. If a lot of guys start to demand a specific feature, we put them higher on our list of things to do.

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.