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 which caused the crash. A sign of a crash is a "Saving chunks" screen. The most common cause of crashes are mods and preexisting bugs. 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 (e.g.: before the beta 1.6.5 update, shift-clicking an item into a full chest would crash 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), to reduce your losses should a world become corrupted as a result of a crash.

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

Mods
Crashes can easily occur due to mod conflicts, or buggy mods. If you've installed several mods, try renaming the "bin" directory in the Minecraft folder, then start Minecraft. A new bin folder will be created. 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 a problem known as 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 lots of 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), which you will have to pay for, 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 damaged components, 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.

Software
Though unlikely, unrelated software can conceivably cause crashing in games such as Minecraft. The most likely candidates are User Account Control (Win7), 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 using Google. Another certain crash is to set all the files in the .minecraft folder to read-only.

Manual initialization
You can also trigger a crash manually by holding and. This is used for debugging, and is the safest possible crash.

How to get a crash report
More often than not, Minecraft automatically closes itself after a crash rather than displaying an error report. Here are some methods to find the error report.

Method 1

 * 1) Browse to the folder that contains your minecraft.exe launcher
 * 2) With no files selected (left click on background to deselect), Shift+Right Click anywhere in background of the window, and choose "Open command window here"
 * 3) Copy the following code: "%ProgramFiles%/Java/jre7/bin/java" -Xms1G -Xmx1G -cp Minecraft.exe net.minecraft.LauncherFrame
 * 4) Right click in the command window, select Paste and then press enter
 * 5) Login, start Single or Multiplayer and reproduce the crash
 * 6) Once you have obtained the crash report, right click on it, select all and press Enter to copy, then paste it to the proper mod thread for assistance

Method 2
 Make a new text file, and open it. Put the following code into the file: "%ProgramFiles%/Java/jre7/bin/java" -Xms1G -Xmx1G -cp "%APPDATA%\.minecraft\bin\*" -Djava.library.path="%APPDATA%\.minecraft\bin\natives" net.minecraft.client.Minecraft pause Save the file, not as a text document, but using the All Files type. Choose a name of your liking, but use the extension ".bat" Run the file. This will make the game run in offline mode, but should get you the error report. Once you have obtained the crash report, right click on it, select all and press Enter to copy, then paste it to the proper mod thread for assistance 

Method 3

 * 1) Open notepad and paste this code: "%ProgramFiles%/Java/jre7/bin/java" -Xms1G -Xmx1G -cp Minecraft.exe net.minecraft.LauncherFrame > log.txt
 * 2) Click "save as", name the file minecraft-report.bat
 * 3) Underneath where you put the file name there will be a pull down menu named file type, select the file type as All Files, and click save.
 * 4) Run the bat file that you just created. Try to duplicate the crash.  Upon crashing, an error report will be created, named "log.txt".  Congratulations, you have just created an error report.
 * 5) Open the log.txt file
 * 6) Once you have obtained the crash report, right click on it, select all and press Enter to copy, then paste it to the proper mod thread for assistance.

Method 1

 * 1) Open mcpatcher.
 * 2) Click "Test Minecraft"
 * 3) Go into a singleplayer world or multiplayer server
 * 4) Commit a bug that crashes the game somehow.
 * 5) You should now get the error.

Method 2

 * 1) Go to Macintosh HD/Applications/Utilities and open Console.app
 * 2) Run minecraft and when it crashes the java log will be added to the console, which you can then select and copy

Method 3
This method is similar to Windows' method 2 in that you can use a separate file to launch Minecraft.
 * 1) Create a new text file and open it
 * 2) Make it a plain text file (In TextEdit, use ++)
 * 3) Copy and paste the following code: cd ~/Library/Application\ Support/minecraft/bin; java -Xms512M -Xmx1024M -Xincgc -cp "minecraft.jar:jinput.jar:lwjgl.jar:lwjgl_util.jar" -Dorg.lwjgl.librarypath="$(pwd)/natives" -Dnet.java.games.input.librarypath="$(pwd)/natives" net.minecraft.client.Minecraft
 * 4) Save the file with any name you like, but uncheck both "Hide extension" and "If no extension is prvided, use '.txt:'.". Use extension ".command"
 * 5) Run the file (which will open a Terminal window), and the next time Minecraft crashes, the log will be spit out into Terminal

Linux

 * 1) Open a terminal (on distributions such as Ubuntu/Linux Mint, this is done with  +  + )
 * 2) Run   and watch the console output. You can select and copy it after making the game crash.

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 not be changed, and are hardcoded into the game.

Additionally, Witty comment unavailable :( is displayed if a comment fails to get selected, which should be rare due to the way these comments are coded.

Crash Plantages Crash 崩溃