Find answers, guides, and resources to help you get the most out of OCCT.

Support - OCBASE/OCCT

OCCT Support

Welcome to OCCT's support page. Here you will find information on how to use the application, and how to troubleshoot common issues.

Overview

The bar graph will appear once a benchmark is run, and if upload to ocbase is enabled. This graph shows a graphical representation of your current score against other CPUs, and how it fares in your own category. Each bar contains a very detailed tooltip showing you the system details that got this particular score.

Bar graph

Controls the number of threads launched by the benchmark

Threads

Controls the instruction set that will be used by the benchmark.

Instruction set

Selects which type of benchmark will be run on the memory.

Memory

This benchmark aims at giving you proper figures for latency and bandwidth for your CPU caches and Memory components. Unlike others, we do not think it is a wise decision to lock you out of important metrics for your memory subsystem, so this test will give you full figures, for free, unlike some old competitors. 

Measuring those values is very dependent on how many concurrent processes are running - we strongly advise to kill as many processes so the test can have as few competition as possible.

Description

Controls which part of your memory subsystem the test will give figures for.

Type

Latency & Bandwidth

This button will only appear if the following conditions are met : you have a valid license, a benchmark must have been run, and uploading your results to ocbase must be enabled in the settings. Use this button to view the current benchmark on ocbase.

View online

Displays how you rank against other scores obtained in OCCT's benchmark.

Global rank

Displays how you rank against other scores obtained in OCCT's benchmark in the same category. A category is a type of hardware that resembles yours, so you know how you rank relative to people owning the same hardware as yourself. For CPU, each category is defined by people using the exact same CPU. For memory, a category is composed by a Memory type (DDR3, DDR4,...) and the number of active channels.

Category-specific rank

Ranking

Benchmark

A stability certificate is a pre-defined test that you must pass without any errors (WHEA or compute errors) for it to be successful. 

Once passed, an online report will be generated on ocbase, and you'll be given a link to share over the web. As storage costs money, and a stability certificate is a lot of data (especially monitoring), you have a limited number of slots available. When full, newer certificates won't be visible. 

Onced logged in, you can manage your stability certificate, delete old ones you don't want / need anymore, and activate those that are in pending status.

Concept

Stability certificates can target your whole system, or individual components. Use the tabs to choose.

Component

Stability certificates comes in different levels. Higher levels last longer and are more thorough, but they take much longer to execute. The schedules for each component are described in detail in the sections below.

Level

Give a title to your stability certificate, for future reference. It will be displayed on top of your stability certificate. Be mindful of any information you include here, as it will be public. Anything offensive will be moderated. Limited to 200 characters.

Title

Use this field to include any additional information you'd like to share. Only text is supported (for now). Be mindful of any information you include here, as it will be public. Anything offensive will be moderated. Limited to 2000 characters.

Comments

The bronze stability test will run for a to 2 hours and will go through the following sequence:

Bronze

The silver stability test will run for 3 to 4 hours and will go through the following sequence:

Silver

The gold stability test will run for 6 to 8 hours and will go through the following sequence:

Gold

The platinum stability test will run for 12 hours and will go through the following sequence:

Platinum

System

System (No 3D)

The bronze CPU stability test will run for 1h and will go through the following sequence:

The silver CPU stability test will run for 3h and will go through the following sequence:

The gold CPU stability test will run for 6h and will go through the following sequence:

The platinum CPU stability test will run for 12h and will go through the following sequence:

The bronze Memory stability test will run for 1h and will go through the following sequence:

The silver Memory stability test will run for 3h and will go through the following sequence:

The gold Memory stability test will run for 6h and will go through the following sequence:

The platinum Memory stability test will run for 12h and will go through the following sequence:

The bronze GPU stability test will run for 1h and will go through the following sequence:

The silver GPU stability test will run for 3h and will go through the following sequence:

The gold GPU stability test will run for 6h and will go through the following sequence:

The platinum GPU stability test will run for 12h and will go through the following sequence:

Stability Certificate

Stability testing is the DNA of OCCT. A stability test aims at detecting hardware errors by running calculations which results are known in advance, and check if the result is to be expected. 

It is heavily tied to usage : the more stress the components is subject to, the faster an error will occur and is detected. There's a strong misconception that errors only appear during stress - an unstable component can generate errors at any time. Putting the component under stress is just a way of making those appear faster. 

By giving you access to a variety of stability tests, OCCT is the most complete stress test available right now.

Here is a quick overview of the layout of the stability test window:

Layout

Use the start button at the bottom to launch the currently selected test.

Start a test

Duration

Data Set

Mode

Load type

Start at cycle

Thread settings

Cpu + RAM

Version

Linpack

Test Type

Thread count

Selected Preset

Test Sequence

Valid Test Sequence

What is Interleaving ?

Block: Check

Block: Loop

Block: Legacy Test

Block: TM5 Refresh

Block: TM5 Simple

Block: TM5 Inverted

Block: TM5 Arithmetic

Block: Checkerboard

Block: Walking Zero

Block: Walking One

Block: Blank Read

Block: Mirror Move 1

Block: Mirror Move 2

Block: Mirror Move 4

Block: Mirror Move 128

Block: Double Flip

Block: Idle Milliseconds

Block: Idle Minutes

Graphic card

Graphic card selection

Error detection

Shader complexity

Usage limit

Intensity explained

Test type

3D Adaptive

Compute

VRAM

Power

Monitoring only

Configuration

Displays a summary of the currently running test. It will display the test name on top, as well as the test parameters (for instance, the instruction set used), and some figures about the running test (for instance, the amount of memory being used by the test).

Summary

This buttons stops the currently running test.

Stop the running test

This buttons appears as soon as a test is stopped (by clicking on the stop button, if it is finished...). Click on this button to save a report about the test that just finished. The report generated will vary depending on your edition of OCCT: PNG-based for Personal; PNG and CSV for Pro; HTML, CSV and JSON for Enterprise.

Save report

Use this to go back to the test configuration screen.

Go back

This indicator shows the current status of the test. The outer rings are animated to visually cue whether the app is properly running, or if the computer froze for some reason. The icon in the middle will change depending on the test status.

Status indicator

These two values shows the time left in the test. The top value is the time elapsed, the bottom opne is either the total time to spend testing, or an infinite sign.

Timer

The detailed log about the currently running test. it will display all the events that occured during the test: test started, test stopped, error detected... An icon at the beginning of each message hints at the severity of the event.

Use this button to copy the contents of the log to the clipboard. Useful for sharing in forums, Discord...

Execution

Stability Testing

OCCT is able to monitor a wide range of sensors, from the CPU temperature to the GPU power consumption.

Here is a quick overview of the layout of the monitoring window:

Displays all sensors for the selected sensor type in a table format.

Monitoring table

Table

Displays all selected sensors as real-time graphs. The graph size and arrangement depends on the number of sensor selected. Each graph has a tooltip that shows the Mininmum/Maximum/Average values for this sensor. You can click in each graph to get exact values for each point.

Graphs

This drag button resizes the graphs and table to another ratio. Try it for yourself!

Resize bar

These 3 buttons allow you to switch between the table view, the graph view, or both.

Display toggle

This search bar allows you to filter the sensors displayed in the table. Only sensors with a name containing the search string will be displayed.

Search

Use this area to filter by sensor name, or to show/exclude devices, sensor types, and show only selected. You can right click on a filter button to deselect/select all to gain time !

Filters

This button resets the min/max/average values of all sensors to the current ones.

Reset

Toolbar

Monitoring

Displays an overview of your system by condensing the available information into cards.

Displays an overview of all the components found in your computer.

Motherboard

Use theses tabs to switch between the different components. If a particular tab is missing, there's no information available for that component, even if highly unlikely to happen.

Component tabs

Shows information about the currently selected component. The information is organized in sections, that can be collapsed or expanded at will. On the CPU component, a 'flag' button is also available, showing you all the feature flags detected and enabled on your CPU.

Component details

System information

This option controls the auto-updater, and if OCCT should check for updates on startup.

Check for updates

Skin

Allows for increasing OCCT's font size. Higher numbers means bigger fonts.

Use this to enable or disable benchmark score upload to Ccbase. When a benchmark score is displayed and this is enabled, OCCT will send anonymous data to Ocbase with your system information and your benchmark score. This is used later on for calculating rankings, and enabling your score to be displayed in the benchmark leaderboards.

Upload to Ocbase

General

When this setting is enabled, OCCT will check any enabled temperature sensor, and checks their value against the maximum threshold specified. If any value exceeds the threshold, OCCT will stop any running test.

Critical temperature

If this setting is enabled, OCCT will stop any running test upon finding an error.

Stop on error

If this setting is enabled, OCCT will stop any running test upon finding a WHEA error. A WHEA error is usually caused by a driver crashing and being recovered by Windows. This can be due to the driver itself, or from instability.

Stop on WHEA error

Security

This setting only has effect if the Monitoring engine is enabled. This sets the interval at which the monitoring engine will be refreshed, and its values updated (sensors, etc). Updating the monitoring engine costs CPU, so you may want to increase the interval to save some CPU Usage, at the cost of a less often-refreshed monitoring information.

Update interval

Use these values to enable and disable part of the monitoring engine. Disabling some section improves the compatibility of HwInfo, at the cost of missing sensors. Changing any of these settings require an application restart to take effect.

Flags

Settings

OCCT Enterprise adds additional features to OCCT. As such, please refer to the other categories for help on how shared features works. Only additional features will be described in this section.

OCCT Enterprise supports command-line switches to automate its behavior. It differs from OCCT Command-line in that the GUI will be displayed during operation - this requires a desktop access, and thus prevents unattended use. It is still very convenient for automating a test while still having the GUI displayed. 

Make sure to run OCCT Enterprise from an elevated, administrator command prompt to avoid annoying UAC popups!

Presentation

Initiated in V11, OCCT now uses verbs to select what you want to do with the application. The syntax is "OCCTEnterprise 'verb' 'switches". 

The --help switch is available everywhere to guide you through the options !

Verbs

The following switches are available for all verbs:

Common switches

The 'test' verb allows you to run a saved test schedule. The following switches are available:

Switches for the 'test' verb

The 'stabilityCertificate' verb allows you to run a stability certificate. The following switches are available:

Switches for the 'stabilityCertificate' verb

The 'customCertificate' verb allows you to run a custom certificate. The following switches are available:

Switches for the 'customCertificate' verb

Command line options

OCCT's report is a complete report of the test execution.

A single report will generate 3 different files, giving you all the necessary information about a test execution.

Files

The HTML report has a 'Print' button that will format the report in a more concise, printer/PDF-friendly format. This way, you can easily share the report with your customers.

Notes can be added to the printed report by clicking on the 'Add notes' button. Be aware that the notes are not saved in the report file, and will be lost if you close the report (if you have set a value during the report generation, it will default back to said value).

You can also add your company logo to the report, either by placing a 'logo.png' file in the same folder as OCCT, or by injecting it during report generation via command line (see 'Command line options' section).

Printable version

Test report

The format is pretty simple : it's a json-file, containing an array of objects. By default, all sensors are created disabled (i.e. the checkbox next to their name is empty in the UI). They are then enabled based on the provided set of rules. The structure is as follows (example for one rule): [ { "SensorClass": "Temperature", "Name": "*CPU*", "DeviceType": "Cpu" }]

The following options are available in the sensor rules file:

Reference

Sensor rules file

This new area shows the test schedule as it will execute. Each button shows a test period and its duration, and the schedule will be executed by executing each period in succession. This allows you to chain test periods, defining a complete stress test fitting your needs. 

Click on each test to select it and configure it in the Test configuration section located just below.

Test schedule

Use the small arrows below each test period to reorder their order. You can also clone a test period or use the trash icon to remove it from the schedule. Finally, use the "+" button to add a new test period to the schedule.

OCCT Support

Find answers, guides, and resources to help you get the most out of OCCT.

Overview

Need further help ?

Overview

Overview

Need further help ?

Join the OCCT Community

Where enthusiasts gather