Fiery

The mentioned new AIDA64 beta update is available for download at: http://www.aida64.com/downloads/latesta64xebeta Let me know how it works

That was a bug that we've fixed in the latest AIDA64 beta update: http://www.aida64.com/downloads/latesta64xebeta

AIDA64 supports one PSU. We don't plan to support multiple PSUs, since it is a very-very rare usage scenario among AIDA64 users. We've fixed that in the latest AIDA64 beta update available at: http://www.aida64.com/downloads/latesta64xebeta That's certainly an interesting idea, but it is just as challenging and complicated to make happen as it sounds intruiging We may implement it, but definitely not in the near future.

The way it works is that each of those Samsung SPF devices have a limit of a certain maximum JPEG file size. If you pass a bigger file, they will malfunction, and you have to reset them to make them work again. The problem with JPEG is that it's not easy to predict the resulting file size from the input bitmap. So when you specify a JPEG quality of e.g. 80%, the resulting file may be 200KB or 210KB or 180KB, depending on how complex the rendered bitmap is. And since with AIDA64 you can build a dynamic layout, one that may look less complicated or more complicated, depending on the system state, it's not easy to find a proper JPEG quality setting. Sometimes 80% would work for hours, but then a frame comes where the 80% setting yields into a bigger JPEG file, and then the frame freezes. That's why we've introduced the JPEG file size limiter, that will automatically lower the JPEG quality in case the resulting file gets too large. The problem with that setting is that you have to play with it a lot to find the right size for your SPF device. Samsung sadly doesn't publish that data, and AFAIK there's no information on that on the internet anywhere either

No, since by multiplying those values the resulting Wattage amount is constantly lower than if you add up the power draw amounts for the individual voltage rails. In your case for example, Pkt#88 x Pkt#89 is around 310 Watts, but the sum amount of power drawn by the voltage rails is cca. 318 Watts.

Wear level is not a fake value at all It's calculated as: Fully Charged Capacity / Designed Capacity * 100 Regards, Fiery

JPEG limit is only need to be configured when there's an issue while using complicated LCD layouts. Do you find any issues with your old or new layout?

We are the developers behind the AIDA64 for Android app. We can upgrade our app, but cannot upgrade the platform (Android). Regards, Fiery

Probably you've changed your Windows Desktop or monitor configuration, and that made AIDA64 display its main window on a position that was outside the visible area of your default Windows Desktop. AIDA64 has got an automatic mechanism to prevent that from happening, but maybe yours is a special case where it failed to fix it up automatically. If it happens in the future, just close AIDA64, start Registry Editor (via Run --> REGEDIT.EXE), navigate to: HKEY_CURRENT_USER\SOFTWARE\FinalWire\AIDA64 And remove all values that have a name the starts with Window

We've checked the new Android N Developer Preview 2 on our Nexus 9, but the Vulkan layer doesn't seem to work properly yet. When we try to initialize Vulkan by calling vkCreateInstance, it says: E/vulkan: failed to load vulkan hal: No such file or directory (-2) Maybe a different device or the next preview would help. Or maybe there's a trick, maybe it is necessary to use special initialization with Vulkan for Android. We'll keep trying...

That's normal, since hot-plug support for AX206 LCD is not yet implemented in AIDA64. It will be implemented though in the next AIDA64 beta update due in a few days from now I'll post a message into this topic once the new beta is available for download.

Pkt #96 is simply the rail power, not the total power of the PSU. Bank #0 / Pkt #96 is the +12V power, Bank #1 / Pkt #96 is the +5V power, and Bank #2 / Pkt #96 is the +3.3V power. Those power values however are less accurate than when you take the rail voltage and rail current, and multiply them to get the calculated rail power. That's why AIDA64 ignores Pkt #96 values. And BTW, when current cannot be measured due to firmware issues, Pkt #96 also indicates zero Watts. So when it comes to total PSU power measurement, it wouldn't help to switch to using Pkt #96

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.