Fiery

Please try to disable Intel Virtualization Tech in the BIOS Setup, in case you don't use virtualization.

We happen to have the exact same MSI Z77A-GD55 motherboard (BIOS Version 1.11) with a Core i7-3770K CPU, and there everything works fine. Please make sure to have the option called Limit CPUID Maximum at its default state of Disabled in the BIOS Setup.

In your dump above your CPU is definitely not at default settings, since all Turbo Boost ratios are set at 42x there Or you mean you've updated the BIOS and returned your CPU back to default settings after posting the dump above?

Thank you for the data. Something causes your CPU from providing incorrect (mostly zero) values for several internal CPUID and MSR registers. While other Core i5-3570K processors have no issue providing those registers properly. Without those registers it's not possible to detect CPU cache sizes and other CPU related properties that are necessary for our benchmarks to work properly. Do you have any special virtualization environment installed? Or maybe you've adjusted something in the BIOS Setup that may be related to CPUID registers? Have you tried to return your CPU to factory default settings?

I'm afraid we also couldn't find out what motherboard you've got If it's possible, try to have a visual inspection of the motherboard PCB and find markings that may lead to the manufacturer's identify or the part number (model ID) of the motherboard.

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.