Fiery

I'm afraid it could be due to a number of issues, including: faulty memory module(s), incorrect memory timing/voltage settings, compatibility issues between your memory modules and your motherboard, Windows driver or configuration issue (low chances IMHO), power supply failure, motherboard failure, CPU failure. Since you seem to have a brand new CPU, motherboard and PSU, it's unlikely that they cause the issues. We've seen similar problems with an ASRock Z170 motherboard and HyperX DDR4 modules, where no matter what we tried, the motherboard kept being unstable with those memory modules -- but the same motherboard worked great with Crucial DDR4 modules, and the HyperX modules worked flawlessly in a Gigabyte Z170 motherboard. In your case I'd try contacting Asus to find out whether your memory modules are 100% compatible with your motherboard. If Asus said yes, then I suppose a RAM RMA or replacement to different brand modules may be necessary to resolve this. Although it's not really possible to diagnose such issues remotely, so please take everything I said as pure guesses, and not definitive guidelines or diagnosis. Regards, Fiery

Device Manager: You can try re-installing Intel chipset software package, it may help. But, if the device is still there, you don't have to worry about it. It doesn't bring any useful functions to Windows, but it also doesn't require a driver to be installed. Chassis fans: Thank you for the data. Please note that the 3rd chassis fan is already there on the Computer / Sensor page of AIDA64, it's just called Power Supply fan. We will fix the labelling issue in the next AIDA64 beta update. Video card fan: Thank you for the data, but we need 2 different dumps, one for the fan spinning state, and another for the fan stopped state. So we could compare the registers output to see where the catch is. Thank you for your time.

That was a special limited-period promotion that is now over. I've sent you a private message about this.

Thank you for the feedback

Fortunately there's no alert method for computer self-destruction

You don't have to. You can renew an old, expired license anytime. We currently have no plans to introduce a lifetime license.

1) The device is most likely the Thermal Controller of the Z97 PCH. On some systems the BIOS hides that device, but AIDA64 will re-enable it in order to provide PCH Diode temperature readout. 2) Several ASRock motherboards use a poorly implemented fan muxing mechanism that is unsupported by AIDA64. On your particular motherboard that effectively means that only one of the CPU fan headers can be monitored by AIDA64. However, the rest of the fan headers should be available on the Sensor page of AIDA64, albeit they may be labelled differently, like System fan or Aux fan. If they're not there, then please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. 3) The video card fan issue is most likely because even after the fan is stopped, your GPU still reports the last fan RPM for whatever reason. It could be a VBIOS issue or a GPU pecularity. We can check what's going on, but in order to do that, we would need to see how the GPU registers look like when the fan is not spinning, and also when it is spinning. So if it's possible, please issue an ATI GPU Registers dump for both states, by right-clicking on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic. Thank you for your help. Regards, Fiery

Thank you for the feedback.

Thank you for the feedback. And yes, feel free to send us an email with your questions.

We've issued an update to the AIDA64 UWP app in the Windows Store, and it's already available for download. It includes the mentioned workaround to avoid the crash on the Windows page.

We've issued an update to the AIDA64 UWP app in the Windows Store, and it's already available for download. It includes the mentioned workaround to avoid the crash on the Windows page, and also the necessary tweakings about your Xiaomi device.

Have you tried to restart Windows and reinstall RTSS? I don't know of other software that could output AIDA64 readings to a full-screen OSD.

Thank you, we'll update the ETA reading to show the ETA string in the next AIDA64 beta update due next week.

Do you mean how to use AIDA64 for network monitoring and network management? If yes, then it would be best if you could go through the following documents: http://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf http://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-manual.pdf Also there's the Domain Network Installer: http://www.aida64.co.uk/domain-installer Regards, Fiery

Yes, you can import all your old settings and your entered license key by backing up and restoring the AIDA64.INI and PKEY.TXT files. But, you can also just take the new beta ZIP package and extract it to your existing AIDA64 installation folder. Let it overwrite any existing files. It will retain your existing settings and license.

We've now tested it with 3 different devices, and as I've suspected, it's a platform issue. It comes up only on certain devices -- and not all devices --, because the Windows 10 Mobile Insider Preview upgrade wasn't performed properly. If you upgrade from WP8.1 or another Win10 Preview, and you don't perform a device reset (Settings / System / About / Reset your phone), then all kinds of weird things may happen. Now we've done the improper upgrade flow on 3 devices, and all 3 devices crash on the Windows page of AIDA64. While previously, when we performed the "Reset your phone" step after every preview build upgrade, no such crash happened on the same devices of ours. I of course understand that it's not easy to perform such reset operations on a device in use, but if you skip that step, Win10 preview builds will not function 100%. We will try to come up with a workaround in the next AIDA64 app update.

Thank you for the info. We've now tested it with 3 different devices, and as I've suspected, it's a platform issue. It comes up only on certain devices -- and not all devices --, because the Windows 10 Mobile Insider Preview upgrade wasn't performed properly. If you upgrade from WP8.1 or another Win10 Preview, and you don't perform a device reset (Settings / System / About / Reset your phone), then all kinds of weird things may happen. Now we've done the improper upgrade flow on 3 devices, and all 3 devices crash on the Windows page of AIDA64. While previously, when we performed the "Reset your phone" step after every preview build upgrade, no such crash happened on the same devices of ours. I of course understand that it's not easy to perform such reset operations on a device in use, but if you skip that step, Win10 preview builds will not function 100%. We will try to come up with a workaround in the next AIDA64 app update.

BTW, on your Lumia 920 did you perform a device reset after upgrading to Windows Mobile Preview Build 10581?

We'll try digging deeper to find where the problem might be. It's not easy, since we don't do anything special on the Windows page, and it works under 10581 on our test devices (Lumia 535, Lumia 930, and various PCs as well). And since another user reported similar crash on the Windows page, with a Lumia 930 running Windows 10 Mobile Preview, and since with a similar device and similar Windows build it's working fine for us, I'm leaning towards putting the blame on Windows 10 Mobile Preview. BTW, did you perform a device reset after upgrading to Windows Mobile Preview Build 10581 on all 3 devices? Thanks, Fiery

Thank you

Yes, we can switch from the current ETA seconds to the new ETA string. But make sure to properly specify the string type. Is it Ansi string or Unicode or UTF-8? It would also be great to improve the accuracy of the shared memory fields description by specifying whether they are signed or unsigned values, and also their endianness.

Thank you for the feedback. I'm afraid custom formatting for hardware monitor values is not possible.

You can download the mentioned new AIDA64 Extreme beta update from: 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.

You can download the mentioned new AIDA64 Extreme beta update from: 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.

You can download the mentioned new AIDA64 Extreme beta update from: 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.