Back to benchmark

Reference Reports

Case Reports

These example reports show how to map raw benchmark metrics to concrete diagnosis and next actions. Use the same structure for your own run logs so results stay comparable over time.

CR-001

10 min / 1080p / Ultra / 60 FPS

Laptop thermal check after 12 minutes of load

Observations
Average FPS declined by ~18%, drop frame ratio rose above 13%, stability score fell from 84 to 68.

Interpretation
Pattern matches heat saturation and likely thermal throttling under sustained power limits.

Action
Re-test on AC power with performance mode and higher fan curve; compare decay slope.

CR-002

5 min / 1440p / High / 60 FPS

Post-overclock validation on desktop GPU

Observations
Average FPS improved slightly, but 1% low collapsed and frame-time spread exceeded 9 ms.

Interpretation
Throughput gain came with unstable pacing, indicating unstable frequency or voltage settings.

Action
Reduce memory/core offsets and rerun until 1% low recovers near baseline.

CR-003

10 min / 1080p / Ultra / 60 FPS

Cooling upgrade A/B comparison

Observations
With upgraded cooling, drop frame ratio stayed below 3% and end-of-run FPS stayed near start values.

Interpretation
Cooling changes improved sustained consistency rather than only peak performance.

Action
Keep updated fan curve and record this run as new baseline for future maintenance checks.

CR-004

3 min / 1080p / High / 60 FPS

VM acceleration sanity test

Observations
Average FPS was far below host baseline and pacing oscillated despite low visual complexity.

Interpretation
Likely fallback to weak virtualized acceleration path or constrained passthrough configuration.

Action
Verify GPU passthrough/acceleration settings and rerun with identical browser build.

CR-005

5 min / 1080p / High / 60 FPS

Gaming stutter complaint triage

Observations
Average FPS remained high, but 1% low sat near 55% of average with intermittent spread spikes.

Interpretation
Headline FPS hides pacing instability; issue is likely contention, driver jitter, or thermal oscillation.

Action
Close background GPU tasks, retest, then correlate with desktop telemetry for clock and temperature spikes.