Like many of you, I was encountering a severe FPS issue with Minecraft 1.8.8 after upgrading my device (a Surface Pro 3) from Windows 8.1 to Windows 10. I was using a 64x64 suite of resource packs (Misa's with patches). I didn't pay much attention to FPS before the upgrade, so I am not sure what I was running at. But I have an older machine (Surface Pro) that ran just fine with the 64x64 resource packs, and when I compared it, it was running with around 33 fps.
On the Windows 10 machine, when I tried to check the fps rate, it was running at 0-4 fps with the 64x64 resource packs loaded. Without them loaded, the fps was around 14-18. Yuck!
I tried a variety of issues to fix the problem:
Updated java
Increased memory settings from 1-2 GB (the -Xmx parameter)
Set Javaw.exe compatibility mode to Windows 8
Set Javaw.exe compatibility mode to Windows 8 with Run as administrator
None of these worked. And then I realized that Minecraft was still running Java version 1.8_25 64-bit, because this version of Java downloads with the program and is in a subfolder of Minecraft. So I tried changing the profile to use the 64-bit version of 1.8_51. Still no luck.
And then I found a solution:
Edit your profile
Under Java Settings (Advanced), check the Executable path checkbox
Change the path to the 32-bit version of the latest version of Java: C:\Program Files (x86)\Java\jre1.8.0_51\bin\javaw.exe
After this change, Minecraft ran on my Windows 10 machine at 33-35 fps without the 64x64 resource pack, 25-30 fps with the 64x64 resource packs. Of course, this was without the game maximized. When maximized, the game runs with an fps of about half that - 16-18 fps.
Or at least it did until I made this additional change:
Edit your profile
Under Java Settings (Advanced), check the JVM Arguments checkbox
Add this setting after the -Xmx setting: -Xms1G
Here's the complete set of settings in the textbox: -Xmx1G -Xms1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
This increased the allocated memory to match the maximum memory, and doing this added back 10-15 fps, so the game with the 64x64 resource pack loaded was running at the same rate as the fps without the resource pack and this new setting. (In other words, back up to 33-35 fps, 25-30 fps when maximized.)
The end result is, Minecraft is now playable on my Surface Pro 3 running Windows 10 after making the above two changes.
Notes and Disclaimers
First, let me just say that these results are on my machine. These fixes may or may not fix your problems with frame rate on your machine. Nor do I know if this will fix the crashing issues that others are encountering. (However, I would not be afraid to give this fix a try to see if the crashing is also resolved.). I am posting this primarily to give everyone something to try that worked for me.
Second, I don't know if Minecraft runs fine on 32-bit. (I haven't noticed anything yet, but it's early.). If you have the answer to this question, please post a note to let everyone know.
Third, this seems to be an issue with 64-bit Java running under Windows 10. I don't know what changed, but this problem might go away with either a Java update or a Microsoft update or both. Keep an eye out, as you'll probably want to switch these settings back once the issue is resolved.
Happy Minecrafting, everyone!
UPDATE:
Okay, good news to report. Microsoft released several Windows 10 patches and an update for the graphics driver for my Surface Pro 3. I just installed them tonight, and Minecraft performance has improved again. The Faithful 32x32, Glimmer's Steampunk 64x64, and Misa's 64x64 (with patches) resource packs are all working and running with only slightly less FPS (18-24) than the un-resource packed game (28-40).
I've only played for a short while, but so far the game is vastly better than it was before. So I suspect the Windows 10 problem has been solved.
I had the same issue. I was running Minecraft fine at 60 fps on my 64 bit Windows 8.1 laptop the other day. As soon as I updated to Windows 10 I experience major lag (around 10 fps) so it was pretty much unplayable without the tiny minimized window. I tried everything, updated my drivers, reinstalled different versions of java. At one point, I got rid of java and launched Minecraft.exe from the website, which installed the new-ish built in Minecraft java. This fixed my problem completely. But then the next time I relaunched it was down to 10 frames again. So I'm back to square (block) one. I honestly don't know what's going on. Any ideas? Is it a problem with Java? Will Microsoft have an updating fixing this?
I hope so, though it wouldn't surprise me if this was a Windows 10 and a Java fix (to make Java compatible with Windows 10). The downloaded Java that installs with Minecraft seems to be the 64-bit version. So I'd try downloading and installing the 32-bit version of Java from Java.com, then switch Minecraft to using that. That may fix the problem for the short term, or at least it did for me and a few others.
I've been playing the game and haven't noticed any issues with running under 32-bit, just a reduced render distance maximum.
The other item to watch out for is running any other primary applications at the same time as Minecraft. For example, I've got the game going while I'm writing this, and typing in the Edge browser is rather slow. (By primary, I mean programs like a browser, Word, Excel, etc. If you have a virus scanner or other Internet protection software, don't disable that.)
Second, I don't know if Minecraft runs fine on 32-bit. (I haven't noticed anything yet, but it's early.). If you have the answer to this question, please post a note to let everyone know.
At least in my case, allocating 1 GB of RAM is asking for an out of memory error (an in-game screen that says "Minecraft has run out of memory"; the game itself doesn't actually crash and lets you go back to the title screen) which is a bit misleading in that it is due to the 32 bit process space (2 GB max, including memory used by the JVM itself and native libraries) being exhausted, not due to actually running out of heap space; this also appears to be the main reason why older versions (1.6.4 and earlier, 1.7 apparently removed it) gave you a warning about using Far render distance on 32 bit Java, where it is very likely to occur, I've even had it on Normal (8 chunks) when going to/from the Nether. For this reason I use the following JVM arguments when playing; note that this is on a 32 bit Windows 7 Ultimate computer but the same should apply to Windows 10:
-Xmx768M -Xms768M -Xss1024K
Note the last argument as well - that's to avoid crashes due to stack overflow, during world generation, and should be used with 32 bit, particularly since 1.7 and/or with mods, since it only allocates a third of the stack space as 64 bit (1024K), at least on Windows with Oracle Java (this varies by OS and JVM vendor/version). Otherwise, most of the issues I've seen with running Minecraft on 32 bit Java occur when the OS itself is 64 bit, which makes sense since it has to emulate a 32 bit environment instead of running natively, which takes additional resources.
NB: This is also when running 1.6.4, which I find works better without the other JVM arguments which were added for 1.8; otherwise, you may just want to change the memory settings of the default JVM arguments. Also, sp614x says that the "CMSIncrementalMode" argument may not be ideal, and I do get stuttering when using it; the default GC does cause a single longer lag spike from time to time but is much less frequent.
Ahh, thank you for that, TheMasterCaver. The -Xss switch is not one that I was aware of. I have added it to my game. The rest of your post is also great. Thank you for sharing the information.
FYI, everyone, I have replaced the Misa pack with another 64-bit one (Glimmer's Steampunk), and FPS seems to be better using that pack, even without the MCPatcher that Glimmer recommends. So if you're using a Resource Pack, try changing it to see if a different one gives better performance.
I just installed Windows 10 update KB3081424 and switched back to using the 64-bit version of Java. Latest version of Java seems to work best (not the one that downloads with the PC version). Frame rate seems to have improved with no resource packs installed.
The frame rate is still uber-slow when a 64-bit resource pack like Glimmer's is installed.
So right now, I have a choice - play 64-bit vanilla with no resource packs (or find a smaller sized one that works and still looks good), or play on 32-bit where things seem to be a bit flaky (blocks sometimes don't break, tools with enchantments break but then magically reappear for a short time) and have a really nice looking game.
For now, I'm going to play the 64-bit version without a resource pack, to see if the issue is really fixed, or if performance degrades over time.
Good news and bad news. The good news is that the Windows patch today does allow Minecraft PC to be playable. I'm getting between 20 and 42 fps, with an average around 33-35 fps with no texture packs installed.
The bad news is that texture packs, even 32x32 packs, are still not usable. Even the Faithful 32x32 pack causes lag. And while movement is possible with the Faithful pack, the lag is just bad enough to make the game annoying rather than enjoyable.
So we're not quite out of the woods yet. Hopefully the next patch will finish clearing things up.
I have the same problem. With 125 mods and 64x resource packs for almost everything, with 64-bit Java 8u51 on Windows 7 Pro SP1, fully patched, I was mostly in the 30-40 FPS range, which would probably make most twitch gamers recoil in horror but is perfectly playable in Minecraft, particularly on a builder-oriented 1.7.10 private server. I tried adding the -Xms1G, but it has made little or no difference. I also tried turning off all of my 64x resource packs, and that made no difference either. A new single-player 1.8.8 game with the same set of 64x resource packs loaded runs at the full expected speed.
I've tried this with and without -XX:+CMSIncrementalMode with no discernible difference in performance. I just restarted in order to apply KB3081424, and it also has made no appreciable difference.
I'm typically seeing memory allocation at about 44%, or just under 2G. The machine has 16GB RAM and six cores (AMD PhenomII processor, Thuban microarchitecture) and an Asus-built nVidia GTX560Ti video card. I just manually forced reinstall of the nVidia driver to make certain I'm using the correct latest-version Win10 x64 driver.
Solved my performance problem ... and it wasn't any kind of tuning issue at all.
I've been suspicious for a whole of my Mushkin Chronos SSD. Windows 7 Pro didn't seem to get on very well with it, I had a lot of strange issues with things like file copy errors and window position settings not being saved. It appears Windows 10 REALLY did not like the Mushkin; I swapped it out this afternoon for a Samsung 850 Pro and let Samsung's tuning wizard properly tune Windows 10 for the SSD, and I'm now seeing up to 70-80FPS with no other changes.
Yeah something is wrong with Windows 10 x64 and Java 8u51 x64. I can't do squat while having a texture pack on (soundpacks are fine). One time it even BSOD'ed my Windows. Until Microsoft and Oracle uploads updates, we can't do anything about it.
On the bright side, I can confirm this works. On Windows 10 with a 128x resource pack and a 3D model pack.
Yeah something is wrong with Windows 10 x64 and Java 8u51 x64. I can't do squat while having a texture pack on (soundpacks are fine). One time it even BSOD'ed my Windows. Until Microsoft and Oracle uploads updates, we can't do anything about it.
On the bright side, I can confirm this works. On Windows 10 with a 128x resource pack and a 3D model pack.
I tried turning off all my 64x resource packs and it made no difference. In fact I just started up my client and connected to my server with no resource packs installed at all, then created a new single-player world with my full modpack and no resource packs, and I'm still unplayably slow at single-digit FPS, to a maximum of maybe 20FPS. I'm pretty certain there is some kind of compatibility issue with Windows 10, and I have a suspicion it's at the device-driver level. Minecraft on my Windows 10 box is acting as though it's running on an unaccelerated dumb VGA card. But another player on my server, using a laptop with a different graphics chipset from my gamebox, has no issues. This really seems to suggest it's a video driver issue, not a Java issue per se. (Although on the other hand, even just loading and logging in, before there's any graphics rendering going on at all, are also horribly slow. So maybe there is a Java problem as well...)
Okay, good news to report. Microsoft released several Windows 10 patches and an update for the graphics driver for my Surface Pro 3. I just installed them tonight, and Minecraft performance has improved again. The Faithful 32x32, Glimmer's Steampunk 64x64, and Misa's 64x64 (with patches) resource packs are all working and running with only slightly less FPS (18-24) than the un-resource packed game (28-40).
I've only played for a short while, but so far the game is vastly better than it was before. So I suspect the Windows 10 problem has been solved.
Got one possible clue. My video card is an ASUS nVidia GTX560Ti DirectCU II card, Fermi chipset, with 1GB VRAM. However, DXDiag is reporting it as having just shy of 4GB (4045MB).
Is Windows 10 misreading the memory on the card and trying to use VRAM that isn't there...? Could Windows 10 or DirectX be detecting that the card has "only" 1GB of VRAM and trying to backfill it to 4GB using system memory...? Because I'm pretty sure that would SUCK. You know, sort of like it's doing now.
Capsule summary: The API used by DXDIAG was not written to handle more than 1GB of graphics RAM or more than 4GB of system RAM, and if you exceed either of those, it reports complete garbage.
Like many of you, I was encountering a severe FPS issue with Minecraft 1.8.8 after upgrading my device (a Surface Pro 3) from Windows 8.1 to Windows 10. I was using a 64x64 suite of resource packs (Misa's with patches). I didn't pay much attention to FPS before the upgrade, so I am not sure what I was running at. But I have an older machine (Surface Pro) that ran just fine with the 64x64 resource packs, and when I compared it, it was running with around 33 fps.
On the Windows 10 machine, when I tried to check the fps rate, it was running at 0-4 fps with the 64x64 resource packs loaded. Without them loaded, the fps was around 14-18. Yuck!
I tried a variety of issues to fix the problem:
None of these worked. And then I realized that Minecraft was still running Java version 1.8_25 64-bit, because this version of Java downloads with the program and is in a subfolder of Minecraft. So I tried changing the profile to use the 64-bit version of 1.8_51. Still no luck.
And then I found a solution:
After this change, Minecraft ran on my Windows 10 machine at 33-35 fps without the 64x64 resource pack, 25-30 fps with the 64x64 resource packs. Of course, this was without the game maximized. When maximized, the game runs with an fps of about half that - 16-18 fps.
Or at least it did until I made this additional change:
Here's the complete set of settings in the textbox: -Xmx1G -Xms1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
This increased the allocated memory to match the maximum memory, and doing this added back 10-15 fps, so the game with the 64x64 resource pack loaded was running at the same rate as the fps without the resource pack and this new setting. (In other words, back up to 33-35 fps, 25-30 fps when maximized.)
The end result is, Minecraft is now playable on my Surface Pro 3 running Windows 10 after making the above two changes.
Notes and Disclaimers
First, let me just say that these results are on my machine. These fixes may or may not fix your problems with frame rate on your machine. Nor do I know if this will fix the crashing issues that others are encountering. (However, I would not be afraid to give this fix a try to see if the crashing is also resolved.). I am posting this primarily to give everyone something to try that worked for me.
Second, I don't know if Minecraft runs fine on 32-bit. (I haven't noticed anything yet, but it's early.). If you have the answer to this question, please post a note to let everyone know.
Third, this seems to be an issue with 64-bit Java running under Windows 10. I don't know what changed, but this problem might go away with either a Java update or a Microsoft update or both. Keep an eye out, as you'll probably want to switch these settings back once the issue is resolved.
Happy Minecrafting, everyone!
UPDATE:
Okay, good news to report. Microsoft released several Windows 10 patches and an update for the graphics driver for my Surface Pro 3. I just installed them tonight, and Minecraft performance has improved again. The Faithful 32x32, Glimmer's Steampunk 64x64, and Misa's 64x64 (with patches) resource packs are all working and running with only slightly less FPS (18-24) than the un-resource packed game (28-40).
I've only played for a short while, but so far the game is vastly better than it was before. So I suspect the Windows 10 problem has been solved.
Can confirm this works, thanks man!
You're welcome I sincerely hope this fixes everyone, at least until some patches get pushed out.
Excellent! Very happy to hear this helped you out!
This made my FPS worse.
I had the same issue. I was running Minecraft fine at 60 fps on my 64 bit Windows 8.1 laptop the other day. As soon as I updated to Windows 10 I experience major lag (around 10 fps) so it was pretty much unplayable without the tiny minimized window. I tried everything, updated my drivers, reinstalled different versions of java. At one point, I got rid of java and launched Minecraft.exe from the website, which installed the new-ish built in Minecraft java. This fixed my problem completely. But then the next time I relaunched it was down to 10 frames again. So I'm back to square (block) one. I honestly don't know what's going on. Any ideas? Is it a problem with Java? Will Microsoft have an updating fixing this?
I hope so, though it wouldn't surprise me if this was a Windows 10 and a Java fix (to make Java compatible with Windows 10). The downloaded Java that installs with Minecraft seems to be the 64-bit version. So I'd try downloading and installing the 32-bit version of Java from Java.com, then switch Minecraft to using that. That may fix the problem for the short term, or at least it did for me and a few others.
I've been playing the game and haven't noticed any issues with running under 32-bit, just a reduced render distance maximum.
The other item to watch out for is running any other primary applications at the same time as Minecraft. For example, I've got the game going while I'm writing this, and typing in the Edge browser is rather slow. (By primary, I mean programs like a browser, Word, Excel, etc. If you have a virus scanner or other Internet protection software, don't disable that.)
At least in my case, allocating 1 GB of RAM is asking for an out of memory error (an in-game screen that says "Minecraft has run out of memory"; the game itself doesn't actually crash and lets you go back to the title screen) which is a bit misleading in that it is due to the 32 bit process space (2 GB max, including memory used by the JVM itself and native libraries) being exhausted, not due to actually running out of heap space; this also appears to be the main reason why older versions (1.6.4 and earlier, 1.7 apparently removed it) gave you a warning about using Far render distance on 32 bit Java, where it is very likely to occur, I've even had it on Normal (8 chunks) when going to/from the Nether. For this reason I use the following JVM arguments when playing; note that this is on a 32 bit Windows 7 Ultimate computer but the same should apply to Windows 10:
-Xmx768M -Xms768M -Xss1024K
Note the last argument as well - that's to avoid crashes due to stack overflow, during world generation, and should be used with 32 bit, particularly since 1.7 and/or with mods, since it only allocates a third of the stack space as 64 bit (1024K), at least on Windows with Oracle Java (this varies by OS and JVM vendor/version). Otherwise, most of the issues I've seen with running Minecraft on 32 bit Java occur when the OS itself is 64 bit, which makes sense since it has to emulate a 32 bit environment instead of running natively, which takes additional resources.
NB: This is also when running 1.6.4, which I find works better without the other JVM arguments which were added for 1.8; otherwise, you may just want to change the memory settings of the default JVM arguments. Also, sp614x says that the "CMSIncrementalMode" argument may not be ideal, and I do get stuttering when using it; the default GC does cause a single longer lag spike from time to time but is much less frequent.
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?
Ahh, thank you for that, TheMasterCaver. The -Xss switch is not one that I was aware of. I have added it to my game. The rest of your post is also great. Thank you for sharing the information.
FYI, everyone, I have replaced the Misa pack with another 64-bit one (Glimmer's Steampunk), and FPS seems to be better using that pack, even without the MCPatcher that Glimmer recommends. So if you're using a Resource Pack, try changing it to see if a different one gives better performance.
I just installed Windows 10 update KB3081424 and switched back to using the 64-bit version of Java. Latest version of Java seems to work best (not the one that downloads with the PC version). Frame rate seems to have improved with no resource packs installed.
The frame rate is still uber-slow when a 64-bit resource pack like Glimmer's is installed.
So right now, I have a choice - play 64-bit vanilla with no resource packs (or find a smaller sized one that works and still looks good), or play on 32-bit where things seem to be a bit flaky (blocks sometimes don't break, tools with enchantments break but then magically reappear for a short time) and have a really nice looking game.
For now, I'm going to play the 64-bit version without a resource pack, to see if the issue is really fixed, or if performance degrades over time.
Good news and bad news. The good news is that the Windows patch today does allow Minecraft PC to be playable. I'm getting between 20 and 42 fps, with an average around 33-35 fps with no texture packs installed.
The bad news is that texture packs, even 32x32 packs, are still not usable. Even the Faithful 32x32 pack causes lag. And while movement is possible with the Faithful pack, the lag is just bad enough to make the game annoying rather than enjoyable.
So we're not quite out of the woods yet. Hopefully the next patch will finish clearing things up.
I have the same problem. With 125 mods and 64x resource packs for almost everything, with 64-bit Java 8u51 on Windows 7 Pro SP1, fully patched, I was mostly in the 30-40 FPS range, which would probably make most twitch gamers recoil in horror but is perfectly playable in Minecraft, particularly on a builder-oriented 1.7.10 private server. I tried adding the -Xms1G, but it has made little or no difference. I also tried turning off all of my 64x resource packs, and that made no difference either. A new single-player 1.8.8 game with the same set of 64x resource packs loaded runs at the full expected speed.
This is my current full Java command line:
-Xmx4G -Xms1G -XX:+UseConcMarkSweepGC -XX:-UseAdaptiveSizePolicy -Xmn128M
I've tried this with and without -XX:+CMSIncrementalMode with no discernible difference in performance. I just restarted in order to apply KB3081424, and it also has made no appreciable difference.
I'm typically seeing memory allocation at about 44%, or just under 2G. The machine has 16GB RAM and six cores (AMD PhenomII processor, Thuban microarchitecture) and an Asus-built nVidia GTX560Ti video card. I just manually forced reinstall of the nVidia driver to make certain I'm using the correct latest-version Win10 x64 driver.
Anyone have any other ideas?
Solved my performance problem ... and it wasn't any kind of tuning issue at all.
I've been suspicious for a whole of my Mushkin Chronos SSD. Windows 7 Pro didn't seem to get on very well with it, I had a lot of strange issues with things like file copy errors and window position settings not being saved. It appears Windows 10 REALLY did not like the Mushkin; I swapped it out this afternoon for a Samsung 850 Pro and let Samsung's tuning wizard properly tune Windows 10 for the SSD, and I'm now seeing up to 70-80FPS with no other changes.
I spoke too soon. Now I'm down to frequently 3-5fps again.
I think there's something around my base that is rendering HORRIBLY slowly on Windows 10. I just don't know yet what it is.
Yeah something is wrong with Windows 10 x64 and Java 8u51 x64. I can't do squat while having a texture pack on (soundpacks are fine). One time it even BSOD'ed my Windows. Until Microsoft and Oracle uploads updates, we can't do anything about it.
On the bright side, I can confirm this works. On Windows 10 with a 128x resource pack and a 3D model pack.
I tried turning off all my 64x resource packs and it made no difference. In fact I just started up my client and connected to my server with no resource packs installed at all, then created a new single-player world with my full modpack and no resource packs, and I'm still unplayably slow at single-digit FPS, to a maximum of maybe 20FPS. I'm pretty certain there is some kind of compatibility issue with Windows 10, and I have a suspicion it's at the device-driver level. Minecraft on my Windows 10 box is acting as though it's running on an unaccelerated dumb VGA card. But another player on my server, using a laptop with a different graphics chipset from my gamebox, has no issues. This really seems to suggest it's a video driver issue, not a Java issue per se. (Although on the other hand, even just loading and logging in, before there's any graphics rendering going on at all, are also horribly slow. So maybe there is a Java problem as well...)
3D model pack?
Huh. I just reloaded my 64x texture packs, without exiting that single-player game, and my framerate actually IMPROVED slightly.
Go figure.... there is something really, really freaking weird going on. And I'm certain Windows 10 is central to it.
Okay, good news to report. Microsoft released several Windows 10 patches and an update for the graphics driver for my Surface Pro 3. I just installed them tonight, and Minecraft performance has improved again. The Faithful 32x32, Glimmer's Steampunk 64x64, and Misa's 64x64 (with patches) resource packs are all working and running with only slightly less FPS (18-24) than the un-resource packed game (28-40).
I've only played for a short while, but so far the game is vastly better than it was before. So I suspect the Windows 10 problem has been solved.
Got one possible clue. My video card is an ASUS nVidia GTX560Ti DirectCU II card, Fermi chipset, with 1GB VRAM. However, DXDiag is reporting it as having just shy of 4GB (4045MB).Is Windows 10 misreading the memory on the card and trying to use VRAM that isn't there...? Could Windows 10 or DirectX be detecting that the card has "only" 1GB of VRAM and trying to backfill it to 4GB using system memory...? Because I'm pretty sure that would SUCK. You know, sort of like it's doing now....Actually, never mind that. I just found this: https://support.microsoft.com/en-us/kb/2026022
Capsule summary: The API used by DXDIAG was not written to handle more than 1GB of graphics RAM or more than 4GB of system RAM, and if you exceed either of those, it reports complete garbage.
how can i install that windows 10 patch