Fiery

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.

Please upgrade to the latest beta version of AIDA64 Extreme available at: 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. If not, then 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.

Please upgrade to the latest beta version of AIDA64 Extreme available at: 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 makes a difference.

Thank you for the feedback

Thank you. It means your video adapter uses an UEFI BIOS, you use an UEFI boot, and the system BIOS/firmware doesn't emulate the classic video BIOS region (the C000 segment). In such cases AIDA64 will not be able to detect the video BIOS date using its classic method, so it will not show any video BIOS date on the Motherboard / BIOS and Computer / Overclock pages. Then you will have to go to the Display / GPU page to check the video BIOS date for your video card(s).

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

Please right-click on the Overclock page in the left page menu --> Quick Report --> Plain text. Scroll down to the end of the report, and copy-paste the section called "Debug - Video BIOS" into this topic. DMI means motherboard model is extracted from the DMI block. You can see the full DMI information on the Computer / DMI page.

It's quite odd. Please let us know more about your system configuration: 1) Windows version, 32-bit or 64-bit? 2) Motherboard and CPU model? 3) Video card(s) model? 4) Any external (USB, FireWire or eSATA) storage devices connected? We'll try to reproduce the issue on a similar system in our labs.

The card reader issue may be caused by a firmware glitch in your card reader. You can try disabling the two RAID-related options in AIDA64 / main menu / File / Preferences / Stability, that should fix that issue. Make sure to restart Windows after altering that option.

You need to disable ULPS to make AIDA64 recognize and handle both your GPUs properly. You can disable ULPS by scanning the Registry (using e.g. REGEDIT.EXE) for all occurences of EnableUlps, and set all values of that to zero (0). Please note that you need to restart Windows after disabling ULPS, and you need to do that procedure after every Catalyst upgrades.

The values are shown and configured in milliseconds since AIDA64 v4.20. One second equals to 1000 milliseconds. Regards, Fiery

Shifting only one pixel would make the graph look quite odd. We've done test runs with it, and the best visual feedback is by using 2-pixel step rate.

Have you tried to run AIDA64 v4.20 after a Windows reboot?