Fiery

It is coming, in a few days

Yes, but only via Fraps. You need to install and configure Fraps, and then you can add a new item named Fraps to your LCD or OSD in AIDA64. Regards, Fiery

The only thing I can spot there is the HID UPS call. If you don't have a smart UPS, then please disable HID UPS sensor support in AIDA64 / main menu / File / Preferences / Stability. If you do have such a UPS, then try to disable the same option to see if it makes the thread creation error go away.

It looks as if something went south in the NT kernel, and not in the user mode modules like AIDA64.EXE or NTDLL.DLL. Please try to restart Windows, and see if it fixes it up.

If you start AIDA64 as a standard user (not an administrator), then no UAC prompt will be displayed, and AIDA64 will run in limited mode, since it has no access to its low-level features.

I suppose yes.

1) Are you sure you don't have a temperature correction value applied on the core temperatures in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction? 2) Also, do you have the TJMax temperature value set to Automatic in AIDA64 / main menu / File / Preferences / Hardware Monitoring? On Core i3/i5/i7 processors it's best to leave the TJMax at automatic, since those processors are capable of providing the right TJMax value through a CPU register, so no need to play with manual settings. Thanks, Fiery

Thank you for the info. We'll fix the device names in the next AIDA64 beta release.

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.