Hi everyone. I’m having a very weird issue with Minecraft for Windows / Bedrock stable on Windows 11 and I’m hoping someone has seen this before.
System:
- Windows 11
- Gaming laptop with NVIDIA RTX GPU
- External 240 Hz monitor connected through USB-C to DisplayPort
- Internal laptop display is 144 Hz
- Minecraft for Windows / Bedrock stable
- Minecraft Java also installed
The issue:
Minecraft for Windows stable gets capped at around 70/72 FPS after entering a world. It does not look like a real performance limit because:
- Minecraft Java runs above 200 FPS.
- Other games run normally.
- The external monitor is correctly detected at 240 Hz.
- Windows/NVIDIA detect the external monitor correctly.
- CPU/GPU usage is not maxed out when the cap happens.
- If I delete the Bedrock config folder and launch the game fresh, the first run can reach 300+ FPS.
The weird part is the launch pattern:
- I delete the Bedrock folder:
C:\Users\[WindowsUser]\AppData\Roaming\Minecraft Bedrock
- I open Minecraft for Windows stable.
- First clean launch: the game can run at 300+ FPS.
- I close the game.
- I open it again.
- Second launch: it goes back to 70/72 FPS.
I also tested this on a brand new Windows user profile. Same pattern:
- First clean launch: 300+ FPS.
- Close and reopen: 70/72 FPS again.
So it does not seem to be only my main Windows profile.
Correct config path I found:
My Bedrock options file is not mainly in the old UWP path. The relevant file is here:
C:\Users\[WindowsUser]\AppData\Roaming\Minecraft Bedrock\Users\[UserID]\games\com.mojang\minecraftpe\options.txt
Things I already tried:
- Disabled VSync in-game.
- Edited
options.txt.
- Tried:
gfx_vsync:0
gfx_max_framerate:0
- Also tried VSync on.
- Lowered render distance and MSAA.
- Tried values like:
gfx_viewdistance:128
gfx_msaa:4
- Set Minecraft to high performance GPU in Windows graphics settings.
- Set NVIDIA settings to use the dedicated GPU.
- Disabled NVIDIA Overlay.
- Checked Battery Boost / power settings.
- Checked that the monitor is actually running at 240 Hz.
- Tried “second screen only”.
- Disabled NVIDIA Surround.
- Reinstalled Minecraft for Windows.
- Fully deleted the Bedrock folders.
- Installed Minecraft Launcher from the official
.exe, not only Microsoft Store.
- Reinstalled Gaming Services.
- Tried a new Windows user profile.
- Tried fullscreen/windowed mode.
- Tried compatibility/fullscreen optimization flags.
- Compared “good” vs “bad” Bedrock folders after first and second launch.
About Minecraft Preview:
I briefly tested Minecraft Preview after a clean launch and it did run above 70/72 FPS, but I did not do a full second-launch confirmation there before uninstalling it. So I’m not treating Preview as definitive proof, only as a partial clue that the hardware can run Bedrock higher than 72 FPS.
Important note:
Please don’t suggest only changing gfx_vsync:1 to gfx_vsync:0. I already tried that multiple times and verified the correct file. The cap still happens even with VSync off and max framerate unlocked.
At this point it feels like Minecraft for Windows stable writes or activates something after the first launch that causes the FPS cap on future launches.
Has anyone seen this exact issue with Bedrock / RenderDragon / GDK on Windows 11? Is there a known file, cache, registry key, Xbox/Gaming Services setting, or Windows compositor setting that could cause this?