Fiery

Just run both tests after each other. If you only use the "FPU" subtest, it will test not only the floating-point computation capabilities of your system, but also stresses the cooling solution by driving your system to the highest temperatures. If your system can stand that without any issues, then enable all subtests to run a stress test with diverse computational tasks. Any properly built systems should be able to stand and pass both stress tests.

That only means the Strike7 SDK causes a crash in its DLL, and that pulls AIDA64 main process down with itself I'd be happy to help you out, but at this point we both are at the mercy of Mad Catz. If they could try this out and find the issue in their SDK and fix it up, that would of course fix this whole thing. Or, if they can find an incompatibility between their SDK and AIDA64, then we would be happy to work with them to resolve it. The main problem is that we cannot reproduce the issue on our own Strike7 keyboard. If we could do that, things would probably be a bit easier. Please try to put a bit more pressure on Mad Catz, as a customer who's having issues using their product.

Thank you. I see the point now. Can you please tell me from a technical point of view which method would suit you best out of these two: 1) Embed the HTML code directly. You would have a new LCD item type of HTML Code, and you could enter the tags and text in there, which would then be stored as a fixed HTML snippet in the AIDA64.INI configuration file. If you want to update the HTML code, you would have to reconfigure (modify) the LCD item. 2) Include a HTML code on-the-fly, from a HTML file on your computer. You would have a new LCD item type of HTML Include, and you could enter the filename of a HTML file that will be basically included in (copy-pasted into) the HTML file rendered for the RemoteSensor and Logitech Arx modules of AIDA64. And now that I wrote that last line, I came to realize that you may not be talking about those special LCD variants, but maybe a physical LCD device like Logitech G19? It would be important to clarify, because we cannot include HTML code in our classic LCD/SensorPanel rendering engine -- but we can do that for the HTML based LCD modules, namely RemoteSensor and Logitech Arx.

Do you mean CPU fan or CPU temperature reading? If it's the CPU fan, then such issue could happen when the fan is spinning too slow at idle, and the motherboard sensor chip cannot pick up the fan RPM.

Embedding a fixed HTML code would be a lot less difficult than to embed content from another website. Can you please tell me what is the goal with this feature? If it's not to be published on the forum, then please send me in private message. I'm really curious how someone would actually utilize such a feature.

Yes, that pretty much what needs to be done on all systems, regardless of the CPU model or motherboard type.

Our CFA634 was bought not that long ago, but last year, and it has FW 3.1 in it. When we power up the display, it shows the firmware version as "FW 3.1". What does yours show when it powers up? I suspect yours has got an older firmware (perhaps "SKD204-634 V2.2" means it's FW version 2.2 -- or maybe PCB version 2.2). If it's the case, then we will have to find out how to implement support for older firmware. Most likely the CFA634 communication protocol has gone through major changes in the past 10 years, and AIDA64 can only handle the later (newer) protocol.

Please try to enable the two RAID related options in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64. If it doesn't help, then please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic. Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. Also right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> RAID Dump. Copy-paste the full results into this topic. Thanks, Fiery

Do you mean embedding a certain HTML snippet? Or you would like to display another website content on the LCD?

It means your CPU scales better when AIDA64 is running those benchmarks. VP8 and PhotoWorxx are different beasts anyway. VP8 because it doesn't scale with all cores in the system perfectly, so its behavior is different to all the other benchmarks. And PhotoWorxx relies heavily on the memory and cache subsystem, so in many cases it will not scale well after a certain point because of the narrow memory bandwidth (or cache bandwidths).

No, I'm not saying 2690 is worse than 2660. What I'm saying is that we've already seen such regression in performance before, although it was more about overclocking vs. memory bandwidth and latency. Sometimes adding more resources do not mean an increase in performance. Of course, it would be best to confirm those results by running other benchmarks as well. Of course it has to be such a benchmark that could scale up to 12 cores / 24 threads per socket, and can also be limited to use only 10 cores.

1) Do you use the same AIDA64 version and the same SATA/RAID controller driver now and before? 2) Do you use the same AIDA64 settings (AIDA64.INI) now and before? 3) Are you intentionally running an old AIDA64 version?

It's definitely an odd issue. I can think of 2 issues that might explain this: 1) Turbo Boost and power limits are configured in a way that they kick in too much with all cores utilized, preventing your CPU from running at high clock speeds. 2) Haswell-EP processors may not scale perfectly when going from 10 cores to 12 cores. Maybe 10 cores mean a more ideal configuration than 12 cores, and in certain situations utilizing 2 more cores could mean a regression in overall performance or per-core performance. We've done a test run on our 10-core reference Haswell-EP Xeon system to see how it scales when going from 1 core to 2 cores, then 4 cores, 6 cores, 8 cores, 10 cores, and the scaling didn't show any regression or bump in the performance. The pecularity that you're experiencing may well be related to the 12 cores your CPUs feature.

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