Frequently Asked Questions


  • x86 CPU with SSE2 support (Intel since Pentium 4, AMD since Athlon64 and Opteron)
  • High Precision Event Timer (HPET) available and enabled in BIOS
  • ACPI PM Timer available and exposed through ACPI tables

Operating System

  • Windows 7 or later
  • Windows Management Instrumentation (WMI) service enabled
  • Antivirus settings might need to be adjusted (Windows Defender should be fine, otherwise consider disabling Realtime Protection and exclude the install from scanning)
  • No virtualization/Virtual machines allowed. The exception is the presence of a running Hyper-V hypervisor (for WSL for example).
  • Kernel Debugging disabled

Always use the online installer if the system you are benching is connected to the internet. It is faster by a lot and you uncheck benchmarks that you don't need and they won't get downloaded.

If you are only benching offline, the offline installer is for you. You will download all currently supported benchmarks, tools and prerequisites, but can decide which ones you really want to install. The installation will be slower and use more space than the online installer, because all of the installer's compressed data is copied as well to create a local repository. This is necessary to update or change the installation later.

Even if you are benching offline, you can consider BenchMate's portability to transfer your online installation by just copying the BenchMate directory.

Yes, every version of BenchMate is portable. You can copy the installation directory to another system at any time.

Even the installer (maintenancetool.exe) will work properly on another system, although you will not see a propery entry in the "Apps and Features" tab of Windows.

Known common errors in our client normally provide an error message with one or more recommended solutions. Please read the message carefully.

If you can't find a solution on your own and this FAQ doesn't help either, it's time to get in touch with us. We are providing support on the following channels:

You are probably using an old BenchMate version, that we don't support anymore. Sadly versions prior to BenchMate 0.10.7 can not display the specific web application error returned by the bug report interface.

In any case, please update BenchMate to its latest version. We can not support every old version out there, so if you contact us, we would probably ask you to update anyways.

If the error still persists on the latest version of BenchMate, please get in touch with us:

Yes, you can.

The result data is located at C:\Your\BenchMate\results. Just copy all result files to the same directory in your new BenchMate installation. You will need to restart BenchMate to reload the result list.

The configuration file is located at C:\Your\BenchMate\config.json. Make sure that BenchMate is not running so the source configuration file is up-to-date and the destination file is not overwritten again.

No, it is certainly not (if you have downloaded it from this website).

The technology we are using for BenchMate is very close to software that would normally be used for malicious intent. The same is true for Antivirus itself by the way. The difference is how code like this is used. We are monitoring and protecting benchmark processes as well as protecting BenchMate itself from being tampered. These patterns are well known and are therefore detected by Antivirus software as a false positive.

If you have troubles with your Antivirus software, please consider excluding BenchMate's installation directory from scanning. Windows Defender should be fine though and is thoroughly tested with each release.

BenchMate does not allow any tampering of the executable's process memory. If write access is detected, the benchmark process is locked and you will not be able to create results. This is a security feature.

We have seen this error with various realtime protection features of Antivirus software. For example if you are using F-Secure, you need to disable DeepGuard.

We do not recommend using realtime protection while benchmarking due to its impact on the performance of your system. Windows Defender should be fine though and is thorougly tested with each release.

To fix this warning you will have to setup the timer in BenchMate manually. Right-click the affected GPUPI version in the BenchMate client's launchpad, go to "Options/Tweaks", "Timer Emulation" and select "Driver". GPUPI will now use HPET by default.

This warning should only happen with GPUPI 2.3.4 or yet untested hardware, because the automatic Timer Emulation of BenchMate is not working properly.

Windows apps run in a sandbox with special security restrictions and can therefore not be guarded by BenchMate. Use the bundled versions of CINEBENCH from BenchMate's installer.

We do not recommend to run Windows app versions of benchmarks in general, because the sandbox can have an impact on performance.

You can open a benchmark application immediatly after the client is shown, but you can't start a benchmark run before the client (and sensor service) was successfully initialized. That's when the big icon in the client turns from gray to yellow.

The reason you need to wait is that we are initializing HWiNFO in the client which can take a while before it is ready. Without HWiNFO we can't measure your sensors and without the sensors we can't validate your run. So please be patient, launch the benchmark but wait for the big yellow icon before you actually start the run. We are looking for ways to improve this in upcoming versions.

The hotkey F6 allows you to save the last result that was produced. If you are starting other applications after the result was captured, they will get internally selected as the last benchmark that is active. They don't have a result to save, so that's why the error pops up.

We are working to improve the handling for the hotkey to always select the right result. As a workaround please select the result to save manually in the client.

This happens when you downloaded GPU-Z manually and you are trying to add it using the "+" button in the client. The GPU-Z executable has its version in its executable name (for example: GPU-Z.2.36.0.exe) and is therefore not recognized. Rename it to "GPU-Z.exe" and it will work.

As the latest GPU-Z is bundled with BenchMate it's best to just install or add it with BenchMate's installer.

Yes. Starting with BenchMate it is allowed to have Hyper-V enabled and running. Scores made within a Hyper-V virtual machine will be flagged as invalid though.

Virtual machines, or to be precise the underlying hypervisor, can mock calls to CPU registers which may influence the hardware detection and timer skew measurements. To preserve our high standard of validation we therefore disallow the use of virtualized environments.

The only exception is currently the presence of an enabled Hyper-V hypervisor, which is necessary to run WSL or other development-specific virtualization.

The developer of Geekbench doesn't want his benchmarks integrated and threatened with legal action. We will continue to look into the situation and are open to resolve the dispute at any time. Our vision is to support all benchmarks of interest with our common validation standard.

BenchMate 0.9.3 is the last known version to run Geekbench 3, 4 and 5. We do not provide a download for this version nor do we offer support. Old BenchMate versions can only be installed and used in parallel with BenchMate 0.10.6 or higher.

The FAQ is work in progress. Please be patient while we add more content in the next few weeks.

Your questions wasn't answered?

Join us on Discord. We have our own area in the well-frequented official HWBOT channel.

Join Discord