Fiery

Thank you for your understanding and cooperation about this issue. I forgot to mention that you should ask Amazon for a refund ASAP, but you already did, so all is cool

Yes, Amazon was selling pirate license keys via a fraudulent seller. We've already notified them about this issue, and they already removed the seller from their site. Our Sales Team will contact you about possible resolutions to resolve this issue. Regards, Fiery

Thank you for your idea. We currently have no plans to implement a 3D benchmark. We already have the GPGPU Benchmark module that offers various tests to benchmark the compute capabilities of any modern GPUs.

In case Asus finally implements the industry standard synchronization mutexes that AIDA64 and roughly a dozen other monitoring software already use for years, then we can add the missing temperatures. We've been pestering Asus about that issue for years, without luck so far though.....

Thank you for letting us know about the resolution. I've checked, and both our Win7 64-bit test systems had the TdrDelay value set to 30 seconds. So that explains everything We'll display a warning message when the value is set below 8 seconds in the Registry, and offer a quick fix.

You're right, it wouldn't need a http session. However, it would still require hammering the storage device with a new write operation every second or so. In the age of flash memory based devices, it's one of the worst solutions. Foobar needs to put that information into shared memory, it's a way better solution.

WATER_IN and WATER_OUT temperature cannot be monitored, since they would require EC (Embedded Controller) bank switching, which is a dangerous thing to do on Asus motherboards. Switching the EC bank could cause system instability or even lockup. WATER_FLOW fan header is monitored, but it will only appear in AIDA64 if you have a fan or pump connected to it.

Thank you. I'll let you know in this topic once we have a new beta update with NVMe RAID support.

R That solution would imply that we need to start a HTTP client session for the URL you've quoted. That's what I meant about quite complicated and overkill. If you open a new HTTP session once a second, that uses a lot of system resources.

PKEY.TXT is either saved into the installation folder of AIDA64; or into your Local AppData folder, under FinalWire\AIDA64 folder there. Example: C:\Users\<your username>\AppData\Local\FinalWire\AIDA64 You need to check if you have a PKEY.TXT file at either location, and remove them both. However, in case while you're entering your product key you immediately get an error message, it means the key you're trying to enter is not the new key, but your old key. If you want to verify your key, send it to me in private message, and I'll let you know when did you purchase that particular license.

It displays the FPS provided by Fraps or RTSS, simple as that. You need to make sure those software measure the value you want to be displayed via AIDA64

We've tested AIDA64 v5.90 on two Windows 7 64-bit SP1 based systems. One of them had a Gigabyte GV-N1060WF2OC-6GD video adapter, while the other had a Asus GT610-SL-1GD3 video adapter. They both used ForceWare 378.92 WHQL drivers. Both system ran the GPU subtest of the AIDA64 System Stability Test properly, and they also ran the GPGPU Benchmark suite properly. We've seen no crashes or other issues.

Enumerating members of NVMe RAID arrays is currently not supported by AIDA64. We'll work on it in the upcoming weeks. BTW, are those SSDs put into a Z270 or Z170 chipset based motherboard?

What version of Norton Security do you have installed? And under what version of Windows? Thanks, Fiery

You need to enter your new license key in AIDA64 / main menu / Help / Enter Product Key. If it still doesn't work after entering your product key, then close AIDA64, try to remove any instances of the file called PKEY.TXT from your system, and enter the key again. Let me know how it goes. Regards, Fiery

Thank you for your feedback

Great, thank you for your feedback AIDA64 is supposed to stop and unload its kernel driver before initiating the upgrade process, but sometimes it gets stuck in the deep "bowels" of the Windows driver stack

Thank you for your feedback

Most likely the Preferences window remembered an incorrect window size setting from a previous instance, and failed to resize itself automatically to fit the LCD preview properly. In such cases if you manually try to resize (or maximize) the Preferences window, it recognizes the issue and adjusts the window size properly.

If you can track the battery life via the manufacturer's supplied software, it doesn't mean the API for that is exposed to 3rd party software like AIDA64. LGS uses a proprietary interface to measure battery life for G533s, and only LGS can do that, we can not with AIDA64

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.