Fiery

That is due to the nVIDIA Optimus feature of your notebook. When you start AIDA64 with the GeForce chip sleeping, it will not appear on the PCI bus, and so it will not be detected by AIDA64. That is a side-effect of how Optimus works.

I'm afraid we cannot implement that. AIDA64 can only read Windows information for the running Windows instance. Regards, Fiery

Most PSU's do not provide a temperature reading On mobile systems ACPI temperature comes usually from the EC (Embedded Controller) or simply shows an average of the Intel DTS core diode temperature readings.

Aux looks like just an invalid reading that you should ignore. 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. Based on that data we can check what Aux represents on your motherboard, and fix any potential issues about sensor readings on your motherboard. Thanks, Fiery

Thank you. We'll get an Optimus capable notebook, and analyze this issue. I'll drop a message in this topic once we have an update on this matter. Thanks, Fiery

You can create a custom profile by starting AIDA64, then opening the Report Wizard --> Custom selection --> select the pages you want in your profile --> Save button. Regards, Fiery

/SAFE command-line option disabled using low-level calls in AIDA64. Such calls are required to detect SPD information, measure sensor readings, etc. You may want to remove /SAFE from your command-line. BTW, in case you have an acitve EVEREST license, feel free to upgrade to AIDA64 at: http://www.aida64.com/everest-upgrade Regards, Fiery

That looks great! A small typo though: "Temerature"

Thank you for the feedback

Automatic update overwrites existing (old) files, but it doesn't remove your settings (e.g. AIDA64.INI file) and it doesn't remove your existing license. Regards, Fiery

Modern GPUs can be used to accelerate HD video playback, to offload that task from the CPU. So what you experience about VE utilization while playing video is very much normal. While playing games the HD video acceleration is not utilized, but the usual graphics rendering part of the GPU (that accelerates 3D games) is under heavy load. I'm not sure why your CPU is working at 100% while playing a Blu-ray movie. I don't think it's normal...

Thank you. We've fixed that up in following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1653jkm2bdr9lwzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

We've fixed that in the latest AIDA64 beta release Thanks, Fiery

VE = Video Engine MC = Memory Controller Regards, Fiery

Thank you for the feedback

Thank you. Temperature readings come from Dell SMI sensor, so if you deem they're too high, it may be due to inaccurate readings provided by the BIOS via SMI. As for the Optimus issue, can you please provide more insights? For example, does the issue of "GT540 is going ON,OFF,ON,OFF,ON,OFF" occur only when running from batteries? Or it's a constant issue, regardless of power source?

1) Can you please post a screen shot that shows HD Tune Pro readings and AIDA64 Storage / SMART page side-by-side on the same screen shot? 2) Which SF-2281 based SSD or SSDs have you tested? Thanks, Fiery

1) Do you start AIDA64 at Windows bootup? 2) What motherboard do you have? 3) Are you running Windows 7 64-bit? 4) Do you have any RAID arrays defined? 5) Do you have any external disk drives connected via USB, FireWire or eSATA? Thanks, Fiery

Default setting for AIDA64 automatic updates is update only to stable releases. It means AIDA64 will update itself only cca. 6-8 times a year. By default AIDA64 Business Edition will have the automatic update feature disabled, to avoid issues in enterprise networks. Of course you can override those settings in the Preferences if you want to update to weekly beta releases.

I guess the wrong expansion slots list is for G41T-M v1 board, so we'll have to separate the two board revisions in the AIDA64 motherboard database. 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. That dump will help us to find out how to distinguish G41T-M v1 and v2 revisions. Thanks, Fiery

We've just released AIDA64 Beta Build 1651. It's available for auto-update, or can be downloaded from: http://www.aida64.com/downloads/aida64extremebuild1651ctmw8qszdnzip It implements the requested new option in AIDA64 / main menu / File / Preferences / General. During the auto-update process AIDA64 will place not only the ZIP package in that folder, but also the changelog in a TXT file. The changlog can also be seen as a list item hint in the NetUpdate window. The hint will appear while you hover the mouse cursor over the bottom part of the window, where AIDA64 lists the available updates with their corresponding version, date and file size info. We've also added more tricks about the auto-update, e.g. from the next update it will pop up a bubble over the System Tray icon after a successful update stating how many new devices have we added to the AIDA64 Hardware Database.

Sounds a bit weird, but I'm glad you managed to resolve it.

It looks like AIDA64 is unable to use its kernel driver. We've completely revamped the kernel driver in Build 1635. It means the current kernel driver cannot be loaded by an old AIDA64 version, and vice versa. Maybe while performing the upgrade you didn't overwrite the old KERNELD.* files with the new ones? Or maybe some other issue occured during the upgrade process. Please try to completely remove any AIDA64 installations you may have on your system, and restart your computer. You can keep your AIDA64.INI files of course, to keep your Preferences settings. Then manually download beta 1649, extract it into an empty folder, enter your license, and check if it works now. Let me know how it goes

1) Exactly which XPS model do you have? 2) Do you have Win7 64-bit installed? 3) Which version of ForceWare driver do you have installed? Thanks, Fiery

Have you tried to restart your computer after upgrading to the new release?