Fiery

Thank you. I suppose when SVID support is disabled, the power circuitry doesn't go through the standard path where the processor could measure its own power draw. I'm afraid we have no idea how to get around that limitation Intel's CPU documents do not feature enough details to fully understand how the power circuitry and its various modes work exactly

Haswell-E/EN/EP/EX processors feature two quad-channel memory controllers (IMC), but on Haswell-E only the first one is utilized. Server parts (Haswell-EP for example) may have both controllers utilized, so you can use a total of eight DDR4 memory channels per CPU socket. As for the DIMM module size issue, we're aware of that, but it seems a bit complicated. The chipset (IMC) itself reports that memory module size, and so far we haven't found a proper way to come up with a workaround for that. We'll keep trying Till then, you can use the Motherboard / SPD page to check the full and accurate details on your installed memory modules. Regards, Fiery

The Desktop Gadget subsystem has been removed from Windows 8.x, and most likely it won't be restored in Windows 10. While the AIDA64 SensorPanel is completely independent from the underlying operating system and its capabilities.

No, we don't plan to get the EXE package back. BTW, you can create a Desktop icon for the AIDA64.EXE executable by right-clicking on the file --> Send to --> Desktop (create shortcut).

AIDA64 Business is geared towards corporate use. Corporate users (e.g. network administrators) prefer the portable (ZIP) package, and don't need the added features the self-installer (EXE) package provides. Regards, Fiery

Thank you for the feedback

For that purpose you can use the existing Logging facility (AIDA64 / main menu / File / Preferences / Hardware Monitoring / Logging).

Please right-click on the bottom status bar of AIDA64 main window --> CPU Debug --> CPUID & MSR Dump. Copy-paste the full results into this topic, or attach the results as a TXT file to your post. We'll have to check the registers, and compare them against our 5820K. Maybe there's a way to fix it up by applying a workaround. Thanks, Fiery

Can you please check if you experience the same issue with HWMonitor? BTW, on our 5820K + Gigabyte X99-UD4 system AIDA64 measures cca. 10W at idle and 100W under heavy load. So the problem may be related to 5930K or Rampage V Extreme motherboard.

Please upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3206lgct2wrjxkzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how if it helps.

Please report the issue to cleverbridge, our online payment processor. They will have to investigate this. Thanks, Fiery

In case the FPU-only test also works fine, then yes, it should be considered a safe setup.

What kind of data or conclusion would you be able to draw from such output? Regards, Fiery

We believe the AIDA64 System Stability Test is a great tool to challenge your system's stability. Enable all subtests, press the Start button, and leave it running for a few hours. If it can stand that, then stop the test, enable only the FPU subtest (and the GPU subtest in case you've got a discrete video adapter, like a video card), press the Start button, and leave it running for a few hours again. In case your system can work under both settings stable, then I'd consider it a stable configuration. BTW, the first test I've mentioned is geared towards challenging computing stability, while the second test is to test thermal stability, ie. whether your system cooling is adequate. Regards, Fiery

Do the memory timings appear properly on the Motherboard / Chipset page?

Problem is: the USB protocol for LCDsysinfo was only published for the original LCDsysinfo device, but not for the more advanced GOverlay device. We've contacted the company behind the GOverlay both in email and through eB*y to request specifications, API description, SDK or any other material to let us connect to the device in AIDA64, but we've got absolutely no response from them. It's quite tough to work this way, and I cannot promise anything at this time about GOverlay.

It depends on the motherboard PCB layout. But it's a safe assumption that the temperature diode measuring VRM temperature is placed close enough to the VRM circuitry.

Our slight concern is the motherboard-integrated VRMs are not really inside the CPU package or even right next to the CPU socket in a strict sense. So using the CPU icon may not be closer to the truth than using the current icon.

The issue will be fixed in the next AIDA64 beta release due in a few days from now

What sort of security software do you have installed? Maybe that is the one that blocks AIDA64 from starting up at Windows boot.

Make sure to upgrade to the latest beta version of AIDA64 Extreme available at: http://www.aida64.com/downloads/aida64extremebuild3203dw9pkvh8sxzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know if it helps. Thanks, Fiery

The icon in question isn't actually a battery icon, but more a generic power icon. It shows the battery in the background and a power plug in front of it. I admit, it's not the perfect icon to represent power delivery, power supply or a VRM, but there're other kind of VRMs that may or may not be directly related to the CPU, that's why we use a more generic power icon. Regards, Fiery

I've sent you a private message about this.

Notebooks, especially the ones using Intel Haswell-class processors, tend to operate at much higher temperatures than comparable desktop systems. Maximum temperature of 80 Celsius is actually not bad at all. Also, Haswell processor based processors can easily get to a point of overheating and throttling, it is considered normal operation for them. I'm not sure about cooling pads, never used such a thing. I suggest you to try googling for: notebook cooling pad review Regards, Fiery

We've tried to replicate the issue on our DeathStalker Ultimate, but had no luck. For us everything worked properly. We've put a set of custom gauges on a gauge that we've put on Page#1, and then we've used another set with another gauge we've put on Page#3. Both gauges displayed fine, with the appropriate custom gauge state images. Please let me know if you experience a different issue. Also make sure to upgrade to the latest AIDA64 beta, it may (or may not) help http://www.aida64.com/downloads/aida64extremebuild3203dw9pkvh8sxzip