Fiery

Thank you, the bug will be fixed in the next AIDA64 beta release. Please note that upgrading to a new AIDA64 beta works as: 1) Close AIDA64 2) Download the beta ZIP package 3) Extract the ZIP archive to the existing installation folder of AIDA64, and let it overwrite any existing files

1) Did you have to install any drivers for the Vantec NexStar enclosure? 2) Do you know what sort of controller chip does the Vantec NexStar enclosure has inside? Thanks, Fiery

Please right-click on the bottom status bar of AIDA64 main window --> Disk Debug --> SMART Dump. Copy-paste the full results into this topic. We'll analyze that data, and fix the bug in AIDA64.

Thank you for the photo. We'll fix the sensor information in the next AIDA64 beta. As soon as the new beta is available, I'll drop a message in this topic.

Can you see any SMART attributes for your SSD on the Storage / SMART page in AIDA64? If not, then try to enable the two RAID-related options in AIDA64 / main menu / File / Preferences / Stability, update AIDA64 to the latest beta (link below), and update Intel RST or RSTe drivers to the latest WHQL release (if you have an Intel AHCI or RAID controller in your system). http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip Let me know if that helps. If not, then we'll dig deeper

Thank you for your kind words

Thank you. Can you please check how many temperatures the BIOS Setup can monitor on the H/W Monitor or PC Health Status page? Please also let me know what voltage values you can see there.

1) I think what you need to use is the "Remember last page" option in AIDA64 / main menu / File / Preferences / Layout. 2) The long start time of AIDA64 is related to your chipset and CPU actually. The X79 chipset and the Sandy Bridge-E processor has a lot of PCI devices, and enumerating and identifying all of them takes more time than on a mainstream desktop or notebook system (with e.g. Z77 chipset and Sandy Bridge-DT processor) where there're much less PCI devices. The other component that may slow down the AIDA64 startup is a high number of storage devices, especially when they're in RAID arrays. If you notice AIDA64 taking a lot of time at scanning RAID arrays or SMART details at its startup, then try to update the Intel RSTe drivers to the latest WHQL release, and update AIDA64 to the latest beta release as well: http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip If the scan is still slow, and you have a USB storage device (e.g. a flash drive, external HDD/SSD, card reader) connected, then try to disconnect that device, and see if it makes AIDA64 start up quicker. If you can identify a particular USB device that makes AIDA64 startup slow, let us know the USB hardware ID of the device, and we'll add it to the "blacklisted" USB devices list to exclude it from RAID and SMART scannings. Regards, Fiery

Thank you. Since (unfortunately) both drive variants share the same model ID, what we can do is remove the "Micron 25nm" text and extend the "Marvell 88SS9174" text to "Marvell 88SS9174/9187". In case Plextor comes up with a distinct model ID for the newer variant in the next firmware update, then we can re-adjust the SSD database entries to show more accurate information. Regards, 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. Based on that data we can calibrate sensor readings to better support your motherboard. Thanks, Fiery

1) CPU temperature may be different in case MSI's software shows core temperature, instead of the temperature measured by the sensor chip itself. 2) We have no information and no reference points on how to measure +5V on your board If you can find out which sensor register holds that value, then we can implement +5V reading. 3) DRAM voltage is not measured by your sensor chip. What MSI's software shows is the voltage setting in the BIOS Setup. 4) It should be +3.3VSB. As you can see, the measured value is much closer to +3.3V than to +5.0V Thank you for the feedback.

We've fixed an issue in the BIOS detection module of AIDA64. I hope it will fix the issues on your system. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works As for the ACPI VFCT table: it's a table where AMD stores the Radeon video BIOS when the system is booted up in UEFI mode. We can add VFCT table details if you could post a VFCT table dump. You can create such dump by right-clicking on the bottom status bar of AIDA64 main window --> ACPI Tool --> Save Table --> VFCT.

We've implemented sensor adjustments for your motherboard in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Thanks, Fiery

We've fixed an issue in the BIOS detection module of AIDA64. I hope it will fix the issues on your system. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2327vtb1dhc3yjzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

Yes, you can.

You can install AIDA64 on up to 3 computers in the same household. More info on AIDA64 licensing at: http://www.aida64.com/licensing-aida64 Regards, Fiery

ULPS needs to be disabled everytime you change (e.g. upgrade) the video driver (Catalyst).

I think the issue may be CrossFire. In CrossFire mode AMD GPUs tend to use a power-saving trick called ULPS. When ULPS is active, it's absolutely not safe to detect any GPU properties for the non-primary GPU(s). Measuring temperatures when ULPS is active could cause a BSoD or system lockup This is a ULPS implementation limitation that cannot be fixed from software. Regards, Fiery

You need to right-click on the bottom status bar of AIDA64 main window --> Video Debug --> ATI SMBus Dump. Copy-paste the full results into this topic. Thanks, Fiery

If you follow the steps above, then the line will be there

We'll try to reproduce the reported issues with Endpoint Protection 12.1. I'll let you know in this forum topic once we have an update. BTW, on your client computers do you have a 32-bit or 64-bit version of Endpoint Protection installed? Is it installed for all users, or per user? Was Endpoint Protection installed as Managed Client or Unmanaged Client? Do your client users have administrator privileges on their Windows 7 Pro based computers?

I guess it means your motherboards cannot stand AIDA64 System Stability Test -- which is an extremely demanding task, but all computers (theoretically) should be able to stand it and run it without issues. The test apparently raises a false alarm or some other sort of electrical warning that your BIOS misreports as a PSU surge. I guess if in all other tasks your computer is 100% stable, you just need to avoid running the AIDA64 System Stability Test.

Thank you for the data. I'm afraid that means those voltage rails cannot be monitored, but only their voltage levels can be adjusted. Hence a monitoring software cannot monitor those voltages.

We did implement support for Endpoint Security v12 in AIDA64, but apparently it doesn't work in all cases. We'll check it again on different configurations, in a hope that we can catch the bug and fix it up.

1) 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. 2) Also right-click on the bottom status bar of AIDA64 main window --> Sensor Debug --> SMBus Dump (Full). Copy-paste the full results into this topic. 3) Do you have a software that can show those values under Windows? Like MSI Core Center or MSI Control Center? 4) Can you see the mentioned voltage values on the H/W Monitor page of the BIOS Setup? Thanks, Fiery