Fiery

Fan speed monitoring and fan control are 2 very different issues. AIDA64 uses Dell SMI calls to measure fan speed and temperatures on your device. Dell SMI has no special EC states or such, but it's a universal method that works similarly across devices. It may be possible to talk to the EC directly, but AIDA64 doesn't work that way on your device, so I cannot give you the EC states (or EC registers).

All I can tell you is that sadly it's quite normal with fan controllers and smart PSUs that the manufacturer supplied software collides with any 3rd party software that tries to talk to the device. So if you close CAM, it should work with AIDA64. If you keep both software running, AIDA64 readings can only be accurate in case CAM implements the necessary synchronization mutexes. 3rd party monitoring software like AIDA64, CoreTemp, CPU-Z, GPU-Z, HWiNFO, HWMonitor, SIV (etc) are all synchronized with each other to assure they wouldn't collide when talking to various hardware. Unfortunately most hardware manufacturers develop their own monitoring software in a way that they don't really care about 3rd party monitoring software. So they don't care about synchronizing their software with any other monitoring software out there. In case NZXT is the unique exception who would be willing to implement the necessary mutexes, we would of course be more than happy to work with them. Please note that the necessary job to do is merely adding no more than 10 lines of code to the existing CAM sources. So it's not a huge job, it's not even a sizable amount of coding necessary.

Sounds interesting. And also, it doesn't really make much sense Unless by removing some visual elements the JPEG image size falls under a certain limit where the device stops failing

It is possible of course. SPF-72H is one of the oldest SPF series devices, so it may not work as reliably as newer models like SPF-87H and 800P

Alright We'll do the necessary adjustments in the next AIDA64 beta update.

I'm afraid it's not possible to do that with AIDA64. Regards, Fiery

SPD is enumerated in a completely different way in AIDA64. But yes, it may be possible to use that numbering scheme to make the labels look slightly better. It would still not be perfect in all configurations, but it may work better in most configurations.

It's not a stupid question at all. But it's outside the scope of our expertise, so I don't have the answer.

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