Frequently Asked Questions

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

To be sure to have all dependencies installed (ie: KB4474419 and SSL root certificates) as well as propery entry in the "Apps and Features" tab of Windows, please use the installer.

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 10.10 can not report a bug.

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.

Your configuration files are located in BenchMate's root path: C:\Your\BenchMate\. Make sure that BenchMate is not running so the source configuration file is up-to-date and the destination file is not overwritten again.

• Since BenchMate 10.10: cient.json and app.json (app settings)
• Old versions: config.json

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.

This was necessary due to the complex ways to read bus frequency on all AMD Zen generations. In some cases the readout has to fall back to reading the CPU's LAPIC timer, which is error-prone especially on high load scenarios. So starting with HWiNFO 7.30 (and BenchMate 10.12) a bus frequency derived from the LAPIC tiemr is only read once during initialization to avoid irregular values. That means any bclock changes between BenchMate's initialization and the end of a benchmark run will not be reflected in the bus-dependent frequencies shown on the result dialog.

We mitigated the problem with two new features. At HWiNFO init we read the bus detection method to know if the bus clock will be unreliable. In addition we check the LAPIC timer between init and the end of a run and if a skew of more than 0.2% is detected, all bus-dependent clocks will be marked as "unreliable" and a warning appears on the bottom of the result dialog. 0.2% is the equivalent of 10 MHz on a 5000 MHz core frequency.

For us it is always important to show reliable information and communicate edge cases as good as possible. The new bus frequency reliability check lets you know, when AMD Zen frequencies are not to be taken for granted.

To get reliable frequencies derived from the bus, we ultimately need a solution from AMD.

The name is derived from the well-known Copy Waza tweak. You need to move files with specific file sizes between hard drives to reduce the usage of System Cache in Windows. This clears reserved memory blocks by the OS and helps to speed up allocations on the heap and fits more reads and writes into the File System Cache. At least that's our best bet to understand the additional gains of this tweak.

It turns out that our RAMDisk AWE tweak's performance is also susceptible to problematic System Cache states. After a few runs and reboots, 32M results started to deteriorate. More research revealed a problem with the memory layout being prefilled by the OS to improve daily performance. And yet again, Copy Waza helped to mitigate the problem.

To avoid having to implement strange copy patterns no one every fully understood, we found a new way that has an even better impact. As this is a big shortcut to the original Copy Wazaa, we are simply calling it "Sloppy Wazaa". By enabling this tweak the Wazaa will be invoked on the launch of the Super PI process. If you feel that runs are getting slower, just close Super PI and reopen it again.

Installing BenchMate 0.10.8 or higher will automatically fix this problem by advertizing a higher QPC frequency so BenchMate thinks HPET is enabled. Internally it's just another scaling factor.

For older versions of BenchMate you can fix this warning by setting the timer for GPUPI manually in BenchMate. 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 can only work for GPUPI 3+ due to technical reasons.

If you are on X58 or any other legacy platform, search for a BIOS option to enable ACPI 2.0.

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 immediately 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.

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 0.10.7.1 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.

1. On the Start menu, select Run. In the Open box, type gpedit.msc. If you don't have the group policy editor (gpedit.msc) installed in your OS, check this FAQ entry on how to download and install it.
2. The Group Policy dialog box opens.
3. On the Local Group Group Policy console, expand Computer Configuration.
4. Expand Windows Settings.
5. Expand Security Settings.
6. Expand Local Policies.
7. Select the User Rights Assignment folder. The policies will be displayed in the details pane.
8. In the pane, scroll to and double-click the "Lock pages in memory" policy.
9. In the Local Security Policy Setting dialog box, select "Add User or Group..." and add the user you have logged on with into the object textarea.
10. Click on "Check Names" to verify that this user exists. Click "Ok".
11. Now click "Apply" and you should see your username next to the "Lock pages in memory" policy.
12. On some Windows versions you need to REBOOT before the policy is finally applied.

There are other ways to enable SeLockMemoryPrivilege, for example:

• Using ntrights.exe (Source)
• Using secedit or existing Powershell scripts that use secedit to change group policies (Source 1, Source 2)

If you have a Windows Home edition or stripped your OS of the group policy editor, you can download it using the following commands in command window using admin privileges:

FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~\.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")*

FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~\.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")*

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.