Fiery

AIDA64 stores the LCD layouts and all other settings in the AIDA64.INI file. That's all you have to back up.

You need to download the Strike7 SDK from: http://www.madcatz.com/downloads/strike7/ Then copy the 32-bit Strike7API.dll file from the latest Strike7 SDK ZIP package into the AIDA64 installation folder. In the Strike7 SDK ZIP package you can find that file in the API/Win32 folder. Let me know if you did that, and it still fails to work.

Thank you. Those registers do not seem to contain a valid CPU temperature reading though. Can you please start SuperODoctor, close it, and then create and copy-paste a new ISA Sensor Dump? Maybe SuperODoctor reconfigures the sensor chip. BTW, we haven't touched the CPU temperature measurement code about your motherboard, so both old and new versions of AIDA64 should display the same reading. The only difference may be due to another software possibly reconfiguring the sensor chip, or a BIOS update re-adjusting something about the sensor chip.

Please avoid posting a single issue into multiple topics. I've replied in your other topic.

Note that certain USB devices fail to report the connection speed properly. What is the USB device in question? Please avoid posting a single issue into multiple topics. Please keep posting in English. This is an English language forum, and I'm afraid we cannot speak Russian. Thanks, Fiery

Yes, that's an intriguing idea, and kind of similar to my idea #2 above Problem is: we've checked it on a BlackWidow Chroma keyboard, and it doesn't seem to work all that well. The main issue is that the keyboard matrix is not a regular matrix, so it's not like a real matrix of LEDs. You would have to look at the keyboard from several meters of distance to make up the displayed characters, and even then it's not just a simple glance. It would be much easier if the keyboard buttons were arranged in a regular matrix, like this: Fortunately the rest of the ideas seem to work fine, so all we have to do now is implement the whole thing in a new hardware monitoring module

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Using that data we can see what's going on about the various temperature inputs provided by the sensor chip of your motherboard Thanks, Fiery

No, it doesn't add those values up. It simply reports committed memory as swap space, that's all. In order to avoid further confusion, in the next AIDA64 beta we will remove the Virtual Memory section and rename Swap Space to Virtual Memory.

AIDA64 supports Koolance TMS-200 since the first version of v1.00

AIDA64 already supports TMS-200. Have you tried to enable it? (AIDA64 / main menu / File / Preferences / Stability) Maybe it would support TMS-205 as well. Let me know if it doesn't work

Thank you, we'll add that GPU to the next AIDA64 beta update due in a few days from now. Regards, Fiery

The latest AIDA64 update implements full support for the upcoming Intel Skylake processors, adds advanced support for Microsoft Windows 10 and Windows Server 2016 operating systems, and supports the latest graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - Microsoft Windows 10 RTM and Windows Server 2016 support - AVX2 and FMA accelerated 64-bit benchmarks for Intel Skylake and Broadwell-H CPUs - Optimized 64-bit benchmarks for Intel Braswell and Cherry Trail processors - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APUs - Improved support for Intel Braswell, Broadwell-H, Cherry Trail and Skylake CPUs - Preliminary support for AMD Stoney APUs - Preliminary support for Intel Cannonlake, Goldmont and Skylake-E/EN/EP/EX processors - AlphaCool Heatmaster II sensor device support - Support for Modding-FAQ, Noteu, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - Portrait mode support for AlphaCool and Samsung SPF LCDs - SMBIOS 3.0 support - Kingston HyperX Savage, OCZ Trion 100, OCZ Vector 180 SSD support - GPU details for AMD Radeon Rx 300 and R9 Fury Series - GPU details for NVIDIA GeForce GTX 980 Ti, Tesla M60 What's new since AIDA64 v5.00 - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - Optimized 64-bit benchmarks for AMD Carrizo APUs - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell CPUs - Aquaduct, Aquaero, AquaStream XT, MPS, PowerAdjust 2, PowerAdjust 3 sensor devices support - Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Odospace LCD devices - SensorPanel and LCD: right-to-left bars, static label control strings - 0.01 Celsius temperature measurement resolution for select sensor items - System certificates information - CUDA 7.0, OpenCL 2.1 support - Corsair Neutron XT, Crucial BX100, Crucial MX200, SanDisk Ultra II SSD support - GPU details for nVIDIA GeForce GTX 960, GeForce GTX Titan X [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ Press Release (Русский) ] [ Press Release (český) ] [ Press Release (polski) ] [ What's new in AIDA64 v5.30 ] [ Download ]

I think this may have been avoided by disabling booting from USB devices in the UEFI Setup (BIOS Setup)

We will add RIL serial number information to the next AIDA64 for Android app update.

Thank you for the data. The issue will be fixed in the next AIDA64 stable update due on Tuesday.

Thank you for the feedback. Please note that the quoted pecularity was actually a feature called ZeroCore Power, not a bug Probably AMD disabled it on your card with the latest Catalyst update to avoid various issues.

Which one of the above proposed 4 ideas would you use? We've tried idea #2 on BlackWidow Chroma, but it didn't seem like something you would actually want to use The big numbers were hard to read, even from a distance. The other 3 ideas seem to be more practical. K70 and K95 do not feature a SDK, and their API is not documented either. However, there seems to be some useful information on the web about how to access them directly, so we'll give that a try

Have you restarted your system after disabling ULPS? Or you've disabled it a while ago? If you disabled it a while ago and since then you've updated Catalyst, then there's a chance ULPS got re-enabled by Catalyst. Anyway, if you're 100% sure ULPS is disabled, and that Multi-GPU support is enabled in AIDA64 / main menu / File / Preferences / Stability, then please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers, and copy-paste the results into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump, and copy-paste the results into this topic.

Yes But please give us cca. 2 or 3 weeks, since currently we're very busy working on the upcoming update to AIDA64 that will cover such things like Windows 10, Skylake, Nolan, etc I'll get back to you in this topic once we have an update. Thanks, Fiery

Not yet

AIDA64 will only measure those values in a CrossFire setup when ULPS is disabled. With ULPS enabled accessing the registers for the secondary adapter could cause a system crash. Do you have ULPS disabled?

To me it doesn't seem to be a voltage issue. But I'm not sure what could it be It's not easy to diagnose such issues remotely, but maybe someone else here on the forums will have an idea...

Thank you. Yes, I can confirm that "Aux" is the CPU temperature on your motherboard. We'll fix the labelling issue in the next AIDA64 update

Most likely "Aux" will be the CPU temperature. What motherboard do you have?

It largely depends on the actual Turbo Boost multiplier and power limit settings. The FPU subtest of the AIDA64 System Stability Test is very demanding, so in most cases the CPU cannot use its highest Turbo multiplier due to TDP constraints. Regards, Fiery