Fiery

You should It's a bit tricky and somewhat time-consuming to build a proper SensorPanel layout, but when it's done, it works and looks great

AFAIK it's not possible to detect touchscreen sensor brand and model in Windows PCs or mobile devices. Regards, Fiery

The data displayed on the Sensor page is not meant to be customizable at all. If you need to rename the sensor readings, and/or hide some of them, then it's best to use the OSD Panel, Desktop Gadget or SensorPanel modules. With them you can completely customize the layout to your preference.

The problem is that it's not easy to detect what the motherboard can actually support, out of the capabilities of the memory controller. For example, when an Ivy Bridge-E/EP CPU has got 2 memory controllers, each supporting 4 memory channels, and each memory channel supports 3 DIMM slots, the CPU in theory can handle up to 24 memory modules. And when walking through the memory channels and DIMM slots, numbering must follow the capabilities of the CPU (more specifically, the CPU integrated memory controller), and not the capabilities of the motherboard. AIDA64 cannot know for sure what slots can it skip when enumerating DIMM slots. That's why you have gaps of 2 DIMMs between memory channels, and not just 1 DIMM.

DIMM labelling is a big challenge, considering all the various memory controllers out there. Even if we'd switched to using DIMM A1/B1/C1/etc formula, in many cases there would be strange jumps in the numbering. As for the System Stability Test, we'll expand the current 12 slots to 14 in the next AIDA64 beta update due in a few days from now

There's nothing to disable there. If after 6 hours of heavy stress your CPU still doesn't throttle, then you can tick a box of "CPU cooling" there Maybe then it's the video card that throttles? Have you tried to use the logging facility of AIDA64? Go to AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging, and enable logging to HTML. Select only the items for Date, Time, CPU utilization, CPU clock, GPU utilization, GPU clock, and GPU temperature. Once the game starts to act out, close AIDA64 and check the HTML log. You should be able to see what happens to the GPU clock and GPU temperature once the game becomes unplayable. Maybe after a certain period of time your video card overheats, throttles its clocks down to very low levels, and you lose video performance while gaming.

Go to: http://www.aida64.com/downloads Download AIDA64 Extreme, install it, run it, and go to main menu / Tools / System Stability Test. Uncheck all subtests except for FPU, and press the Start button. Watch the bottom graph, particularly the green graph that shows CPU throttling activity. Wait for at least an hour, and see if the green graph becomes red, indicating that your CPU throttles. No matter what various temperature readings show actually. If your CPU throttles under heavy load, then you have to do something about cooling to prevent that from happening

In your case most likely Aux is actually the temperature of the CPU. You need to improve the cooling of your processor, and/or the ventilation of the PC case. BTW, HWMonitor is not our software

Such issue usually comes up when a value disappears and then reappears in the list of sensor items. Can you see which value is the culprit on your system?

Thank you for the feedback. Do you mean automatic sleep after a certain period of time, as configured in Windows power settings? Do you have a desktop or mobile system?

PCH Diode is important in case you are worried of the PCH (motherboard chipset) overheating under heavy load.

CPU and CPU Package should be the best, if you don't want to monitor all of them

I've just sent you a private message about this

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