Fiery

You can check the L3 cache performance using AIDA64 Cache & Memory Benchmark (AIDA64 / main menu / Tools / Cache & Memory Benchmark). In case your processor have L3 cache enabled, you will see it evaluated there

Do you have Asus AI Suite installed?

Please check Q#10 at: http://www.aida64.com/support/knowledge-base Regards, Fiery

Thank you for confirming the bug fix. Hopefully Roblion would also find it stable now

Thank you for the feedback

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip 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 device context leakage issue. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've fixed the device context leakage issue. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2029bcq0xs8flwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

AIDA64 can only detect one O&O product license, SafeErase. Do you mean that software, or some other one by O&O?

It means maybe not the Shared Memory feature itself, but one of the items would cause the handle or memory leak. Can you please check what happens if you enable the Shared Memory feature, disable Registry exporting, and enable all items in the Ext.Apps items list? Then check how many handles does Task Manager show on its Performance tab, and how much memory, threads and handles does AIDA64 use for its main process on the Processes tab (there you may have to enable the Handles and Threads columns from main menu / View / Select Columns). Then play some games, and when AIDA64 or Event Viewer becomes sluggish, check the handles and threads values in Task Manager to see which one is piling up. I'm sorry to request so many test runs, but apparently on our test systems even enabling all Ext.App items, no issues can be found with the AIDA64 Shared Memory + LcdStudio combo And what we've previously thought may be the root cause of the issues is actually done properly, so there must be something else. We suspect it may be something about video driver calls when detecting GPU clocks -- or something like that. It's quite tough to diagnose such bugs

Thank you for the feedback

Yes, that's our suspicion too. We already have a theory about where the Shared Memory feature piles up the handles, but it's not easy to reproduce and verify it. We'll work on it in the upcoming days, collect feedbacks from other beta testers as well, and hopefully we can fix it up soon.

Yes, that's it.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2025y4wsqxjd7hzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. If not, then please let us know what video card(s) do you have, and whether you have any RAID arrays defined or any external storage devices connected via USB, eSATA or FireWire. Thanks, Fiery

Yes, you need to remove all unwanted sections (AIDA64 information pages) from your RPF file to make sure you only get such details in your reports that you actually want to have there. Using /SAFE a lot of pages get disabled (and so not written into the resulting report file) due to AIDA64 not being able to utilize its low-level features. Prime examples are the Chipset page, Sensor page, SPD page, ACPI page, GPU page, etc.

Thank you. That's quite puzzling, since there doesn't seem to be any direct correlation between the 3 temperatures read from the onboard Fintek sensor chip and the values displayed by MSI Control Center. We'll need to do more research to try finding the logic behind that. Yes, it's normal, and it's due to the fact that GPGPU computations require a lot of traffic between the CPU and the GPU, so even though that's not the point, the CPU also gets stressed.

It should be available. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2025y4wsqxjd7hzip 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, but which one is the North Bridge temperature there? And using which method could you identify that reading as the North Bridge temperature? I'm just asking because officially your motherboard is not able to measure that reading...

I'll move the thread under the General Discussion later today. As for the increase in detected sections, I'm not sure what you mean, since you seem to be already using the /CUSTOM command-line option that limits the detected (reported) information to your preference.

/SAFE will disable SMBus support. And you need SMBus support to detect SPD memory modules

I'm afraid we haven't been able to figure that out yet

Please note that Core 2 processors feature very inaccurate core temperature diodes The cooler the processor gets, the more inaccurate values the diodes produce. Close to +20 Celsius they can be plus/minus 20 Celsius off, and around zero Celsius they usually stop working completely. Intel only fixed that issue in Sandy Bridge. BTW, if you want, you can adjust TJMax value in AIDA64 / main menu / File / Preferences / Hardware Monitoring.

Thank you for the feedback

As Squall Leonhart suggested, you need to have the latest Intel RST Enterprise WHQL driver installed, and you need to enable the options RAID member enumeration and RAID SMART support in AIDA64 / main menu / File / Preferences / Stability. Make sure to use the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...25y4wsqxjd7hzip Let me know how it works. Thanks, Fiery

Thank you, we're already working on this issue. I'll post a message into this topic once an update is available.