Fiery

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

Yes, of course such a reverse gauge would be more suited for the drive space items, but we currently have no such gauge designs in AIDA64. We may add such gauge variants soon

1) Does the Database Manager feature of AIDA64 Business Edition work properly on your system or not? 2) What version of MySQL Server do you have installed on your database server? 3) What version of MySQL Connector/ODBC do you have installed on your client computer? 4) What sort of Windows do you have installed on your client computer? Windows 7 SP1? 32-bit or 64-bit kernel? 5) What version/build of AIDA64 Business Edition do you use? Thanks, Fiery

It's not possible to detect that, since every applications (every threads actually) could have a different active keyboard layout. We could detect the active keyboard layout for AIDA64, but it wouldn't be relevant at all for other running applications Regards, Fiery

Thank you for both the XLS and the forum post. We would prefer to wait until you can get confirmation on your chart on the Khronos forum, because non-definitive values and question marks should not be provided in a compliancy test in AIDA64

When you say "VP8: badly failed", what exactly does happen on your system? Do you get a BSoD while running the VP8 benchmark? Or you get very low scores for VP8? (how low? what exact scores do you get?)

AIDA64 loads a bit slow at Windows startup due to its dynamically loaded kernel driver. I'm afraid we cannot fix that, since it's not AIDA64 that gets slow, but Windows itself gets sluggish while loading the dynamic kernel driver of AIDA64. Regards, Fiery

Thank you for the feedback. We have disabled Dell SMI sensor support on Alienware M17xR4 systems.

AIDA64 uses fairly regular Dell SMI calls to measure fan speed and temperature readings on Dell and newer Alienware systems. If you suspect AIDA64 may stop your system from utilizing its fan control logic properly, then please try to disable Dell SMI sensor support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. If that solves the issue, then we will completely disable Dell SMI calls on Alienware M17xR4 systems. So please let us know how your tests go on the replacement system. Thanks, Fiery PS: I'm not sure if Dell SMI calls are the actual problem, since we've only activated them on M17xR4 at AIDA64 Beta Build 2105. So both AIDA64 v2.20.1800 and v2.30.1900 should have the Dell SMI calls not utilized on M17xR4, and so there should be no difference in their behavior...

Thanks Sensor readings will be fixed in the next AIDA64 beta release.

Thank you. I'm sorry to bug you more with dumps, but it seems this board has 2 different sensor chips, 1 more than what we've expected So please also submit a SMBus Dump (Full) dump.