Fiery

Please note that old user results will not be shown when you upgrade to a newer AIDA64 version, because results obtained with previous AIDA64 versions cannot be compared to the current version results. A warning about that fact is displayed every time you run a benchmark Regards, Fiery

Those temperatures are normal. As for MCP, please check Q#30 at: http://www.aida64.com/support/knowledge-base

Thank you for the feedback. It seems we have to keep looking for Vdimm Can you please do the following: 1) Set 1.50V in the BIOS, and create an ISA Sensor Dump. Please also create a SMBus Dump (Full). 2) Set 1.60V in the BIOS, and create another ISA Sensor Dump + a SMBus Dump (Full). Hopefully we'll be able to find the register responsible for Vdimm in there this time Thanks, Fiery

No, it's not possible.

AFAIK Marvell SATA/RAID controllers cannot pass SMART commands to Windows software like AIDA64. Regards, Fiery

Thank you for the dumps. I've just sent you a private message about this.

Changing labels for External Applications is not possible at this time -- but you can hide the labels if you want. We may add the labels configuration feature sometime next year. Regards, Fiery

Thank you for the data, and I'm sorry for the delays. Can you please post 2 another ISA Sensor Dumps, both made before sleep, when DIMM voltage is shown as 2V? One dump at default 1.50V DIMM voltage, and the other at a slightly different one, like 1.55V or 1.60V. That way we can check which register is responsible for holding the DIMM voltage value. Thanks, Fiery

If you have the option Enable CPU throttling measurement (in AIDA64 / main menu / File / Preferences / Hardware Monitoring) enabled, then try to disable that option and see if it fixes the issues. Regards, Fiery

ACPI Tool was never a public or official feature of AIDA64, but more a debugging tool to help us find issues in AIDA64 related to certain ACPI BIOS bugs. It has been removed from AIDA64 at v4.00. Regards, Fiery

We can add eDrive detection once it gets included in the ATA specification. Unless of course there's an alternative method of detecting that capability -- but we have no information on that at this time. Regards, Fiery

There's no logging in the AIDA64 System Stability Test simply because the elapsed time doesn't change the fact that the system is either stable or unstable If the computer can't stand the stress test for 5 seconds, it is considered unstable -- but it's also unstable if it can run it for 5 hours and only after then it fails But, you can activate the Logging facility of AIDA64 (main menu / File / Preferences / Hardware Monitoring / Logging) to track various system parameters while running the Stability Test. Regards, Fiery

I'm sorry for the delays. We've done quite a few test runs on similar configurations in our test labs, but couldn't reproduce the issues The only thing "suspicious" about your system configuration is the Rampage IV Extreme mobo, which has support for AI Suite II. Do you have that software installed? Or, if not, then do you happen to have the AI Suite services still installed and running? Please note that since Asus refuses to implement the necessary synchronization techniques in AI Suite, it may collide with AIDA64 sensor measurement code and cause all sorts of issues that may lead to sensor values dropout. If possible, please uninstall AI Suite, and verify if it has any services left after its uninstallation. FYI, for unknown reason even after uninstalling AI Suite it leaves a few services installed and running, that will still keep polling sensors and collide with other monitoring applications like AIDA64

We've done a lot of improvements to the CHiL and ONSemi sensor chip functions, and revamped many generic communication functions around there to make GPU sensor measurements more stable, and make the initial scanning of GPU sensor chips quicker. I'm glad that -- as a side effect -- it solved the issues you've experienced

Thank you for the update on this issue. Please note that when you enable stressing GPU(s), it's normal that during the AIDA64 System Stability Test the whole system consumes more power and runs at higher temperatures than while running a game or another stress test. You've got a very powerful configuration, but a game like Battlefield will only drive your GPUs do high levels, but not the CPU. While with the AIDA64 System Stability Test you can push all components to their limits simultaneously. Regards, Fiery

Nice 1st post, thank you And you've got quite a fleet of PCs

Yes, we do have plans about that, but unfortunately the current software stack for Corsair Link architecture doesn't allow multiple applications access the Link hardware simultaneously. Corsair said they will roll out a brand new software stack with 3rd party applications support sometime next year. As soon as their new software stack is ready, we'll get back to implementing Corsair Link support in AIDA64. Regards, Fiery

The latest beta version of AIDA64 Extreme implements full support for Radeon R5, R7 and R9 Series: http://www.aida64.com/downloads/aida64extremebuild2714szdhb5yw8gzip Regards, Fiery

I think it is due to a BIOS programming issue. Maybe it programs the measurement unit field incorrectly, and that's why you get too low readings. We'll add OCZ Deneva 2 and Talos 2 SSDs in the next AIDA64 beta release due in a few days

1) What motherboard and CPU do you have? 2) What version of Windows do you have installed? 3) Are the disappearing WDC drives are internal drives or external (e.g. USB) drives? Thanks, Fiery

I'm not sure if the incorrect temperature readings are due to a motherboard failure, a motherboard sensor chip failure, a BIOS issue or a mixup in software/OS installation. And BTW, for such small issue I wouldn't change a motherboard. There are plenty of other sensor readings you can rely on

Thank you for your understanding and your support We try to get more and more AIDA64 users to subscribe to our newsletter -- that is the method to gain access to such special promotions

For some reason, on your motherboard both motherboard and CPU temperature readings are invalid. Even Asus AI Suite reads invalid values (check the Asus ATK0110 section in the dump above). We cannot fix such issues from AIDA64 -- but fortunately you will still have the core temperature readouts to let you track the CPU temperature Regards, Fiery

Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / OSD / OSD Items, select any of the items (or multiple items using Ctrl key), and press the Configure button. You can change label, font name, font size and font style of any OSD item that way. Regards, Fiery

It could be due to a pecularity of the IMC (integrated memory controller) of your processor. Maybe the benchmark hit a bottleneck, or there's a memory interface instability at DDR3-2400 using the seemingly strict memory timings you've configured. Can you please post a similar screen shot, with the memory running at DDR3-1866? Thanks, Fiery