GPU Stress-Test Log Template for FurMark

What data should I record during a FurMark run?

Keep a compact log of the GPU model, driver, Windows version, FurMark build, test preset and sensor behavior. Repeatability matters more than the highest number.

Prepare a controlled Windows test

FurMark is a deliberately demanding graphics workload and should not be treated as a routine background task. Make sure the computer has adequate cooling and normal airflow, close other graphics-heavy programs, and locate the manufacturer’s published operating limits for your exact graphics card. If a system already has cooling problems, do not begin the test.

Write down the test date, room conditions, GPU model, driver, API, resolution, AA mode, power plan, clock behavior, peak temperature and any warnings. Save an initial baseline before changing settings.

Keep conditions consistent

If you change a cooling component or driver, note the change in the log and keep everything else as constant as possible. Include whether the PC was plugged in and what background programs ran.

For repeatable results, preserve the FurMark major version, graphics API, preset, resolution, anti-aliasing mode, driver version and Windows power configuration. Keep a record of whether the GPU started cool or had just completed another workload. Changing several of these at once makes a before-and-after comparison unreliable.

Understand the results

Use the log to detect trends rather than infer hardware health from one result. Stop unsafe tests rather than trying to fill every field.

Observe the trend of temperatures and clocks rather than one peak value. A completed run demonstrates how the particular device handled that particular test; it does not certify the GPU, power supply, memory or overall PC. If performance varies, compare readings from the same system and consider a second, less intense real-world workload.

Stop conditions and next steps

End the run immediately if cooling no longer appears effective, the screen displays corruption, the graphics driver repeatedly resets, Windows freezes, or temperatures approach the manufacturer’s stated limit. Do not disable thermal or electrical protections. Allow cooling time before troubleshooting and avoid repeating crashes just to reproduce a result.

For a broader introduction, see how to use FurMark. For deeper context on this topic, use the related detailed guide, or browse the complete Windows guide library.

Frequently asked questions

What data should I record during a FurMark run?

Keep a compact log of the GPU model, driver, Windows version, FurMark build, test preset and sensor behavior. Repeatability matters more than the highest number.

Does passing this test guarantee that my GPU is healthy?

No. A passing stress test cannot rule out problems under other APIs, games or application workloads. Combine supervised measurements with normal usage and hardware documentation.

Should I maximize the power limit to improve the result?

No. Follow the hardware manufacturer’s published limits and do not defeat safety protections to obtain a higher benchmark score.