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

I'm afraid we haven't yet found a way to display SensorPanel when using Aero Peek. I'm not even sure if that's possible to do...

Here's the fix for the new firmware CFA-835 LCD: http://www.aida64.com/downloads/latesta64xebeta

Thank you for the feedback

No, I'm a real person, just like Siri And sadly, I cannot reply everyone as soon as I'd want to... I'm glad you've managed to solve it. Sometimes things are easy, but not obvious. And we cannot possibly wire everything to the user interface without making it unusable

There's no way to do that automatically, from AIDA64. What you can do however is: 1) Close AIDA64 2) Save your AIDA64.INI file (backup) 3) Open AIDA64.INI file in Notepad or another text editor of your choice 4) Replace all occurences of HWMonLCDItemLgQ1 with HWMonSPItem 5) Save the changes, and start AIDA64. Enable the SensorPanel, and see if it look as intended. You may have to adjust the SensorPanel size to 320x240 pixels. Please note that the above explained steps will only convert the 1st Logitech G19 LCD page to SensorPanel. Also note that any existing SensorPanel items will also be kept, so before step#1 above, you may want to clear all SensorPanel items first. I hope it helps Regards, Fiery

You can set it in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Update Frequency.

It seems the problem is that AIDA64 handles CFA835 LCDs following the first spec issued for the display, based on firmware rev 0.1. We'll also update our CFA835 device to firmware rev 0.6 and adjust the LCD module to fit the major changes that the latest CFA835 firmwares introduced. I'll soon send you a new AIDA64 beta to try

We've tried in on our CFA835, and it works fine. If you delete all items on all 4 pages, and press the Apply on the Preferences window, will it display the splash screen? If not, try to adjust the contrast again, maybe it will help.

The mentioned update about handling the CFA-835 LCD has been implemented in the latest AIDA64 stable release we've rolled out today: http://forums.aida64.com/topic/2583-aida64-v470-is-out/

The new AIDA64 release introduces support for 33 new LCD and VFD screens, adds support for parallel and serial port connected displays, and improves the handling of monochrome and Razer SwitchBlade UI devices. It also provides CUDA 6.5, Mantle and OpenGL 4.5 diagnostics for the latest AMD and nVIDIA graphics accelerators, and supports several new SSD devices. New features & improvements - Support for new LCD and VFD devices: Acer Idea 500, Adafruit, Aquaero, AX206, BWCT, CH424, Crystalfontz, ct-Mausekino, Cwlinux, Dangerous Prototypes HD44780, Futaba DM-140GINK, Futaba MDM166A, GLCD2USB, IkaLogic, LCDInfo USB13700, LCDInfo USBD480, LPT, Matrix Orbital LK RS232, Matrix Orbital GLK RS232, Odroid-Show, Phidget, picoLCD, POS, Pyramid, Roccat Valo, Samsung SPF, SoundGraph iMon LCD, SpikenzieLabs MPTH, Sure Electronics, Trefon, USB2LCD+, Wallbraun LUI, Yoctopuce - Microsoft Windows 10 Technical Preview and Windows Server 2015 Technical Preview support - Advanced support for Razer SwitchBlade UI LCD - Support for LGA2011-v3 motherboards - CUDA 6.5, OpenGL 4.5 support - AData SP610, AData SP910, Corsair Force LX, Corsair Neutron, Corsair Neutron GTX, OCZ Arc 100, Seagate 600, SanDisk Extreme Pro, SanDisk X300s SSD support - GPU details for AMD Radeon R9 285 - GPU details for nVIDIA GeForce 900 Series What's new since AIDA64 v4.00 - Microsoft Windows 8.1 Update 1 and Windows Server 2012 R2 Update 1 support - OpenCL GPGPU Benchmark Suite - AMD Mantle graphics accelerator diagnostics - Multi-threaded memory stress test with SSE, SSE2, AVX, AVX2, FMA, BMI and BMI2 acceleration - Optimized 64-bit benchmarks for AMD “Kaveri”, “Bald Eagle”, “Mullins”, “Beema” APUs - Optimized 64-bit benchmarks for Intel Atom C2000 “Avoton” and “Rangeley” SoC - Optimized 64-bit benchmarks for Intel “Bay Trail” desktop, mobile and tablet SoC - Full support for the Intel “Haswell Refresh” platform with Intel “Wildcat Point” PCH - Support for new LCD and VFD devices: Abacom (ExpertProfi), AlphaCool, Digital Devices, LCD2USB, Mad Catz Venom, Matrix Orbital LK, Matrix Orbital GLK, Matrix Orbital GX, nMedia Pro-LCD, Pertelian X2040, SDC Megtron, SoundGraph iMon VFD, VL System LIS, VL System LIS 2 - Improved support for Intel "Broadwell" CPU - Preliminary support for AMD "Carrizo” and "Toronto" APUs - Preliminary support for Intel Quark X1000 “Clanton” SoC - Preliminary support for Intel "Skylake", "Cherry Trail", "Denverton" CPUs - Improved support for Intel “Haswell-E” CPU and DDR4 memory modules - Support for DDR4 XMP 2.0 memory profiles - Intel H97 and Z97 chipset based motherboards support - Socket AM1 motherboards support - SMTP SSL support - Improved handling of XSL files - Revamped Direct3D Compute Shader devices enumeration - CUDA 6.0, OpenGL ES 3.1 support - Improved support for OpenCL 2.0 - Support for VirtualBox v4.3 and VMware Workstation v10 - A-Data SP920, Crucial M550, Intel 730, OCZ Vector 150, OCZ Vertex 460, Plextor M6M, Plextor M6S, Samsung 845DC Evo, Samsung 850 Pro, Samsung XP941 SSD support - GPU details for AMD Radeon R5, R7, R9 Series - GPU details for nVIDIA GeForce 700 and 800 Series [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v4.70 ] [ Download ]

AFAIK your motherboard is unable to measure those voltage rails. Please don't mix voltage setting and voltage measurement. If you set those voltages to a specific value, and your BIOS Setup shows that value mixed with the actually measured voltage values, it may seem like it is actually measuring those values, while it doesn't. Regards, Fiery

In case the missing temperature was something meaningful and important when overclocking or tuning your system, Gigabyte would show it as a PWM or VRM temperature in the UEFI Setup and in their software as well. To me it doesn't make much sense to go to lengths in implementing a hardware temperature sensing logic, to assign valuable space on the motherboard PCB for connecting an external temperature sensor to the sensor chip, and then not showing he measured value on the user interface.

It's due to a bug about contrast adjustment: AIDA64 sets the contrast in a way that even the maximum contrast is lower than the visible range of contrast of CFA835. It will be fixed in the next AIDA64 beta update due in a few days from now. I'll post a message in this topic once the new update is available for download.

No problem, I suppose you've upgraded to the latest AIDA64 beta that already implements support for GeForce GTX 970 and GTX 980 Regards, Fiery

CPU-Z may report CPU VID as Vcore. Please compare AIDA64 readings against HWiNFO64 or Asus AI Suite instead

1) What is the file size of the Strike7API.dll file you've copied into AIDA64 installation folder? 2) Have you tried it with the latest AIDA64 beta update as well? http://www.aida64.com/downloads/latesta64xebeta

1) We'll fix the fan labels in the next AIDA64 beta update. 2) AIDA64 reports the actual Vcore, while CPU-Z reports the CPU VID. 3) CPU temperature and CPU Package temperature may or may not match. It's due to the difference in measurement methodology, you don't have to adjust any of those values. 4) Unidentified temperature readings can only be added if your motherboard also shows those values in the UEFI Setup or Gigabyte's own monitoring software. Otherwise, those values could well be just bogus readings, invalid values, or unconnected sensor chip wires. Regards, Fiery

We'll check that And keep posting any issues or ideas. I cannot promise you that we can fix every issues, or that we can implement everything you come up with, but we will do our best to improve AIDA64

It should be able to show that information, unless the video adapter is in deep sleep mode. In your case I suppose the secondary video adapter (nVIDIA) only wakes up when AIDA64 starts up, and then goes back to sleep, and wakes up again only when you start a graphics-intensive application like a 3D game. Try to start AIDA64, and go immediately to the Display / GPU page, and check if the clocks are reported for the nVIDIA GPU. And then watch if it goes to sleep, and the clocks disappear or turn to zero. If the clocks stop showing a meaningful value, it means your nVIDIA video adapters went to sleep (to save battery power).

Try to enable the option Wake GPUs up at AIDA64 startup in AIDA64 / main menu / File / Preferences / Stability. Restart AIDA64 after altering that option. It should help to monitor both GPUs properly. Regards, Fiery

It's not quite that easy I'm afraid. You could sync a photo to your phone, but that means writing 2 or 4 MegaBytes of data two times a second to the flash memory of your mobile device. It would quite quickly exhaust the flash memory write cycles and render your device useless, so you have to avoid that. The data -- whether it is a bitmap or a bunch of descriptors about the image -- has to stay in memory, and that's why any existing apps wouldn't work.