Fiery

Does your Windows user have administrator privileges? AIDA64 needs to be launched with maximum privileges to let it use its low-level kernel driver. Also, you seem to be using an older release. Make sure to update to AIDA64 v2.60 Regards, Fiery

We've implemented an improved method for AMD AHCI & RAID controllers in the new AIDA64 v2.60 stable release: http://www.aida64.com/downloads/a64xe I hope it will now produce similar output than other software. Please note that due to AMD RAID driver limitations, it won't be perfect with RAID arrays (only the first member can be detected).

Thank you for the info. The current solution in AIDA64 v2.60 uses separate code path when AI Suite is installed and when it is not installed. In both cases AIDA64 is now able to read all temperature, fan speed and voltage values. So if you don't need AI Suite, then make sure to uninstall it. AIDA64 will then be able to utilize its low-level functions about Rampage IV, and there should be no thread creation issues. We'll also try to find out why the thread creation problem comes up when AI Suite is installed. BTW, please note that even if you close AI Suite application, its low-level service still continues to be running. So to avoid any potential conflicts between AIDA64 and AI Suite, you need to completely uninstall AI Suite. Regards, Fiery

The latest AIDA64 update extends the SensorPanel module with graphs and gauges, adds a new Speech API information page, and implements full support for the complete nVIDIA GeForce 600 GPU family and the latest generation Intel and OCZ SSD drives. New features & improvements - VIA VX11 platform, Nano X2 and QuadCore CPU support - Optimized 64-bit benchmarks for AMD A-Series "Trinity" APU - Microsoft Windows 8 RTM and Windows Server 2012 RTM support - OpenGL 4.3, APP SDK 2.7, CUDA 5.0 support - GPU details for nVIDIA GeForce GTX 650, 660 Series What's new since AIDA64 v2.00 - OpenCL GPGPU Stress Test - Enhanced UPS support - SensorPanel graphs and gauges - Revamped Desktop Gadget - Support for Intel Atom "Cedarview" processors - Support for Intel Core "Ivy Bridge" APUs and Intel 7-Series chipsets - Preliminary support for Intel "Haswell" APU and Intel "Lynx Point" PCH - Preliminary support for Intel "Penwell" SoC - Speech API information - ACPI 5.0 and OpenCL 1.2 support - Intel 330, Intel, 520, Intel 710, OCZ Vertex 4, Samsung 830 SSD support - GPU details for AMD Radeon HD 7000, nVIDIA GeForce 600 Series [ Press Release ] [ What's new in AIDA64 v2.60 ] [ Download ]

Yes, I know, and I was referring to such thing as unfortunately not being implemented in AIDA64

I'm afraid an automatic comparation facility (that doesn't require visual inspection from the sysadmin) is not supported by AIDA64

Yes, AIDA64 Business Edition does implement a feature that should be able to help you. You need to create a few CSV reports; or put the reports straight into a SQL database. Then load the reports into the AIDA64 Audit Manager (main menu / File / Audit Manager), and click on the "List 4 (Computer)" in the left tree menu. It will display all data for the computers in a chart. You can select the chart columns if you press the Preferences tool bar button, go to the Components tab, and tick the columns you wish to see. Regards, Fiery

Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...75jgq7h5fwslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. The latest beta has a revamped sensor code for Rampage IV Extreme, Formula and Gene, and also for Maximus V Extreme and Formula. It basically implements a sophisticated -- yet quite suboptimal -- workaround that has 2 working modes. First mode is when AI Suite is not installed, then it will handle the EC directly, it will now switch EC banks (to access the previously missing readings), and also supports the special Asus EC chip. The other working mode is when AI Suite is installed, then it will acquire sensor readings from AI Suite, via a DLL call. Problem is: that DLL call is quite slow compared to direct EC access, but at least it should not collide with AI Suite. The other problem is: this is not a generic solution for all Asus motherboards, so we have to implement it motherboard by motherboard, which is a tiring and slow process, not to mention it is still not a proper fix, just a workaround Third problem: on Sabertooth boards, even with this fix not all readings can be read when AI Suite is installed. We'll continue improving this solution once Asus is ready to fix AI Suite.

Thank you for the feedback. We've implemented the changes in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2075jgq7h5fwslzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade.

I'm glad you managed to fix your computer. The Corsair GS PSU family is a great one, you don't have to worry about it. Great value for the price.

As I've written above, AMD drivers are badly written, and there's no perfect solution. The current solution is the best we can do in our software. As soon as AMD rolls out a better AHCI/RAID driver for WinXP, we'll get back to improving our solution.

Thank you for the feedback

I've sent you a private message about this.

Alerting is a part of AIDA64 that definitely needs improvement. It should be way more flexible than it is now. We'll work on it later this year, and hopefully we can introduce a revamped Alerting module soon. We're watching this topic, and also the other topics about Alerting-related matters, so make sure to post your experiences, ideas and requests here, and discuss how would you imagine a new Alerting facility in AIDA64. Thanks, Fiery

I understand your frustration about the issues about your computer. It looks like a classic case of PSU (Power Supply Unit) failure. With the new graphics card I guess it worked better because GT610 draws a lot less power than GTS450, especially when the GPU is under heavy load (e.g. GPU stress test in AIDA64 SST - System Stability Test). When you run AIDA64 SST, the most demanding task for most computers is the FPU subtest. It makes the processor to work at full clocks, utilizing Turbo Boost (if supported), and every floating-point processing units are driven to excessive load. It effectively means while running the FPU test your processor will draw the most power through the PSU it is possible. When you enable the GPU subtest on top of the FPU subtest, your GPU is also driven to full load, and so the power draw increases even more. A weak PSU may fail at either the FPU or the GPU subtest, but most definitely cannot stand FPU+GPU subtests combined. Of course, I may be wrong about the PSU issue, so if you have a chance to borrow a reliable PSU from a friend, it may be the best way to further diagnose this issue. There's a slim chance the memory modules are failing, or the motherboard has some weak capacitors, or some other hardware or software flaws occur. But if I had to bet some cash on which component is it, I'd put my money on your PSU I hope this helps. Please let us know about your progress on resolving this issue. Regards, Fiery PS: Don't worry about the fan RPMs. As long as the bottom Throtting graph in AIDA64 SST stays at 0% while running the FPU subtest, your processor is not overheating. While 80 Celsius is quite high, it's not the first thing you need to take care of. First make sure to resolve the restarts and lockups, then you can step on to putting the heat down a bit

Thank you We've fixed the temperature labels, and also implemented support for the CHL8318 chip of your video card. A new special AIDA64 beta is available at: http://users.aida64.com/aida64extreme_build_2073_lightning.zip Please verify all GPU-related readings on the Sensor page. If everything looks fine, then we'll of course roll out these improvements in the next regular AIDA64 beta update, and in the upcoming AIDA64 stable release as well.

Thank you. We've done quite a few test runs using various settings on our LGA2011 systems, but couldn't reproduce the issue. Even when all OSD items, Desktop Gadget items and Logging items were enabled, the clock was still properly measured as 1200 MHz when the system was idle. Maybe on your system there's another monitoring software running which is interfering with AIDA64 hardware monitoring module?

Thank you. We've renamed the 2 new temperatures to match Afterburner readings in the following new special AIDA64 beta release: http://users.aida64....2_lightning.zip If it's possible, please submit a new nVIDIA SMBus Dump, since there was a small glitch in the previous AIDA64 beta about that. We may be able to add more readings for the onboard CHL8318 chip using the dump Thanks, Fiery

Thank you Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...71ky1xzfcthvzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Then please create and send us an updated nVIDIA GPU Registers dump and a nVIDIA SMBus Dump. Please also check if any new readings appear on the Computer / Sensor page.

Thanks for the info. It seems to be the well-known event of low-level hardware calls of AI Suite colliding with similar calls of AIDA64 If you leave AI Suite off your system, it should be fine.

Thanks for Thanks for the info

Thank you. We've checked the dumps, and all 5 fan speeds seem to be properly measured by AIDA64. Are you sure they're not on the Computer / Sensor page? Please note that Opt1 fan speed will be shown as Fan #1 and Opt2 will be shown as Fan #2.

Thank you. If it's possible, please create an I2C Dump using MSI Afterburner too. Steps to do that: 1) Open a Command Prompt 2) Navigate to Afterburner's installation folder, by typing in: cd "%programfiles(x86)%\MSI Afterburner" 3) Create an Afterburner I2C Dump by typing in: MSIAfterburner.exe -i2cdump 4) If you did it properly, then a message box should appear stating "I2C dump has been saved to the application folder". If that's the case, then please send us the I2CDUMP.TXT file you can find in Afterburner's installation folder. 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. Then right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. Thanks, Fiery

It looks like a weird anomaly, so if you could provide more info about your configuration, then we'll try to reproduce the issue on one of our LGA2011 test systems in a hope that we can fix it. Please let us know what Windows version do you have running and what motherboard do you have.