Fiery

In case you're using Arx on an Android device, then it's still the issue of the Logitech Arx Android app that Logitech should soon update to fix a few bugs. You may want to switch to using RemoteSensor while you're configuring your layout, and once you're done, you can switch back to Arx. You can freely copy-paste items across Arx and RemoteSensor layouts, since they're 100% compatible with each other.

That looks a bit like you were using right alignment on your Simple Sensor Items. If you do so, you may have to place the items at a different location than the preview may suggest. In your case you would have to move it 100 or so pixels to the left to make it right.

I'm afraid your memory is not quite correct about the SensorPanel's history First of all, it was unveiled in June 2011, roughly 7 months after FinalWire came on the scene and we've introduced AIDA64 v1.00. So it was never a project tied to the previous generation of software (Everest). Another slight correction: both AIDA64 and Everest are commercial products, so the business sense, our approach hasn't changed due to that switch back in 2010 at all. All our software are there to satisfy user's needs, but in exchange we need a bit of financial compensation to keep things going forward. I'm not here to complain, but we have to allocate considerable resources to keep the quality and dependability of AIDA64 on the level that our faithful users got used to. As for the SensorPanel, we've never promised or planned to implement such features like transparency or a full-blown rendering engine. If we would want to do such things, we may be better off moving the whole thing under Direct3D or OpenGL anyway, but then people would complain about the impact of the rendering engine on battery performance and CPU power saving features. We have to (and want to) cater for everyone: AIDA64 has to be easy to use so less-experienced users can understand it and perform certain tasks with it; but it also has to offer unique tools and sometimes very specialized and rather compelx features to satisfy the needs of users who are blessed with a deep knowledge about computer matters. I admit, sometimes it's tough to find the balance between those very different expectations, but the fact that we're on this scene and keep doing basically the same thing for 20 years now proves that we must be doing something right Not perfect, of course, but most things in life are not (and can not) be perfect. As for the initial excitement about SensorPanel vs. the current level of users interest, well, that's another topic that could easy fill a few pages One of the reasons behind that phenomenon is that since 2010 people keep moving more and more to ultra-mobile devices (smartphones and non-x86 tablets), and spend less and less time in front of their regular desktop or notebook PC. With the introduction of the Logitech Arx and RemoteSensor modules we've done our first steps to react to that trend, and in the upcoming months you'll see many exciting things happening...

Thank you for the feedback

You can download the mentioned new AIDA64 Extreme beta update from: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

You can download the mentioned new AIDA64 Extreme beta update from: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

Thank you for the screen shots. We've checked a few logs and it seems at one point Asus added those voltages, and we weren't aware of that change. The first BIOS releases for Asus Z97 boards did not have those readings Anyway, we'll add the 2 missing voltage readings to the next AIDA64 beta release due in a few days from now.

Yes, you can.

Please try the following: 1) Upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/latesta64xebeta 2) Disable Turbo Boost in the UEFI Setup, and make sure your memory modules get the right voltage, use the right Command Rate setting (generally speaking, CR2 is more stable), and are running at stock 800 MHz (DDR3-1600) frequency 3) Try the cache stability test again Let me know how it goes Thanks, Fiery

I'm afraid we currently have no plans to support portrait mode for landscape external LCD screens.

Thank you for the debugging. We'll add the requested option to the AIDA64 / Preferences / Hardware Monitoring / LCD / Samsung page in the next AIDA64 beta update due in a few days from now.

1) Does your Windows user have administrator privileges? 2) Is AIDA64 installed originally using the self-installer EXE package?

The graphs look fine and normal. AIDA64 uses OpenCL kernels to stress the GPU (or GPUs). Currently OpenCL is tied to the video driver, and queuing and job prioritization is not really sophisticated in current OpenCL implementations by AMD, Intel and nVIDIA. It will take a few more years for those companies to finally decouple OpenCL from the video driver and make OpenCL a lot more useful and a lot more dependable than now. Because right now, as you can see, passing a new job to the OpenCL implementation takes too much time, and during that time the iGPU may switch power states. This whole issue is a limitation of OpenCL that cannot be fixed from those software that utilizes OpenCL for either computational or stress testing purposes. Regards, Fiery

I'm afraid we currently have no plans to add such API to the RemoteSensor.

It seems different SMART monitoring software consider the severity of the End-to-End Error issue differently. For us any limits being exceeded is a serious issue and so the HDD should be immediately backed up and replaced. Other software may treat such issues more lightly, but for us (and our stance is being reflected in the logic AIDA64 operates) data integrity and safety is very important, so we treat any reported problems at the highest degree. Of course, SMART is not an interface that could predict what's gonna happen with 100% certainty. We own such HDDs where the SMART layer reported some degree of predicted failure years ago, and they are still going on to this day. But, we don't store anything important on such drives, and you should neither. We've seen a few occasions already where SMART started to report an issue, the owner of the HDD didn't care much for it, and then the HDD died slowly or rather quickly and he lost some or most of his data. I don't think it's worth the gamble, but it's your call

Thank you for the feedback

You can ignore the negative values. We however will need to implement stronger workarounds to filter out negative/invalid readings

Note that recent AMD GPUs use a different register access mechanism than previous generation GPUs, so as long as the other software does poll your GPU, a collision may just occur, and it would be different than how it worked on the previous HD7850 card you used to have.

We only have control over the actual USB protocol as long as you're using our Samsung SPF drivers based on LibUSB. If you use Samsung's own mini-monitor driver, then USB transactions are controlled and governed by Samsung's driver.

Do you have any other monitoring or overclocking software running in the background? The issues sounds like a collision between AIDA64 and another software that would poll the video adapter for sensor readings or clock measurement. Regards, Fiery

I'm afraid it's currently not possible to accomplish any of the listed actions with AIDA64. Regards, Fiery

Please 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 Thanks, Fiery

You're right, and we've fixed it up in 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. Thanks, Fiery

Please 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 if it helps about the fan labelling issue. Also, I'm not sure what CPU#1 do you mean. Where can you see that in AIDA64?

Thank you for letting us know about the resolution Regards, Fiery