Reference
Troubleshooting
This page covers common problems you can encounter when you use Novabench. It also has tips for getting accurate and consistent results, and answers to frequently asked questions.
Common issues
A game reports NovabenchDriverWin10.sys
This driver came with Novabench 4 for Windows. Novabench 5 and Novabench 6 do not include it.
Follow the Novabench 4 driver removal steps to fix anti-cheat errors in Fortnite.
Benchmark scores are lower than expected
If your scores seem low for your hardware, check the following:
- Close background applications. Web browsers, antivirus scans, cloud sync services, and media players all compete for CPU, GPU, and memory resources. Close unnecessary programs before you run a benchmark.
- Check power settings. On laptops, connect the power adapter and set the power plan to Balanced or High Performance (Windows) or disable Low Power Mode (macOS). Power-saving modes limit processor speeds.
- Update GPU drivers. Outdated GPU drivers are one of the most common causes of low GPU scores. Check your current driver version in the system information panel and update from the manufacturer's website.
- Check for thermal throttling. If your system overheats, the CPU or GPU reduces its clock speed to lower its temperature. Run a stress test to check for throttling. On laptops, make sure that the device is on a hard, flat surface with clear airflow.
- Run multiple iterations. Use multi-iteration mode to run the benchmark several times in a row. If scores vary significantly between iterations, background activity or thermal problems are likely the cause.
On Plus, Explain can analyze your specific results and provide targeted recommendations.
Scores vary between runs
Some variation between benchmark runs is normal, typically within a few percentage points. Larger variations usually indicate:
- Background processes starting or stopping between runs. Check your task manager or activity monitor for unexpected activity.
- Thermal throttling during longer sessions. If scores drop on successive runs, the system is probably accumulating heat. Allow a few minutes of cool-down between runs.
- Disk caching effects on storage tests. The first run after a reboot may differ from later runs because of filesystem caching.
Use multi-iteration mode and look at the average across runs for the most representative score.
GPU test fails or produces errors
GPU test failures typically have these causes:
- Outdated or corrupted drivers. Uninstall your GPU driver completely (use a tool such as DDU on Windows). Then reinstall the latest version from NVIDIA, AMD, or Intel.
- Unsupported GPU. Very old GPUs can lack support for the graphics APIs (DirectX 12, Vulkan, Metal) that Novabench uses. Check system requirements for GPU compatibility.
- GPU hardware instability. If the GPU test consistently crashes, run a stress test against the GPU to check for hardware-level instability.
- Multi-GPU conflicts. On systems with multiple GPUs (for example, a laptop with integrated and discrete graphics), make sure that the correct GPU is selected before you run the test.
NPU test does not appear
The NPU benchmark only shows when Novabench detects a supported neural processing unit. If your system has an NPU but the test does not appear:
- Make sure that NPU drivers are installed and up to date. Check Device Manager (Windows) or System Information (macOS) for your NPU device.
- Restart Novabench after you install or update NPU drivers.
- Some NPUs require specific OS versions. Make sure that your operating system meets the requirements for your NPU hardware.
Stress test shows failures
A stress test failure means the hardware could not sustain the workload for the configured duration. Common causes:
- Inadequate cooling. High temperatures trigger thermal shutdowns. Check the max temperature reported in stress test results. If temperatures exceed the manufacturer's specified thermal limit, improve cooling (clean dust, replace thermal paste, or improve airflow).
- Unstable overclock. If you have overclocked your CPU or GPU, a stress test failure indicates the overclock is not stable at the current settings. Reduce the overclock or increase voltage (with caution).
- Power delivery problems. Insufficient power supply wattage or cable connections can cause GPU stress test failures. Make sure that your PSU meets the GPU's power requirements.
- Hardware defect. Consistent failures at stock settings (no overclock) with adequate cooling can indicate a hardware problem. Compare against the throttle time and failure point data in your stress test results.
Network test issues
Speed test shows lower speeds than expected:
- Use a wired Ethernet connection instead of WiFi for the most accurate results.
- Close bandwidth-heavy applications (streaming, downloads, cloud sync).
- Test at different times of day, since ISP congestion affects results.
- On Plus, use regional server selection to test against servers closer to you.
Traceroute shows incomplete results:
- Some hops may appear as timeouts. This is normal because many routers do not respond to probe packets.
- Corporate firewalls and VPNs can block ICMP packets. On Plus, try UDP or TCP protocols instead.
- If all hops time out, check your internet connection and firewall settings.
DNS benchmark shows high latency:
- High latency on your system DNS can indicate a slow resolver configured by your ISP or router. Consider switching to a public DNS provider.
- On Plus, test with DoT, DoH, or DoQ protocols, which can route differently than plain UDP.
- If all resolvers show high latency, the problem is likely network congestion rather than resolver performance.
Battery test does not start
The battery test requires:
- A laptop with a battery installed
- The power adapter disconnected (the test measures battery drain)
- A Plus subscription
If the test button is disabled, make sure that Novabench detects your battery. Some virtual machines and certain hardware configurations do not expose battery data.
Application tests not available
Application tests require a Team plan. They are not available on Free, Plus, or Pro. If your organization has a Team plan but the tests do not appear:
- Make sure that you are signed in to the correct account in the Novabench app. A personal Pro account does not unlock application tests.
- Check that your team's plan is active (not expired or in a grace period).
- Restart Novabench after plan changes.
If most suites appear but a specific one is missing, the reason is usually the application itself. Each suite drives real software, so Novabench only offers a suite when it detects that application on the device. Install the application, then restart Novabench so it scans again.
Tips for accurate results
Follow these guidelines to get the most representative and repeatable benchmark scores.
Before benchmarking
- Restart your system. A fresh boot clears memory, resets caches, and stops accumulated background processes. Benchmark scores after a reboot are typically more consistent.
- Close all applications, including browser tabs, chat applications, and background utilities. On Windows, check the system tray for hidden applications.
- Plug in the power adapter on laptops. Battery power activates power-saving modes that limit CPU and GPU performance.
- Set power plan to High Performance (Windows) or disable Low Power Mode (macOS). After the benchmark, you can revert to your normal power plan.
- Let the system idle for a minute before you start. This allows CPU temperatures to settle and background startup tasks to complete.
During benchmarking
- Do not use the computer while the benchmark is running. Mouse movement, keyboard input, and application switching can affect results, especially GPU scores.
- Keep the room at a consistent temperature. Ambient temperature affects cooling performance, which affects benchmark scores. Do not run benchmarks in direct sunlight or next to heat sources.
For comparison accuracy
- Run the same Novabench version on all systems you want to compare. Benchmark algorithms can change between major versions, which makes cross-version comparisons less meaningful.
- Use multi-iteration mode and compare averages. A single run captures one snapshot, while averaged results smooth out transient variations.
- Submit results to the Novabench database so you can use histograms and percentile rankings to compare against other users with the same hardware.
Frequently asked questions
What does the Novabench Score mean?
The Novabench Score is a single number representing your system's overall performance. It combines individual scores from CPU, GPU, Memory, Storage, and (where available) NPU tests. Higher scores mean better performance. The score is comparable across platforms, so a Windows score and a macOS score of the same number indicate similar performance. See understanding your scores for a detailed breakdown.
Are Novabench scores comparable across different versions?
Scores within the same major version of Novabench are directly comparable. Benchmark methodology can change between major versions, so comparing a score from Novabench 4 with a score from Novabench 5 is not meaningful.
Does Novabench test the full capability of my hardware?
Novabench tests real-world workloads that reflect typical usage patterns. Scores are practical and comparable. They do not push hardware to its absolute theoretical maximum. For sustained load testing, use the stress test.
Can I benchmark a specific drive or GPU?
Yes. If your system has multiple GPUs, Novabench lets you select which one to test before starting the benchmark. For storage, Novabench tests the primary drive by default, with options to select a specific drive. See storage benchmark for details.
Do I need an account to use Novabench?
No. You can run benchmarks, view local results, and run stress and network tests without an account. You need an account to submit results for comparison, access Plus or Pro features, and sync results across devices. See account management for details.
How do I get help?
If you encounter a problem not covered on this page, visit the Novabench support page for assistance.
