Problems we are still tracking. Workarounds are included where they are safe and repeatable.
The optimized AFTER stage can stop before recording a valid result when CS2 cannot be placed on the selected CPU cores or the Steam handoff does not complete.
What to do: Keep Steam signed in, close any Family View or sign-in prompt, then retry the benchmark. If it fails again, send the test ID and TinyBoost diagnostics to support.
Reset All restores changes that TinyBoost recorded. Older CS2 video or launch-option edits, removed apps, imported driver profiles, and third-party startup changes may have no original-state backup and cannot be guessed safely.
What to do: Follow any pending or manual-restoration message shown by TinyBoost. Do not assume an item was restored when the app reports otherwise.
GPU temperature, voltage, power, or utilization may show as unavailable when TinyBoost cannot obtain a fresh reading from the supported sensor providers. Stress tests stop when required safety readings are lost.
What to do: Close other hardware-monitoring tools, restart TinyBoost, and retry. Persistent gaps should be reported with diagnostics and the exact GPU model.
On some custom Windows installations that force all apps to run as administrator, TinyBoost may not work as expected.
On rare occasions, the automated Tweaked Benchmark may record lower performance in the AFTER result. This is a known intermittent issue and does not necessarily indicate a lasting reduction in system performance.
What to do: Restore your BIOS settings to their defaults, then rerun the automated benchmark. The test can reveal instability in your system's configuration.
Include what you were doing, the exact message, and your TinyBoost diagnostics.