Thread:MilkMC/@comment-30645975-20161217022759/@comment-27219153-20161217032318

Some crashes are very common and caused by simple things, not enough RAM or ticking entities. These are easy to fix as well.

In the first few lines of a crash report, there is a description. The description gives you a basic idea of what the problem is, but some descriptions aren't very helpful, such as: Unexpected Error. In this case, I would then proceed to read the crash report line by line. You don't have to have coding experience to do this, just read the words that you understand and try to make sense of it.

Then I proceed to the system details. I check the operating system, java version, and RAM. Then I check the mods to see if any of them have errored and also to see what mods the player is using, in case one of them is known to have issues. I usually read the rest of the crash report, but rarely does it help to find the issue.

If I've done all that and still don't know what's causing it, I may try Googling the error, and possibly rereading the crash report, just in case I missed something. Of course, if none of this works, trial and error is a good method, although usually time consuming.

The most important thing is probably experience. Many of the crashes are similar or the same and experience goes a long way. For example, I have seen this crash many times. The first time I saw it I had no idea what was causing it, but I used Google to find another person who had the same problem that had already been solved. Seeing it again today, I suspected the problem when I saw the description and confirmed my suspicion by reading through some of the crash report.

Just remember that every crash that you don't know the cause of is just another opportunity to learn. Anyway I hoped this helped. Please let me know if you have questions about any of this.