Fiery

Thank you for the data. Your motherboard uses the usual ASRock fan mux logic, so only one of the CPU fans can be monitored by AIDA64. If you connect the fan to the other CPU fan connector, AIDA64 will show the RPM for it. As for core temperatures and GPU diode temperature, they are quite low, and it is due to the common hardware issue of modern AMD processors (e.g. FX, Llano, Trinity, Richland). They measure unrealistically low temperatures at idle, but the measurements get much closer to real when the system is under heavy load. Unfortunately this is a hardware issue that cannot be fixed from software. Regards, Fiery

What is the exact command-line you entered into the "Run program" field?

What GPU-Z does it quite dangerous, ie. to poll both GPUs when ULPS is active. AIDA64 tries to stay on the safe side. Catalyst is quite different, since it can do things internally (between Catalyst Control Center and the video driver) that other software can't. No, it's a completely different technology. ULPS is developed by AMD, while PCI Express link state power savings is a generic technology developed by PCI-SIG, the group behind the PCI and PCI Express specifications.

Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction. Push the New button (below), select CPU #1 / Core #1 in the list, and enter a value (e.g. 30) in the Offset field to apply a positive offset value on the temperature readout. Then press OK and OK again to save your settings.

Your system seems to have ULPS feature of Catalyst drivers enabled. When ULPS is active, polling non-primary GPUs may cause a system lockup or BSoD. Hence AIDA64 cannot show GPU details when ULPS is active. You can disable ULPS by setting all occurences of EnableUlps to 0 (zero) in the Registry, and restart Windows. Please keep in mind that you need to do that again everytime after updating Catalyst. Regards, Fiery

In the BIOS Setup processors cannot use their power-saving features (like Cool'n'Quiet, C1E, SpeedStep), so in there the CPU temperature readings will always be higher than under Windows.

I'm afraid that may be due to the improperly implemented temperature diode logic of Llano, Trinity, Richland, Zambezi, Vishera processors Such issue can only be fixed by applying an offset on the temperature readings in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction.

Thank you. We've been able to make our box work on a USB 3.0 port with a NEC uPD720200 controller. However, through the course of a 3-day test run we haven't been able to reproduce the disconnection issue We've tried it with driver version 2.1.39.0 and also with an old version 2.0.20.0. However, when we've tried to connect the box manually to the USB 3.0 port, the box worked roughly once out of 5 tries, so 4 times the board didn't even sense a connection, and so Windows didn't find any devices connected and failed to mount the HDD in the box. On the rare occasion of a successful manual connection, the box worked just fine until we unmounted it via the System Tray icon. We prefer not to point fingers on hardware, but on this particular issue we strongly believe the VIA VL700 controller is the one to blame, since with an Etron USB 3.0 controller chip it fails to connect everytime, and with our NEC USB 3.0 controller chip it fails to connect a lot of times. While on USB 2.0 ports it works just fine everytime. BTW, we have a few USB 3.0 boxes, converters and flash drives around with various controller chips, but we've only found issues with the VIA VL700 controller based box of ours.

Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2406twdq1v8hcszip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. It would also be a huge help for us if you could create an ISA Sensor Dump using this beta release, and copy-paste the results into this topic. You can create such dump by right-clicking on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump.

For MySQL you need to select the MySQL ODBC driver in the Driver drop-down list, enter your Database name, enter your Server address (hostname or IP address), and enter your credentials (User + Password). If you fill in all those fields, you can leave the Data source field empty. Regards, Fiery

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

Thank you. It's definitely not C1 stepping, but C2, so AIDA64 is correct. C1 in the BIOS Setup may refer to the X79 PCH stepping.

It may use a correction value (offset) on the raw temperature readout to make it look more real. You can apply such offset on the temperature values with AIDA64 as well, if you go to main menu / File / Preferences / Hardware Monitoring / Correction.

Modern AMD processors (including FX Series, Trinity, Richland) implement such a temperature diode that only provides meaningful values when the system is under heavy load. This is a hardware limitation, and not the fault of AIDA64. Regards, Fiery

Please let us know what the 3rd line on the Motherboard / CPUID page of AIDA64 says about the CPUID revision of your processor. Thanks, Fiery

I'm sorry for the misunderstanding. What you're looking for is AFAIK cannot be detected under Windows.

The current SATA revision used by your HDD/SSD drives is displayed on the Storage / ATA page of AIDA64. Regards, Fiery

With both benchmarks it is very crucial that you have proper memory bandwidth. With single-channel memory your scores will be much lower than the reference systems. Single-channel memory is a huge bottleneck in your system, so make sure to install at least 2 identical memory modules to activate dual-channel operation. Regards, Fiery

Alternating values for the same reading is not really the best idea, since that would make it tough to configure an item on the OSD Panel, Logitech LCD or SensorPanel.

Yes, that's grammatically true. However, AIDA64 uses a fixed label, so based on the current battery status (discharging / charging / neutral) it's not possible to change the sensor reading label. Instead, AIDA64 uses a negative value to indicate discharging, a positive value to indicate charging, and zero value to indicate the neutral state. It's not a perfect solution, but it works Regards, Fiery

AIDA64 detects Windows Firewall status via a standard Microsoft API call: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365287(v=vs.85).aspx In case the API reports the firewall is disabled when it isn't, then it seems to be a bug of Windows rather than an AIDA64 bug... Although, quite frankly we've never heard of this API failing on any systems. Regards, Fiery

Thank you, the bug will be fixed in the next AIDA64 beta release. I'll post a message into this topic once the new beta is available for download. Regards, Fiery

That could happen when AIDA64 cannot load its resources from AIDA_CPUID.DLL because the file is missing or corrupted. You need to reinstall AIDA64 from the authentic download package: http://www.aida64.com/downloads/aida64extreme270exe Regards, Fiery

Thank you for the feedback

Thank you. I've just sent you a private message about this issue.