Hi everyone,
I'm troubleshooting severe stuttering in Minecraft Java. The game feels like a slideshow during chunk loading and while moving, even when the median FPS is still around 250. It also happens in other games. GTA V is the exception so far. Same behavior on Windows 11 and on CachyOS, so this is not a Windows-only issue.
I took two CapFrameX captures. The first is 1080p. About 20 minutes later I switched to 1440p and captured again. The 1440p run looks much better on paper. I do not believe the resolution actually made the game faster, and the obvious GPU and thermal explanations do not fit. I want a check on the reading below.
Specs
- CPU: Intel Core i7-12700F (8P+4E). Stock limits are 65 W PL1 / 180 W PL2. I have never changed them. E-cores are still enabled.
- GPU: Gigabyte RX 9070 XT 16 GB, Adrenalin 26.8.1. ULPS already disabled.
- RAM: 32 GB DDR4-3200, 2 sticks. Tested with XMP on and off. No change.
- OS: Windows 11 build 26200. Same stutter on CachyOS.
- Minecraft: Java, Fabulously Optimized, plus Voxy. Render distance 2, vsync off. I normally cap at 180, but these captures were not capped (medians are 249 and 284).
- Java version does not matter. I have tried several. Same hitches.
- What I was doing: flying, placing and breaking blocks, opening the creative inventory, killing mobs.
Control run, so this is not a dying GPU
Unigine Superposition 1.1, 4K Optimized, DirectX: score 21078, min 130 / avg 157.2 / max 189. Overlay 1% lows stayed about 124–140 against that 157 average, GPU clock about 3.0–3.4 GHz. When the card is fed, pacing is normal for a 9070 XT.
1080p, first capture
- Average FPS: 156.5 | Median FPS: 248.6
- 1% low: 11.0 | 0.1% low: 5.7 (~175 ms)
- Adaptive STDEV: 95.60
- CPU max thread: 74% @ 4220 MHz, package 65 W, ~49°C
- GPU: 47% @ 2608 MHz, 113 W, ~34°C
1440p, about 20 minutes later
- Average FPS: 244.5 | Median FPS: 283.6
- 1% low: 28.5 | 0.1% low: 4.5 (~222 ms)
- Adaptive STDEV: 38.81
- CPU max thread: 64% @ 4505 MHz, package 63 W, ~52°C
- GPU: 79% @ 3003 MHz, 248 W, ~43°C
What changed, and what did not
From 1080p to 1440p the median went 249 → 284 and the average went 157 → 245. Adaptive STDEV fell 96 → 39, and the 1% low rose 11 → 28.5. The GPU went from idle (47%, 113 W, 34°C, 2608 MHz) to actually working (79%, 248 W, 43°C, 3003 MHz).
The median only rose about 14%. The GPU clock rose about 15% (2608 → 3003). Those match. At 1080p the card was at 47% and never held full clocks. At 1440p the load was steady enough for it to sit near 3 GHz, so the normal frames got a bit faster.
The average did not jump because 1440p is cheaper. At 1080p the median was already 249. The average was 157 only because hitches dragged it down. At 1440p those hitches got rarer, so the average was allowed to sit near the median.
The 0.1% low did not follow. 5.7 FPS at 1080p (~175 ms), 4.5 FPS at 1440p (~222 ms). The freezes got less frequent. The worst one did not get shorter. Resolution is not what those freezes are.
GPU power did not rise because a throttle let go. 113 W at 47% and 248 W at 79% are the same performance per watt. A 9070 XT that is power-limited sits near 300 W at full load. At 1080p it was waiting on the CPU. At 1440p the CPU fed it more often, so power, clock, and temperature rose together. Superposition already showed the card is fine when something feeds it.
CPU temperature only went 49°C → 52°C. This is not thermal throttling.
Package power stayed 65 W → 63 W. The busiest thread dropped 74% → 64%, and the clock rose 4220 → 4505 MHz. 65 W is the 12700F's PL1. Power cannot go above that. In the 1080p run more threads were busy, so that 65 W was spread thinner and the P-core clock sagged. In the 1440p run fewer threads were busy, same budget, higher clocks. I also changed resolution and waited 20 minutes, so those two are mixed together. This was not a clean A/B.
What I think it is
The 1080p run is the CPU thread stalled (chunk generation, Voxy LOD, block updates, inventory), so the GPU sits at half load and frametime variance is huge. The 1440p run is that calming down: average and median recover, the GPU gets frames, STDEV drops. The ~200 ms freezes are still there.
Both runs pin the 12700F at its 65 W base limit, with E-cores still on and sharing that budget. The clock only moved because the thread load moved. Temps near 50°C mean the cooler is not the limit.
It is not only Minecraft. Other games hitch the same way, on Windows and on CachyOS. GTA V does not. Voxy plus flying will make Minecraft worse than a clean game, but it does not explain the other titles or the other OS.
Not done yet
- Set PL1 = PL2 ≈ 180 W and retest. The CPU is at 50°C, so the thermal room is there.
- Disable E-cores for one run. At 65 W they steal power from the P-cores.
- Two captures in one already-generated spot, same view: 60 seconds at 1080p, then 60 seconds at 1440p. No flying, no inventory.
- HWiNFO limit reasons during both (I expect PL1 / package RAPL = Yes).
- CapFrameX CPU Busy vs GPU Busy, not just FPS.
- One capture with Voxy off, same path, to separate the mod from the CPU limit.
- Motherboard : Asus H610M-V2, Bios Version : 3403, i did NOT try to hard-reset, remove ram, or remove cmos battery , i did not check if there are any bent pins or debris because i very recently got my pc cleaned and assembled again by a friend of my dad, he showed me it's all good.
Please help. I can't play like this.
Thanks.
