Fiery

The requested feature will be implemented in the next AIDA64 beta update It will be rolled out later this week.

Thank you for the feedback. We're constantly working on the already implemented LCD protocols, while in the same time keep adding new ones. So the whole LCD module evolves rapidly, and hopefully soon it will cater for everyone

I'm glad it worked out

Try to double-click on the GPU temperature item, and select the actual GPU temperature from the list of temperatures. It may be called "GPU Diode". Note that "GPU" temperature and "GPU Diode" temperature are different readings, so if your old video card supported "GPU" but the new one supports "GPU Diode", then you have to reconfigure the relevant SensorPanel items.

Thank you for the links. We'll definitely have to do a lot of measurements to find out where does our DRAM:BCLK ratio detection code have issues.

That is yet again due to the enermously slow SPD bank switching mechanism of DDR4 modules. We'll do our best to come up with a fixed AIDA64 beta in a few days from now. Sadly, we cannot do that without an actual test hardware on hand, since we have to tweak and optimize the DDR4 SPD bank switching code to make sure it becomes quick enough to let you use AIDA64 without any slowdowns.

Thank you, we'll fix the voltages in the next AIDA64 beta. Rampage V Extreme and X99-Deluxe brought many changes to the sensor layer, so it takes a bit of time for us to figure out the layout

Even though it looks like if it was frozen, AIDA64 doesn't actually lockup there, but just slows down due to the SPD bank switching being very slow on DDR4 modules. You have to wait cca. 10 seconds to let it go through, to let it scan all DIMM slots for any possible DDR4 modules installed, and then things will get back to normal. That scanning will only take place once per an AIDA64 session, but if you close AIDA64 and start it again, sadly it will have to do it again. We'll of course fix that as soon as our DDR4 platform arrives.

Thank you

It doesn't a make a difference whether you overclock your system or not. A stable system should be able to perform any subtests in any combinations, without an error.

You can use the AIDA64 System Stability Test subtests in any combination you wish Regards, Fiery

If it's a DDR4 system, then the long initialization is unfortunately normal at this time. It is caused by the new SPD bank switching mechanism specific to DDR4 modules. The bank switching unfortunately takes a lot more time than we've anticipated, usually 5 to 10 seconds at least, but maybe in your case it's even longer. We'll implement a workaround to put that delay down to less than a second as soon as our DDR4 system arrives. I'll post a message into this topic once a fixed AIDA64 build is available for download.

A minute to load AIDA64 is definitely unusual. In what circumstances does it take a minute to load AIDA64? What kind of computer do you have and what Windows version are you running? At which stage (e.g. "Scanning SMART Devices") does AIDA64 send a lot of time?

Thank you for the feedback. We've double-checked it, and the register AIDA64 currently uses to read CPU temperature seems to be the right one. You can verify that by checking CPU temperature in AI Suite. If you decide to install AI Suite for the test, then please create a new ISA Sensor Dump before and after installing AI Suite. There's a slim chance AI Suite may reconfigure the sensor chip about temperature measurement. As for the Cache & Memory Benchmark, what exactly happens? Is it just slow to complete, or an error message pops up? Please note that on DDR4 systems certain parts of AIDA64 may slow down for cca. 5 to 10 seconds, and it may look as if those modules locked up. But it's just a slowdown, and as soon as that "penalty" elapses, everything gets back to normal. The slowdown is due to the SPD bank switching mechanism of DDR4 modules. The bank switching sadly takes a lot more time than we've anticipated, which causes the 5 to 10 seconds slowdown when reading SPD memory module information. We'll work on that as soon as our X99 test platform arrives.

AMD keeps updating the hardware DirectX version of their GCN-class GPUs, even for the old(er) ones. It's not easy to keep up with that Soon every GCN GPUs will officially support DirectX 12, not just 11.2. Anyway, we'll update GCN GPUs to indicate support for DirectX 11.2 now. Thanks, Fiery

1) On Aquaero 4 you have to select the USB-LCD screen. On Aquaero 5 & 6 you have to change one of the screens to USB-LCD. 2) Yes, we can read the information block from the Aquaero, but its layout is quite complex, so we need a bit more time to process it and "wire" it to the existing sensor module of AIDA64.

We've just rolled out a new AIDA64 beta that supports Adafruit, Dangerous Prototypes HD44780, LPT (Parallel Port Connected) HD44780, Odroid-Show, picoLCD 20x4, Pyramid, Roccat Valo, USB2LCD+, Wallbraun LUI LCDs: http://forums.aida64.com/topic/2498-new-lcd-device-support-usb2lcd/

The mentioned fix has been implemented in the latest AIDA64 Extreme beta release available at: http://www.aida64.com/downloads/aida64extremebuild3136dqmxb7y2znzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works

We've added support for parallel port connected HD44780 character LCD and VFD displays, using the classic 8-bit Winamp wiring scheme. We've also implemented support for parallel port connected KS0108 LCD displays. You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is the LCD to be connected to a parallel port. PCI and PCIe parallel port controllers cards are fully supported. SilverStone FP54 and similar parallel port connected drive bay devices using HD44780-compatible displays are also supported. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Adafruit, Dangerous Prototypes HD44780, Odroid-Show, picoLCD 20x4, Pyramid, Roccat Valo, USB2LCD+, Wallbraun LUI LCDs are also supported now by the latest AIDA64 beta. Note: upcoming AIDA64 beta releases will implement support for more parallel port connected LCDs. If you have such an LCD, please post a message into this topic stating what kind of LCD do you have and what sort of controller (driver) is it based on. Regards, Fiery

The mentioned fix for Asus X99 motherboards is available for download at: http://www.aida64.com/downloads/aida64extremebuild3136dqmxb7y2znzip

We've added support for character based LCD displays using the USB2LCD+ protocol, as described at: Coder for Life - Project - USB2LCD+ You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. After enabling it, make sure to set the LCD size (on the same page of the AIDA64 Preferences), since USB2LCD+-capable devices will not provide such information to AIDA64. Currently the following LCD sizes are supported: 16x2 16x4 20x2 20x4 The only thing needed to enable this feature is having the appropriate USB2LCD+ drivers installed, and the LCD to be connected to a USB port. You can verify if your device is USB2LCD+ compliant by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be 5BCD-5BCD. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Adafruit, Dangerous Prototypes HD44780, LPT (Parallel Port Connected) HD44780, Odroid-Show, picoLCD 20x4, Pyramid, Roccat Valo, Wallbraun LUI LCDs are also supported now by the latest AIDA64 beta. Regards, Fiery

There's a Core i5 result in our reference benchmark results list And we do not want to add too many systems there, since that's not the point of the reference results. Our reference systems are strictly controlled, to provide a stable, reliable, accurate and reproducable result with all our benchmark tests. We tend to build only one or two systems for each platform, so if you look at the list, you'll see that there's one Ivy Bridge there, two Haswells, one Ivy Bride-E, one Sandy Bridge-E, one Kaveri, one Richland, one Trinity, one Vishera, etc. If we would add more Core i5, then Core i3, Pentium or Celeron owners would feel left out If we would add all of those, then the list would be too long, and our efforts on keeping the reference systems strictly controlled would waste too much of our resources. Regards, Fiery

It simply does the same thing as the memory CRC checking, but with such block sizes that would fit in the L1, L2 and L3 caches of your CPU. So it heavily stresses all CPU caches. In your case, considering how many things you've tried to replace in your system, I'd say it could either be the CPU or the motherboard. Out of those two, I'd start with trying a new CPU. It could be an affordable Celeron as well, you could probably borrow one easier than a high-end Core i5/i7 part. Regards, Fiery

Thank you, the reported bug will be fixed in the next AIDA64 beta release due in a few days from now. I'll post the download link into this topic once the new beta is available. Thanks, Fiery

Thank you for the info and the data. The sensor-related bugs will be fixed in the next AIDA64 beta release due in a few days from now. I'll post the download link into this topic once the new beta is available. As for the strap, please provide us a bit more time to work on that. Our X99 test platform hasn't arrived yet, and we'll need that to fix a couple of issues. Thanks, Fiery