Minecraft Wiki
Please do not add any issues to this page. 
Per community discussion, this page is no longer for listing bugs or annoyances of any kind. Issues with the newest release version, weekly snapshot or pre-release belong here.

A summary of the community decision and some ideas for the page can be found here. One of the thoughts that came up was that the name "Known bugs" is no longer accurate.

Discuss and vote on possible new names for this page. After a name is decided on, we'll perform the move and remove all issues from the main/root page (this page).
This Minecraft Wiki page is about PC edition issues. For Pocket edition issues, see MCW:Issues/Pocket Edition 0.5.0.
Full releases
Weekly releases

This page's purpose is to list all the issues in the PC Minecraft version that players have come across. They pertain to the unmodified, unhacked game. Most of the single-player issues also apply to multiplayer.

Version history also contains newer issues that may not be listed on this page at the moment.

Bugs and feature requests can now be logged at Get Satisfaction: Mojang.

Make sure that your issue isn't already listed in this page! One report of each issue is already enough, no matter in which section (SMP, SSP, SMP&SSP) it stands. This page is way too big to have double reported issue standing in it!


There is no need to place bullet points before issue labels. Use bullet points only for comments. Be sure to leave a single totally blank line before each new issue (but not before comments), unless the issue appears directly beneath a header.

Please ensure that the bug is tested on a 'vanilla', installation of with NO MODS installed

Please specify whether the bug was found on SSP, SMP or Creative and if it is repeatable on other modes.

Please mark your issue with one of these issue labels: (listed from highest priority to lowest)

  • [!!] = {{bl|!!}} = Critical bug that can crash a Minecraft client or server.
  • [!] = {{bl|!}} = Major bug. Use this tag sparingly; if there is consensus your bug is not major, it will be downgraded.
  • [A!] = {{bl|a!}} = Major annoyance. Think very carefully before flagging an annoyance as major. Is it really more important than most minor bugs? Use this tag sparingly; if there is consensus your annoyance is not major, it will be downgraded.
  • [X] = {{bl}} = Minor bug.
  • [A] = {{bl|a}} = Annoyance.
  • [?] = {{bl|?}} = Potential issue that you are unsure of or that the community (on the discussion page) believes requires further vetting. Note: do not use this label to indicate this-is-not-a-bug; instead, replace the issue's current label with [A] or [A!]. Furthermore, it is inappropriate to use this to flag something you disagree with; instead, express your opinion in a comment. When you apply this label to an issue, place it after the issue's existing labels; do not remove those labels.

Labels for indicating that an issue happens only in a particular game mode: (These labels cannot stand alone; you must use them in addition to, not instead of, the ones listed above.)

  • [SP] = {{bl|sp}} = Single-player.
  • [MP] = {{bl|mp}} = Multiplayer.
  • [Su] = {{bl|su}} = Survival mode.
  • [Cr] = {{bl|cr}} = Creative mode.

Labels for indicating that an issue is restricted to a particular OS:

  • macOS = {{OS|OSX}} = Mac OS
  • Windows = {{OS|Win}} = Windows
  • Linux = {{OS|Linux}} = Linux

Labels that Mojang uses:

  • [F] = Bugs that have been fixed in the next update.
  • [N] = This is not a bug. (It is intended behaviour and will not be changed)
  • [S] = Bugs that will be skipped/ignored for now.
  • [U] = Bugs that Mojang tested but was unable to reproduce. Append this tag to the end of existing issue labels, instead of replacing them.

To produce these labels, use the following code: {{bl|c}} where c is the code of the label you wish to use. (e.g., a for annoyances, etc.)

The default issue type is minor bug; you can produce this label with the shorthand {{bl}}.

Be sure to sort issues by category, type, and priority: redstone issues go in the Redstone section, etc.; bugs go in the Bugs subsection, with major bugs listed before minor bugs, annoyances in the Annoyances subsection, with major ones before minor ones, and issues that Jeb has marked as fixed or skipped are moved to the Fixed/Skipped section. Issues that Jeb cannot reproduce, however, are to remain in their original place.

Please sign all issue reports and comments by typing ~~~ (three tildes; tilde may be found above Tab ↹ on USA keyboards, and to the right of @ on British keyboards).

Finally, please do not spontaneously delete an issue report or comment, unless it is patent nonsense submitted by someone who has not logged in. If possible, contact the submitter by user-talk first and tell them about your concerns. They will almost certainly oblige. As always, assume good faith.

Both single and multiplayer Minecraft (SP and MP)


[!!] Attempting to go into Video Settings will cause the game's renderer to "conk" out, displaying a dirt background. Attempting to do anything at this state will crash the game and display a black screen. The only way to edit video settings is to edit the settings file. (windows 7-64, 64-java, geforce 405)

[!] Cannot place a lever on glowstone.

  • Glowstone is now a glass type block, so you can break it with your hands dropping dust, and you can't put anything on top of it.

[!] Mobs glitch through walls in SMP, making them invincible, the block unminable and most exp grinder designs useless.

[!] When moving or jumping(arrow keys & spacebar) you cannot switch between items using the number keys 1-9

[A!] Playing with Skype open on the background, Minecraft's window will stop rendering for the time a Skype notification is shown on the screen. The game is not frozen, as you can still move and take damage, but it will start rendering again only when said notification will disappear.

[!!] On some clients, looking at any entity will cause a crash, this includes mobs, Players, and paintings. This occurs randomly, but appears to only happen when your reticule is directly over an entity. There are cases where looking at them will not cause a crash, but again, it is imminent to happen at any time. Tested with multiple clean runs, fresh java install, and multiple attempts at causing the crash. After looking directly at a third entity, game crashed, showed the Dirt background, and further action led to a black screen.

[!!] If you destroy a block that is destroyed instantly while scrolling the mouse wheel, minecraft displays the "saving chunks" message and crashes. This seems to be fixed in 11w47a, but it's still a problem in 1.0.0.

[!!] There is an inconsistent issue logging into servers that have been upgraded to 1.0.0 where you receive an error "The server responded with an invalid server key" and then the client will not connect to said server until either the client or server is restarted.

  • Seems to stop if the server is set to online-mode=false. This bug has been present since RC1 I believe. - TheSTAGcast 20:08, 20 November 2011 (GMT+10)
    • This is not an acceptable solution. I can verify this bug. Apocalypse r 05:40, 21 November 2011 (UTC)
  • After the first attempt, the error changes to "End of Stream". This can be worked around if there are many possible connect strings for your server (e.g. domain1.tld, domain2.tld, IP address) - each different form has one chance to either connect or give the key error, then every subsequent attempt will give "End of Stream" Frymaster 17:09, 20 November 2011 (UTC)
  • I found a fix for this. [1] --Lolmaster 19:50, 21 November 2011 (UTC)

[!] Mobs do not spawn on maps made in 1.0.0

  • Tested on 1.0 SSP, normal difficulty. New map. Lots of cows around spawn area and skeletons in nearby cave. 18:53, 20 November 2011 (UTC)
  • Tested here as well. Please make sure you're not playing on easy difficulty (SSP) or have "spawn-monsters" set to "false". Otherwise, please provide more info. — minrice2099 talk

[!!] There is a bug where on windows XP(and maybe other versions of windows but unconfirmed) minecraft closes after logging in and/or updating, this is for both when updated and not(I have tried both)and the game closes(When running other programs the game simply freezes instead of closing). The game worked fine in 1.7.3 and lower but since 1.8 and higher i have only been able to play in a web browser. (Minecraft.net)

  • This seems like an issue with java and not with minecraft. Apocalypse r 05:40, 21 November 2011 (UTC)

[!!] There is a bug when you hit a Dragon Egg with a enchanted pickaxe it crashes the game and show the "Saving Chunks" than black screen

[!!] There is a severe client bug that may involve something that arrived in the 1.8 sound update and/or the Single Player Commands mod. Screenshots taken in any way will cause Minecraft to crash and show the "Saving Chunks" screen, and then turn black. This occurs on both ssp and smp, but on Multi-player, only the dirt texture shows without the "Saving Chunks."

  • If it involves mods then it shouldn't be on this page since it does not affect vanilla minecraft. Unable to verify. Apocalypse r 05:40, 21 November 2011 (UTC)

[!!] On some Windows systems (possibly other systems too, but unconfirmed) Minecraft has problems with loading and unloading chunks, what causes to crash Minecraft frequently within 5 minutes if exploring constantly. On SMP this is even worse.

  • This seems to be caused by memory issues rather than by chunk loading and unloading. The issue does not seem to be present when using a 64 bit version of java. Still, its a horrible performance issue and should be fixed. Apocalypse r 05:40, 21 November 2011 (UTC)

[!!] On Windows XP systems with less than 1gb of RAM Minecraft causes a fatal crash (EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000084c1) in Java versions 6 and 7 after less than 5 minutes of entering a world (regardless of whether graphical settings were lowered or additional page memory has been assigned). The issue affects all versions 1.8 and up. A possible workaround is disabling sound, or using sfPlayer1's soundsystem fix, which prevents minecraft using up to 200MB more RAM than has been allocated when sound is on.

  • I can run minecraft on xp systems with less than half that much ram. access violation means segment fault, check your video drivers. Apocalypse r 05:40, 21 November 2011 (UTC)
  • Another possibility is that you are using 32-bit Java. Consider installing 64-bit if running on x64. -- 11:46, 24 November 2011 (UTC)

[!!] Huge memory leaks on Linux. On Windows XP and Vista as well - the server just increases memory usage over time even without players.[1]

  • can't reproduce here, linux server's been up 7 hours and still only using 500MB Frymaster 17:22, 20 November 2011 (UTC)
  • That citation is a log from a 1.9pre5 server. — minrice2099 talk

[!!] ATI users with 6.x drivers will not be able to run the game at all.

  • there is actually a fix for this I believe, and its an issue with lwjgl if I recall correctly, not minecraft. Apocalypse r 05:40, 21 November 2011 (UTC)

[!!] The renderer occasionally "conks out" leaving the user with the dirt background or a black screen. If the user has the dirt background and attempts to do anything, it will then give the user a black screen. If you tab out, or try to click or press keys, it will crash.

[!!] If you close the game when the end credits/story are running (after you kill the dragon) next time you load the save the game crashes.

  • Unable to reproduce: If I close during the credits or the poem, when I load the world, I end up before leaving the end. Apocalypse r 05:40, 21 November 2011 (UTC)

[A!] On SP, there is sometimes no minecart curve rail, but on MP, there is a curved rail texture.

  • Rails curve automatically when you place them; there is no "curved rail" item. Detector and powered rails cannot curve. If this is still an issue, could you give a bit more detail? — minrice2099 talk

[A] [1.0.0] Fences occupy the same physical space as they do visually, whereas fence gates occupy a whole block when closed.

[A] [1.0.0] When opening the left door of double doors, it opens the right door. When closing the right door of double doors it closes the left door. (The left and right are if you are facing the doors when there at the front of the block they are on). Not a bug, it is a FEATURE. Its use is opening double doors without having to click both of them.

[X] If you're in a boat, then you save and quit, then reload the world, you fall out of the boat.

[!] Whenever some Windows users lock their computers by either using "Start -> Lock " or a keyboard shortcut, and then log back in, the game window will be completely black. This can only be fixed by closing the engine or toggling the game between maximized and windowed settings.

[X] Sometimes you can see through everything; this randomly happens on all games on all platforms. Toggling the fog distance will change everything back to normal (Default key is F3+F).

[X] Rarely, the game can think you are 1 block high while in water, and permits walking through water as if it was air. Your view will not be affected in both first and third person, but if you are in a one block deep water, the underwater screen shows and you may drown.

[X] "Login failed" in Ubuntu and OSX. When several keyboard mappings are configured for the user, the username input uses the current mapping whereas the password input uses the default mapping, and leads to "Login failed" errors.

[A] Players can cheat by using special texture packs that make common blocks see through, thus allowing players to find minerals and other structures underground. This ruins gameplay on many multilayer servers.

  • As irritating as this is, it isn't a bug. Marked it as an annoyance (though it may be fixed in the future) Apocalypse r 05:40, 21 November 2011 (UTC)

[!] In Multiplayer, a player can see 2 players, one is moving and one is not moving. This can happen when a player teleports to somebody suddenly. It creates some lag, and then you will see another player from where the player teleported.

[X] If you tab out without having a GUI open (Esc/Inv) it will act as if shift is held down when clicking on items.

[X] It is possible to place a painting on a block that already has a button, this renders the button useless and the only way to get rid of the painting is to destroy the block.

[X] You aren't able to place a Jack 'o' lantern or a pumpkin on a fence.

[X] When having your aim on a transparent block and looking up at the clouds, the clouds go through the line.

[X] When Fishing with field of view (FOV) different than the default the fishing line graphically becomes disconnected from the rod.

[!] Minecraft sometimes cannot be closed, especially after the Out of Memory screen shows up.

[!!] When walking in a certain spot in Minecraft it may crash. The only way to fix this bug, is having a back-up of your world, otherwise your world will become unplayable forever. [2]

  • This is way to vague to be here in my opinion. Please post a world seed and coordinates so we can at least test it. — minrice2099 talk
  • this sounds like either map corruption or the result of a mod. Map corruption in particular causes issues very like this. Apocalypse r 05:40, 21 November 2011 (UTC)

[X] If you're flying in Creative mode, then save and close, then reload the world, you stop flying.

  • This has been fixed in 1.0.0. I'm not mojang, so I'll leave its status alone Apocalypse r 05:40, 21 November 2011 (UTC)

[!] When playing Minecraft for a long time (like 1 hour), trying to expand the Minecraft window can cause to freeze Minecraft for half a minute.

[?] While sprinting if you hold the jump button and repeatedly hit the ceiling you will move at about twice the speed of normal sprinting.

[?] While sprinting on ice and jumping, you jump farther

[X] While you set on a boat and minecraft crashes, once you login back on your world you will get off the boat and the boats will be duplicated.

[A!] Reduced performance on windows servers with more than 10 people. Caused by quad core processors due to minecraft not being able to run on multiple cores. Note: This has been tested on 8 different servers with no large processes running with adequate RAM and 100mbit-1000mbit connections. The result was CPU 1 nearly maxed out while cores 3-4 were mostly parked.

  • Minecraft servers don't perform as well on windows as they do on other operating systems, even when using the exact same hardware. It has more to do with windows' network handling not being up to par with linux's. Apocalypse r 05:40, 21 November 2011 (UTC)