Fiery

I'm glad it worked out for you. What we'll do is gradually add more and more hardware monitor items, so more readings would be available for other applications. But the underlying WMI and shared memory solution is simple and useful enough to not require constant improvements.

What you can try is: 1) Start AIDA64 Extreme 2) Go to main menu / File / Preferences, press OK button without altering any settings 3) Close AIDA64 4) Go to AIDA64 installation folder, and open the file called AIDA64.INI 5) Find the following 2 lines in the AIDA64.INI file ... HWMonSharedMemName=AIDA64_SensorValues HWMonWMIProvName=AIDA64_SensorValues ... and replace them with the following 2 lines: HWMonSharedMemName=EVEREST_SensorValues HWMonWMIProvName=EVEREST_SensorValues That will make the shared memory and WMI provider modules of AIDA64 backwards compatible with the same features Everest used to have. That should help you to make AIDA64 compatible with LCDC. If not, then I'm afraid you have to contact the authors of LCDC and push them to adjust their software to be compatible with AIDA64. Regards, Fiery

Thank you. Please confirm that the 2 video cards in question have the full part number as: Asus GTX780-DC2OC-3GD5 Asus Poseidon-GTX780-P-3GD5

1) Yes, I can confirm that AIDA64 is able to put sensor readings to the LCD of DeathStalker Ultimate keyboard. 2) As for AlphaCool issues, please refer to the following forum topic: http://forums.aida64.com/topic/88-aida64-plugin-for-alphacool-lcd/

With both video adapters, please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. Thanks, Fiery

It's currently not possible, but we may implement that sometime in the future. Regards, Fiery

Thank you for the feedback

There's no specific way to enforce that from AIDA64. It will automatically use the Windows user under which AIDA64 was executed. If it doesn't suit your needs, then you may want to copy the scheduled task in Task Scheduler under a different name, alter it to suit your needs, and disable the Load at Windows startup option in AIDA64.

I'm glad you managed to fix it up. Thank you for letting us know about the resolution.

Changing the date, time or time zone while running the Stability Test may affect the Elapsed Time counter, but wouldn't cause a false-positive hardware failure warning. However, it's best not to change those system properties and generally avoid altering system settings while running the Stability Test. Regards, Fiery

I don't think it's damaged or flawed at all. You may just need to use a bit more conservative overclock settings, or return to stock settings to make things work stable again.

I think it may be because the stress testing process crashes without providing a feedback. That might happen when the CPU or uncore is excessively overclocked Regards, Fiery

It's not on our short-term roadmap. You can however cut out a part of the desktop wallpaper and put it into the SensorPanel background, which would effectively "emulate" a transparent effect. It's not a perfect solution, but many AIDA64 users went that way. Regards, Fiery

We've been trying to reproduce the issue on our local systems, but with no luck so far. I suppose the crash is caused by an "odd" scheduled task, maybe one that was created improperly by a software installed on your system. Can you please try to go manually to the Software / Scheduled page in AIDA64, and click through the tasks in the top-right list, and see if that causes a crash or any other anomaly? If yes, then please let me know which task is it.

I'm afraid I don't understand what you mean. Can you please explain your issue more detailed? Thanks, Fiery

Switching between 4 pages is already supported. The left-most 4 buttons in the bottom row are dedicated to switching between pages, and the 5th button brings up the Preferences. The only problem is: due to an unknown reason the Razer SBUI SDK isn't able to put images on the buttons. We'll keep investigating this as soon as Razer updates the SDK to a newer release. Regards, Fiery

Then I guess the problem is due to you are running AIDA64 as a normal user, instead of running it with administrator privileges. Many low-level features of AIDA64 requires administrator rights to function properly.

Yes, that seems to be a bug in Catalyst. But please note that OpenCL support for Radeon HD 4000 Series was never validated, and so you shouldn't expect it to work at all. ATI/AMD only offers official and stable OpenCL support for Radeon HD 5000 and later models.

I'm not sure what you mean there. Basically, the global update frequency controls the update rate for most sensor items. And there are exceptions from that rule, like the Master Volume, which is never updated more frequently than once per 3 seconds.

Thank you for the feedback, it sounds great!

We believe that such anomalies are caused by certain odd behavior of the ForceWare drivers. We've already implemented workarounds for that, but it may not work 100% sometimes. What version of ForceWare are you using? And what exactly do you have to do to get the values back?

It's normal. To make sure the hardware monitor module of AIDA64 doesn't consume too much CPU cycles at each update, some items are updated at a minimum of 2, 3 or 5 seconds update rate.

Intel HD Graphics 3000 doesn't support OpenCL.

You can open the GPGPU Benchmarks panel from AIDA64 / main menu / Tools. But please note that GPGPU benchmarks are only available in AIDA64 v4.00 (latest version). Regards, Fiery

1) What Windows version do you have installed? 2) Are you using AIDA64 v4.00? (latest version) Thanks, Fiery