Fiery

We've had to revamp the kernel driver of AIDA64 to implement preliminary support for Windows 8. When we change the kernel driver, a one time system restart is necessary.

Please reinstall Build 1641 (latest beta), and restart your computer. If it doesn't work, then remove all copies of AIDA64 you may have on your system, restart your computer, and install Build 1641. Regards, Fiery

Both Catalyst 11.8 and 11.9 suffer from the OpenGL issue. AIDA64 v1.85 will not work with them. But the latest AIDA64 beta will work fine since it uses static linking for the OPENGL32.DLL module: http://www.aida64.com/downloads/aida64extremebuild1641xc8yz5fwkpzip

Thank you for the feedback

Thank you for the suggestions. 1) Virtual cores cannot be ignored, because it would make the CPU utilization measurement completely false. Even when the virtual cores are only working at 1-digit percentage load most of the time, such small load will still count. And with proper benchmarks and proper stress test modules (like what AIDA64 implements) it's quite easy to stress all cores -- incl. virtual ones -- to 100%. If you're bothered having your virtual cores sleeping all the time, then you may want to disable HyperThreading in the BIOS Setup 2) Less than a second polling time may be handled by your processor quite easily -- and in fact most multi-core processors could do that --, but the problem is not there. AIDA64 has a hardware monitoring module that has a set of sub-modules to handle various tasks. One of those sub-modules is for core temperature monitoring, another is for motherboard sensor chips, a third is for GPU monitoring, etc. etc. A few of those sub-modules use HID or COM (serial) port sensor devices like T-Balancer and Koolance. Such communication protocols tend to be very slow compared to other modules, which effectively means reading sensor values could last 200 to 800 msec (!), regardless of how fast CPU you have in your system. On top of that, when you have a high-end desktop system with 6 or 12 cores (1 or 2 CPU sockets), 3 or 4 GPUs (e.g. two HD6990 cards) with multiple sensor chips connected, the regular sensor readouts can also take more than 500 msec combined. Hence using a more rapid update rate could well mean a constant sensors polling or a deadlock. 3) We'll check the LCD screen drag&drop ability, IMHO it's a good idea. Regards, Fiery

Thank you for the feedback

Thank you. We've fixed the sensor readings in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1641xc8yz5fwkpzip 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 for the data. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1641xc8yz5fwkpzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Please upgrade to the following new special beta release of AIDA64: http://www.aida64.com/specialbeta/aida64extreme_build_1641_apicdis.zip This beta has the APIC clock measurement completely disabled, to isolate whether it is the cause of the lockups. It will have a side effect of less responsiveness to SpeedStep and C1E activity, and also less accurate CPU core clocks will be measured. Please let me know how it works. Thanks, Fiery

1) What processor do you have? 2) Which version of AIDA64 are you running? 3) Are you sure both EIST (SpeedStep) and C1E (Enhanced Halt State) are disabled? Thanks, Fiery

Thanks for the feedback

We do know how to adjust the necessary GPIO switches to switch between the 2 muxed fan readings on ASRock boards. However, the mux acts weirdly, e.g. it takes several seconds to safely have the mux switched. Such silly hardware solution simply doesn't fit into the hardware monitoring layer of AIDA64, which is designed to have an update rate of 1 second. As soon as ASRock retires the slow switching mux in favor of a proper solution, we'll be happy to implement that in our software.

Several ASRock boards use a proprietary fan mux logic to connect two fan readings into a single register. On such motherboards only the primary reading can be measued by AIDA64 and other 3rd party monitoring applications. Regards, Fiery

Thank you. 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. Thanks, Fiery

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. Thanks, Fiery

Thank you for the feedback

Does it lock up if you launch AIDA64 without Sidebar support enabled? If that's the case, then please check if it locks up when you go to the Computer / Sensor page. BTW, which driver do you use for the GTS450? Did you install a Win7 ForceWare? Thanks, Fiery

Thank you for your kind words. We're still pushing hard to keep AIDA64 on the cutting-edge. We'll soon roll out the Check for Updates feature, followed by the Automatic Online Update feature. We're currently working on implementing support for the latest processors (Intel Cedarview) and the upcoming new generation processors and chipset from both AMD and Intel (e.g. Bulldozer, Trinity, Krishna, Wichita, Sandy Bridge-E/EP, X58, C600). Unlike previous years we now get tremendous help and assistance from those companies, and it makes things a lot easier. We'll have a few surprises for next year, that we are going to roll out as a special forum release in its alpha and beta stages, just like how we handle the Windows 8 topic here. Regards, Fiery

You need to enable RAID SMART support in AIDA64 / main menu / File / Preferences / Stability. Make sure to restart AIDA64 after altering that option. Regards, Fiery

Thank you for the bug report. We've fixed Centrino compliancy tests in the following new beta release of AIDA64 Extreme Edition: http://www.aida64.com/downloads/aida64extremebuild1639q1ynp3i9xuzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

Thank you both for the screen shots. We've fixed sensor readings for both motherboard. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1639q1ynp3i9xuzip 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 implemented sensor tweakings for M5A97 boards. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...39q1ynp3i9xuzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please make sure to compare AIDA64 readings against Asus' own monitoring software (Asus AI Suite 2 or PC Probe II) only. Other 3rd party software may or may not provide 100% accurate readings. Thanks, Fiery

1) You can create a custom report layout (custom report profile) by starting the Report Wizard --> Next button --> Custom selection --> Next button --> select the pages you want to have in your profile --> Save button. Save the results into a .RPF file, e.g. MYPAGES.RPF. 2) Then you can use the /CUSTOM command-line option to create reports using your report profile. Example: \\server\share\aida64\aida64.exe /R \\server\share\aida64reports\$HOSTNAME /CUSTOM \\server\share\aida64\MYPAGES.RPF /CSV /SILENT /SAFE Regards, Fiery

You can use the Windows key + M key combination to show your Desktop but still keep AIDA64 SensorPanel showing. Regards, Fiery

AIDA64 only shows DTS (core temperature) readings for real cores. For a 6-core / 12-thread processor only 6 readings should be available. Please let me know where can you see 12 readings to be available. Please also right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic. Thanks, Fiery