Fiery

It's normal, since integrated video on the AIDA64 CPUID Panel refers to a chipset-integrated or CPU-integrated video controller. Your Volari is integrated on the motherboard, and it works independently from the motherboard chipset and the CPU. Regards, Fiery

Make sure to configure a different port for each remote feature of AIDA64. You cannot use the same port on all features.

Different WAN address is not a problem, it should work fine in your scenario as long as the port forwarding is properly configured, and the remote computer has its firewall port open.

We'll disable detecting the rest of the SMBus sensors on the AMD Discovery platform. Maybe that will help you to let you re-enable the SMBus stability option.

Please verify if both the local computer and the remote computer has the same TCP/IP port configured for remote control in AIDA64 Preferences. Also verify that the remote computer has accepting incoming connections enabled via e.g. /ACCEPT or /ACCEPTBG command-line option, or via AIDA64 / main menu / Remote / Accept Incoming Remote Connections. Regards, Fiery

Thank you, the +12V reading will be fixed in the next AIDA64 beta release due next week.

Thank you

Then please try to disable the following options in AIDA64 / main menu / File / Preferences / Stability: Apple SMC sensor support Asus ATKEX sensor support Dell SMI sensor support HID UPS sensor support Koolance TMS-200 sensor support T-Balancer sensor support DIMM thermal sensor support Toshiba TVALZ sensor support Please let me know if it helps.

We have currently no plans about any kind of video benchmarks. Regards, Fiery

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

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

Thank you, we've added the 2 mentioned lines to the AIDA64 language modules. Regards, Fiery

It all depends on the logical processor ordering of your operating system. On Vista and later Windowses ordering goes as: Core #1 / HTT Unit #1 Core #1 / HTT Unit #2 Core #2 / HTT Unit #1 Core #2 / HTT Unit #2 ... etc. So to select Core #1 and Core #4, you would have to use a binary bit mask of 01000001 which is hex 41. Regards, Fiery

No problem about the time. We definitely want to find this issue and implement a fix or a workaround to get around it. I've just sent you a private message about this.

Please let me know the English name of the page at step 7. Is it the Sensor page or the Portable Computer page? I understand that your system is based on the AMD Beema processor, but I wonder which platform (which motherboard) is that. I suppose it is the AMD Discovery-ML motherboard. Can you please confirm that? Also, if it's possible, 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.

Thank you The strange thing is that the issue seems to be coming up when doing plain & simple string operations while scanning for Windows Devices. We suspect the issue could be caused by a driver of an installed device in your system that returns a scrambled text that causes the string operations to go south. If you have a bit more patience about this issue, I can send you a special beta build of AIDA64 that would output a lot more debug information, so we could dig down deeper and hopefully find out which device causes the issues, and which device information string has the improper content that makes the string operations go wrong. BTW, the actual device that is behind these issues must be a rare one, since we haven't got similar bug reports from other users. Do you happen to have a very unique, very rare device in your system? Either a PCI/PCIe card, a USB or eSATA device?

We currently have no plans about adding DXVA detection to AIDA64. Regards, 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.