3DMark Vantage Support

3DMark Vantage FAQ

  • Start Here

    Before going any further, ensure that you have the latest version of 3DMark Vantage installed and update if necessary.

  • Is 3DMark Vantage compatbile with Microsoft Windows 8?

    Yes, but you need an update. See our Windows 8 information page for full details.

  • Is 3DMark Vantage compatbile with Microsoft Windows 7?

    Yes, 3DMark Vantage is fully compatible with Microsoft Windows 7.

  • When I click on the "Run Benchmark" button in 3DMark Vantage, the whole thing freezes during "Scanning System".

    Please verify that you have the latest version installed and update if necessary. If you are still getting a complete system hang during SystemInfo scan, ensure that HPET is enabled in your BIOS settings. SystemInfo requires HPET (High Precision Event Timer) to function. Also ensure that your motherboard BIOS is up to date.

    Alternatively this could indicate a problem with SystemInfo module that gathers data about the hardware configuration. Ensure that the SystemInfo module is up to date. There may be updates published after the latest benchmark installer was released.

  • The benchmark tests seem to run really slow and then the benchmark quits and I get a notification that says "Display driver stopped responding, but has successfully recovered." What does this mean and how can it be corrected?

    This message indicates that a "Timeout Detection and Recovery, (TDR)" has occurred during the benchmark run. The TDR is a feature of Windows Vista which helps to recover the system in case of possible display driver related problems are being detected. Depending on the system configuration and selected benchmark settings, the tests may run at such a slow frame rate that the operating system suspects that the display driver may have encountered problems and performs a driver reset. TDR's are more likely to occur with the High and Extreme presets and can occur with other presets and certain features tests as well, depending on your system configuration and selected benchmark settings. You can try to enable the "Flush on Low FPS" option in the benchmark settings, and try again. Microsoft has posted information on TDR and how to disable it, but it is not something we can recommend unless you are 100% sure what you are doing. The tutorial can be found here: http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

  • I ran 3DMark Vantage and got a score of P1020. What does "P" stand for?

    In 3DMark Vantage you get a letter with each 3DMark score. E = Entry preset, P = Performance preset, H = High preset and X = Extreme preset. This was done to differentiate the presets.

  • I purchased the Advanced Edition to benchmark my graphics card Anti-Aliasing performance. When I enable Anti-Aliasing in the settings, I get 0 3DMarks. Is it a driver issue or did I something wrong?

    3DMark Vantage outputs 3DMark scores only if you have selected a preset (entry, performance, high or extreme). If you select any settings outside the pre-defined presets, your preset is "custom" and no 3DMark score will be shown. You can use the graphics score to see the performance impact of Anti-Aliasing, or any other optional settings.

  • I submitted a result to 3DMark.com, but it says that my graphics driver is not approved by Futuremark. How can I get an approved driver?

    Please use one of the currently approved driver versions appropriate for your hardware configuration. You can find the list of approved drivers here: 3DMark Vantage Approved Drivers.

  • I'm getting an "Unable to locate component...PhysXLoader.dll was not found" error message when launching 3DMark Vantage, how can this be corrected?

    Please re-install 3DMark Vantage from the original installation package, this should correct the problem.

  • I receive an error message "ID3D10Device::CreatePixelShader failed (E_INVALIDARG)" when trying to run 3DMark Vantage or I get complete system hang when benchmark test loading completes, just before the test starts. How can this be corrected?

    The most likely cause for this is a corrupted shader cache. Please delete the contents in the folder C:\ProgramData\Futuremark\3DMark Vantage\cache and try running 3DMark Vantage again.