Fiery

The new release comes with support for a wider range of external LCD and VFD displays, including alphanumeric, monochrome and color panels, on which AIDA64 can directly display temperatures, voltages and fan speeds as well as other system information. The July update also introduces support for the latest and upcoming processor and graphics technologies and storage devices. New features & improvements - 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 - Advanced support for monochrome LCDs - SMTP SSL support - Improved handling of XSL files - OpenGL ES 3.1 support - Revamped Direct3D Compute Shader devices enumeration - Plextor M6M, Plextor M6S, Samsung 845DC Evo, Samsung 850 Pro SSD support - GPU details for Mobile AMD Radeon R9 Series, FirePro W8100 - GPU details for nVIDIA GeForce GT 730, Quadro K2200M 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 - Razer SwitchBlade LCD support - 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 - CUDA 6.0 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, 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) ] [ Press Release (Русский) ] [ Press Release (český) ] [ Press Release (polski) ] [ What's new in AIDA64 v4.60 ] [ Download ]

We've checked, and unfortunately Microsoft doesn't offer a method to verify whether an instance of the gadget is already running on your desktop. The interface itself claims that only one instance can be run at any given time, but in your case it seems things work a bit different for some odd reason. http://msdn.microsoft.com/en-us/library/windows/desktop/dd378390(v=vs.85).aspx We'll have to do more test runs and come up with a workaround (or a new option in the AIDA64 Preferences) to fix the issue that you're experiencing. I'll let you know in this topic once we've got a resolution. Thank you for your patience. Thanks, Fiery

1) We've implemented a workaround for the CPU multiplier decimal digits issue. It will round the values on Intel Nehalem family (Bloomfield, Nehalem-EP, Clarkdale, Arrandale, Lynnfield, Clarksfield, Gulftown, Westmere, Sandy Bridge, Ivy Bridge, Haswell, Crystal Well, Broadwell, Skylake, etc) and Intel Silvermont family (Bay Trail, Avoton, Rangeley, Cherry Trail, Denverton, etc) processors. The fix will be rolled out with the next AIDA64 update due in 3 days from now. 2) I'm not sure what you mean about that idea. Please explain with more details Thanks, Fiery

It means your system is not stable. You have to return to a more conservative overclocking/tweaking setting, or find out which hardware component causes the issues. Regards, Fiery

Th Please note that what you're experiencing is not what should happen -- it's not by design AIDA64 System Stability Test has got a lot checkpoints in it, and when it finds any unusual or unexpected results, it should report it and stop the test by changing the System Stability Test window to red colour (indicating an error). What you're experiencing however looks more like if the Stability Test background process was crashed, before it could detect the issue. In many cases a BSoD, system lockup or unexpected system restart (reset) comes before the stress testing process could find an error.

Yes, they should work like that.

You can check the order of the CPU utilization readings and their relation to phyisical cores if you go to the Motherboard / CPU page, and scroll down to the bottom of the page. Under modern operating systems (Vista, Win7, Win8, Win8.1, etc) it usually alternates between physical and virtual cores. So first logical processor is first physical core, second logical processor is first virtual core, 3rd logical processor is 2nd physical core, 4th logical processor is 2nd virtual core, etc.

Okay, we'll work on it in August

Is the system in question overclocked or specially tuned? I'm just asking because if it is, then maybe the stress testing process simply dies because the system is unstable.

On the Computer / Sensor page only physical cores are listed. Please note that many processors use half-step multipliers like 20.5x, and some of them use even less round numbers like 1.75x. Regards, Fiery

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

What does the Task Manager (Performance tab) show about memory utilization once the AIDA64 System Stability Test gets into the dormant state? Is your system memory exhausted or there's plenty more left?

For Intel iGPUs it's not possible to measure iGPU utilization. What a Windows software could measure on Intel iGPUs is Direct3D utilization. Would it be something you would be interested in?

Are you using AIDA64 v4.50? (latest version)

iGPU utilization is already measured and shown for AMD and nVIDIA iGPUs. Do you have an Intel iGPU?

It is mandatory to install MySQL Connector/ODBC on each computer. Regards, Fiery

Before the new stable update is out, you can try the new option in the latest AIDA64 Extreme beta: http://www.aida64.com/downloads/aida64engineerbuild3046y3r8cmsztnzip After upgrading to this new version, make sure to restart Windows to finalize the upgrade. Let me know how it works Please note that after altering the new option (AIDA64 / main menu / File / Preferences / Hardware Monitoring / SensorPanel / Prevent SensorPanel from being minimized) you need to restart AIDA64 to apply the changes.

No, I'm afraid it's not possible with AIDA64. It's simply because the SensorPanel is a regular (standard) window that catches mouse clicks and processes them. Regards, Fiery

We're working on it It should be available before the end of July as a new stable update for AIDA64. I'll let you know in this topic once a new AIDA64 update with the requested feature is available for download.

We've added support for several Matrix Orbital USB character based and monochrome graphical LCD displays, including LK, MX, PK, VK, GLK, GLT, GX Typhoon, and their drive-bay and external variants as well. You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the appropriate Matrix Orbital USB LCD drivers installed, and the LCD to be connected to a USB port. You can verify if your device is supported by AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 0403-FA01 0403-FA02 0403-FA03 0403-FA04 0403-FA05 1B3D-011F 1B3D-0120 1B3D-0121 1B3D-0123 1B3D-0125 1B3D-0127 1B3D-012C 1B3D-0134 1B3D-013E 1B3D-013F 1B3D-0140 1B3D-0141 1B3D-0155 1B3D-0156 1B3D-0157 1B3D-0158 1B3D-015E 1B3D-0161 1B3D-016A 1B3D-016B 1B3D-016C 1B3D-0176 1B3D-017B 1B3D-01F0 1B3D-01F1 Due to their interface bottleneck BGK, EGLK, GLK and GLT displays perform display updates quite slowly, so visual discrepancies may be experienced when using the GLK (graphics) protocol on these displays. It is possible to use the LK (character based) protocol on GLK displays as well, which will work much faster. In order to switch between the GLK and LK protocols, you need to first disable the GLK protocol (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD), and then enable the LK protocol on the same page. Ignore the error, and restart AIDA64 to apply the switch. You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Abacom, AlphaCool, Digital Devices, LCD2USB, Mad Catz Venom, and SDC Megtron LCDs are also supported now by the latest AIDA64 beta. Regards, Fiery

We've added support for Digital Devices colour graphical LCD displays, e.g: http://shop.digital-devices.de/USB-Display-128x64-Entwicklerversion http://shop.digital-devices.de/USB-SideshowTouchDisplay-320x240-Entwicklerversion You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the appropriate Digital Devices LCD drivers installed, and the LCD to be connected to a USB port. You can verify if your device is made by Digital Devices by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs: 4243-EE09 4243-EE0A 23AE-EE09 23AE-EE0A 23AE-EE10 23AE-EE11 23AE-EE12 23AE-EE20 23AE-EE21 23AE-EE22 23AE-EE23 23AE-EE30 23AE-EE31 23AE-EE40 You can find the new AIDA64 beta update at: http://www.aida64.com/downloads/latesta64xebeta Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Abacom (ExpertProfi), AlphaCool, LCD2USB, Mad Catz Venom, Matrix Orbital, and SDC Megtron LCDs are also supported now by the latest AIDA64 beta. Regards, Fiery

Please let me know how the Megtron support and support for multiple AlphaCool displays worked out on your system

That must have been a hell of a job to compile those results. Thank you for posting them!

There's no setting in the BIOS Setup for that.

Try the following: 1) Close AIDA64 2) Start Registry Editor (press Windows key + R --> type in: REGEDIT.EXE --> press Enter) 3) Navigate to: HKEY_CURRENT_USER\Software\FinalWire\AIDA64 4) Delete the following entries in the right-side panel: SensorPanelPosX SensorPanelPosY 5) Also check that SensorPanelWidth and SensorPanelHeight contain meaningful values. 6) Start AIDA64 and see if the SensorPanel appears now or not. Let me know how it goes. Regards, Fiery