BAPCo Knowledgebase
BAPCo provides full support on the latest versions of its products .
All other products continue to receive limited support through BAPCo website and email support for incidences which have a known solution. End of life products are no longer supported.
For all publication, evaluation, testing and tendering purposes BAPCo strongly recommends using the results from the latest version of all its products.
Product patches downloaded or revisions integrated into updated installation media are not expected to materially change the performance of a platform compared to that of any previous patch or version number; as such results generated with the newest patch or version are currently considered by BAPCo to be comparable with results generated with any previous patches for the given product series.
Search BAPCo Support
SYSmark 30
This error may occur on the SUT when testing with MobileMark 2018, MobileMark 25, SYSmark 30 if the system does not have an audio driver installed and an audio device such as headphones, or speakers connected to the SUT. Note that Bluetooth devices may not be sufficient as the SUT may place them in a low power mode or disconnect them completely in order conserve energy.
To avoid this error, please install an audio device driver and connect an audio device to the SUT prior to installing and testing with BAPCo benchmarks.
The SYSmark 30 whitepaper is located on the SYSmark 30 product page
MobileMark 25
This error may occur on the SUT when testing with MobileMark 2018, MobileMark 25, SYSmark 30 if the system does not have an audio driver installed and an audio device such as headphones, or speakers connected to the SUT. Note that Bluetooth devices may not be sufficient as the SUT may place them in a low power mode or disconnect them completely in order conserve energy.
To avoid this error, please install an audio device driver and connect an audio device to the SUT prior to installing and testing with BAPCo benchmarks.
The MobileMark Index score combines the DC Performance score and Battery Life score into a single
metric which helps users find the best compromise of performance and battery life to fit their needs.
This FAQ applies to MobileMark 25, SYSmark 25, MobileMark 2018, and SYSmark 2018.
Upon completion of a benchmark run, a folder called ‘Results’ is created on the desktop, and the output from the run will deposited into a subfolder that matches the project name. For example, if the project is ‘My Project’ the output folder will be on the desktop under ‘../Results/My Project/’.
CrossMark
An issue has come to BAPCo’s attention that can cause the Windows version of CrossMark to incorrectly report a high Responsiveness scenario score (above 5000). The issue appears when running the Windows version of CrossMark on a system where the directory path to the CrossMark input/output files contains certain non-English characters. This generally occurs when the username contains non-English characters. The high score is the result of a failed workload operation and is therefore invalid.
If a test result shows a Responsiveness scenario score above 5000, the test result is impacted by this issue and should be considered invalid.
To resolve this issue, BAPCo expects to issue an update for CrossMark (expected in late December 2021 or early January 2022) to resolve it. Once the update is released, the BAPCo result database will begin to automatically reject submissions from earlier versions of CrossMark. Users should update to the latest version once it is available. In the meantime, BAPCo is regularly monitoring the results database for problematic submissions and removing them from the results database.
Until an update is available, the user can work around the issue if they have Administrator access to the test system. The user should create another user account with name containing only English characters (e.g., “TEST”) and run CrossMark from the newly-created user account.
The CrossMark technical white paper is located on the CrossMark product page here.
SYSmark 25
Windows Defender status can produce an impact to some BAPCo benchmarks. BAPCo benchmarks will automatically attempt to disable Windows Defender (if possible). Microsoft Windows 11 Operating System prohibits all 3rd party attempts to disable Windows Defender.
This error may occur on the SUT when testing with MobileMark 2018, MobileMark 25, SYSmark 30 if the system does not have an audio driver installed and an audio device such as headphones, or speakers connected to the SUT. Note that Bluetooth devices may not be sufficient as the SUT may place them in a low power mode or disconnect them completely in order conserve energy.
To avoid this error, please install an audio device driver and connect an audio device to the SUT prior to installing and testing with BAPCo benchmarks.
This FAQ applies to MobileMark 25, SYSmark 25, MobileMark 2018, and SYSmark 2018.
Upon completion of a benchmark run, a folder called ‘Results’ is created on the desktop, and the output from the run will deposited into a subfolder that matches the project name. For example, if the project is ‘My Project’ the output folder will be on the desktop under ‘../Results/My Project/’.
MobileMark 2018
Windows Defender status can produce an impact to some BAPCo benchmarks. BAPCo benchmarks will automatically attempt to disable Windows Defender (if possible). Microsoft Windows 11 Operating System prohibits all 3rd party attempts to disable Windows Defender.
This error may occur on the SUT when testing with MobileMark 2018, MobileMark 25, SYSmark 30 if the system does not have an audio driver installed and an audio device such as headphones, or speakers connected to the SUT. Note that Bluetooth devices may not be sufficient as the SUT may place them in a low power mode or disconnect them completely in order conserve energy.
To avoid this error, please install an audio device driver and connect an audio device to the SUT prior to installing and testing with BAPCo benchmarks.
This FAQ applies to MobileMark 25, SYSmark 25, MobileMark 2018, and SYSmark 2018.
Upon completion of a benchmark run, a folder called ‘Results’ is created on the desktop, and the output from the run will deposited into a subfolder that matches the project name. For example, if the project is ‘My Project’ the output folder will be on the desktop under ‘../Results/My Project/’.
SYSmark 2018
SYSmark 2018 v1.5 is an update release by BAPCo to address the needs of our customers who require Windows 11 support for SYSmark 2018. SYSmark 2018 v1.5 is a new, paid product release. Customers with existing licenses for SYSmark 2018 v1.0 will not be able to download a patch installer to upgrade in place. Please contact BAPCo sales for information on how to purchase SYSmark 2018 v1.5 licenses and access the product download.
Documentation and support for SYSmark 2018 v1.5 can be accessed through the SYSmark 2018 product page, SYSmark 2018. v1.5 product page, and the Support FAQ section for SYSmark 2018 v1.5.
Please note that the EOL for SYSmark 2018 v1.0 remains 1 August 2022, after which time BAPCo will cease all sales and support and will no longer accept results submissions for SYSmark 2018 v1.0.
SYSmark 2018 v1.5 will EOL on 31 January 2023, after which time BAPCo will cease sales and support and will no longer accept results submissions for SYSmark 2018 v1.5.
Customers are strongly encouraged to begin their transition to SYSmark 25 as soon as possible.
This FAQ applies to MobileMark 25, SYSmark 25, MobileMark 2018, and SYSmark 2018.
Upon completion of a benchmark run, a folder called ‘Results’ is created on the desktop, and the output from the run will deposited into a subfolder that matches the project name. For example, if the project is ‘My Project’ the output folder will be on the desktop under ‘../Results/My Project/’.
Windows 10 build 20H1 (19041.450) introduced a change that prevents the user from permanently disabling Microsoft Defender. The inability to disable Microsoft Defender may negatively impact scores when running BAPCo benchmarks. Microsoft has provided documentation for users that may wish to roll back their instance of Microsoft Defender to a previous version.