Fiery

Yes, because AfterBurner sets the other fan controller's duty cycle

1) Are you using the Larne-ML platform or the Discovery-ML platform? 2) Have you tried it with the latest AIDA64 beta as well? AIDA64 Extreme: http://www.aida64.com/downloads/aida64extremebuild2820nk4ztxrp6fzip AIDA64 Engineer: http://www.aida64.com/downloads/aida64engineerbuild2820j1zdvnkblhzip

Thank you for the data. I suppose the confusion comes from the fact that your GPU has an on-die integrated fan controlling logic that is currently not utilized, but set to 100% duty cycle; whereas your video card also has a sensor chip (ADT7473) that also has a fan controlling logic that is utilized and is set to 92%. On the Sensor page AIDA64 shows the more relevant information, the duty cycle for the on-board ADT7473 sensor chip. Regards, Fiery

Please let me know what motherboard and CPU do you have in your computer. Thanks, Fiery

We've done quite a few changes to threading features of AIDA64, so please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2820nk4ztxrp6fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

I suppose it's more than a coincidence that both of you have a Logitech G1x keyboard, and the issue happened cca. 10 hours after starting AIDA64. Please let me know what update rate do you have configured for your LCD (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD). Thanks, Fiery

Even if you disable System Restore for all logical drives, Windows 7 will still report System Restore as active. It is a limitation of Windows I'm afraid cannot be fixed from AIDA64. Regards, Fiery

It's 0% because the video BIOS configures the fan duty cycle register accordingly. Smart solutions configure it to 0% to indicate a stopped or non-existent fan; while less smarter video BIOSes just leave it at 30% or 40% or so, not caring for it too much, since there's no fan installed.

On fanless video cards you can simply ignore the fan duty cycle value. It may show 0% or a non-zero percentage, but it doesn't make any difference. Regards, Fiery

Thank you for the feedback. The sensor module was disabled under VMware, because some of the motherboard sensor modules caused slowdowns and lockups under VMware. We simply disabled the whole sensor module, which caused the GPU sensor features to get disabled as well. So far it didn't cause any issues for our users, but your special usage scenario called for a re-enablement of the non-motherboard sensor features As for 3rd party apps, currently only Fraps is supported. You can however export the values measured by AIDA64 to get processed by other applications (AIDA64 / main menu / File / Preferences / Hardware Monitoring / External Applications).

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2820nk4ztxrp6fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. If not, then try to update your touchpad drivers to the latest release as well. If that still doesn't solve it, then please let me know what sort of touchpad does your notebook have. Thanks, Fiery

Thank you for the data. Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2820nk4ztxrp6fzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.

Please send us 3 register dumps to let us understand the virtualized hardware configuration, as AIDA64 sees it: 1) Right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. 3) Then right-click on the bottom status bar of AIDA64 main window --> System Debug --> PCI Dump. Copy-paste the full results into this topic. Thanks, Fiery

It's absolutely normal. It's because the onboard sensor/PWM chip is connected to the I2C bus of GPU2, and not GPU1. It's just a technical decision made by the video card manufacturer. The chip itself may measure the properties and status of GPU2, GPU1 or the whole video board, it all depends on how the manufacturer designed the PCB of your video card. Regards, Fiery

I'm sorry, but your memory modules do not seem to have a DIMM TS module integrated. Regards, Fiery

1) Do you have Asus AI Suite installed? 2) Do you have the Asus ATKEX sensor support option on the AIDA64 / main menu / File / Preferences / Stability page enabled (checked) or disabled? 3) What version & build of AIDA64 are you using? Thanks, Fiery

First of all, please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild2815jtcqw4m3dzzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If the problem persists, then do the following: 1) Please right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

Maybe the Access violation message comes up on your systems when your computers go to sleep? Can you please try to initiate a manual sleep, and see if the error comes up? Thanks, Fiery

I'm afraid we ran out of ideas, and none of our efforts to try reproducing the issue had any useful results. One thing you can try though is right-clicking on the bottom status bar of AIDA64 main window --> HWMon Modules, and disable all of the modules there. If it fixes it up, then try to enable them again, one by one, and try to find which one causes the issues.

Fraps is still supported.

You can enable logging to a .ADO file (which is a plain text output file) if you alter your command-line like this: \\IP\Aida\aida64.exe /r \\IP\AidaReports\$HOSTNAME /database /sum Of course you need to create a new network share (\\IP\AidaReports), and provide your network users write-only access to the folder. BTW, do you have MySQL Connector/ODBC installed on your client stations?

Thank you, your monitor will be added to the next AIDA64 beta release due next week. Regards, Fiery

Thank you for the feedback

1) Do you have Asus AI Suite installed? If yes, then did you rename any of the fans in AI Suite? 2) Do you have the option Asus ATKEX sensor support enabled in AIDA64 / main menu / File / Preferences / Stability?

Please try to upgrade to the latest AIDA64 Extreme beta release: http://www.aida64.com/downloads/aida64extremebuild2808b9s8mvtkpqzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps.