Fiery

That's of course possible. Just let me know the name of the DLL file, the function declaration we should call to send the image, and the expected image format. If it's your own developed DLL, then you may want to develop a fully fledged SDK, to make it more sophisticated for AIDA64 to utilize your interface. For example, you can define a DLL init call that returns the expected LCD resolution and bit depth to AIDA64, or a callback function that AIDA64 can use to be notified about LCD page change. If you prefer to continue this discussion directly in email, then please send me your email address in private message.

Originally, we wanted such a solution to utilize the LCD screens of mobile devices. The problem with that envisioned solution was that it would only work with Android based devices, and only when they're connected via USB. Most AIDA64 users want a wireless solution, and many of them use iOS, WP8 or BlackBerry. The RemoteSensor feature of AIDA64 v5.00 works with virtually any mobile device, regardless of the operating system running on them. We currently have no plans to develop a native Android app, or any other native mobile app for remote monitoring. Rgeards, Fiery

The SwitchBlade UI LCD indeed looks great. It's larger, it has multi-touch capabilities, and it's got 10 dynamic keys attached to it. My only problem with it is that it lies flat, so you cannot see it as easily as the tiltable G19 LCD. I'm not a gamer though, so I cannot really tell how can it be used when gaming, or whether the DeathStalker Ultimate overall is a better gaming keyboard than the G19 or not. All I can tell is that I believe a perfect product would be a lovechild of the DeathStalker Ultimate and the G19 But as it seems, Logitech and other companies are moving towards utilizing mobile device LCD displays, just as we did with AIDA64 v5.00.

Here you go:

Are you sure that temperature has an actual meaning on your motherboard? In many cases such temperature inputs on the sensor chip is not utilized and shows a random or bogus value. Make sure to check in the UEFI Setup that your motherboard indeed could monitor 3 separate temperature values. Thanks, Fiery

Thank you, we'll rename it to NCT6779D in the next AIDA64 beta update. Regards, Tamas

Thank you for the feedback

Here's the first beta update to implement AquaStream XT, MPS, PowerAdjust 2 and PowerAdjust 3 sensor support, when those devices are connected via USB. They were already supported by older AIDA64 releases when they are connected to an Aquaero controller device via Aquabus. http://www.aida64.com/downloads/latesta64xebeta In case you find any discrepancies or missing readings, please create a screen shot of Aquasuite 2014 or 2015 with the reference measured values, and right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post.

Here's the mentioned fixed AIDA64 beta update: 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

Here's the mentioned fixed AIDA64 beta update: 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

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Aquaero Dump. Copy-paste the full results into this topic, or attach it as a TXT file to your post. Thanks, Fiery

An update: on our GTX580, using the latest ForceWare WHQL driver suite (347.09) everything works just fine, no freezes or any latency issues while AIDA64 is monitoring the system.

Thank you for the feedback. HWMonitor is not our software, so I cannot really recommend it as a reference for such comparisons. That software may or may not be able to properly measure temperatures and voltages on your motherboard. Make sure to use a manufacturer (Asus) supplied monitor software as a reference.

Thank you, the issue will be fixed in the next AIDA64 beta update due in a few days from now. Regards, Fiery

1) Thank you, we'll fix the sensor readings for the EQ45M-S2 v2 motherboard in the next AIDA64 beta due in a few days from now. 2) The reported MWDMA mode is correct. The controller can decide whether to drive the HDD in PIO, MWDMA or UDMA mode. But, for SATA drives all those info have no relevance anyway Regards, Fiery

You can simply ignore that suggestion. It says it is relevant only for CRT displays anyway, and a RDP session is not a CRT display Regards, Fiery

Thank you. Please 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. Let me know how it works.

No, I'm afraid I cannot see anything in the profiling dump that would suggest a slowdown in the monitoring module of AIDA64. It looks more like as if the AIDA64 GPU monitoring driver (NVAPI) calls would cause ForceWare drivers to stall for a second, but we've never seen such a thing to happen with any ForceWare releases before, on any nVIDIA GPUs. We'll try to reproduce the issue on our own GTX580, with ForceWare 347.09. Meanwhile, you may want to try downgrading to an older WHQL ForceWare release, and check if it fixes the issue. If you do that, please let us know about the results.

AIDA64 doesn't monitor disk drives in that way yet. We may work on that in 2015 though Regards, Fiery

It looks awesome, good job! Currently it's not possible. We may work on that in 2015

Thank you. The hardware change shouldn't make a difference, but maybe you've also reinstalled Windows after changing the motherboard? Do you have the same type of Windows installed now than was on your previous motherboard? Quite frankly, the only case where we've seen such white screen shots was about Acrobat Reader, when a certain document streaming solution prevented the user to make screen shots of sensitive document pages. In such cases the screen shots just showed a blank white page. Can you please check what happens if you open the AIDA64 CPUID panel or Cache & Memory Benchmark panel, and you press Alt+PrtScr, and then you start MS Paint (like via mspaint.exe entered in the Run dialog box after pressing WindowsKey+R), and press Ctrl+V (Paste) in MS Paint? I wonder if it also results in a white shot, or it works properly. If that solution works properly, then you can use it as a temporary alternative to the save screen shot feature of AIDA64 until we can find the root cause of the issue and fix it up. BTW, there's a chance the issue is due to a recent Windows patch, due to a recent ForceWare update or something else that is not necesserily related to AIDA64. We will do our best to find out what's causing it, and fix it up if possible.

AIDA64 can provide information on your PSU only if the PSU is capable of providing such measurement data. As far as I can tell from the XFX website, your PSU is not capable of measuring the mentioned data. Regards, Fiery

1) Is the GPU load all zero for only one of the GPUs, or for both? 2) What version of AIDA64 are you using? 3) What version of ForceWare drivers do you have installed? 4) What kind of operating system do you have? 32-bit or 64-bit? Thanks, Fiery

Thank you. I'm afraid it looks all fine, so the problem must be somewhere else. My best guess is that the monitoring module of AIDA64 collides with another application, process or service running in the background. Do you think you have any other software running in the background that may also poll sensors or the GPU? Such as AI Suite, Rivatuner, or such?

Can you please check what bit depth do you use for your Windows Desktop? Is it the default 32-bit?