Fiery

ASLR and DEP support may be available in some compilers, but the compiler we use doesn't support such options. We've already adjusted AIDA64 source code to make it possible to compile it to 64-bit. We may release a 64-bit main binary as a beta later this year. Please note that most AIDA64 customers don't need and wouldn't benefit from having a 64-bit main binary. A 64-bit main binary would mean a larger disk footprint, larger memory footprint, and slightly slower overall operation as well. Critical AIDA64 components (CPU/FPU/cache/memory benchmarks and the System Stability Test) are already in a native 64-bit module. Regards, Fiery

If all tables are empty, then it means AIDA64 inserted the report(s) not into the MDB file that you're viewing. Make sure to verify which MDB file AIDA64 uses for its database.

It is there in the MDB file. A new line is inserted into the Report table for every reports, and a number of new lines inserted into the Item table for every reports.

It means it all went well. Go to AIDA64 / main menu / File / Database Manager to browse the reports that have been inserted to your database

Do you get any message after the report creation process finished?

Make sure to use DB - Access.mdb file, not the Access'97 one. The trial version should be able to put the report into the database. No installation is required for AIDA64. You can use it from a flash drive or SD card if you want. You can even run it from a CD-ROM or DVD-ROM disc, although that way you cannot save data on the disc

Yes, it should be possible to do that. You need to choose MS Access 2000/XP/2003 as Provider, select the .MDB file as Database. Then you can create reports using the Report Wizard. Make sure to select ADO as report format. Regards, Fiery

Thank you for the feedback.

Thank you for the feedback

Standalone hard disk drives provide the same performance beyond 4 KB block size. Standalone SSD drives act the same, but the limit there is around 128 KB block size. The bigger block sizes (e.g. 1 MB) are there in the AIDA64 Disk Benchmark to let you measure the performance of RAID arrays. We'll extend the maximum block size to 8 MB in the next AIDA64 release.

Can you please explain in what scenario a 1 GigaByte (or 1 Gigabit?) block size would yield to higher scores than the current maximum block size? Thanks, Fiery

AIDA64 motherboard database has the following entries about P8Z68 Deluxe models: Asus P8Z68 Deluxe Asus P8Z68 Deluxe/Gen3 So it does differentiate between them. I don't see a reason to indicate the non-Gen3 model with e.g. "Asus P8Z68 Deluxe (non-Gen3)", since that would just look a bit silly

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1856ykhfgv3djmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how the sensor readings look now.

We've fixed the mentioned issues in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...56ykhfgv3djmzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Please let us know if you find any further issues

Yes, I know, but it's not possible to disable the Portable Computer page.

You cannot hide just any page in AIDA64

That page lists the platform tests for Intel Centrino mobile platforms. On capable Sony mobile systems it also shows VAIO-specific information. On certain mobile computers it shows physical information coming from the AIDA64 mobile computer database. Regards, Fiery

Thank you for the feedback

Thank you. It looks like the I2C bus is still operational on your video cards, but the CHL8228 VRM chip disconnects or disappears from the I2C bus. Since AIDA64 is still capable of reading other I2C devices (e.g. EDID block of the monitor) in that state, we assume this is a hardware flaw or a collision between another software and AIDA64. If it's possible, please uninstall any software that may read or write any video card related data. If that solves the issue, then it is definitely a collision between that software and AIDA64.

Yes, Aux looks like it is the CPU temperature actually. The next AIDA64 beta release will fix the temperature labelling and voltage ratio issues. I'll post a message into this topic once the new beta is available for download.

Thank you for the feedback

They're both good ideas, we'll work on them. Regards, Fiery

We'll see what we can do about your little bro

Can you please create an ATI SMBus Dump after the GPU VRM temperature on the master GPU freezes? And another ATI SMBus Dump after restarting AIDA64 and getting back the GPU VRM temperature again. So we could compare the register output for the CHiL chips for normal state and "frozen" state. You can create such a dump by right-clicking on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump. Copy-paste the full results into this topic.

I'm afraid that's still normal At rest, when only 1 of the cores are stressed a little bit (because AIDA64 CPUID Panel dynamically refreshes CPU clock, FSB, chipset info, etc) your CPU momentarily switches up to the highest Turbo setting. While at 100% CPU load all cores are under heavy load, and so the CPU cannot switch up to the highest Turbo setting. Turbo Boost is designed so you could achieve the highest performance when not all of the available CPU cores are stressed.