Fiery

Thank you for the feedback!

They should be reported. Can you see detailed SMART attributes info for your 850 Evo drive on the Storage / SMART page in AIDA64? Thanks, Fiery

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

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

Please upgrade to the latest beta version of AIDA64 Extreme available at: https://www.aida64.com/downloads/latesta64xebeta After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

When it comes to a network of 100 computers, and you want to create a report of every computer (in order to compile a network inventory or audit), AIDA64 Network Audit and AIDA64 Business are the product editions to use. AIDA64 Engineer is geared towards troubleshooting and benchmarking, and even though you can create reports using command-line with it too, such reports (TXT, HTML and MHTML) are not for network auditing purposes.

Yes, AIDA64.INI contains the settings for Sensor Icons, OSD Panel and SensorPanel as well. Regards, Fiery

Yes, you can do that with AIDA64 Business. You can learn more about how to set AIDA64 Business up in a network in the following guide: https://www.aida64.co.uk/sites/default/files/public/download/documents/en/aida64business-setupguide.pdf

Thank you. We've double-checked, and it should be correct with the latest beta update. It's quite puzzling. Can you please do the following: 1) Create an ISA Sensor Dump and an Embedded Controller Dump 2) Install Asus' own software (AI Suite) 3) Create a new ISA Sensor Dump and Embedded Controller Dump 4) Compare the values in AI Suite and AIDA64 Sensor page, especially the temperatures, and make a screen shot that shows the values side-by-side Thanks, Fiery

Thank you for letting us know about the resolution

I'm afraid I don't know the answers. Some bits and pieces of Windows are quite mysterious, even to us If you're unsure about the translation, then either leave the terms in English, or translate them directly, word by word.

Automatic report creation is only supported by AIDA64 Business. Regards, Fiery

"PCH" and "PCH Diode" are the temperatures of the onboard Intel chipset (PCH), while "Motherboard" is the temperature of the sensor chip. Both the sensor chip and the PCH are integrated on the motherboard PCB, but they're usually far from each other. And while the relatively simple sensor chip always runs quite cool, the very complex PCH could heat up quite heavily when there's a lot of data traffic flowing through it. Regards, Fiery

"CPU" temperature is measured by the onboard sensor chip (onboard = integrated on the motherboard PCB), while the core temperatures are measured by the CPU itself. Under heavy load both temperatures should be reliable, but at idle many modern AMD processors measure unrealistically low core temperatures (e.g. 0 or 5 Celsius with an ambient temperature of over 20 Celsius). As long as all CPU or CPU related temperatures are below 80 Celsius, you're fine.

Thank you for posting that package! Regards, Fiery

I don't think we'd ever had 5VSB reading available for Asus Z87-Pro A different motherboard you used to have may have had that reading, but it's not available on just any motherboard out there, but only on some.

If it's possible, please send us two ISA Sensor Dumps and two Embedded Controller Dumps. One pair of the dumps where the CPU, VRM and PCH (so generally the system) is cool, and one when it's hot (or less cool), so we can compare the various temperature readouts and figure out what could go wrong. If it's possible, please also check whether the problemous thermal readings are stuck in the BIOS Setup too.

What's wrong about them? They aren't reported at all? Are they inaccurate? Are they showing the temperature of each other, so they're swapped? Or ... ?

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

We will add the requested information to the Motherboard / BIOS page in the next AIDA64 beta update. Regards, Fiery

Thank you, we will fix that issue in the next AIDA64 beta update. Regards, Fiery

We will fix that issue in the next AIDA64 beta update The secondary IMC is because all Ivy Bridge-E/EP, Haswell-E/EP and Broadwell-E/EP processors include two memory controllers, but in many cases only one of them is utilized. Regards, Fiery

Font Resolution is LOGPIXELSY from: https://msdn.microsoft.com/en-us/library/windows/desktop/dd144877(v=vs.85).aspx Pixel Width is ASPECTX from the same call. Pixel Height is ASPECTY, and Pixel Diagonal is ASPECTXY. Regards, Fiery

Under modern Windows systems it could be quite a challenge to pick the actual primary network adapter. AIDA64 relies on Winsock to pick the primary network adapter, and then it will report its IP address. If it's not the IP address you're looking for, then I'm afraid it's not the fault of AIDA64. You can see all network adapters and their IP addresses (+ MAC addresses) on the Network / Windows Network page. Regards, Fiery

"Motherboard" and "CPU" temperatures are both read from the sensor chip that's integrated on your motherboard, while the core temperatures (that CoreTemp as well as AIDA64 measures) are read directly from the CPU. Reading CPU temperature from the motherboard sensor chip however requires sensor chip bank switching which could collide with other monitoring software also doing the same bank switching. So for example, if you have both CAM and AIDA64 running in the background, when they both try to switch sensor chip bank in the same time, one of the reported values (either the one in CAM or the one in AIDA64) will end up in an unpredictable result. In your case I suspect CAM collides with AIDA64. We've already contacted NZXT to convince them to implement the industry standard synchronization mutexes in CAM, in order to avoid such collisions, but we've received no response from them so far. If you can narrow this issue down, and verify my theory on CAM vs. AIDA64 collision, then you as an end-user (and customer) of a NZXT product may also contact NZXT and ask them to team up with us to resolve this issue. We're 100% open and willing to resolve this, but we need NZXT's assistance too. BTW, the mentioned synchronization mutexes are already implemented by a wide range of 3rd party monitoring, tweaking and benchmarking software, including AIDA64, AMD OverDrive, CoreTemp, CPU-Z, EVGA E-LEET, GPU-Z, HWiNFO, HWMonitor, MSI Afterburner, RealTemp, Rivatuner, SIV, SpeedFan, etc.