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 AIDA64 beta is available for download.

Please also post a CPUID & MSR Dump. Right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Thanks, Fiery

Can you please post a full Scythe part number for your card reader? We'll try to purchase one to perform test runs in our labs.

Are you sure you have driver version 3.3.107 installed? That looks like a very old release, since the latest Logitech LCD drivers is v8.45.88: http://www.logitech.com/en-us/support/g19-keyboard-for-gaming?crid=404&osid=14&bit=64

Thank you for the feedback

Thank you for the test runs. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2419txgzqv3nwhzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

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

I'm afraid that may happen in such cases when the UEFI BIOS refuses to emulate the classic system BIOS region with valid data. The System BIOS Date field shows that the system BIOS is invalid. We haven't yet found a proper workaround to fix such issues

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2412dt8hwjrp4mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. If it still doesn't work as expected, then please try to disable SMBus access in AIDA64 / main menu / File / Preferences / Stability, and let us know if it makes a difference. After altering the SMBus option, make sure to restart Windows. Thanks, Fiery

It's not useless at all. You just have to keep in mind that "43C" means "under 44C"

It sounds a lot like a PSU (Power Supply Unit) failure to me. If it's possible, try to get a new PSU. Borrow it from a friend to make sure you don't spend too much on this issue if the PSU is not at fault afterall. If the PSU is fine, then my second guess would be the motherboard: one of the capacitors may have given in. But, before you start dealing with hardware issues, make sure to update the motherboard to the latest BIOS version, restore your settings to factory defaults (make sure your system is not overclocked), apply all Windows updates/hotfixes, and update your video driver to the latest version. Regards, Fiery

It looks quite true

Thank you for the feedback. We'll keep on working more on the Apple SMC module throghout April, and we'll add even more readings if possible.

We've added EU count and Intel GPU generation information to the Display / GPU page. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2412dt8hwjrp4mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

We've further improved on the Apple SMC sensor support. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2412dt8hwjrp4mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

Thank you, we've fixed that up as well Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2412dt8hwjrp4mzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

As for command-line, while doing our test runs we used the following one: "F:\tweak\nVIDIA Inspector 1.9.7.0 Beta\nvidiaInspector.exe" -setMemoryClock:0,2,444 -setShaderClock:0,2,1222 It worked flawlessly for us, so I'm sure that the command-line handling of AIDA64 Alerting facilty works fine. --- "Number of ours between sending repetitive alerts" means after firing an alert, how much time AIDA64 should wait before firing another alert for the same condition. "Update Frequency/Alerting" means the polling frequency of the alerting items, to check whether they are inside or outside the configured limits.

We've tested it with an Asus GeForce GT 520 (GF108-based) card, and memory clock can be adjusted via a similar command-line using AIDA64 Alerting facility, so the command-line handling definitely works fine in AIDA64. Setting GPU clock from command-line doesn't work though, but it also doesn't work from the GUI of nVIDIA Inspector. I suppose it's due to the fact that GPU and shader clocks are linked together, so you need to adjust shader clock instead of GPU clock, and GPU clock will follow the change as 50% of shader clock.

Try to change it to: "C:\Program Files (x86)\NVIDIA Inspector\nvidiaInspector.exe" -setGpuClock:0,0,620

If the default core temperature values are always zero, then it may be due to the ACC (Advanced Clock Calibration) feature of AMD processors. When you activate ACC in the BIOS Setup, then core temperature measurement will be impossible by any software. They will always appear as zero Celsius.

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