Fiery

As Squall Leonhart suggested, under Windows Vista and Windows 7 you can find the scheduled task that starts AIDA64 at Windows boot using Task Scheduler. Please check if the task is there, and if it is enabled. There's a chance NIS removes the task, or prevents AIDA64 from creating the task. Regards, Fiery

It looks like the AIDA64 Remote Control Server had some issues on the workstations. We'll check what's going on, although as I can see you already have up on AIDA64 If you reconsider sometime, then you can fix such issues by removing the DLL file that causes the issue (AIDA_RCS.DLL). That will of course disable the Remote Control feature, but at least you can evaluate the other features without such error messages. Regards, Fiery

System instability is something you cannot measure using a mathematical formula or a specific detection method. Some of the instability issues can be revealed by only AIDA64, some others can only be revealed by Prime, and some can be revealed by any of them. BTW, AIDA64 System Stability Test has multiple subtests. Sometimes an instable system can be put to "its knees" by only using the FPU subtest (and leaving the rest of the tests disabled), while in other cases you should enable all subtests to reveal the instability. It takes a lot of time to check out how stable your system is, but if you can achieve a high clocks via overclocking, then it worth the efforts to play around with stability tests Regards, Fiery

It is definitely a conflict between Asus AI Suite II and AIDA64. We've already contacted Asus a while ago, and asked them to implement the now industry standard mutexes that many sysinfo and diagnostics software use (e.g. AIDA64, HWiNFO32/64, CPU-Z, HWMonitor, SpeedFan, SIV, etc) to make sure their low-level code doesn't collide with each other when you use multiple of such software in the same time. But Asus don't seem to care about that at all. So in case you observe any collisions between such 3rd party software and AI Suite II, then I'm afraid it can only be solved if you put a bit of pressure on Asus to improve their software. Regards, Fiery

Thanks for the feedback

If it's possible, please try it with EIST (SpeedStep) enabled, C1E disabled, C-States enabled. Let me know if it makes any difference. BTW, are you using the latest BIOS for your motherboard? Thanks, Fiery

No problem Please let us know if you have any further issues with AIDA64. Regards, Fiery

Thank you for the data. We've tweaked the sensor readings to better support your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

Thank you for the data. We've tweaked the sensor readings to better support your motherboard. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

We've improved the sensor readings for your motherboard in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've implemented the requested menu item in the System Tray menu in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1822hfxtpmdk4vzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

The issue will be fixed in the next AIDA64 beta release that will go online later today.

Please right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump. Copy-paste the full results into this topic. Thanks, Fiery

No, I'm afraid it's not possible on the Sensor page. But the System Stability Test has a Statistics tab where you can see those values. Also, the Logging feature can create a HTML statistics file where it lists min/max/average values. Regards, Fiery

1) In your first post you said AIDA64 is supposed to open up on the primary monitor, but it opens up on the secondary monitor. In the second post you said it always opens up on the primary monitor. Which one is the case? 2) Do you configure or adjust anything about the multi-monitor setup in ForceWare, or you simply connected both monitors and use default settings? I'm just asking because we've set up a 2-display configuration with a LCD connected to DSub, and another LCD connected to DVI, but weren't able to reproduce the bug of "closing on the primary display but opening on the secondary display". Our hw config was: GT520 + Win7 64-bit SP1. Thanks, Fiery

Thank you for the feedback

Yes, you can do that. AIDA64.INI file is fully portable between version upgrades or downgrades. Regards, Fiery

Previously you wrote Aux temperature doesn't associate with any reference temperatures, that's why we've removed it. Can you please post a screen shot that shows AIDA64 Sensor page and MSI Afterburner temperature readings side-by-side, so we can directly compare the values against each other? As for GPU1 vs GPU2, the difference in GPU ordering may be the explanation. AIDA64 orders GPUs based on their position on the PCI bus. So e.g. the GPU appearing on PCI bus#3 will come first, and the other GPU appearing on PCI bus#5 will be labelled GPU2. Other software may follow a different logic ordering GPUs.

Thanks for the feedback

Thank you for the feedback

Fixed it, please try it now.

We've fixed the lockup under Win8 on Intel Nehalem+ processors. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've fixed the SensorPanel Battery Voltage issue in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...17wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1817wmksq1gtjrzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery