Troubleshooting My Results

When you upload or view a result, at times you may notice a box at the top of the page indicating that there is something wrong with your result. Don’t Panic. Possible messages include:

  • Graphics driver is not approved.
  • The physics score is invalid. PhysX GPU acceleration used.
  • Benchmark tessellation load modified by AMD Catalyst driver, result invalid.
  • Unable to verify AMD Catalyst tessellation setting, result invalid.
  • This result is invalid as Virtu MVP HyperFormance was enabled. Please turn off Virtu MVP and re-run the benchmark.
  • This result is invalid as we were unable to determine your Lucid Virtu MVP settings. Your Virtu MVP software may be an older version, please check for updates from Lucidlogix.
  • This result is invalid as we were unable to determine your Lucid Virtu MVP settings. Please install the latest version of SystemInfo from our website and re-run the benchmark. Your Virtu MVP software may also be an older version, please check for updates from Lucidlogix.
  • There was an unexpected problem detecting Virtu MVP HyperFormance settings.
  • Processor is not recognized.
  • Graphics card is not recognized.
  • SystemInfo scanning was not enabled for this benchmark run. Please enable SystemInfo from benchmark settings and run re-run the benchmark.
  • There was a problem parsing the Futuremark SystemInfo data. Please contact Futuremark Support and include a link to this result.
  • Non default settings were used in benchmark. Score could not be computed / Result is not comparable to other results.
  • Time measuring inaccurate.
  • Result is invalid, status: (status code number)

The practical drawbacks of non-validated results are fairly minor. Such results will not be shown on Futuremark benchmark leaderboards and they cannot participate in any benchmarking contests we run from time to time. Non-validated results might also be unsuitable for comparisons between different hardware – you should determine why exactly the score wasn’t deemed valid.

Graphics driver is not approved

This message is displayed if your benchmark result was obtained using a set of graphics card drivers that are not (yet) approved by Futuremark.

In order to ensure that drivers do not breach our Driver Approval Policy, Futuremark tests video drivers and validates the results. Drivers are sent for testing and approval as soon as they are published but this process takes some time – usually between one and two weeks. Any results uploaded during this time initially shows as “not approved” but will turn to approved results when the driver approval process is complete for the specific driver version – you do not need to do anything, your result will transform into approved result in time.

Results obtained using beta, “hotfix” or otherwise non-WHQL drivers will also show this message and normally non-WHQL drivers are not approved for use with our benchmarks unless specifically requested by the graphics card vendor.

If there are no WHQL certified drivers yet for your video card/chip – usually if you buy your hardware right after they become available – you will have to wait until the first WHQL approved drivers with support for your card are made available for valid results. You can benchmark even with beta drivers – the results just won’t be certified as valid and the result page will show that the drivers are not approved.

More information on driver approval and currently approved drivers

The physics score is invalid. PhysX GPU acceleration used

This message can appear only with 3DMark Vantage results and it means your benchmark run was done with PhysX GPU acceleration (running PhysX on NVIDIA video card). This is against the driver approval policy as the physics test cannot run on the GPU or the score for that test is considered invalid. You can fix this issue by selecting “Disable PPU” in benchmark settings or by disabling GPU PhysX in NVIDIA driver options and then re-running the benchmark. This does affect the score but it is required for a score that can be compared to hardware from other vendors.

Benchmark tessellation load modified by AMD Catalyst driver, result invalid.

This message can appear only with 3DMark 11 results from systems using ATI/AMD video cards. It appears when the benchmark run was done with non-default Tessellation Controls in AMD Catalyst control panel, modifying the tessellation workloads and invalidating the result for benchmark comparison purposes.

By default, AMD Catalyst control panel is set to “AMD Optimized”, tessellation is unmodified unless a specific application is detected. 3DMark 11 will not trigger a modified tessellation profile as doing so would be against Futuremark driver approval policy. This is the approved method for benchmarking ATI/AMD DirectX11 video cards with 3DMark 11, any other setting of Tessellation Controls will invalidate the result.

To correct this error, return Tessellation Controls to default in AMD Catalyst control panel and re-run benchmark.

Unable to verify AMD Catalyst tessellation setting, result invalid

This message can appear only with 3DMark 11 results from systems using ATI/AMD video cards. It appears when the benchmark run was done with too old SystemInfo module and there is no way to verify if AMD Catalyst Tessellation Controls were modified for the benchmark run. Most likely the result is comparable with other scores, but there is unfortunately no way to tell.

This error should appear only with old benchmark results submitted prior to the introduction of Futuremark SystemInfo 4.2. To correct the problem, update SystemInfo module to the latest available and re-run benchmark. Latest SystemInfo installer can be found here.

This result is invalid as Virtu MVP HyperFormance was enabled. Please turn off Virtu MVP and re-run the benchmark.

This message can appear only with motherboards that support Lucidlogix Virtu MVP HyperFormance technology. HyperFormance modifies the rendering in Futuremark benchmarks in a way that makes the score unsuitable for comparing system performance with results that do not use it. You should disable HyperFormance in Virtu control panel and re-run the benchmark to get a score that can be used for comparisons.

Scores obtained with HyperFormance enabled are not accepted for Futuremark Hall of Fame and cannot participate in any benchmarking contests run by Futuremark.

This result is invalid as we were unable to determine your Lucid Virtu MVP settings. Your Virtu MVP software may be an older version, please check for updates from Lucidlogix.

This message can appear only with motherboards that support Lucidlogix Virtu MVP HyperFormance technology. HyperFormance modifies the rendering in Futuremark benchmarks in a way that makes the score unsuitable for comparing system performance with results that do not use it.

In order to detect if HyperFormance was enabled or not, Virtu MVP software must be updated to a version that includes support for detecting the settings that were used. It is possible that a result showing this problem may be comparable but unfortunately there is no way to tell. Contact Lucidlogix for updated version of Virtu MVP software or uninstall Virtu MVP before re-running the benchmark.

This result is invalid as we were unable to determine your Lucid Virtu MVP settings. Please install the latest version of SystemInfo from our website and re-run the benchmark. Your Virtu MVP software may also be an older version, please check for updates from Lucidlogix.

This message can appear only with motherboards that support Lucidlogix Virtu MVP HyperFormance technology. HyperFormance modifies the rendering in Futuremark benchmarks in a way that makes the score unsuitable for comparing system performance with results that do not use it.

In order to detect if HyperFormance was enabled or not, SystemInfo needs to be updated to version 4.8 or later. Latest SystemInfo module is available here.

Additionally, Virtu MVP software must be updated to a version that includes support for detecting the settings that were used. It is possible that a result showing this problem may be comparable but unfortunately there is no way to tell. You may need to contact Lucidlogix for updated version of Virtu MVP software or uninstall Virtu MVP before re-running the benchmark (in addition to updating the SystemInfo module).

There was an unexpected problem detecting Virtu MVP HyperFormance settings. Please contact Futuremark Support and include a link to this result.

This is an error message that indicates a problem with detecting Virtu MVP HyperFormance status. Your result would appear to indicate the presence of Lucid MVP software but for some reason we could not figure out if HyperFormance is on or not. Normally you should never see this message – if you are getting this and re-running benchmark does not resolve the issue, please contact us and include a link to the result that has this problem.

Processor is not recognized or Graphics card is not recognized

Both messages indicate that some part of your system was not properly identified by SystemInfo. If you have the latest SystemInfo module installed (available here) then the most likely cause is that your hardware is very new and not yet known to 3dmark.com. If this is the case, please contact us either through Futuremark Product Support on GetSatisfaction or through Futuremark Forums. Remember to include a link to your result that is showing the issue and include details about your hardware configuration (if known).

SystemInfo scanning was not enabled for this benchmark run. Please enable SystemInfo from benchmark settings and run re-run the benchmark.

This means that SystemInfo module was disabled for the run, most likely on purpose. Results can’t be validated without the SystemInfo data that describes the hardware configuration and system settings used.

There was a problem parsing the Futuremark SystemInfo data. Please contact Futuremark Support and include a link to this result.

This message should generally never happen but if it comes up, it means that the data gathered by SystemInfo module is somehow corrupt and we couldn’t properly parse it. Assuming you have not actively tampered with the SystemInfo scan data in the result file, you should definitely report this error to Futuremark Support and include a link to the result so we can investigate what is causing it to happen with your result.

Non default settings were used in benchmark. Score could not be computed / Result is not comparable to other results.

This warning comes up when you run the benchmark using custom settings or if a required test was not run. To ensure that there is no confusion as to what settings were used to obtain a 3DMark or PCMark overall score, such a score can only be computed from runs done using a default preset. 3DMark scores get a prefix based on preset to specify the settings used (X = Extreme, H = High (3DMark Vantage Only), P = Performance, E = Entry).

3DMark and PCMark Advanced and Professional Edition benchmarks offer a wide range of options to customize a benchmark run for detailed investigation of system performance but results from such custom runs could be misleading as the results are not comparable with results from other systems unless exact same settings are used in both cases.

Usually custom runs are used for investigating how performance of a single system configuration changes when varying the benchmark load and for this purpose comparison is still possible by directly comparing scores from individual tests (like Graphics Score and Physics Score in 3DMark 11).

Time measuring inaccurate

This message indicates funny business with the system clock during benchmark run. In most cases, this means that, no, you cannot cheat in 3DMark by adjusting Windows timers during benchmark run or otherwise tampering with the measurements done by the benchmark. If this message persists and you have not done anything out of the ordinary, it may indicate a hardware issue with the real time clock of your system or a presence of a background program that somehow twists the time-space continuum of your operating system in such a way that this anti-cheat detection is tripped.

Result is invalid

This message appears if your result was otherwise deemed invalid. Usually this indicates a corrupt or tampered result file or tampered benchmark executable. If the problem persists, contact Futuremark support with as much detail as possible.