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

We've just released the first 2011 beta: http://www.aida64.com/downloads/aida64extremebuild1212psk4n0yrvxzip As for the next stable release, it depends on how we progress with the new features we'd like to see implemented. E.g. GPGPU benchmarks, GPGPU stress test, new hardware monitoring features, revamped benchmarks, etc. We plan to do a release in Q1'11, but only time will tell if it will become v2.00 or v1.70 or v1.55

Thank you, we've added your monitor to the AIDA64 monitor database. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1212psk4n0yrvxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Regards, Fiery

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

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

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

Everest and AIDA64 share the same CSV log format, so the PHP script should still work with AIDA64 CSV logs.

Thanks for the feedback. The explained issue was in fact fixed right before the release of AIDA64 v1.50 Happy New Year!

A computer restart while running the System Stability Test could happen due to overheating, or because of motherboard failure, system memory failure or power supply failure.

Thank you for performing the test. I suppose Intel Rapid Storage drivers will need to get a few iterations to mature, since other users also reported issues like you did, and it also seems to be a fault of the Intel RAID drivers We've been told that Intel is already working on RST v11, so let's hope they can finish it up in a few weeks.

In case the latency spikes are approx. 20 seconds away from each other -- as it seems --, then I suppose it's caused by the SMART detection layer of AIDA64, which is used to measure HDD/SSD temperature. AIDA64 now uses a special driver call to pass through the Intel Rapid Storage RAID drivers, in order to reach the RAID member drives. I guess Intel drivers will need some more iterations to mature

Yes, I know But it would be necessary to verify if the SMART module of AIDA64 is really the cause of the CPU hogging.

It's rather weird, since nothing has been changed about the Intel RAID handling between AIDA64 v1.20 and AIDA64 v1.50. Please try to disable SMART handling in AIDA64 v1.50 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps to avoid the CPU hogging issue. BTW, what motherboard do you have, and what Windows version are you running? Thanks, Fiery

You can verify the video driver status on the Display / Windows Video page in AIDA64. You may need to revert back to the previous Catalyst driver in case that proved to work better with your video adapter. Regards, Fiery

Please let us know more about your system configuration: 1) Motherboard model 2) CPU type 3) Video card (or cards) model 4) Number of internal or external hard disk drives or SSD 5) Any special sensor devices connected 6) Windows variant, kernel type (32-bit or 64-bit) Thanks, Fiery