Fiery

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?

That's an issue we've never seen before, it's quite interesting. Did it start to happen after you've performed an AIDA64 upgrade? Or did you change a hardware component and that triggered the issue? Thanks, Fiery

With the GPU monitoring enabled, please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Sensor Profiling Dump. Copy-paste the full results into this topic. Thanks, Fiery

Thank you for the report, it's perfect in German. Try to disable GPU monitoring by right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules --> GPU. If it doesn't help, try to disable the other HWMon Modules as well, one by one, and see if any of them cures the issue. If none of those helps, and you've got Asus AI Suite installed, try to uninstall it, and see if it helps.

Thank you for the dumps. I suppose the issue may be the fact that your system has multiple PCI bus segments. We'll have to come up with a workaround for such situations. If possible, please export the following Registry path out to a .REG file: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI Rename the .REG file to .TXT, and attach it to a post. Maybe, but I'm not sure. It may worth a try. But please do the Registry export under Windows 7 or Windows Server 2008 R2. Thanks, Fiery

You can move the file to your flash drive manually, and it will be used by AIDA64 running from the flash drive.

We'll have to check how can that be rendered. Most likely it would be no problem to render it on the SensorPanel and on most external LCDs, but it may be difficult to achieve it with the HTML based LCD modules (Logitech Arx, RemoteSensor). We'll also have to check how can we combine that effect with the existing 3D effect.

I've just sent you a private message about this.

AIDA64 is supposed to save the entered product key into a file called PKEY.TXT in the folder where you start AIDA64 (via its main executable module called AIDA64.EXE) from. Check if the user running AIDA64 has the right to write to that file on your flash drive. Regards, Fiery

Thank you for the feedback

Before the development of the Logitech Arx and RemoteSensor modules, AIDA64 already had a facility called External Applications. Many users use those tricks (like shared memory) to export the sensor values AIDA64 measures and get the values processed by their own software or solution. It is just as legal and fine as connecting to the AIDA64 RemoteSensor HTTP server with a native mobile app that you would develop. The only trick is: we cannot provide technical support for that app, since it's not our development, so you would have to deal with the users questions in the new forum topic you would maintain. We do however will support your efforts to make sure the RemoteSensor HTTP server can communicate with your app properly. BTW, it's a great idea to develop a native app. We're looking forward to giving it a try

That's absolutely incredible It looks great, and I can see that you've put a lot of efforts into producing custom graphic material.

Thank you, and Happy Holidays!