Fiery

That should work then, since 1B1C-1C0A is a proper device ID that is handled by the HXi/RMi PSU code of AIDA64 already. Are you sure the PSU related readings are missing from the Computer / Sensor page?

Yes, we're aware of that. It's caused by a bug in Intel's legacy Windows 10 video drivers. We haven't yet found a way to get around the issue on our end

Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Does your Windows user have administrator privileges?

Thank you, although that's not the dump I've requested Based on the Sensor page content, it seems it's the classic case of your PSU not being able to properly provide +3.3V electrical current reading. We've seen many AXi Series PSUs with that issue, and we suspect it is due to a firmware issue. And without +3.3V current and power reading, AIDA64 cannot calculate a total PSU power draw value. +5V and +12V current and power values are still measured and shown on the Sensor page.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Corsair Link Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Have you enabled Corsair Link sensor support in AIDA64 / main menu / Preferences / Stability? Do you have the driver installed for the PSU?

Have you enabled Corsair Link sensor support in AIDA64 / main menu / Preferences / Stability? Do you have the driver installed for the USB dongle?

Please upgrade to the latest AIDA64 release of v5.70.2800 available at: http://www.aida64.com/downloads It will solve that issue. After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Measurement of CPU Package temperature is not supported by many processors out there. What CPU do you have?

We will fix the issue in the next AIDA64 beta update due later this week. I'll post a message into this topic once the new beta is available for download.

A few days from now. Less than a week

Your device doesn't use the Corsair Link framework. I know, it's quite confusing, since it still uses the Corsair Link software We cannot make it any better than now, unless Corsair comes up with a special API in the Corsair Link software that would allow us to avoid talking to the H100i GTX, and instead gain the sensor readings from Corsair Link software. What we can do right now is to add a new option to Preferences / Stability, called Asetek LC sensor support, that you can disable to avoid the discussed problems on your system. We will do that in the next AIDA64 beta update. I'll post a message into this topic once the new beta is available for download.

Most virtualized computers do not provide MSRs, or not the whole set of MSRs otherwise available on the host CPU.

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.