Fiery

A couple of issues may cause such consistently low benchmark results: 1) CPU clock discrepancies. E.g. when the CPU is running all the time at LFM (Low Frequency Mode, e.g. 600 or 800 MHz) instead of full clocks. I suppose that's not the case, since CPU core clock seems to reflect values matching HFM (High Frequency Mode). 2) CPU throttling. In other words, your system may be overheating, and the processor is slowing (throttling) itself down to prevent fatal damages. You can check that by launching the AIDA64 System Stability Test (main menu / Tools / System Stability Test). Check if the bottom throttling graph shows any activity (any values other than 0%). If there's a throttling activity even at idle, the overheating is quite serious. If you don't see throttling at idle, then try to enable only the FPU subtest (untick the rest of the tests), and press the Start button to initiate the stress test. Wait for a few minutes, and check if the throttling graph shows any activity. If it does, then your system is overheating under heavy load. Either way, if there's any throttling occuring ever, it is a problem that you need to address by cleaning the exhaust ports of your notebook. 3) Background processes. There may be other software or service running in the background that uses a lot of CPU cycles, and that impacts benchmark results. Try to close all background software, especially ones that may also be monitoring your CPU or system. Regards, Fiery

PCH is the chipset component of your motherboard. It tends to run a bit hotter than processors, especially at idle. Anything above 80 Celsius is considered high for chipsets, and beyond 90 Celsius is considered critical. Regards, Fiery

I'm afraid AIDA64 SensorPanel and OSD Panel are not usable while you're running a full-screen application or a 3D game.

We've already got the SDK -- check my previous post above I'm not sure what you mean. AIDA64 already measures all of those, except for the FPS counter. You can configure graphs with AIDA64 SensorPanel to display all those information on a single SensorPanel.

The slow startup of AIDA64 is caused by Windows itself that has difficulties loading the dynamic kernel driver of AIDA64 on some configurations. Even if we stripped down AIDA64 to an even lighter software (which we will not do), Windows would still load the very light sized AIDA64 kernel driver (less than 30 KiloBytes) rather slowly. All of the Windows Gadgets that come built-in with Windows Vista and Windows 7 do not use a kernel driver, hence their loading at Windows startup could be swift. BTW, before you call our software a bloatware, make sure to check what size is its files are (combined), and what memory footprint does AIDA64 have. Both values (typically both are under 30 MegaBytes) are fractions of a modern 3D game and several of the software you have installed on your Windows system. Regards, Fiery

Right-click on the SensorPanel --> SensorPanel Manager, and push the Import button on the top of the window to import a .sensorpanel file. Regards, Fiery

TMU count is calculated from the shader count, so it will also be fixed

So you mean those sensors are automatically updated for small drives, but not automatically updated for large drives?

Thank you for the data. The bug will be fixed in the next AIDA64 beta release due in 5 days.

I'm not sure what do you mean by "the information is not updated for all types of sensors"... Can you please explain more detailed? What happens exactly?

Please let us know what version of Logitech G19 drivers do you have installed. Also, do you use 64-bit Win8 or 32-bit?

Thank you for the data. I suppose the only issue is that AIDA64 remembered your choice of OSD item labelling, so you need to edit the problemous item in the Preferences. Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD / Items, double-click on the HDD item, and push the Default button to fix the label.

Thank you for the feedback

1) Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> ATA Dump. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. 3) Also, please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

1) Please copy-paste the full content of the Display / GPU page into this topic. 2) Also right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI GPU Registers. Copy-paste the full results into this topic. 3) Can you please check how many shaders GPU-Z v0.6.6 (latest version) reports? Thanks, Fiery

The Ukrainian translation wasn't done by us, but by Zenoviy Demianchuk. And since we don't speak Ukrainian, we cannot judge whether you are right or not about this particular issue. Please try to contact Zenoviy, and discuss this issue with him. As far as I can tell, "it does not have something" would be fine for the Portable Computer page, since it lists particular hardware components, and indicates whether the system has those components or not. Regards, Fiery

We'll work on those

MB/GB issue has been resolved by implementing decimal points for drive space readings. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...39jcn9g8sqvbzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

Here's the previously mentioned new AIDA64 beta release that implements sensor adjustments for your motherboard: http://www.aida64.com/downloads/aida64extremebuild2239jcn9g8sqvbzip

Thank you for the tip, we'll work on getting AIDA64 into Steam in January. Regards, Fiery

Could you provide programming details on how can a 3rd party application read FPS values from Fraps? We've checked out Fraps, but couldn't find such an option there...

Thank you for the feedback

If any of the benchmarks or the System Stability Test causes the system to power off, then it's definitely a hardware flaw that needs to be addressed. If your system is overclocked, then try to restore all settings to their factory default values. Also, updating the motherboard BIOS to the latest one may also help. If those wouldn't help, and you already swapped the PSU, then it could either be a memory (RAM) issue or a motherboard failure. It's quite difficult to diagnose such issues remotely

Please try to update MySQL Connector/ODBC to the latest version.

The kernel driver of AIDA64 is a fixed file, with checksum, digital signature and all that buzz. You cannot load parts of it, but only the whole file. Which is only 30 KiloBytes, so not a big thing at all