Shared session

By @kleiN

Minecraft (Java)

Sep 22, 2026, 03:36 PM · 29 min · 18 min gameplay

AMD Ryzen 7 9800X3D 8-Core Processor · NVIDIA GeForce RTX 4080 · 46 GB RAM · 2560x1440 · driver 616.64Windowed

Detected by: system event · End: the game closed

Key takeaways

Smooth session

The time lost to stutters stays below the threshold.

53 stutters (65 slow frames including 10 freezes) · 5.3 s lost

Main cause: Game computation (62 occurrences). The worst stretch cost 761 ms of lost frames.

Pace set by the processor

The processor set the pace on 100% of the frames: it decides how many frames per second you get, not the graphics card.

Performance

FPS, lows and stutter breakdown

Frame timing

18 min active / 29 min total

Average FPS

144

Session average

1% low

66

Average of the worst 1% of frames

0.1% low

31

Average of the worst 0.1% of frames

Frame p99

12.5 ms

Time per frame, in the slowest 1%

16.7ms · 60 FPS33.3ms · 30 FPS0 s13 min26 min

Worst frame of each slice (ms) over the session: on this older session, the line traces each slice’s maximum, not the usual pace. Red dots = frames that clearly break from the session’s pace.

Slow frames (65)

5.3 s lost
Game computation62(5.2 s)
Not enough RAM2(0.1 s)
Drive loading1(0.0 s)

System state

CPU, GPU, VRAM averages and temperatures

Game CPU

?

8%

GPU

?

24%

CPU temp max

?

72°

52° on average

GPU temp max

?

60°

57° on average

hot threshold · 90 °C CPUhot threshold · 83 °C GPU30 °C63 °C95 °C0 s15 min29 min

Processor · Graphics card over the session, peak of each slice. The dashed lines are the thresholds of the thermal summary.

Advanced sensors (PawnIO driver)

VRM max 50 °CCPU fan max 4,123 RPMGPU fan max 1,138 RPMCPU power avg. 58 WGPU power avg. 47 W
Pace set by the processor

The processor set the pace on 100% of the frames: it decides how many frames per second you get, not the graphics card.

VRAM peak

?

3.5 GB

Input lag p99

?

28.9 ms