Fiery

Please enable the option RAID SMART support in AIDA64 / main menu / File / Preferences / Stability, and restart AIDA64 to apply the changes. Let me know if it helps. Thanks, Fiery

AIDA64 uses the industry standard GlobalMemoryStatusEx Windows API call to detect memory status. That function returns a structure called MEMORYSTATUSEX. The swap space info is taken from the structure entries called ullTotalPageFile and ullAvailPageFile. You can read about their meaning and purpose at: http://msdn.microsoft.com/en-us/library/windows/desktop/aa366770(v=vs.85).aspx Regards, Fiery

Thank you for the feedback

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

Thank you. We've fixed the Vcore reading, so please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1754ks2vmhxr7dzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

Thank you. We've fixed the sensor readings, and also implemented a series of new readings for your board. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...54ks2vmhxr7dzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

I'm glad you worked it out. Thank you for letting us know

Write benchmarks on disk drives are not used by most AIDA64 users, mostly because they erase all data from the tested drive. And also, using write benchmarks on SSD drives will shorten their lifespan. We already have separate write tests for disk throughput and access tests, so you can use them if you need to test write performance. Regards, Fiery

We currently have no tutorial made for the remote features of AIDA64, but please feel free to ask questions or ask for guidelines here, or via email: support AT aida64.com

Thank you for the dumps. If it's possible, please also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> Embedded Controller Dump. Copy-paste the full results into this topic. Thanks, Fiery

No, you don't have to unlock the position. Just make sure to close AIDA64, then you can alter the mentioned Registry entries.

1) The INum column in the Item table is supposed to be a unique identifier column. We also use the IID column there to identify specific information bits, although IID values can be repeated: if for example you have multiple video adapters, you'll have multiple IID = 523 entries. 2) The lack of updating is there for two reasons. First, most of AIDA64 Business Edition users want to see changes between audit snapshots, using either AIDA64 Change Manager or a proprietary query solution. Second, it may raise security concerns if any network user would be able to modify (update) an entry related to his (or another user's) audit data. Imagine a user install a specific software or malware in his computer, and then update the daily audit snapshot to remove or alter the entry that would reveal what he's done I don't actually mean to talk you into using AIDA64 with all that, I just felt it's best to clarify those concerns Regards, Fiery

1) You can do remote monitoring, remote reporting and remote control between different OS versions. 2) There's no such restriction. All you need to have is TCP/IP connection between the computers.

Thank you for the new dumps. Please upgrade to the following new AIDA64 beta: http://www.aida64.com/downloads/aida64extremebuild1751p8r9djxchszip Let me know how it works Thanks, Fiery

Using the latest AIDA64 beta, 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. Also copy-paste the full content of the Computer / Sensor page of AIDA64 into this topic. Thanks, Fiery

There's a SQL_Schema folder in AIDA64 Business Edition installation folder. You can find the necessary SQL schemas there which you can use to initialize the required SQL tables. Regards, Fiery

No, it's definitely not measuring anything based on ambient temperature. You can adjust the core temperatures if you think it's off by e.g. 20 or 25 Celsius using the Correction feature of AIDA64 (main menu / File / Preferences / Hardware Monitoring / Correction).

Thank you for the feedback

Thank you. Please upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild1747rfmh8jz2cyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. There's a slim chance the CPU Vcore and CPU VTT voltages are reversed. Please watch them both, and let us know if we need to swap them. CPU VTT should be very stable, while the CPU Vcore readings should fluctuate according to SpeedStep and C1E state changes. Thanks, Fiery

We've changed the minimum bar width and minimum bar height to 1 pixel both. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.co...47rfmh8jz2cyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works As for the graphics memory usage, it can only be measured for nVIDIA video adapters. Thanks, Fiery

We've added support for ZoneAlarm v10 in the following new AIDA64 beta release: http://www.aida64.com/downloads/aida64extremebuild1747rfmh8jz2cyzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Thanks, Fiery

I'm afraid it's not AIDA64. FX processors feature a temperature diode that measures wrong temperatures in basically all conditions. Usually that temperature is unrealistically low, well below ambient temperature. So far noone seems to have an idea on how to implement a workaround. It already happened before, with some AM2 processors, and there a simple offset helped to get proper temperatures. Maybe this time it's the same, but AMD didn't provide any useful information on the issue. Regards, Fiery

NetUpdate is not meant to be translatable, so we wouldn't need to fix that We'll check the "OK" issue. Thanks, Fiery

AIDA64 reads BIOS Settings (as listed on the Motherboard / BIOS page) using Asus ATK BIOS calls. Hence those values reflect the values Asus BIOS provides to Windows applications. In your case I'm afraid there's a BIOS bug that results in improper DRAM voltage calculation by the BIOS. It doesn't mean the BIOS uses the wrong DRAM voltage, so you don't have to worry about that. It's a minor glitch that only affects software that read out the BIOS Settings via Asus ATK BIOS calls. Regards, Fiery

Thank you for the data. It looks like a tough one though (to figure out the voltage registers and voltage ratios), so if it's possible, please provide us with more data. Please go the BIOS Setup and note down all values you can see on the M.I.T.\PC Health Status page, all temperatures, voltages and fan speeds measured there. Or, alternatively, you can also make a photo of that page, if it's easier for you. In case your voltage settings have changed since you made the dumps above, then please create a new ISA Sensor Dump to make sure the BIOS Setup PC Health Status values match the dump. Thank you for your time. Regards, Fiery