Fiery

It means either the CPU made a calculation mistake, or the memory or cache subsystem failed to load a value from your memory. It's such an issue that is impossible to track down any further, since all we can see during the stress test workload is that the calculation didn't end up with the right result. In such cases it's usually due to excessive overclocking or improper (too strict) memory timings setting. Regards, Fiery

AIDA64 lets CPUs have a bit of "break" before it measures the CPU core clock. Hence when the CPU is idle, it should measure the lowest clock rate, the sleeping state. Other software may not let the CPU go to sleep before measuring the core clock, and so the CPU may be stuck at a higher clock rate due to previous tasks ran by the same software. Regards, Fiery

What version of AIDA64 are you using? I'm just asking because we've already fixed a similar issue about Surface Pro 4 and Surface Book in AIDA64 v5.60. Thanks, Fiery

Only the high-end Asus ROG motherboards suffer from such issues about EC bank switching. AFAIK Maximus VIII Gene, Hero, Hero Alpha, Impact, and Ranger boards do not use such mechanism. PCH Core and PCH Diode temperatures are both motherboard specific. Regards, Fiery

AFAIK VTT voltage is not monitored by Rampage V Edition 10. And the other 2 voltage readings would require using an Embedded Controller bank switching mechanism which would collide with AI Suite. And such a collision could cause system instability or system lockup. We've already notified Asus about this issue. Regards, Fiery

Please send me your AIDA64 product key in private message. Also send me your email address, so I can contact you directly. Thanks, Fiery

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, or attach the results as a TXT file to your post. You may need to enable status bar in AIDA64 / main menu / View first. Thanks, Fiery

Bar is already supported, albeit not with different coloured sections. We currently have no plans to expand gauges with new design options.

We've tried to replicate the issue using ForceWare 372.54, but it didn't come up on our test systems. Let me know if the issue still comes up with the latest ForceWare WHQL release of 372.70. Thanks, Fiery

No, we haven't implemented it yet, because it's not quite clear whether altering the RGB backlighting setting would write the onboard flash or not. Can you confirm it wouldn't update the flash?

1) We've checked and the Type option is still available for gauges displayed on Razer LCDs. 2) Due to the fundamental difference between the rendering engine used for RemoteSensor (and Logitech Arx), the classic gauge cannot be used for those special displays. Arc gauge is more flexible and requires less efforts on the user's part to have it customized. 3) We currently do not have a 3D game plugin that could be used to detect API/Renderer information, so such detail cannot be detected by AIDA64 at this time. Regards, Fiery

On Maximus VIII Extreme T_Sensor2 and T_Sensor3 temperature readings are only accessible via Embedded Controller bank switching. Which is a dangerous mechanism to use, since bank switching done by concurrent software (mainly AIDA64 and Asus AI Suite) could cause system lockup or stability issues. We've already notified Asus about this issue. Regards, Fiery

The only local change you may have to do -- depending on the network architecture -- is to make sure AIDA64 is auto-executed. The portable version can be used on any machine, without any sort of installation or pre-configuration procedure. There are no DLL, driver or runtime dependencies, so you don't need to install e.g. Visual C++ Redistributable Packages, .NET Framework or such.

Please read the setup guide that I've linked above

Only AIDA64 Business and AIDA64 Network Audit feature full command-line driven automation. You can read more about it in the following documents https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-manual.pdf https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf Regards, Fiery

Correct. Business edition is typically for a single company or organization, used to audit and monitor their full network of computers.

You need the Engineer edition for such purposes. A single Engineer license will entitle you to use AIDA64 on any client's computers for diagnostics or troubleshooting purposes. Your client however will not be able to keep using AIDA64 for his purposes. Yes, we do have a portable version for all AIDA64 editions. Regards, Fiery

1) Yes, it's possible. 2) It's possible to configure alarms (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting), but alarms are not reflected/shown on the SensorPanel itself. 3) No, AIDA64 doesn't support such things. 4) Most of them should be there. Just download AIDA64 v5.75 (trial version is fine), and check it out. 5) You can request a system shutdown (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Alerting) once an alert is fired. 6) AIDA64 doesn't support fan speed PWM (duty cycle) control. 7) AIDA64 implements a feature called External Applications that other software can use to display readings that are measured by AIDA64. The reverse is not supported by AIDA64, so AIDA64 is not capable of importing values from Aquaero. 8) Yes, you can do that using the external LCD module that you can configure in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD.

If you want to put maximum stress on your memory modules, then use the Memory Read benchmark instead of the RAM subtest of the System Stability Test.

Which AIDA64 benchmark method are you referring to? Memory Read? Thanks, Fiery

What kind of items do you miss from that list?

What kind of report and problems do you mean? Our app still has nothing to do with Bluetooth, so reporting a Bluetooth related issue or fixing any such issues is out of the scope of our app...

Yes, correct.

On Nehalem and later Intel processors, the TJMax value is SKU specific, and is encoded into a MSR (Model Specific Register). Hence it can be detected, and no need to use static presets or hard-encoded values. However, it also means that the TJMax value may vary between individual parts, so it's not guaranteed that e.g. your i7-6900K would use the same value as your friend's seemingly similar i7-6900K part. Regards, Fiery

Thank you! Can you please mention one or two of such memory intestive program?