Fiery

That's great news, we can at least rule out throttling then. Can you please check if the latest AIDA64 version (v5.70) provides the same low memory bandwidth scores?

The CPU type is correct, it's just not complete. You can enable the CPU clock column to let you break down a certain CPU family (like AMD Sempron) with a better resolution. For modern AMD processors the complete CPU SKU is shown there, like: "QuadCore AMD A10-7850K". Regards, Fiery

Thank you for the info. Android N Developer Preview 2 is out, but it's not yet available as an OTA update for our Nexus 9. We keep checkin' ...

Thank you for the feedback Supporting non-US keyboard layouts about RGB LED is unfortunately a big challenge, regardless of the keyboard manufacturer in question. I think the ultimate solution will be to offer custom key list building, so you can specify exactly what keys do you want to be lit as a row. That's true. Corsair hasn't yet come up with a proper SDK for its RGB LED products, so we have to talk to the device directly. That will then collide with CUE. The ultimate solution for this issue will be when Corsair introduced a RGB LED SDK with proper synchronization and device sharing across multiple applications.

Thank you for your suggestion. We do have plans about adding customizations to the AIDA64 Windows 10 UWP app, and the dark theme sounds like an interesting idea. But we expect that along with the Windows 10 Redstone update Microsoft may just implement the selection between light theme and dark theme as a system-wide setting anyway, and then the whole thing would be controlled by the user just like in the "good old" Windows Phone 8.x days

Ah, I see now, I'm sorry, it was my mistake. Reading DRAM voltage is the responsibility of the motherboard sensor logic. It doesn't need any kind of hardware support by the memory modules themselves. Your motherboard (ASRock X99 Extreme11, I suppose) doesn't seem to be able to measure DRAM voltage though.

If you're absolutely sure there's no background process or service that could affect the benchmarks, then try to check the other benchmarks too. It would be important to check if any other benchmarks are also affected by this anomaly. It would be best to use the latest AIDA64 version of v5.70.

Are you sure the cooling of your CPU is adequate to keep it in the normal temperature range? Have you checked the AIDA64 System Stability Test, using only the FPU subtest, to see if the CPU can stand long-term high load? If you do that, make sure to focus on the bottom graph: your CPU shouldn't show any throttling activity, any non-zero percentages, even after hours of heavy stressing. If it shows non-zero throttling, it means your CPU is overheating under load, and that could well affect benchmark scores and in-gaming performance too.

Most memory modules simply do not feature a DIMM TS compliant temperature sensing logic. Are you sure your new memory modules are capable of measuring their own temperature?

iOS and Windows Phone (Windows 10 Mobile) use way stricter sandboxing than Android or Tizen. If something's possible under Android, it doesn't mean you can do the same on other platforms too Under iOS it's not possible to measure or detect battery health, battery temperature and charge rate.

You can override the unit with your own choice, but you also have to make sure the measured value is scaled accordingly. You can use the Correction feature (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction) to do that.

1) The linked Adafruit device is only a LCD module that you cannot connect via USB. You need a device with the following USB backpack to work as a standalone LCD screen connected via USB and ready to be used by AIDA64: https://www.adafruit.com/products/784 You may also want to order an acrylic stand for it: https://www.adafruit.com/products/1365 2) Odroid-Show and Odroid-Show2 would work without any additional hardware. But, please note that they feature a very slow serial protocol, and so screen update rate with AIDA64 is only approx. 1/3 FPS 3) If you only want to output a few data to an external LCD, and you don't need native support for the screen in AIDA64, then LCDsysinfo may also work: http://www.ebay.com/itm/LCDsysinfo-for-GOverlay-USB-2-8-TFT-LCD-Module-gamer-gadget-FPS-Hype-Smartie-/121106592717?hash=item1c3283f3cd:g:kpIAAOxyRHdR3kcY But I'd like to stress the fact that since LCDsysinfo developers refuse to publish the protocol used by their devices, we cannot support those devices natively in AIDA64. It will still work fine using LCDsysinfo's own software though. 4) There's also picoLCD 20x2 OEM which is fully supported by AIDA64: http://www.mini-box.com/picoLCD-20x2-OEM 5) If you're willing to spend a bit more on the display, there's a great picoLCD graphical device, also fully supported by AIDA64: http://www.mini-box.com/picoLCD-256x64-Sideshow-CDROM-Bay 6) And for quite a bit more there're stunning graphical OLED options from Yoctopuce, fully supported by AIDA64: http://www.yoctopuce.com/EN/products/category/usb-displays I hope this helps

It's most likely caused by a background process or service that trashes the branch buffers of your CPU. Make sure to close everything running in the background, including Skype, BOINC, etc. Also make sure to check if a background virus scanning or Windows Update process is in progress or not.

We've fixed that issue in the latest AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta Please let me know how it works

There's no size limit for the SensorPanel. You can design a 1920x1080 pixel resolution SensorPanel and move it to your secondary display at the top-left position to make it full-screen.

In case multiple items are frozen on the SensorPanel, then the issue may not be RTSS, but rather a configuration issue on your side. Have you tried to lower the SensorPanel update rate in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency?

We currently have no plans to implement that.

You don't need the Custom Variables feature or AIDA64 Business to do that. You can simply write your readings into the Registry, under: HKEY_CURRENT_USER\SOFTWARE\FinalWire\AIDA64\ImportValues Where String type values should be named as Str1 to Str10, and 32-bit integer (double-word or DWORD) type values should be names DW1 to DW10. AIDA64 will automatically pick those values up and display them among the available sensor items. You can then place them on the LCD screen just like you place any other temperature or fan speed reading. That feature is available in AIDA64 Business, AIDA64 Engineer and AIDA64 Extreme.

It doesn't matter which power profile do you have configured in the Control Panel. AIDA64 automatically adjusts Windows power settings to make sure the CPU is running at the highest clocks while the stress test is running. As for the restart, it was due to Windows Update forcing a system restart, by forcing AIDA64 to quit.

Both temperatures are right and valid. I don't know what they refer to exactly, but they are both valid.

PSU efficiency is calculated using a proprietary (and not public) formula by manufacturers' software like Corsair Link Software, Enermax Digifanless Software, Thermaltake DPSApp, etc. Since it's not actually measured, we believe it's not an accurate and scientific way of providing incoming power draw measurement. That's why we're not pursuing finding out how those formulas work. Especially since the formula is not only specific to a certain series of PSUs (like Corsair AXi), but also different across PSU models inside a series. So for example, there's a formula for AX760i, and a different one has to be used for AX1500i.

It is the combined power that the motherboard, CPU(s) and video card(s) draw from the PSU.

We will fix that in the next AIDA64 beta update due next week. As previously, I'll post a message into this topic once the new beta is available for download I hope you'll have a great weekend too!

That's unfortunately normal at this point. Corsair Link software doesn't implement the necessary industry standard synchronization mutexes that other 3rd party software (like AIDA64, HWiNFO, CPU-Z, GPU-Z, etc) already use to avoid such collisions. Corsair said they are already working on the resolution.

Thank you for the feedback, I'm glad now it works properly on your system