Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2013jdgxb3fcslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it works better than the previous UpTime measurement solution. Thanks, Fiery

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2013jdgxb3fcslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Make sure to scroll down to the very bottom of the OSD Items list to try finding the previously missing items for NIC#5 and NIC#6.

We've added the requested Preferences menu item to the System Tray right-click context menu, and also made the Preferences remember the last used page. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2013jdgxb3fcslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2013jdgxb3fcslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Even without running HDSentinel you could try disabling SMART support in AIDA64 to see if that portion of AIDA64 causes the issues or not. Then re-enable SMART support and disable GPU sensor support to see if maybe that portion is the one behind the headaches.

I'm not sure what sort of installer did it download and run, because the automatic update process doesn't involve any installer. It simply downloads the update in a ZIP package, extracts the ZIP content and copies the files over the old ones. All of it should go automatically, without user intervention. The only user interaction is necessary before AIDA64 restarts itself to finish up the auto-update. That restarting of AIDA64 is required to let AIDA64 replace its own main executable binary (AIDA64.EXE) with the new one. Neither AIDA64 or the auto-updater portion of it would alter any directory permissions. So I'm not sure how things could go south on your system The only thing I can think of is some sort of 3rd party application, maybe an anti-virus software would block one or more steps of the AIDA64 automatic update process, and/or would quarantine either the old files or the new files, and so changed the directory permissions to block you out from the "malware" that it thinks AIDA64 is. What you may try to do is start Windows in safe mode, and completely remove all AIDA64 related files and folders. Then install AIDA64 v2.50 from scratch, and hopefully it will then work properly.

Please export your SensorPanel settings (right-click on the SensorPanel --> SensorPanel Manager --> Export button) into a file, and attach the .sensorpanel file into a message in this topic. We'll check your settings and provide you a solution. Thanks, Fiery

Thank you for the feedback

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2003g7xvjmls4zzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Using this new beta release, please create and submit a new ISA Sensor Dump. We've added a bit more data for your system to that dump.

Thanks for the info. In order to check if it is caused by a conflict between HD Sentinel and AIDA64, it would be great if you could temporarily disable SMART support in AIDA64. It would make it much easier to diagnose this if we could narrow it down to either the SMART issue or the GPU (video driver) issue.

I'm afraid we haven't found a reason behind the fan issue on your system. Everything looks good in the dumps, so we're kinda stuck

1) Do you have any of the hardware monitoring features of AIDA64 enabled? (e.g. SensorPanel, Logging, OSD Panel) 2) Do you use Windows 7 64-bit SP1? 3) What kind of video card(s) do you have? Any SLI or CrossFire configurations? 4) What version of AIDA64 and video driver do you have installed? 5) What motherboard and CPU do you have? 6) Does the problem persist if you disable SMART support? (AIDA64 / main menu / File / Preferences / Stability / Low-level SMART operations) Note: you need to restart AIDA64 after altering that option. 7) Does the problem persist if you disable GPU sensor support? (AIDA64 / main menu / File / Preferences / Stability / GPU sensor support) Note: you need to restart AIDA64 after altering that option. Thanks, Fiery

While we receive the response from Intel, can you please do a little test for us? 1) With ECC enabled, right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. 2) Disable ECC in the BIOS Setup 3) Create a new PCI Dump and post it here. That data may help us to better understand which IMC register controls the ECC function. Thank you for your time.

That's actually one of the reasons we've developed and still fine-tune the SensorPanel feature. It can easily replace other solutions that may or may not work properly, or not updated anymore.

Quite frankly, we've already contacted Intel several times concerning various bugs in Intel RST and RST Enterprise drivers, so they're well aware of the quality of those drivers As far as we understand, they work very hard on the next major WHQL update for both drivers.

It looks like it's an AIDA64-related issue. We'll fix it soon, but first we need to discuss this matter with our contacts at Intel, to have a few things about Sandy Bridge and Ivy Bridge IMC clarified. So the bug fix schedule will depend on their response time. I'll let you know in this topic once we have an update. Thanks, Fiery

I've only had a quick look on their website, but to me it looks like you need to add special modules (DLL) to your application and you need to use .NET Framework to push your data to the Aquaero LCD. Adding external files to AIDA64 package is not something we would want to do, and .NET is quite inefficient, so we have to say no at this point. In case Aqua Computer software developers want to provide direct support for AIDA64 from their end, it's of course possible via either the Shared Memory, WMI or Registry data export methods of AIDA64. Regards, Fiery

You can use the Statistics tab of the AIDA64 System Stability Test for that purpose, or you can activate Logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. Regards, Fiery

1) Do you need it to monitor GeForce 600 Series video adapters? 2) Would it be okay to have a single value that shows the current PCIe link rate for the primary GPU? Thanks, Fiery

Thank you, we'll add your monitor to the next AIDA64 beta release. Regards, Fiery

I'm afraid that information is correct. As this page confirms ... http://msdn.microsof...(v=vs.110).aspx ... .NET Framework 4.5 RC completely replaces .NET Framework 4.0. What it doesn't explain is why the replaced files keep the old version numbers of .NET Framework 4.0. I hope the final release of .NET Framework 4.5 will fix that, and maybe it will also be installed in a new folder under \Windows\Microsoft.NET\Framework, instead of weirdly overwriting the .NET Framework 4.0 files there...

Thank you, we'll fix that in the next AIDA64 beta release.

Thank you for the feedback

Thank you. We'll wait for the next Intel RST WHQL driver update before drawing any further conclusion from that anomaly.

Not all systems are capable of measuring specific power or temperature values. You can find out what your computer can measure on the Computer / Sensor page in AIDA64.