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

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.