Fiery

Please let me know the firmware version of your CFA634, and also the version of the driver you're using. Because we've just tested our CFA634 with the latest AIDA64, and it worked flawlessly.

AFAIK no, there isn't. Maybe one day Odospace will be ported to iOS? http://forums.aida64.com/topic/2776-display-pc-sensor-values-on-android-device-connected-via-usb-odospace-remote-panel/

Thank you for the debug info, we will fix this issue in the next AIDA64 update due next week. Regards, Fiery

Thank you Regards, Fiery

What you need to do to figure out the right resolution to use is select all items in the list of LCD items in AIDA64 Preferences, and push the Hide button. Then press the Apply or OK button on the Preferences window, and check what your device responds. It should display the splash screen with the resolution you need to configure for the current orientation. E.g. an iPhone 5s would require 981x501 in landscape mode, and 980x1648 in portrait mode. It's the pecularity of the integrated web client Logitech Arx uses After you've set the right resolution, you can unhide the previously hidden items of course, and continue using your LCD layout.

Quite odd. I've had NOD32 64-bit + Win7 64-bit SP1 with the same UAC setting running for years, and I have never experienced such issues at upgrades. Do you have any other software running in the background that may cause such issues? Any other security software, firewall software maybe?

Your INI file is still there, with your LCD settings included. AIDA64 update doesn't remove the old INI file. I have no idea what part of Windows refuses to execute AIDA64.EXE. What anti-virus/security product do you have running?

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

No, I'm not blaming your motherboard at all. I'm saying something "could be". I'm listing potential issues that may cause such problems. And with previous versions you may not have noticed the fan reporting "bumps" simply because AIDA64 may have showed the previous value that it cached, instead of removing the reading when the sensor chip fails to provide it for a moment or for a longer period of time. And BTW, I didn't say and I still don't say that the fans or pumps have stopped working. Not at all. What I'm saying is that the sensor chip may fail to measure the fan RPMs or fail to provide the right values to AIDA64. Even if the fans are spinning, their speed may or may not be properly measured by the sensor chip, we've seen many examples of such malfunctions. For example, our Kraken X41 water cooler simply doesn't like some of the fans we hook up to it. And even though it provides the power to make the fans spin, and the fans are indeed spinning and never stop, the water cooler cannot measure the fan RPM most of the time. It's a whole different story to drive a fan, and another issue is to measure its RPM. Measured RPM can drop to 0 or become an unrealistically high value (like 50000 RPM) even when the fan is spinning at e.g. 2000 RPM all the time. Now, coming back to the actual issue that you're experiencing I think it would be important to rule out AI Suite, if possible. But please note that AI Suite has background services that keep polling the sensor chip, even if you close the main application, and even after you've uninstalled the whole software. Yes, it's odd, but that's how it works. So even after uninstalling AI Suite, it would be important to get rid of all its background services and see if it helps. Another useful test could be to have the old AIDA64 running for a longer period of time, and then checking how the fans that with the newer AIDA64 versions disappear from your SensorPanel behave. Maybe they do not disappeear with the old AIDA64 version, but their values never move after some time? Maybe you just think AIDA64 reports the correct values, because they look right, but the values simply do not move? Still, I'm only guessing, I'm trying to come up with ideas, I'm not saying it's the case, I never saw your system running

Please try the following, and let me know what results do you get. Go to the CPU Queen in AIDA64, push the Parameters button on the toolbar, and select 20 CPUs. Then start the benchmark, and note down the score you get. Then do it for CPU PhotoWorxx as well. Thanks, Fiery

Thank you for the feedback

I'm sorry for the late reply. We've implemented a workaround to remove the decimal digits from the Battery Input and Battery Output readings on the OSD, Desktop Sidebar, LCD and SensorPanel. Hopefully this tweaking will be a good compromise to make your layout look perfect http://www.aida64.com/downloads/latesta64xebeta

Thank you. Please upgrade to the latest AIDA64 Extreme beta: http://www.aida64.com/downloads/latesta64xebeta Let me know if it helps

The mentioned new AIDA64 Extreme beta is now available for download at: http://www.aida64.com/downloads/latesta64xebeta

I think it could be because your motherboard has intermittent issues to report those 2 fan speed reading properly, or due to a collision between AI Suite and AIDA64. We keep fine-tuning the SensorPanel and LCD to better handle stopped fans, and also hot-plugged devices like external HDDs, but no matter how we improve it, we cannot fix an issue where the sensor readings cannot be reliably detected.

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

It means the AIDA64 kernel driver cannot be loaded. Try to reinstall AIDA64 v5.50, restart your computer, and make sure your Windows user still has got administrator privileges. You should also apply the Windows 7 SHA-2 security patch KB3033929 if it happens to be missing from your system. Let me know if it helps.

And what exactly do you mean by loss of focus? Do the readings disappear from the SensorPanel? Or they get stuck at a fixed value and stop updating?

I think the issue is that AIDA64 tries to allocate all available (free) physical memory to make sure all the RAM is properly stressed. It seems though that this approach causes resource allocation issues under Windows 10, so from the next AIDA64 beta update we will adjust it to use only 95% of the available physical memory for stress testing. That hopefully will be more user-friendly

Do you have AI Suite installed?

Apply button was never present on that dialog box But only OK and Cancel. Maybe the dialog box is too large (too high in the vertical direction) and the buttons fall out of the visible Windows Desktop area? Can you please post a screenshot of the dialog box?

Thank you, we'll add special sensor support for your motherboard in the next AIDA64 beta update due in a few days from now

Yes, it should be enough to state your system stable under heavy load. AIDA64 can measure up to 127 Celsius on most systems, but CPUs cannot work at such high temperatures. Your CPU most likely works at up to 100 Celsius, and then it starts throttling to prevent permanent damage. Well, that's not an easy question to be honest Surely, with water cooling you could put those temperatures down by 5, 10 or even more Celsius, depending on the performance of the cooling system. But, with regular air cooling, your system will not perform a lot better even with a bigger fan. You could get it down by 5 Celsius, but IMHO it doesn't worth the effort and costs. Especially since what the AIDA64 SST FPU subtest does is the absolute worst scenario. Even gaming all day long (or encoding videos for that matter) will not cause such high temperatures for your CPU, since the CPU load will not be that high all the time while playing a game. So as long as your computer works stable at those temperatures, it is fine and a proper build in my book

That's good news, but I suppose they will also bring a new firmware update, since without that Magician wouldn't work properly. I've heard rumours about 950 Pro having similar firmware deficiencies as SM951-NVMe, but without an actual AIDA64 user feedback I cannot confirm or deny that Fortunately all those issues can easily get fixed by Samsung, and I'm sure they will do their homework soon now.

We'll see. BTW, have you seen any screen shots showing Magician running on 950 Pro, and showing full SMART attributes list? I haven't, yet, but I hope it doesn't mean the firmware is crippled on the 950 Pro as well...