Fiery

Thank you. The issue is caused by the non-working MSRs. In such scenario reliable CPU clock measurement is not possible.

I suppose the issue may be that the motherboard in that scenario fails to provide a stable and accurate APIC clock (ie. BCLK frequency) reading. Without that AIDA64 cannot calculate the CPU core clock properly. Try to right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. You can see five APIC clock readings in that dump. You may need to enable status bar in AIDA64 / main menu / View first though. Thanks, Fiery

Temperature #1 is the water temperature for your H100i GTX. There should also be a Pump #1 indicating the pump RPM. Before the update I suppose AIDA64 didn't handle your H100i GTX device at all, and so it couldn't collide with Corsair's own software.

Then I suppose the issue is that AIDA64 sets the fan speed to its default value (or the one you configured as Asetek fan speed), but then Corsair Link software will override that when it is running in the background. That's a collision that we cannot avoid on our end, and is caused by the improper USB API that some Asetek-6 based water coolers use. The problem is that you cannot detect water cooler temperature and fan RPM reading without altering the fan duty cycle (%) setting So you have to send a duty cycle value in order to get sensor readings back.

Try to set the Asetek fan speed setting to the value you've configured for your fans in the Corsair Link Software, e.g. 60% or such. BTW, have you tried closing Corsair Link software?

Check for new versions is performed at the highest rate of once per 24 hours. If the last check was performed e.g. 6pm yesterday on your system, and you start AIDA64 8am this morning, it won't check for new versions and so you may be "stuck" with the previous version for a few hours If you started it 8am tomorrow, it would have noticed the new version and enabled you to update to it automatically. BTW, you can always initiate the check for updates process from the Help menu. I suppose AIDA64 wasn't closed properly now or sometime in the past on your machine, and that left the old AIDA64 kernel driver loaded by the Windows service layer. Restarting the computer helps in such cases.

You can use AIDA64 under bootable Windows, like Windows PE or BartPE. You cannot use it without any form of Windows though.

The new AIDA64 release introduces advanced SMART disk health monitoring, implements enhanced support for Samsung NVMe SSDs and various power supply units, and supports the latest graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - AVX and FMA accelerated FP32 and FP64 ray tracing benchmarks - Vulkan graphics accelerator diagnostics - Microsoft Windows 10 Redstone RS1 Insider Preview support - Improved support for AMD Zen Summit Ridge CPU - Improved support for Intel Kaby Lake CPU - Corsair AXi power supply unit sensor support - Corsair Link sensor support - Corsair Strafe, Logitech G13, Logitech G19, Logitech G19s RGB LED keyboard support - Corsair, Logitech, Razer RGB LED mouse support - Improved support for Koolance and T-Balancer sensor devices - Multiple pages support for Logitech Arx and RemoteSensor - ACPI 6.1 support - Kingston SSDNow UV300, Samsung CM871, Samsung PM871 SSD support - GPU details for AMD Radeon R5 340X and Radeon R7 350X - GPU details for nVIDIA GeForce 920MX, GeForce 930MX, GeForce 940MX What's new since AIDA64 v5.00 - Microsoft Windows 10 TH2 (November Update) support - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - AVX2 and FMA accelerated 64-bit benchmarks for Intel Broadwell and Skylake CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD Nolan APU - Optimized 64-bit benchmarks for AMD Carrizo APU - Optimized 64-bit benchmarks for Intel Braswell and Cherry Trail processors - Preliminary support for AMD Bristol Ridge, Raven Ridge, Stoney, and Summit Ridge CPUs - Preliminary support for Intel Apollo Lake, Broadwell-E/EN/EP/EX, Broxton, Cannonlake, Goldmont, Kaby Lake, Skylake-E/EN/EP/EX processors - Advanced SMART disk health monitoring and NVMe SSD support - Corsair K65, Corsair K70, Corsair K95, Logitech G910, Razer Chroma RGB LED keyboard support - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream XT, Farbwerk, MPS, NZXT Kraken, PowerAdjust 2, PowerAdjust 3 sensor devices support - Corsair HXi, Corsair RMi, Enermax Digifanless, Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Modding-FAQ, Noteu, Odospace, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - System certificates information - Support for LGA-1151 motherboards and USB 3.1 peripherals - Extended ACPI table decoding - Advanced support for Adaptec and Marvell RAID controllers - CUDA 7.0, OpenCL 2.1, OpenGL ES 3.2, SMBIOS 3.0, VirtualBox v5.0 support - Corsair Neutron XT, Crucial BX100, Crucial BX200, Crucial MX200, Kingston HyperX Predator, Kingston HyperX Savage, Lite-On MU II, OCZ Trion 100, OCZ Vector 180, Plextor M6V, SanDisk Ultra II, SanDisk Z400s, SK Hynix SC300 SSD support - GPU details for AMD Radeon Rx 300 and R9 Fury Series - GPU details for nVIDIA GeForce GTX 950, GeForce GTX 960, GeForce GTX 980 Ti, GeForce GTX Titan X, Quadro M3000M, Quadro M5000M, Tesla M60 [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.70 ] [ Download ]

RTSS FPS monitoring is also available

AFAIK Strike 5 doesn't feature a LCD/OLED display that would useful for 3rd party applications like AIDA64. Also, unlike the Strike 7, it doesn't feature a SDK that 3rd party applications could use to communicate with the keyboard.

Yes, it is. Let it overwrite any existing files. It will retain your existing configuration settings (in the AIDA64.INI file) and your entered license.

The DLL is part of Logitech Gaming Software, and it is linked with other modules of LGS. So it's not possible to copy it over from a different source. Reinstalling LGS usually fixes the issue, just as it did in your case

Make sure to update Logitech Gaming Software to its latest version, and also update AIDA64 to the latest beta version available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

In order to use the built-in Audit Manager and Change Manager features, you need to include the audit-related pages in your report profile. Otherwise, one or more of the pre-defined set of audit items will not work properly. You can check the list of audit-related pages if you create a report file using that report profile, e.g. manually by the Report Wizard, or via the command-line option /AUDIT. Regards, Fiery

Are you using the latest stable version of AIDA64 v5.60.3700? If yes, then please note that there's a bug in that build that we've already fixed in the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

It would be important to narrow it down a little bit more. Please try to find out which one of the 3 options helps to get rid of the slowdown.

Yes, they've told us that they're quite busy, I suppose with finishing up and then rolling out new hardware. They should be able to provide the necessary programming information in a few weeks.

For video cards memory read and memory write speed reflect the performance the GPU can transfer data from/to the host (CPU) through the PCI Express link. In your situation GPU2 seems to be using half the PCI Express bandwidth. It is usually due to it having only x8 link, while your primary GPU should have the full x16 link.

We haven't been able to get our hands on a GRID+ V2 yet. It should arrive next week though, so if we can solve the protocol issue, you can expect AIDA64 to support the device sometime in April.

Thank you for the feedback. We've contacted MSI and they said your board doesn't support monitoring DDRVPP.

We've checked what's available online, but it doesn't seem to be clear at all. Is it possible to handle the device in graphics mode, without writing the bitmap frames to the built-in SD card? Writing one frame per second (or more frequently) to the SD card would destroy the card in a few hours, so it's not feasable. If you're looking for a solution to handle the device in alphanumeric (character) mode, then please let me know what character resolution does your device support, what are the VT100 commands to use to move the cursor to a specific position, how to send text (if there's an escape code to display text), what's the command to clear the display, what's the command for contrast and brightness adjustment, and the bit rate (baud) to use with the additional COM port settings like parity, stop bits, etc. Or, in case there's a single document to explain all that, let me know where can we download it from. I couldn't find one for your specific device that would include programming details and protocol description. Thanks, Fiery

Thank you for the dump. Based on that, it uses an industry standard FT232 USB->Serial bridge chip. The "issue" is behind that chip, ie. how to talk to the LCD using serial commands passed to the FT232 chip. EDIT: I've found some material Let us check how it works, and I will report back in this topic.

I don't think they support passing bitmap data over the USB connection. But, in case you have information on the contrary, please let me know Regards, Fiery

Of course not The AIDA64 System Stability Test, including all its sub-tests can stress any PCs released in the past 20 years, all the way back to the very first Pentium and AMD-K5 processors.

It's a global SMART status. If it says "OK", all drives are fine. Otherwise, one or more drives report an imminent failure. The shared memory tags for power values say "pwr"; whereas the tags for voltages say "volt". If another software picks power readings up as voltages, it's due to a bug of that other software and not an issue about AIDA64