Fiery

We've fixed the reported issue about LAMD SSD controllers in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip 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 for the feedback

Thank you for the bug report. We've fixed it up in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

We've implemented support for the VFCT ACPI table on the Motherboard / ACPI page. Also, AIDA64 now reads flash BIOS from the VFCT table on AMD APUs when the classic video BIOS is unavailable due to UEFI boot. Make sure to upgrade to the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've fixed the bug in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works.

We've implemented the requested feature in the latest beta version of AIDA64 Extreme Edition available at: http://www.aida64.com/downloads/aida64extremebuild2334r5bzp8vxskzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works. Please note that you can not only double-click now to start individual tests, but also double-click on e.g. "Memory" to start all memory tests, or double-click on "Read" to start all read tests.

Open AIDA64 / main menu / Tools / System Stability Test. Enable only the FPU and GPU subtests, and press the Start button. Let the stress test run for a few hours, and once in a while watch the bottom graph: in case the Throttling graph shows any non-zero activity and turns into red, your processor is overheating. In case the test ends with an error message, system lockup, BSoD, unexpected system restart or system poweroff, then you have a serious stability issue with your computer. In that case it's unfortunately not possible to tell which component is behind the issues (none of the stress testing or troubleshooting software is able to tell you that), so you have to go by the usual routine of: 1) Disable all overclocking, return to factory default settings 2) Update system BIOS 3) Update all drivers to their latest WHQL (certified) versions 4) Update Windows to have all service packs and hotfixes applied 5) Change the PSU if none above helps 6) Change the RAM if none above helps 7) Change the motherboard if none above helps I know it's not exactly an accurate answer, but computer instability is much like serious health issues of the human body: in many cases it's impossible to exactly tell what's wrong, so you have to do more tests and apply some changes to find the root of the issues.

HDD/SSD list ordering follows physical drives ordering, so the first drive is the one Windows recognizes as the first drive in its Disk Management module. However, when AIDA64 recognizes multiple drives with the same model ID, then it will also indicate the serial number for each such identical drives in brackets, right next to their model ID. Regards, Fiery

It's a bug in the LCD module of AIDA64 that we'll fix in the next AIDA64 beta release due in a few day from now. I'll drop a message into this topic once the new AIDA64 beta is available for download. Thanks, Fiery

Then I think it would be easier if we implemented one-by-one benchmark starting on the Cache & Memory Benchmark Panel as well. It will be implemented in the next AIDA64 beta due in a few days from now I'll drop a message into this topic once the mentioned improvement is implemented.

Such logic wouldn't fit into "automatic scaling" I'm afraid. It would be some sort of "semi-automatic" solution that we wouldn't want to implement in AIDA64 I'm afraid.

CPU Tweakings is a module that was designed to aid finding bugs, and to read specific information from the processor that is only relevant to us, the developers of AIDA64. The module is not meant to be used by regular AIDA64 users at all, that's why its user interface is not designed to be beautiful or clean I'm also not quite sure what you mean by "more convenient". CPU Tweakings has a similar layout about cache and memory benchmarks than the Cache & Memory Benchmark Panel, it produces the same scores using the same one-click start button. Regards, Fiery

Auto-scaling means AIDA64 will automatically scale the graph's minimum and maximum scale values, according to the recent values measured. There's no need to configure the minimum or maximum values in that case. Regards, Fiery

The hardware hasn't yet arrived to us. We'll ping the local distributor in order to find out approx. when can they deliver the hardware.

We would be happy to fix the bug you discovered, but first we need to reproduce the issue in our own network. And in order to do that, we need the information I've asked for above. You missed one of my questions, so if possible, please indicate your system configuration on: "Was Endpoint Protection installed as Managed Client or Unmanaged Client?" Thank you for your time.

The FPU subtest of the AIDA64 System Stability Test is an extremely demanding task that only a 100% stable system could stand. If it fails on your system with your current settings, then I guess you will need to lower some clocks or up some voltages to stabilize your system. Regards, 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