Crash



Crashes are unexpected shut downs of Minecraft. When Minecraft crashes, it typically closes immediately, though it may show an error report marking the location of the exception that caused the crash. A sign of a server crash is a "Saving chunks" or "Shutting down internal server" screen. The most common cause of crashes are mods, preexisting bugs and updates. Attempting to modify the files of Minecraft or individual worlds, even with advanced editors, can also cause crashes. Crashes can also be caused by bugs in the game. Crashes can sometimes cause the corruption of save files if the player is not careful enough. Because of this, it is highly recommended that you regularly keep a copy of your save folder (located in the %appdata%/.minecraft directory on Windows systems or ~/.minecraft/ in linux), to reduce your losses should a world become corrupted as a result of a crash. Large TNT explosions can also cause crashes. In Bedrock Edition, crashes occurs randomly when the device is overloaded or overclocked.

Crashes used to have an error report screen but that feature has been removed. Yet sometimes an error report can quickly flash right before the game closes. Minecraft occasionally does this on startup, except it stays there, not allowing you to play the game.

A tutorial exists for obtaining the report file generated by the game when it crashes so that you can share it for diagnosis.

Mods
Crashes can easily occur due to mod conflicts, wrong versions of mods, or buggy mods. If you've installed several mods, if using the older launcher, try renaming the "bin" directory in the Minecraft folder, then start Minecraft (Or replace your current minecraft.jar with a clean minecraft.jar from either a clean backup, download a jar file from the internet or force update the game should cause you to get a new clean jar file.). A new bin folder is created. Remove the problematic mod. Now install each mod you desire one at a time, starting Minecraft and assuring that there is no crashing for each mod. Once the crashing starts occurring again, the last mod installed is likely the problem, or another mod simply does not work with it. Either way, either remove the mod you determined to be causing problems, or repeat the first step, except without installing the problematic mod.

Hardware problems
Problems with your computer's hardware can also easily cause crashing, or buggy behavior. If this is the case, it's likely you're experiencing problems in other, unrelated games as well. If Minecraft is the only game experiencing issues, then it is unlikely to be a hardware issue.

If you are indeed experiencing crashing or visual corruption in other games as well, the first thing to check is whether your computer's vents are blocked, or clogged with dust (which inevitably occurs over time). Dust or vent/fan blockages can cause overheating, which may not be severe enough to cause problems during normal computer use, but during more intensive activities such as gaming, the temperature may spike. If you're using a laptop, make sure any vents on its sides or bottom are neither blocked or filled with dust. For a desktop, check obvious fan locations for blockages, and use a flashlight to peer inside the case. If there is much dust, or any internal fans appear to not be spinning, you should either take your computer to a repair shop for a "tune-up" (mention that you suspect there is overheating problems), or read a few tutorials online related to computer cleaning (note that a computer's internal components are highly sensitive to damage from ESD (Electrostatic Discharge, basically a static shock), so it would not be difficult for you to accidentally damage your computer).

If your computer appears to not be suffering from overheating related issues, another cause of game crashing could be a damaged component, especially either the RAM, or the video card. If the problem just recently started occurring, and you have not recently installed any major updates or software such as Anti-Virus suites, you may want to take your computer to a shop to have it tested, or you can do it yourself using tools such as "memtest86+", "Furmark", etc. (however these tools tend to require a medium to large amount of computer knowledge).

It should be noted that even if your computer meets the basic system requirements of Minecraft, there is a possibility that your hardware might have unique issues, one being the use of Intel GMA (Graphics Media Accelerator) cards, known for issues with OpenGL. However, if your graphics card is one of those cards, you can still play 1.7.10 and 1.8. Step 1: Open your version jar (let's say 1.7.10.jar). Step 2: Drag all the files from this mod into 1.7.10.jar. Step 3: Save the jar file. Step 4: Play. Note that you cannot use mods if you do this, but at least you can play Minecraft.mainly you have to delete some of the minecraft mods or just one because it could also be the mods and not just the java,etc.

Software
Though unlikely, unrelated software can conceivably cause crashing in games such as Minecraft. The most likely candidates are User Account Control (Windows Vista, 7 and 8), Gatekeeper (Mac OS X Lion and Mountain Lion), various types of Anti-Malware (i.e. Anti-Virus, Anti-Spyware, Firewall, etc.) software, which could either consume enough system resources to choke other resource hungry applications, or could cause issues as a result of their "Heuristic" real-time scanning. If you recently installed an application such as AV software, try disabling it. If Minecraft stops crashing, you know the AV program is the perpetrator. You can either remove it (not recommended for security reasons), or configure it to ignore Minecraft's folder and executable. If you're unsure of how to, look up some tutorials on the Internet. Alternatively, system processes can often consume a lot of resources (most infamously Windows 10). If there is too much system overhead, there is really not much one can do besides attempting to disable those processes or switch operating systems. Another certain crash is to set all the files in the .minecraft folder to read-only.

JVM Crashes
JVM Crashes are crashes where the Java Virtual Machine, the program that runs Minecraft itself, crashes. These are almost always caused by doing large, potentially groundbreaking operations like moving many blocks, exploding a lot of TNT, or other memory or processor intensive activities, and additionally almost always are caused by running out of RAM. These are unique in that the crash message is quite different, having come from the JVM's crash handler rather than Minecraft's handler. Because of this, they do not generate a crash report in the .minecraft/crash-reports directly, but rather one directly in the .minecraft folder, with name "hs_err_pid.log" where  is the Process ID of the JVM at that time. Additionally, these crashes cannot be stopped by mods that "catch" Minecraft crashes, like VanillaFix.

Manual initialization
You can also trigger a crash manually by holding and. This is used for debugging, and is the safest possible crash. On some computers, pressing key enables the F3 key.

Ticking entities
Rarely, a ticking entity may also crash the game, either vanilla or modded.

Ticking block entities
The rarest type of crashing possible is that of a ticking block entity. This is most likely in Bedrock Edition.

Witty comments
Witty comments are phrases shown at the top of crash reports generated using the process shown earlier in this article. They do not show on crash screens and are similar in nature to splashes. They can be changed by changing your minecraft.jar .class files. They are selected using the system's time in nanoseconds.

Hopper
Hopper is a crash report utility in beta, operated by a group of community volunteers, which manages, stores, maintains crash reports, originally exclusively for technical Minecraft troubleshooting.

When a user is playing and the game crashes, the database is indexed for any matching reports. If one is not found, it prompts the user if they wish to make the report public. Otherwise, if one is found, the server prompts the user to visit a support page.