Fiery

AIDA64 was originally designed to monitor sensor readings (temperatures, voltages, fan speeds), but later it got extended to cover generic system readings like CPU core clock speed and RAM utilization. We've already exceeded the original goal of the hardware monitoring module, but we're up to adding more features as long as they are about monitoring a certain system state or property. Passing the output of another software to an external LCD doesn't fall in that category That other software should be responsible of outputting its displayed data to the external screen.

Thank you, that dump looks just fine. Do you have the option DIMM TS sensor support enabled in AIDA64 / main menu / File / Preferences / Stability? If not, then enable it, restart AIDA64, and check the Sensor page again

Yes, of course.

You've posted the USB PSU Dump, but in your current configuration the Corsair Link Dump is the one that is relevant. The USB PSU Dump would be relevant if your AXi was connected directly or via the USB dongle. I previously (wrongly) assumed that your PSU is connected directly or via the USB dongle, that's why I first requested the USB PSU Dump

AIDA64 works with any combination of the listed 3 choices, even if you use multiple devices. But, if you have the PSU connected to a Link Commander device, then you need to enable Corsair Link sensor support to make it work.

I'm afraid that type of usage is outside the scope of AIDA64. You could however request it as a new feature for Teamviewer.

Thank you for the feedback Regards, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). 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

Yes, but only the first core is under load. The rest of the cores should sleep there. Still, it puts a much higher load on the overall CPU package than when under Windows all cores can execute idle cycles and so cool down.

Your settings and preferences are stored in the file called AIDA64.INI. Make sure to backup that file before fiddling with AIDA64 upgrades. You can however simply extract the new beta ZIP package content into the existing AIDA64 (stable) installation folder. Let it overwrite any existing files. It will retain your existing settings (it will not overwrite or affect AIDA64.INI) and your entered license as well. Only AIDA64 stable updates are available as self-installer packages.

Thank you for the dumps. Please note that you don't need to enable any special options when your AXi Series PSU is connected via the USB dongle. But, when it's connected to a Corsair Link Commander or similar Corsair Link device, then you need to enable Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability to make it work. If you still have issues after enabling that option, then please submit a Corsair Link Dump from the Sensor Debug right-click menu. I'm sorry for the confusion about Corsair PSUs. Connection type (directly connected to USB // connected via USB dongle // connected via Corsair Link Commander) makes a big difference in the way AIDA64 has to handle the PSU or water cooler.

Many modern AMD processors feature such a temperature sensing logic that only provides reliable measurements when the CPU is under load. In the BIOS Setup your CPU cannot use idle cycles, so it's under load. It's an old thing that we haven't had a chance to revamp yet. You're right, for AMD CPUs a single temperature per socket would be enough.

We can check what's going on around monitoring your AX1500i if you could right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> USB PSU 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. Thank you in advance.

Asetek LC is the control and monitoring logic inside such water cooling devices like Corsair H100i GTX and H80i GT. It provides the following readings: liquid temperature, fan RPM and pump RPM. If you disable Asetek LC sensor support, there's no way to talk to the device and so it's normal that you lose those readings. What kind of PSU have you got? Corsair is famous for making very different PSUs on the inside In other words, AXi may sound quite similar to HXi, but AIDA64 has to handle them with different code paths.

In many cases manufacturers of Android phones and tablets encode an incorrect battery capacity value into the Android profile of the device. There's nothing to worry about that, since that value doesn't affect the operation of the battery or the device. Regards, Fiery

We've implemented support for NZXT GRID+ V2 in the latest AIDA64 Extreme beta update available for download at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please note that first you need to enable GRID+ V2 sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. Let me know how it works.

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Then I suppose it was due to Microsoft Hyper-V Which now got disabled due to the lack of hardware virtualization support

It's not possible to tell which exact component causes stability issues. It could be the motherboard, CPU, RAM, power supply unit, a system setting, a Windows driver, etc. etc. I'd update the motherboard BIOS to the latest build, and also re-check RAM settings to make sure they use the proper voltage and timings.

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.