Fiery

You can enable the bottom status bar in AIDA64 / main menu / View Regards, Fiery

It means your system is not stable. You can try a lot of things to make it stable, like returning to default (stock) settings in the BIOS Setup or updating the BIOS. If that doesn't help, then it may still be quite a few components at fault, like RAM modules, motherboard or the power supply unit. Unfortunately diagnosing such issues remotely is not possible.

Just extract the ZIP archive content into the existing installation folder of AIDA64. Let it overwrite any existing files. Your entered license and your existing settings will both be retained.

I'm afraid not. Samsung SPF displays cannot pass information back to the host computer

Your post had no attachment. No report is necessary, if you mean the issue about the motherboard sensor. In case you find some issues about your 950 Pro NVMe SSD, then please let us know. The sensor issue will be fixed in the next AIDA64 beta update due in a few days from now.

Samsung SPF LCD displays do not feature a touch-screen interface. At least not one that could be handled by a Windows software.

Thank you. We'll fix the mentioned voltage rail measurement issues in the next AIDA64 beta update due in a few days from now.

That dump is enough, thank you. The problem is that sensor readings from one of your sensor devices replace (overwrite) the readings coming from the other sensor device of yours. We'll have to revamp the way AIDA64 uses sensor slots about fans and pumps. We'll do that in the next AIDA64 beta update due in a few days from now

What kind of external LCD screen do you have? Or you mean you use the SensorPanel feature to display the sensor values on your Windows Desktop?

You can find out about the assignments if you look at the bottom of the Motherboard / CPU page. The first utilization value is Logical CPU1 there, the second is CPU2, and the last one is CPU12. Regards, Fiery

Close AIDA64, and simply extract the ZIP package into the existing installation folder of AIDA64. Let it overwrite any existing files. Don't worry, it will retain your entered license and all your previous settings and customizations. In case you're ambivalent about such upgrade procedure, then you can extract the ZIP package into an empty folder too. Please note that if you have a valid AIDA64 license, then you can use the built-in automatic updater too. Just first enable upgrading to beta versions in AIDA64 / main menu / File / Preferences / General / NetUpdate.

The reason behind all that is because we prefer AIDA64 to report the temperatures exactly the way the motherboard reports them. If the motherboard doesn't report the 3rd temperature (via the BIOS Setup), there must be a good reason behind that. Usually the reason is that the temperature rail provides incorrect, invalid or inaccurate readings; or reports a total nonsense value (like 255 Celsius). But, in your case, if you're adament the 3rd temperature makes sense on your motherboard and that it provides an essential reading, then please let me know the full model name of your motherboard, and we'll tweak AIDA64 to make sure you get the 3rd reading as "Aux" temperature on the Sensor page.

Thank you, but something went south when you created that dump. Please upgrade to 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. If it still doesn't provide accurate sensor readings, then please post an updated ISA Sensor Dump made using that new AIDA64 beta. Thanks, Fiery

Automatic page cycling is disabled by default. When there's a physical button attached to the LCD screen, you can use them to cycle between pages. But many LCD screens are not equipped with physical buttons. What kind of LCD screen do you have? Regards, Fiery

Many SPF models have sub-models and revisions, some of them have three variants I guess your SPF doesn't support mini-monitor yet, but only a second or third revision -- still named SPF-72H -- does.

H110i GTX does not use the Corsair Link framework, so please create a USB Dump instead of the Corsair Link Dump.

The only 100% reliable reference is the BIOS Setup, or a monitoring software made by the manufacturer of your motherboard. We could read all 3 temperatures provided by the ITE sensor chips, but AFAIK the 3rd one is not utilized on your motherboard.

Are you sure your motherboard is capable of measuring 3 temperatures using the onboard IT8720F sensor chip? Can you see 3 temperature readings in the BIOS Setup, on the HW Monitor or PC Health Status page? I've fixed that for you

Sounds odd. Maybe your device is an old one that doesn't yet have a Samsung USB device ID. Yours seem to have a MXIC (Macronix) device ID. Can you switch it to mini-monitor mode? It would be very useful to see what the device ID is in mini-monitor mode.

Apart from the thermal log, there's nothing useful that could be logged. A system failure due to instability could happen because of many components, and it's not possible to pinpoint the culprit. You can enable temperature, voltage and fan speed logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging.

Progress on Mad Catz's part seems to be slow. The latest Strike7 SDK (v1.1) came out in July 2014. No updates since then...

That's because AIDA64 currently supports "only" up to 14 misc fans We'll expand that to 20 fans in the next AIDA64 beta update

AIDA64 uses standard Android Battery API to measure battery charge rate and other battery parameters. Sometimes, on certain devices the Android Battery API fails to refresh the battery readings in real-time, but instead does it once per 5 seconds or once per 10 seconds only. So what you experience on your device is a limitation of the Android platform that Sony prepared for your phone, and not an AIDA64 app bug. Regards, Fiery

As we've mentioned in other Strike7 related forum topics here, we believe the issue is not in AIDA64, but in the Strike7 SDK that AIDA64 uses to communicate with the keyboard. Please report the issue to Mad Catz, and they should fix it up. I'm afraid there's no other way to re-initialize the keyboard from AIDA64 than restarting it. Regards, Fiery

Yes, it does, but you first need to enable AIDA64 / main menu / File / Preferences / Stability / Corsair Link sensor support, and restart AIDA64.