Fiery

Please 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 the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. 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 the results as a TXT file to your post. Then please create those dumps once more, after the AIDA64 OSD gets mixed. We need all 4 of those dumps to see what's going on after sleep on your system Thanks, Fiery

What exactly is your question or issue about your Samsung SPF device? Please note that Samsung SPF-71ES doesn't support Mini Monitor Mode, hence it cannot be used as an external display via the AIDA64 LCD module.

Thank you. It seems your 4th memory module fails to provide the SPD block. I'm not sure why, it could be a faulty SPD chip for example, or a communication issue between the memory module and the memory controller. BTW, BIOS may be able to configure the memory controller even when not all SPD blocks can be read.

Do you mean the trim operation couldn't be done on your drive? It should work, especially if you use the manufacturer'sown software.

I've just sent you your product key in private message.

We'll make a Youtube video soon, in order to show how to create such register dumps. Meanwhile, please try to launch AIDA64, and press Ctrl-Alt-D. It should show you a popup menu where you should select Sensor Debug, and then inside that submenu SMBus Dump (Full).

Conditional formatting would make the LCD rendering module quite a bit more complicated, and it's already too complicated And you can already use different limit colours for bars, and also custom gauge states to indicate too high or too low readings with different colour. For example, with custom gauges you can even make a long thick red line that would only appear under (or next to) a label when the temperature is above 60 Celsius. You can also make a custom gauge that appears as a red box around a label, but only when the fan stops, etc. As for Power-Grid, we've checked it last year, but it seemed a lot more complicated to implement than Arx. So we've opted to stay with Arx and RemoteSensor. In our opinion those 2 options are fine for most users, and there's very little room where neither of those 2 work properly in case of mobile device based monitoring.

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. If it doesn't help, then 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

No, I'm afraid it's not possible.

RemoteSensor works the same way as SensorPanel. In fact, it uses the very same AIDA64 LCD rendering engine. You don't have to rename anything.

We'll think about that

Yes, it should be able to do what you're looking for. And yes, you need to enable both Asetek LC sensor support and Corsair Link sensor support in AIDA64 / main menu / File / Preferences / Stability first.

Make sure to use the latest AIDA64 beta build ... http://www.aida64.com/downloads/latesta64xebeta ... and also the latest CL4 build. It should work fine then

Thank you, I'm glad it works fine

It is usually due to a background process or service that uses system resources, and causes AIDA64 to "race" for L2 cache usage. Try to close as many background processes and stop as many services as possible. Alternative solution is to measure the L2 scores 10 or 20 times, and ignore the lowest 50% of the results.

We've recently rolled out AIDA64 for Android v1.37 app update that implements full Vulkan support. The enumerated Vulkan devices appear on the Devices page. Please note that even the latest Android N Developer Preview 3 doesn't include a Vulkan-ready nVIDIA ForceWare video driver. It would however work fine with Nexus 5X, Nexus 6P and Nexus Player. As for Samsung's Galaxy S7 and S7 edge, those devices seem to implement a strangely named Vulkan library (libvulkan_sec.so) that may not be suitable for us to use as regular Vulkan library. We'll have to check it in more details, or wait for the next S7/S7 edge system update to find out why the library is not named as libvulkan.so on those devices.

We've just checked it, and it still works fine under both Win7 and Win10, running the latest AIDA64 version. Make sure to check if your firewall software is properly configured, and that you're using the right TCP/IP port.

Thank you for the feedback

Thank you for the feedback

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery

The above mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works Thanks, Fiery

DMI generation is indicated for the underlying hardware, hence it shows its capabilities, as opposed to showing its current operating mode. We've implemented System Agent clock measurement in the latest AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

We've checked it, and it still works for us, under both Windows 7 and Windows 10. What Windows version are you using? Do you still have both NICs listed properly on the Network / Windows Network page in AIDA64, with their respective download/upload rate shown there too?

AIDA64 is already localized to Spanish.

You're right, it would work if we implement conditional rounding of electrical current and power readings. It will be featured in the next AIDA64 beta update due in a few days from now. I'll post a message into this topic once the new beta is available for download.