Why does Minecraft stutter so badly on my high-end PC with shaders and modpacks?

August 3, 2026 4 answers
Asked by MellowOrbit42
I recently built a PC with an RTX 5080 Aorus and a Ryzen 7 7800X3D running at 3.1 GHz with an undervolt. Most games run very well, but heavily modded Minecraft has surprisingly unstable performance. I mainly play Prominence II, All the Mods 10, and Beyond Depth, usually with Faithful and medium-to-high shader settings. My render distance is 18โ€“20 chunks, shadow distance is 8 chunks, and simulation distance is 16โ€“20 chunks. FPS starts around 130โ€“140 while the world is loading, drops to roughly 100โ€“110 when moving around, and can eventually fall to 45โ€“85 FPS even when there are no major bases or farms nearby. Is this normal for modded Minecraft, or could my high simulation distance, GPU overclock, or CPU undervolt be causing the stuttering?

Answers

CedarVale7
Modded Minecraft can have heavy performance dips because much of its workload, especially world and entity simulation, is limited by CPU performance and Java behavior rather than simply GPU power. Large bases, farms, and chunk generation can make it worse, but dips can still happen early in a new world.
Reply to this answer
SilverCactus5
Shaders and high render distances add another layer of load, but a 5080 and 7800X3D should generally handle these settings better. Watch frametime graphs rather than average FPS, and check whether the drops happen during chunk generation, garbage collection, or CPU saturation. Also make sure the modpack has its recommended performance mods and an appropriate amount of RAM allocated.
Reply to this answer
QuietHarbor31
Test your system at stock settings. Temporarily remove the CPU undervolt and disable or reduce any GPU and memory overclock, then check whether the stutters remain. If the problem disappears, gradually restore each change until you find the unstable setting. An undervolt can appear stable in ordinary games while failing during Java or modded workloads.
Reply to this answer
BrightMango_8
A drop from 140 FPS to below 60 with almost nothing built is worth troubleshooting instead of writing off as normal. First lower simulation distance to about half of render distance, such as 8โ€“10 chunks. Simulation distance can be much more expensive than render distance because it controls active world processing.
Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions