Fiery

1) Core temperatures are measured by the CPU itself, using Intel DTS. "CPU" temperature is measured by the motherboard, using the sensor chip mounted on your motherboard. Due to the fundamental difference on measuring methodology, it's not advised to compare core temperatures and "CPU" temperature. 2) As for the fan RPMs, please copy-paste the results of the following dumps and info into this topic: - Computer / Sensor page - right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> ISA Sensor Dump Thanks, Fiery

We've done several test runs on various Intel chipset based configurations, but couldn't reproduce this issue. We suspect it may be the fault of the SATA driver, since AIDA64 uses industry standard driver calls to collect disk temperature readouts. Have you tried to update the Intel SATA drivers? Have you seen the same issue with other tools like HD Sentinel or HWMonitor?

What version of Logitech drivers do you have installed?

Please compare the measured values against Asus' own hardware monitoring software called PC Probe II. If you can see any discrepancies there, please let me know. Thanks, Fiery

It will be implemented in the very next beta release of AIDA64. I'll post it into this topic, so you can give it a try

One of the differences between AIDA64 and the last release of EVEREST is that AIDA64 supports a lot of new hardware (e.g. Sandy Bridge processors, SSD drives, Radeon HD 6000 family, GeForce GTX 500 family, etc) that EVEREST doesn't. And that effectively means that -- unlike EVEREST -- AIDA64 is able to monitor those new hardware, hence it reads more information from new hardware.

We've never had such issues on our G15 and G19 keyboards. Can you please let us know which keyboard do you have, and what version of Logitech drivers do you have installed? BTW, have you tried to alter the option "Allow Program to Force Itself to Foreground on Display" in Logitech LCD Manager? That may be a solution for your issue. Thanks, Fiery

That's a good point. Fads, please try to switch the option "nVIDIA GPU SMBus access through ForceWare" option in AIDA64 / main menu / File / Preferences / Stability. That may bring back the missing sensor readings. Make sure to restart AIDA64 after altering that option.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. 3) Finally, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

As far as we know, APIC ID is assigned by the BIOS, so when the order is unusual or unexpected (even by Windows), it is the fault of the BIOS. If you want that to be fixed, then I suppose the only one to contact is the motherboard manufacturer. APIC ID is used by modern multi-processor kernels to identify the CPU cores and the CPU packages. In various situations a software (or the operating system itself) has to know which logical processor belongs to which CPU package, or which CPU core. I'm not sure why you brought that up. Thermal protection is managed by the processor itself, and it's a completely automatic process. Once a core is overheating, the CPU will immediately start throttling the affected core down. If it still doesn't help to lower the temperature of the affected core, the whole CPU package will shut down. Hence there's no real need to know which core is at fault, and no need to shut down the system manually at all. The whole APIC ID assignment business is managed by the BIOS, and interpreted by the operating system, and the APIC ID is not checked or verified or read by the CPU itself. Especially not when it comes to thermal protection mechanism The CPU itself knows which of its cores are which, and you don't need to know which is which. BTW, when a core is overheating inside a CPU package, it always affects the rest of the cores, especially for monolithic multi-core processors. Hence when core#0 overheats, it will also affect (heat up) every other cores in the same package.

Thank you. Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

1) Do you have any RAID arrays defined? 2) Do you have any external USB, eSATA or FireWire disk drives connected? 3) Have you tried disabling the SMART layer in Preferences / Stability? Thanks, Fiery

Thank you. Unfortunately for Asus P67 boards the sensor registers are inaccessible using standard methods, so we cannot use those dumps

1) All editions of AIDA64 can be used directly from an USB flash drive, without the need for an installation procedure 2) Only AIDA64 Business Edition supports processable report formats (CSV, XML). You can contact ABSEIRA (the distributor of AIDA64 Business Edition products) and request a price quote at: http://www.abseira.com/aida64-business-price-quote Regards, Fiery

Yes, the Aux reading was related to a not-connected sensor pin, so we've removed it. We've also recalibrated the voltage readings

I'm afraid AIDA64 cannot measure FPS. Regards, Fiery

Thank you, and Happy New Year! Please give us a couple of days, because Asus completely revamped the sensor solution on their new P67 boards, so we'll need to do a lot of testing and research to find out how to calibrate the sensor readings.

1) Please copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. 2) Then right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA GPU Registers. Copy-paste the full results into this topic. 3) Finally, right-click on the bottom status bar of AIDA64 main window --> Video Debug --> nVIDIA SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

I think there may be an issue due to mixed up APIC ID due to a BIOS bug. However, since even Windows logical processor handling doesn't take that into account, I don't think we'd implement a workaround for that issue. As for the core temperatures accuracy, it's yet again the old arguments over Intel's DTS implementation. Intel designed DTS not for core temperatures measurement, but to fight overheating, and to protect the processor from physical damage due thermal issues. Intel defined a TJMax value for each processor part. TJMax means the temperature (in degrees Celsius) threshold for the CPU package. Once the processor gets close to TJMax, it starts throttling itself down. The major issue with DTS is: due to it was designed for accurate temperature measurement only around TJMax, the more far you get from TJMax the more inaccurate the calculated core temperatures get. Around 40-50 Celsius running temperature the DTS accuracy is no better than +/- 10 Celsius, while around 20 Celsius the accuracy could be +/- 20 Celsius (!) DTS then completely stops working and reports invalid values around zero Celsius. It's simply not a feature designed and implemented for temperature measurement, and it's certainly not designed to measure "normal" temperatures, like 40-50 Celsius. So even if you put the core temperatures in "proper" order, it wouldn't make the temperature values accurate

Thank you for the feedback

As far as we know, it's the fault of the SSD firmware. You can check if other software (e.g. HD Sentinel, HWMonitor) can read it, but I'm pretty sure they will also measure the same 1 Celsius temperature

Most notebooks are not equipped with a full-blown sensor chip like desktop motherboards, hence measuring voltages and fan speeds (RPM) are not possible on most notebooks. This is a lack of hardware implementation, and not a software deficiency. I hope you find other useful features in AIDA64 that would justify the purchase Regards, Fiery

I'm afraid you have to ask the author of the gadget to adjust it to work with AIDA64. It's a very quick job as long as you are the author of the gadget.

In case you want to compile a network audit, track hardware and software changes on your whole network, monitor your networked computers remotely, remote control one or more of the networked computers, then you need the AIDA64 Business Edition product. In that case, you're gonna need 500 licenses of AIDA64 Business Edition. In case you don't need to compile network audits or manage & monitor your computers remotely, but you simply need a utility that you can use for local troubleshooting and diagnostics, then you need the AIDA64 Extreme Engineer product. The licensing on that product dictates that you need one license for each your engineers who would use the product in your company. In other words, you don't need to buy 500 licenses, but only 1 or 2 or 3 (etc) licenses, depending on you have 1, 2 or 3 (etc) colleagues who would use AIDA64 Extreme Engineer in their everyday job. Either product you're interested in, you can get a price quote at ABSEIRA, the official distributor of AIDA64 corporate products at: http://www.abseira.com/aida64-business-price-quote Regards, Fiery

You can backup and restore the AIDA64.INI file for that purpose. It holds all the Preferences settings, and it includes no personal data or other sensitive info. Regards, Fiery