After a short period of time (between 10 seconds and minute, most commonly about 30 seconds) the game freezes. The crash doesn't seem to be related to any particularly action and is much more prevalent in some worlds than others. I've observed it in 1.7.9 and 1.6.4 but haven't tired other versions inbetween.
The crash mode is that the screen goes blank and the task is marked (in the task manager) as "Not responding". It can, however, be killed with the task manager. Any already started sound effects continue but no new ones are started. It doesn't respond to any input and does not ever resume responding.
There is no output to the game log other than a few lines reporting that the game stopped unexpectedly (hence the launcher is reshown). The reported error code is usually 1 but sometimes a large negative number. There is no Java stack backtrace.
The crash occurs both in windowed and full screen mode. When in windowed mode the AMD control centre reports that the driver has crashed but has recovered.
This appears to be an unfortunate interaction between Minecraft, Java, OpenGL and the AMD drivers but as none of them produce an error report it's impossible for me know what actually happened.
For clarity:
- The same machine will run high-end games for hours on end without crashing; I don't believe this is a power supply or over-heating problem
- The crashes do not happen on the same machine when using the integrated GPU (Intel HD 4600).
- The crashes do not happen on another machine using the same graphics cards (but with Windows 7).
- Moving between Java 7 and 8 makes no difference
- There are no other graphical issues with the game