Fiery

I'm afraid your HM65 chip is still the old B2 stepping. You can verify the revision ID + stepping value combinations for Intel 6 Series chipsets at: http://www.intel.com/Assets/PDF/specupdate/324646.pdf On page 9 you can see that revision 04h belongs to B2 stepping. Your chipset must have 05h in the revision field to be B3 stepping.

1) Displaying anything in 3D games or other full-screen 3D applications would require developing several hooking modules to "inject" the graphics to all possible 3D interfaces, e.g. Direct3D9, Direct3D10, Direct3D11, OpenGL, etc. We may do that in the future, but I'm afraid it won't happen this year. 2) You can backup all AIDA64 settings -- including SensorPanel configuration -- by backing up the AIDA64.INI file you can find in the installation folder of AIDA64. We'll soon implement SensorPanel profiling, to let you export or import complete SensorPanel configurations, including images.

What does AIDA64 display on the Motherboard / Chipset page, in the line of "Revision / Stepping"? On B3 stepping it should say: 05 / B3 Please avoid posting a single issue into multiple topics. The rest of the topics have been removed. Regards, Fiery

We'll soon implement SensorPanel profiling, to let you save your panel configuration -- including background images -- into a single file, and backup it, or share it with other users.

In the beta SensorPanel topic, you can see a few examples of how other users built up their panel design:

Even though the SensorPanel feature is not capable of doing that, you can get similar functionality using either the AIDA64 Logging feature, or the AIDA64 System Stability Test. You can enable and configure Logging in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging. You can see the min/max values in the System Stability Test on the Statistics tab.

Do you mean to display not the current temperature, but the absolute minimum or maximum measured since AIDA64 was started?

Please make sure to enable the option RAID SMART support in AIDA64 / main menu / File / Preferences / Stability. After changing that option, make sure to restart AIDA64. Let me know if it helps. Thanks, Fiery

We'll soon completely revamp the AIDA64 Alerting module, to make it more suitable for advanced use. When we do that revamp, we'll implement new alert triggers, e.g. CPU utilization, GPU utilization, memory utilization. I'll let you know in this topic once we have a new AIDA64 beta with the requested new feature implemented. Thanks, Fiery

Thanks for the feedback. It seems, lately RAID controller manufacturers are revamping their drivers to make them work in RAID mode even when only standalone drives are connected. Or, at least the drivers stop providing the usual Windows API interfaces for standalone drives enumeration. Hence you need to activate RAID SMART support with those drivers to let AIDA64 scan RAID controllers using RAID methods either.

BTW, do you have the option RAID SMART support enabled in AIDA64 / main menu / File / Preferences / Stability? You may need that to enable AIDA64 to recognize the drives you have connected to a RAID controller.

Thank you. We've tried to tweak it a bit in v1.80.1450, but apparently it didn't work out. We've also done some test runs on a 88SE91xx controller, but it seems our test motherboard is not affected by the issue you experience on your system. We'll try to get another motherboard with a Marvell controller, and hopefully it will be suitable to replicate the issue.

AIDA64 licenses are not version-limited, but time-limited. Hence if you buy a license that entitles you for 12 months of free upgrades, it means for the next 12 months you can upgrade to any AIDA64 releases, e.g. v1.90, v2.00, or even v3.00. After the 12 months expire, you can still use the last version you upgraded to, for an unlimited time -- but you won't be able to upgrade to new releases anymore. If you want to extend your maintenance (upgrade) period, you can buy an upgrade license anytime at 70% cost of a new license. There're additional options to buy a longer maintenance period, e.g. 24 months at 1.5x price of a regular 12 months license, and 36 months license at 2x price of a regular 12 months license. Upgrade licenses are also available for both 24 months and 36 months.

We've done a few test runs on our DP67BG motherboard, and it seems no matter if we configure 1T or 2T setting for Command Rate, the system provides virtually identical memory performance in AIDA64 benchmarks. It must mean there's a BIOS bug, and the motherboard is stuck at 1T Command Rate all the time. We'll contact Intel and send them our findings.

We've made more test runs, and as it turned out, it's a bug in the rendering part of SensorPanel. You can only avoid that by increasing the window size of the main AIDA64 window. The bug will be fixed in the next beta release. I'll drop a message here in this topic once the new beta is released.

Thank you. It seems either we got an incorrect information on how to detect Command Rate on Sandy Bridge processors, or Intel XTU has a bug about Command Rate configuration. We'll do more test runs, contact Intel, and I'll get back to you in this topic once we have a development about this. Thanks, Fiery

Yes, the transparency setting is correct now. Please try to select a different background color (e.g. red), press OK, then try to select black again, and press OK.

Try to hide or remove the first item (sensor_background.jpg) in the SensorPanel Manager. Also, check if you have the right background color selected for the SensorPanel (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel), and also that you have all transparency settings disabled there too.

Bar width can be set at any value. It can even be wider than the total width of the sensor item The placement (location) of the bar is selected by the Place setting on the Bar tab. You need to try all 4 possible placement settings to see which one means what. The last one (3-line) is designed to be used for vertical bars. Vertical bars can be configured if you select a smaller bar width value than the bar height value.

Do you happen to use a big black background image? If not, then please post a screen shot of the SensorPanel Manager, maybe there's an issue about the items you have on the SensorPanel.

We only have plans to improve the SensorPanel and the Logitech LCD features. With the SensorPanel you can put together a much better looking panel than with the Sidebar Gadget feature.

Yes, or simply from Google image search

Once you enable the SensorPanel feature in AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel, and press OK to close the Preferences, an empty blue window will appear. You will then need to use the right-click menu on the blue panel to add new SensorPanel items of your choice. In default we don't show any items on the SensorPanel, since everyone will have a different approach on which items to be shown on his panel. However, since the "empty blue panel" caused a confusion for many of our users, from the next beta version we'll start the SensorPanel with a minimal set of default items already shown there, e.g. CPU temperature, motherboard temperature, etc. Of course you'll be able to remove the pre-configured items if you want, and replace them with your choices.

As Arctucas stated, the System Stability Test will run forever, unless it finds a hardware issue or your computer fails in any ways (BSoD, sudden restart, power-off). Running the Stability Test for at least 12 hours is recommended. However, your computer has a serious thermal management issue. Processors are not meant to work beyond 70-80 Celsius. You need to improve the cooling solution, or you risk shortening the lifespan of your CPU

It may be due to the infamous ULPS feature of Catalyst drivers. Try to enable the kernel driver support, and in the same time disable Multi-GPU support on the same page in AIDA64 Preferences. Alternative way is to disable the ULPS feature by setting all occurences of "EnableUlps" to a zero (0) value in the Registry. Let me know if any of that helps. Thanks, Fiery