Fiery

Once you enable Fraps or RTSS to measure the FPS, a new item for either of them would appear in the list of sensor items in AIDA64. Just enable the new item, and you're good to go.

Don't worry, we'll add those to the reference list of benchmarks soon. Our Ryzen 7 test system died (got EC/BIOS bricked) just minutes before we could perform a reference benchmark run on it while preparing for the latest AIDA64 v5.90 stable release Regards, Fiery

On the GPGPU Benchmark panel we detect GPU properties using OpenCL. That API may not provide the correct information, especially on Intel iGPUs. On the Display / GPU page we collect the same details using hardware detection and an internal hardware database. Those information should be 100% accurate, regardless of the video driver or its OpenCL layer.

Maybe the BIOS configures the RAPL parameters incorrectly. Please try to apply an offset of 0 and a ratio of 100 (100x multiplier) in AIDA64 / main menu / File / Preferences / Hardware Monitoring / Correction on the CPU power measurement. Let me know if it works out. If not, maybe a ratio of 128 would work out?

Try to remove AIDA64.EXE as well, restart Windows, and try to install it again. Something got stuck about the kernel driver on your system.

The new AIDA64 release implements optimized benchmarks for AMD Ryzen “Summit Ridge” and Intel “Apollo Lake” processors, supports the upcoming Microsoft Windows 10 Creators Update as well as the latest graphics and GPGPU computing technologies by both AMD and nVIDIA. New features & improvements - AVX2 and FMA accelerated 64-bit benchmarks for AMD Ryzen “Summit Ridge” processors - Microsoft Windows 10 Creators Update support - Optimized 64-bit benchmarks for Intel “Apollo Lake” SoC - Improved support for Intel “Cannonlake”, “Coffee Lake”, “Denverton”, “Kaby Lake-X”, “Skylake-X” CPUs - Preliminary support for AMD Zen server processors - Preliminary support for Intel “Gemini Lake” SoC and “Knights Mill” HPC CPU - NZXT Kraken X52 sensor support - Socket AM4 motherboards support - Improved support for Intel B250, H270, Q270 and Z270 chipset based motherboards - EastRising ER-OLEDM032 (SSD1322) OLED support - SMBIOS 3.1.1 support - Crucial M600, Crucial MX300, Intel Pro 5400s, SanDisk Plus, WD Blue SSD support - Improved support for Samsung NVMe SSDs - Advanced support for HighPoint RocketRAID 27xx RAID controllers - GPU details for nVIDIA GeForce GTX 1080 Ti, Quadro GP100, Tesla P6 What's new since AIDA64 v5.00 - AVX and FMA accelerated FP32 and FP64 ray tracing benchmarks - Vulkan graphics accelerator diagnostics - RemoteSensor smartphone and tablet LCD integration - Logitech Arx Control smartphone and tablet LCD integration - Microsoft Windows 10 TH2 (November Update) support - Proper DPI scaling to better support high-resolution LCD and OLED displays - AVX and FMA accelerated 64-bit benchmarks for AMD A-Series “Bristol Ridge” and “Carrizo” APUs - AVX2 and FMA accelerated 64-bit benchmarks for Intel “Broadwell”, “Kaby Lake” and “Skylake” CPUs - AVX and SSE accelerated 64-bit benchmarks for AMD “Nolan” APU - Optimized 64-bit benchmarks for Intel “Braswell” and “Cherry Trail” processors - Preliminary support for AMD Zen APUs - Advanced SMART disk health monitoring - Hot Keys to switch LCD pages, start or stop logging, show or hide SensorPanel - Corsair K65, Corsair K70, Corsair K95, Corsair Strafe, Logitech G13, Logitech G19, Logitech G19s, Logitech G910, Razer Chroma RGB LED keyboard support - Corsair, Logitech, Razer RGB LED mouse support - Corsair and Razer RGB LED mousepad support - AlphaCool Heatmaster II, Aquaduct, Aquaero, AquaStream XT, AquaStream Ultimate, Farbwerk, MPS, NZXT GRID+ V2, PowerAdjust 2, PowerAdjust 3 sensor devices support - Improved Corsair Link sensor support - NZXT Kraken water cooling sensor support - Corsair AXi, Corsair HXi, Corsair RMi, Enermax Digifanless, Thermaltake DPS-G power supply unit sensor support - Support for Gravitech, LCD Smartie Hardware, Leo Bodnar, Modding-FAQ, Noteu, Odospace, Saitek Pro Flight Instrument Panel, Saitek X52 Pro, UCSD LCD devices - Portrait mode support for AlphaCool and Samsung SPF LCDs - SensorPanel and LCD: right-to-left bars, static label control strings - 0.01 Celsius temperature measurement resolution for select sensor items - System certificates information - Support for LGA-1151 motherboards - Support for USB 3.1 peripherals - Extended ACPI table decoding - Advanced support for Adaptec and Marvell RAID controllers - Autodetect information and SMART drive health monitoring for Intel and Samsung NVMe SSDs - ACPI 6.1, CUDA 8.0, OpenCL 2.1, OpenGL ES 3.2, SMBIOS 3.0, VirtualBox v5.0 support - Corsair Neutron XT, Crucial BX100, Crucial BX200, Crucial MX200, Kingston HyperX Predator, Kingston HyperX Savage, Kingston SSDNow UV300, Kingston SSDNow UV400, Lite-On MU II, OCZ Trion 100, OCZ Vector 180, Plextor M6V, Samsung CM871, Samsung PM851, Samsung PM871, SanDisk Ultra II, SanDisk X400, SanDisk Z400s, SK Hynix SC300 SSD support - Improved support for Intel NVMe SSDs - GPU details for AMD Radeon Rx 300, RX 400 and R9 Fury Series - GPU details for nVIDIA GeForce GTX 950, GeForce GTX 960, GeForce GTX 980 Ti, GeForce GTX 1000 Series, GeForce GTX Titan X, Quadro M3000M, Quadro M5000M, Tesla M60, Tesla P100 [ Press Release (English) ] [ Press Release (Deutsch) ] [ Press Release (italiano) ] [ Press Release (magyar) ] [ What's new in AIDA64 v5.90 ] [ Download ]

UPDATE: We have fixed #3, #4, #5 and #7 in the latest AIDA64 v5.90.4200 stable update, which is now 100% compatible with AMD Ryzen processors: https://www.aida64.com/downloads/latesta64xe

That's normal, since the classic Direct3D API only handles one 3D accelerator. It is extended to handle multiple adapters with Direct3D 10, and then Direct3D 12 revamped everything again. We haven't yet implemented 3 separate code paths for various Direct3D generations (D3D6/7/8/9, D3D10/11, D3D12), since these days AIDA64 users tend to prefer to focus on the direct GPU detection method (Display / GPU page in AIDA64).

The Dedicated Memory and Dynamic Memory information comes from Direct3D statistics API, which doesn't properly support over 4GB video memory under Windows 7. It was fixed by Microsoft in Windows 8, by extending the counters from 32-bit to 64-bit. You may want to check the Used Video Memory and Free Video Memory sensor items via OSD Panel or another hardware monitoring module of AIDA64. They should work better under Windows 7, since they use NVAPI.

Thank you for your kind words Have a great week!

Do you mean you cannot see the buttons next to the LCD layout preview? Or you cannot even see the list of LCD items next to the preview? Either way, have you tried to resize the AIDA64 Preferences window?

We currently have no plans to localize the documentation, simply because it would be an enermous task to perform for all the 35 languages AIDA64 is localized to. And it will be an even more difficult task to keep the localized documentation up-to-date and accurate. We will however need to work on localizing the external modules of AIDA64 (e.g. CPUID Panel, Cache & Memory Benchmark Panel, System Stability Test, etc), as well as on completely revamping the current UI paradigm of our software. Stay tuned

Thank you, we'll look into this. Do you use 64-bit Windows 10 with latest patches applied?

Thank you. We'll add the missing temperature reading in the next AIDA64 stable update due in only 2 days from now

I'm not sure if you need to be as drastic as to reinstall the whole OS. But, it should help if you could completely remove both video drivers, find the latest version of both, and reinstall them. As for OpenCL, after removing both video drivers and if there's a remaining OpenCL.dll file, that file too... It may help to remove the traces of OpenCL from the Registry, by removing the following Registry entries and its sub-entries: HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenCL HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Khronos\OpenCL

That version measures Vcore by using the CPU VID. You can use the CPU VID reading with the latest beta too, if you reckon it's more accurate, more reliable or more stable than the real Vcore measurement.

You can use Fraps or Rivatuner Statistics Server (RTSS) to measure FPS and then display it on your Mad Catz keyboard LCD via AIDA64.

Just by removing OpenCL.dll you cannot reset the whole OpenCL stack. The actual OpenCL driver is not in the file OpenCL.dll. That file is just a platform passthrough module that calls the other OpenCL platform drivers made by AMD, Intel or nVIDIA.

We have exactlyone app per platform One AIDA64 for each platform, but no multiple apps for any platform (yet).

We've checked, and AIDA64 definitely puts +5V voltage reading into the shared memory. So I assume it was a temporary glitch in Aquasuite.

Thank you. We're not planning to give up on any of our existing six AIDA64 mobile apps

If it crashes with both Intel and nVIDIA GPU, then it can be the OpenCL platform that's got corrupted somehow. Maybe by uninstalling both video drivers and reinstalling them would help. I'm not sure if there's an OpenCL driver scrapping/repair tool -- that certainly would help in this particular case...

Thank you for the data. Do you have Asus AI Suite installed?

It means the OpenCL layer of your video card driver crashes when AIDA64 tries to create an OpenCL compute context. Try to update the video drivers, it should help to fix this up. Regards, Fiery

Thank you, we will fix the issues in the next AIDA64 update due next week Regards, Fiery