FAQ
TL;DR: 60 FPS after reinstall vs 120–300 FPS before; switching to a different Minecraft Launcher fixed it: “I changed the Launcher to another and it works normally.” [Elektroda, RC1212RCXD, post #17492852]
Why it matters: This FAQ helps Windows 7 Minecraft players on older i3/GTX 470 rigs fix sudden 1.13 stutter or a 60 FPS cap.
Quick Facts
- Baseline: i3‑3220, GTX 470 1.2 GB, 10 GB DDR3; issue started right after Windows 7 reinstall. [Elektroda, RC1212RCXD, post #17482432]
- Performance note: 1.12.2 delivered ~200–350 FPS; 1.13 introduced heavy stutter on the same PC. [Elektroda, RC1212RCXD, post #17492813]
- Proven fix: Switching to another Minecraft Launcher restored normal FPS on 1.13. [Elektroda, RC1212RCXD, post #17492852]
- Diagnostics standard: Use HWiNFO sensor logging during gameplay; don’t rely on static HWMonitor screenshots. [Elektroda, enhanced, post #17492606]
- Tuning focus: 1.13 is CPU‑bound on older chips—verify CPU load and update Java. [Elektroda, enhanced, post #17492844]
Why did Minecraft FPS tank after my Windows 7 reinstall?
Two common shifts cause this: moving to Minecraft 1.13, which is more CPU‑bound, and outdated Java/runtime. Check CPU load first. If the CPU pegs high on a few threads, you’re CPU‑limited. Update Java and retest. As one helper said, “it will be based on the CPU.” [Elektroda, enhanced, post #17492844]
What fixed it for the original poster (i3‑3220, GTX 470)?
They switched to a different Minecraft Launcher. After changing the launcher, Minecraft 1.13 returned to normal performance on the same hardware. This points to a launcher/runtime issue rather than failing components or drivers. [Elektroda, RC1212RCXD, post #17492852]
Does 1.12.2 run faster than 1.13 on this hardware?
Yes. The user saw about 200–350 FPS on 1.12.2, while 1.13 exhibited significant stutter. This indicates 1.13’s higher CPU demands on older processors. Testing both versions helps isolate version‑related slowdowns. [Elektroda, RC1212RCXD, post #17492813]
How do I log temps and usage during gameplay to diagnose stutter?
Use HWiNFO and capture a sensors log.
- Open HWiNFO and go to Sensors.
- Start logging to a file before launching Minecraft.
- Play 5–10 minutes, stop logging, and review or share the CSV. [Elektroda, enhanced, post #17492606]
HWiNFO crashes on my PC—what should I do?
Acknowledge the crash and try again after a reboot. If it still fails, temporarily use HWMonitor for basic readings. Then return to HWiNFO for proper logs when possible. Note the crash details for helpers. [Elektroda, RC1212RCXD, post #17492623]
Why run 3DMark11, and what should I share?
A quick GPU benchmark confirms if the graphics card performs within expectations. Run 3DMark11 and submit the result link after testing. Helpers can compare your score to typical baselines. [Elektroda, enhanced, post #17492625]
3DMark11 says a file is missing—how do I proceed?
Capture and share the exact error message or a screenshot. Without specifics, it’s unclear which dependency you missed. Post the details so others can advise the correct fix. [Elektroda, enhanced, post #17492768]
Could a modified launcher cause the lag—or worse?
Yes. A modified launcher can include unwanted processes, like cryptominers. As one user warned, “you were digging someone’s currency in the process.” Use the official launcher to rule this out. [Elektroda, icosie, post #17493347]
Should I update Java for Minecraft 1.13 on Windows 7?
Yes. Update Java to the latest supported build and retest. Outdated Java can worsen CPU‑bound behavior and stability. “Do you have java updated?” was a key troubleshooting prompt in this case. [Elektroda, enhanced, post #17492844]
Could mixed RAM (8+2 GB) or a 600W PSU be the cause here?
Unlikely in this scenario. The issue disappeared after switching launchers, which points to software, not PSU or RAM configuration. Keep them in mind only if problems persist. [Elektroda, RC1212RCXD, post #17492852]
How can I quickly test if my slowdown is version‑specific?
Install and run Minecraft 1.12.2, then 1.13, with similar settings and scenes. Compare FPS and smoothness. Large differences suggest a version/runtime issue, not failing hardware. [Elektroda, RC1212RCXD, post #17492813]
What should I do right after a fresh Windows install to avoid game FPS issues?
Follow a structured diagnostic: install proper drivers, then log CPU/GPU sensors during gameplay. Share logs instead of static screenshots. Work through a step‑by‑step guide before changing hardware. [Elektroda, enhanced, post #17492606]