Since last week I suddenly have a problem.
- Minecraft & Optifine don't load in the latest versions. (Even when I use forge).
- Minecraft worlds load in very slow and freeze a bit at 100%.
- When in a Minecraft world when in the bottom right says: Saving World. My world starts to freeze and when Saving World finish itself, I will setback to the moment where the saving moment started. While this is happening I can not interact with the world.
To solve this I tried everything. Uninstall Minecraft, Update my windows, java, and drivers. Check for virusses, and more.
1.19 to 1.20.1 just have those problems now since thursday and I don't know how to fix it.
I've had this one too on the WindowsOS and nothing seems to help from re-installs to JVM argument configs. Only using Ubuntu I've gotten rid of this.
Update: I think upping the allocated memory with JVM arguments -Xmx4G -Xms4G in the launchers installation tab helped that the world can catch up with my actions after the save finishes. But still it can be up and over 40s of saving.
Rule of thumb when it comes to analyzing causes of new behaviors is something changed to cause it. Whenever a change in behavior occurred, the cause of the change was also at that time.
You mention this started last week so something changed around then to cause it. Try to think what may have changed in the last week then.
Namely, something in your environment or hardware changed (and this doesn't mean changed parts, but it could mean "something is overheating" or "something is failing/faulting now that wasn't before"). It's usually more direct to approach it with the first. That could be a Windows update, a driver update, a game update, a settings change, other software running... the list really is endless.
Your mention of loading a world is slow and freezes at 100% raises some clues. A slow CPU or an issue with the storage drive would be worth looking into.
What CPU do you have? Is it fast enough for the game? Is it perhaps overheating?
What storage drive? How full? Is it in good health?
As the above said, ensure the game/Java has enough memory allocated (and that your PC has enough).
Also if the game doesn't load at all in the latest version, why? What is happening then? Frozen loading? Error message? Does this happen with just Minecraft and no OptiFine or Forge? What does the launcher say?
I'm a bit confused how you can moved back during the saves. Stutters make sense, but I've never seen that one happen. That only sounds possible by sync issues between the client and internet server (client keeps playing, but server has become overwhelmed, and then once it's not overwhelmed, client realizes "oh, the player should really be here instead" and moves you back (in reality, you should be where you see yourself on the client but the server wasn't updating your position due to being overwhelmed?). The above example of this taking 40 seconds is very concerning.
I'm a bit confused how you can moved back during the saves. Stutters make sense, but I've never seen that one happen. That only sounds possible by sync issues between the client and internet server (client keeps playing, but server has become overwhelmed, and then once it's not overwhelmed, client realizes "oh, the player should really be here instead" and moves you back (in reality, you should be where you see yourself on the client but the server wasn't updating your position due to being overwhelmed?). The above example of this taking 40 seconds is very concerning.
This is known as "rubber banding" and is caused by client-server desync with some form of server-side validation of player movement; while the client is mostly in control of the player (you can still move even if the server is completely frozen) the server has checks to make sure the player hasn't moved much more than they could have (basically anti-cheat, this is more noticeable in newer versions, you may have seen "player moved wrongly / too quickly" in the console. I don't think I've ever actually experienced rubber banding in 1.6.4, except on a very minor scale due to a "ghost block" (a block that was only broken client-side so the client attempts to walk into it but the server pushes you back; this is not a "rollback" though), only on 1.8+ (at the time, where it was quite bad given that even when standing still the server could barely keep up); other things caused by desync include block rollbacks (break a block, which produces no drops, then it reappears after some time, then (maybe) disappears and finally drops); mobs suddenly "sprint" forwards after freezing (I saw this a lot with the 1.6 zombie lag issues, the sun/moon would also jump back, and minecarts would stop and go since like other entities they were controlled by the server).
Well, yes, I know what it is, and I even described the cause.
I meant I was confused as to what could cause it to be happening, at least to this severity (the response mentioned an example of 40 seconds). That's why I thought there might be some underlying issue like a very slow CPU (possibly even throttling) or other resource bottleneck like RAM or storage for some reason.
I don't think I've ever actually experienced rubber banding in 1.6.4, except on a very minor scale due to a "ghost block" (a block that was only broken client-side so the client attempts to walk into it but the server pushes you back; this is not a "rollback" though)
That's pretty much the only de-sync issue I recall dealing with (not counting the moon and sun skipping back when first loading a burst of chunks like on world or dimension load), and even that's rare and seemed to occur only with an efficiency tool fast clearing something, typically a shovel and dirt, but sometimes a pickaxe and stone. Oddly, netherack breaks faster and I've never seen it happen with it for some reason. But it's also been a long time since I've seen it at all.
The big one I used to see was the message about the time being wrong and the server being overloaded and behind (maybe the higher render distance back then was part of why) but even that I seldom if ever see now.
Logs seem pretty sparse so I'm not sure if that information is elsewhere now.
That's basically the entire log, along with spawn point being (re)set.
That's sort of why I was wondering what could cause the desync issues described to such a severity. I know what it is and that it might happen, but the severity seems excessive unless there's like a severe lack of CPU speed, RAM, or storage bottleneck? Hence I was asking about those things.
But the latest version of the game also fails to load at all so it sounds like there's other issues. I'm also confused though because 1.9 to 1.20.1 is stated to work but have the issue, but 1.20.1 is also the latest official version (1.20.2 is upcoming) so clarity is needed there.
I'm wondering if something changed with the launcher (there's been some updates lately) or if there was a micro-update applied to all recent enough versions of the game?
There seems to be a bit of people mentioning this so I wonder if there's some common denominator. I haven't had any issues with 1.20.1. I have, however, noticed that when starting either of my 1.19 profiles, the frame rate of the main menu seems a bit jumpy for five seconds or so, but I don't know when that started because I've been spending almost all of my time in my 1.20 profile lately. It doesn't have any issues with saving or general performance though.
I found a report about this issue on the bug tracker, though a commenter brushes it off as a technical support issue (not a valid game bug, and if it is suddenly affecting many people, which is also noted in the report, there has to be something going on, though it could be an update of the OS, antivirus, firewall, or other incompatible software that is the real cause; Mojang does not make "micro updates" to any version, I've seen people who thought that something was changed with some old version (example) but it was only faulty memory as the contents of the jar file showed no changes).
The second Tuesday of each month is the day Windows pushes its monthly updates, so while that was a bit over a week ago now, if people started reporting this issue around a week ago (accounting for some lag time for those updating a bit later, and taking a few days to realize it), then there is some slight correlation with that timeframe. Not saying it is a Windows update that caused it but the timeframe does line up. Maybe Windows pushed an updated driver to some people that's causing it?
The second Tuesday of each month is the day Windows pushes its monthly updates, so while that was a bit over a week ago now, if people started reporting this issue around a week ago (accounting for some lag time for those updating a bit later, and taking a few days to realize it), then there is some slight correlation with that timeframe. Not saying it is a Windows update that caused it but the timeframe does line up. Maybe Windows pushed an updated driver to some people that's causing it?
Somebody recently posted a similar thread in Support and said that updating their "MB drivers" (which I think means "motherboard") fixed the issue for them; as I also noted, a report on the official bug tracker seems to say that everybody with the issue was from northern Europe, so it could be affecting a regional computer brand (if not necessarily exclusive to the region):
Usually means motherboard, yes, but the drivers for those tend to pertain to numerous things as opposed to just one. That could includes any onboard things (like sound and networking). The chipset drivers (one of which is now on the CPU, another of which is on the motherboard) are probably the primary one most people refer to, and those would relate to CPU and storage subsystem (and other I/O like USB, etc.).
The person in the link you provided has a Core i9 13900K and a RTX 4090. I'm going to go out on a limb and presume that's either self assembled, or if it from a reseller, they likely just use off the shelf parts so it's probably not a given OEM brand but either a certain motherboard brand or just certain chipsets/platforms. Therefore, knowing the mothebroard brand and model would possibly be useful.
My Windows was updated last week but I haven't had any issues with Minecraft.
I was also thinking if it was caused by windows update because after update it started lagging. I am also from northern Europe.
edit: I just scanned and updated things on my motherboard manufacturer site. Then I downloaded newest motherboard update. This worked for me I think. Thank you all!
I'm wondering if there's a common correlation here, like Windows version, motherboard chipset, CPU type, or whatever. I wonder if Windows was pushing a "bad" chipset driver to some platforms. At least it sounds like this sudden influx issue had a rather quick solution found?
Since last week I suddenly have a problem.
- Minecraft & Optifine don't load in the latest versions. (Even when I use forge).
- Minecraft worlds load in very slow and freeze a bit at 100%.
- When in a Minecraft world when in the bottom right says: Saving World. My world starts to freeze and when Saving World finish itself, I will setback to the moment where the saving moment started. While this is happening I can not interact with the world.
To solve this I tried everything. Uninstall Minecraft, Update my windows, java, and drivers. Check for virusses, and more.
1.19 to 1.20.1 just have those problems now since thursday and I don't know how to fix it.
I've had this one too on the WindowsOS and nothing seems to help from re-installs to JVM argument configs. Only using Ubuntu I've gotten rid of this.
Update: I think upping the allocated memory with JVM arguments -Xmx4G -Xms4G in the launchers installation tab helped that the world can catch up with my actions after the save finishes. But still it can be up and over 40s of saving.
Rule of thumb when it comes to analyzing causes of new behaviors is something changed to cause it. Whenever a change in behavior occurred, the cause of the change was also at that time.
You mention this started last week so something changed around then to cause it. Try to think what may have changed in the last week then.
Namely, something in your environment or hardware changed (and this doesn't mean changed parts, but it could mean "something is overheating" or "something is failing/faulting now that wasn't before"). It's usually more direct to approach it with the first. That could be a Windows update, a driver update, a game update, a settings change, other software running... the list really is endless.
Your mention of loading a world is slow and freezes at 100% raises some clues. A slow CPU or an issue with the storage drive would be worth looking into.
What CPU do you have? Is it fast enough for the game? Is it perhaps overheating?
What storage drive? How full? Is it in good health?
As the above said, ensure the game/Java has enough memory allocated (and that your PC has enough).
Also if the game doesn't load at all in the latest version, why? What is happening then? Frozen loading? Error message? Does this happen with just Minecraft and no OptiFine or Forge? What does the launcher say?
I'm a bit confused how you can moved back during the saves. Stutters make sense, but I've never seen that one happen. That only sounds possible by sync issues between the client and internet server (client keeps playing, but server has become overwhelmed, and then once it's not overwhelmed, client realizes "oh, the player should really be here instead" and moves you back (in reality, you should be where you see yourself on the client but the server wasn't updating your position due to being overwhelmed?). The above example of this taking 40 seconds is very concerning.
This is known as "rubber banding" and is caused by client-server desync with some form of server-side validation of player movement; while the client is mostly in control of the player (you can still move even if the server is completely frozen) the server has checks to make sure the player hasn't moved much more than they could have (basically anti-cheat, this is more noticeable in newer versions, you may have seen "player moved wrongly / too quickly" in the console. I don't think I've ever actually experienced rubber banding in 1.6.4, except on a very minor scale due to a "ghost block" (a block that was only broken client-side so the client attempts to walk into it but the server pushes you back; this is not a "rollback" though), only on 1.8+ (at the time, where it was quite bad given that even when standing still the server could barely keep up); other things caused by desync include block rollbacks (break a block, which produces no drops, then it reappears after some time, then (maybe) disappears and finally drops); mobs suddenly "sprint" forwards after freezing (I saw this a lot with the 1.6 zombie lag issues, the sun/moon would also jump back, and minecarts would stop and go since like other entities they were controlled by the server).
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Well, yes, I know what it is, and I even described the cause.
I meant I was confused as to what could cause it to be happening, at least to this severity (the response mentioned an example of 40 seconds). That's why I thought there might be some underlying issue like a very slow CPU (possibly even throttling) or other resource bottleneck like RAM or storage for some reason.
That's pretty much the only de-sync issue I recall dealing with (not counting the moon and sun skipping back when first loading a burst of chunks like on world or dimension load), and even that's rare and seemed to occur only with an efficiency tool fast clearing something, typically a shovel and dirt, but sometimes a pickaxe and stone. Oddly, netherack breaks faster and I've never seen it happen with it for some reason. But it's also been a long time since I've seen it at all.
The big one I used to see was the message about the time being wrong and the server being overloaded and behind (maybe the higher render distance back then was part of why) but even that I seldom if ever see now.
Logs seem pretty sparse so I'm not sure if that information is elsewhere now.
[11:21:17] [Server thread/INFO]: Saving and pausing game...
[11:21:17] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:overworld
[11:21:17] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_nether
[11:21:17] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_end
[11:21:18] [Render thread/INFO]: [Shaders] Framebuffer created: dfb
[11:21:41] [Render thread/INFO]: [Shaders] Framebuffer created: dfb
[11:23:52] [Server thread/INFO]: Saving and pausing game...
[11:23:52] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:overworld
[11:23:52] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_nether
[11:23:52] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_end
[11:28:09] [Server thread/INFO]: Saving and pausing game...
[11:28:09] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:overworld
[11:28:09] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_nether
[11:28:09] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_end
[11:28:10] [Render thread/INFO]: [Shaders] Framebuffer created: dfb
[11:29:47] [Render thread/INFO]: [Shaders] Framebuffer created: dfb
[11:30:49] [Server thread/INFO]: Saving and pausing game...
[11:30:49] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:overworld
[11:30:49] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_nether
[11:30:49] [Server thread/INFO]: Saving chunks for level 'ServerLevel[Gaia (Hardcore)]'/minecraft:the_end
[11:30:50] [Render thread/INFO]: [Shaders] Framebuffer created: dfb
That's basically the entire log, along with spawn point being (re)set.
That's sort of why I was wondering what could cause the desync issues described to such a severity. I know what it is and that it might happen, but the severity seems excessive unless there's like a severe lack of CPU speed, RAM, or storage bottleneck? Hence I was asking about those things.
But the latest version of the game also fails to load at all so it sounds like there's other issues. I'm also confused though because 1.9 to 1.20.1 is stated to work but have the issue, but 1.20.1 is also the latest official version (1.20.2 is upcoming) so clarity is needed there.
Sadly that did not work either..
Im having same problem, my whole menu is lagging and slow but world lags same as your. And this started about same time as your (last week)
Legend
Same problem here. Started around the same time, too.
Here also. Worked just fine a week ago, now freezing when it says saving world. Quite impossible to play.
I'm wondering if something changed with the launcher (there's been some updates lately) or if there was a micro-update applied to all recent enough versions of the game?
There seems to be a bit of people mentioning this so I wonder if there's some common denominator. I haven't had any issues with 1.20.1. I have, however, noticed that when starting either of my 1.19 profiles, the frame rate of the main menu seems a bit jumpy for five seconds or so, but I don't know when that started because I've been spending almost all of my time in my 1.20 profile lately. It doesn't have any issues with saving or general performance though.
Something definitely seems up though.
I found a report about this issue on the bug tracker, though a commenter brushes it off as a technical support issue (not a valid game bug, and if it is suddenly affecting many people, which is also noted in the report, there has to be something going on, though it could be an update of the OS, antivirus, firewall, or other incompatible software that is the real cause; Mojang does not make "micro updates" to any version, I've seen people who thought that something was changed with some old version (example) but it was only faulty memory as the contents of the jar file showed no changes).
MC-265470 Autosave lag in single player vanilla
https://minecrafthopper.net/help/known-incompatible-software/ (many are noted to cause freezes, crashes, or degraded performance)
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Same issue, but week a go i installed some windows 10 updates. It try to rollback and see what does it for the game play.
The second Tuesday of each month is the day Windows pushes its monthly updates, so while that was a bit over a week ago now, if people started reporting this issue around a week ago (accounting for some lag time for those updating a bit later, and taking a few days to realize it), then there is some slight correlation with that timeframe. Not saying it is a Windows update that caused it but the timeframe does line up. Maybe Windows pushed an updated driver to some people that's causing it?
Somebody recently posted a similar thread in Support and said that updating their "MB drivers" (which I think means "motherboard") fixed the issue for them; as I also noted, a report on the official bug tracker seems to say that everybody with the issue was from northern Europe, so it could be affecting a regional computer brand (if not necessarily exclusive to the region):
https://www.minecraftforum.net/forums/support/java-edition-support/3187243-extended-loading-and-saveing-times
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Usually means motherboard, yes, but the drivers for those tend to pertain to numerous things as opposed to just one. That could includes any onboard things (like sound and networking). The chipset drivers (one of which is now on the CPU, another of which is on the motherboard) are probably the primary one most people refer to, and those would relate to CPU and storage subsystem (and other I/O like USB, etc.).
The person in the link you provided has a Core i9 13900K and a RTX 4090. I'm going to go out on a limb and presume that's either self assembled, or if it from a reseller, they likely just use off the shelf parts so it's probably not a given OEM brand but either a certain motherboard brand or just certain chipsets/platforms. Therefore, knowing the mothebroard brand and model would possibly be useful.
My Windows was updated last week but I haven't had any issues with Minecraft.
I was also thinking if it was caused by windows update because after update it started lagging. I am also from northern Europe.
edit: I just scanned and updated things on my motherboard manufacturer site. Then I downloaded newest motherboard update. This worked for me I think. Thank you all!
Legend
I'm wondering if there's a common correlation here, like Windows version, motherboard chipset, CPU type, or whatever. I wonder if Windows was pushing a "bad" chipset driver to some platforms. At least it sounds like this sudden influx issue had a rather quick solution found?