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

What is the device that you used for that test? Thanks, Fiery

We've fixed the GPU utilization issue on RS780 and RS880 chipsets in the latest beta release of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2925v1s4kpycljzip We'll fix the voltage issues soon as well.

We do not have a weather plugin for AIDA64, and we currently have no plans to work on such a feature. You can use custom gauge design if you select Custom as gauge type. Then you have to press the "..." button next to States to load the 16 individual gauge state graphics files. Of course, you have to draw all 16 states first, using Photoshop or a similar graphics software. Regards, Fiery

You can find out how to install AIDA64 Business in a corporate environment in the AIDA64 Business Setup Guide: http://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf Regards, Fiery

That does disable HDD/SSD temperature measurement. If the issue persists, then it is caused by another module. You can try disabling HWMon Modules one-by-one (right-click on the bottom status bar of AIDA64 main window --> HWMon Modules), maybe you can find out which one is behind the spikes.

Thank you for the feedback. Those very rare peaks could be caused by the HDD/SSD temperature enumeration.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2920kbxvyrnlsjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it makes any difference.

1) What version+build of AIDA64 are you running? 2)What version of Windows do you have installed? (32-bit or 64-bit) 3) Do you have any external drives connected, either via eSATA, USB or FireWire? Thanks, Fiery

It's best not to use the computer, but in rare cases using the computer could help to get to the system crash quicker

Thanks for the info. So the issue only comes up when RTSS is active?