Fiery

Thank you, got that, and already applied the necessary tweakings. I thought it was you, but wanted to confirm Thanks for the info, 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). BTW, 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 it's working fine for us, I'm leaning towards putting the blame on Windows 10 Mobile Preview. No, we don't, but I'm happy to explain the inner workings of our app, up to a certain degree.

Please note that on Windows Phone and Windows 10 Mobile it's not possible to detect CPU directly due to the strict sandboxing that is enforced by those operating systems. So both the legacy AIDA64 Windows Phone 8.1 app and the new AIDA64 UWP (Universal Windows Platform) app have to rely heavily on their built-in hardware databases. Which in your case doesn't seem to include the device in question. Please submit a report from the About page, and we will add your device to the hardware database of the AIDA64 app, and also fine-tune the CPU detection module to provide more information on your SoC. If you need further clarification on how the AIDA64 apps work, please feel free to ask either here in the public forum, or in private message. As for the Lumia 920 issue, please let me know what operating system does it have installed. Thanks, Fiery

Thank you for your feedback. We do have plans about localizing the Windows 10 Universal AIDA64 app in the future. We do not have plans to further improve the legacy Windows Phone 8.1 AIDA64 app though. We've recently ported the AIDA64 app to the new Windows 10 UWP (Universal Windows Platform), and we continue improving the new app; while providing only bug fixes and small improvements for the legacy Windows Phone 8.1 app. Regards, Fiery

As far as we're aware of, mobile platforms do not support such interrogation, so it's not possible to make an app for it. Regards, Fiery

The requested information will be implemented in the next AIDA64 beta update due in a few days from now.

It's currently not possible to achieve that using AIDA64. But, we'll implement the 2nd option (number of occurences before firing the alert) in the next AIDA64 beta update due in a few days from now.

1) We will add the new column to show the current readings in the next AIDA64 beta update due later this week. 2) Yes, there's such a limit, to make sure the graphs don't get unreadable. Truth be told, it also limits the Statistics list, which it shouldn't do. We however do not have a plan to extend the 12 slots we have there, so if you find that too limiting, then I think the real solution would be to use the Logging facility instead of the Statistics tab of the System Stability Test. You can configure Logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. Regards, Tamas

Yes, they are possible to be implemented. The only problem is that Eset NOD32 (latest version with latest updates) blocks the process of JDownloader 2 Beta installer to download its packages, I suppose because is has malicious or suspicious content. Please ask the author of JDownloader to resolve this. I hope you understand that we do not want to support malicious software in AIDA64 in any ways.

Thank you, we'll implement advanced support for BX200 SSDs in the next AIDA64 beta update due later this week.

Which values would you like to see in AIDA64? And please don't say all of them

Thank you for your kind words We did have plans about Steam, but it was put on hold due to some technical and licensing issues that are tough to overcome. We may reboot the project next year.

Make sure to 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. Regards, Fiery

Thank you for the feedback, I'm glad it works fine on your new drive.

Quite frankly, I have no idea what the Aux temperature is doing there It should be removed as a reading that the motherboard doesn't seem to handle in either the BIOS Setup, or in ASRock's own monitoring software. The only explanation behind the Aux reading could be that it comes from another source, like a secondary sensor device (most likely USB) you have connected.

Thank you That is a 3rd temperature reading for your motherboard. It could be anything, like a 2nd motherboard temperature, a VRM temperature, a 2nd CPU temperature, or just a bogus reading.

Thank you for reporting that issue. We've rolled out Beta Build 3627 to fix it up: http://www.aida64.com/downloads/latesta64xebeta

What motherboard do you have?

The mentioned new beta version of AIDA64 Extreme is now 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 us know how it works. Thanks, Fiery

Generally speaking, we're not so keen on implementing support for motherboard PWM/VRM chips. Because many of those chips are quite sensitive to frequent polling, so it could well cause a system instability just to read the temperature, current and power values from such chips. We however can add support for such boards on a case by case basis, and we just did that about your motherboard in the latest AIDA64 Extreme beta update available at: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

Yes, you will be able to find that file there.

.lglcd files are only created when you export your LCD settings manually. If you never done that, or you did that sometimes in the past, then it's probably best to use the latest AIDA64.INI file. That file includes your current LCD configuration including the LCD layout(s) you have built. Regards, Fiery

It's quite a complicated issue, since it not only depends on Windows version, but also the NVMe driver you've got installed, and the AIDA64 build you have running. But as I've stated above, we will implement full SMART support for Samsung 950 Pro and SM951-NVMe drives in the next AIDA64 update due in a few days from now. You will only need to upgrade to that new AIDA64 build, and also to download the install the latest 950 Pro drivers by Samsung: http://www.samsung.com/global/business/semiconductor/minisite/SSD/global/html/support/downloads.html Stay tuned

Thank you. We will implement full SMART support for Samsung 950 Pro and SM951-NVMe drives in the next AIDA64 update due in a few days from now

We still have no plans about an AIDA64 for Linux software. Regards, Fiery

Yes, it should be possible, but first we have to identify a few key aspects of your configuration, like NVMe driver type. If it's possible, 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. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post. Finally, right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> Disk Controllers Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post. You may need to enable the status bar in AIDA64 / main menu / View before performing those dumps. Thanks, Fiery