MC-54229Total freeze on Radeon 7790 after ~30 seconds
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
Environment
OS: Windows 8.1 fully patched
Java: tied 7 and 8 both 64-bit and both latest versions from Oracle
GFX: Radeon 7790 graphics card with the latest 14.4 Catalyst drivers
PC: Intel i5 4440 CPU, 16GB RAM
Created Issue:
Total freeze on Radeon 7790 after ~30 seconds
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
Environment
OS: Windows 8.1 fully patched
Java: tied 7 and 8 both 64-bit and both latest versions from Oracle
GFX: Radeon 7790 graphics card with the latest 14.4 Catalyst drivers
PC: Intel i5 4440 CPU, 16GB RAM
Cannot confirm with Catalyst 14.4 on a Radeon 6700.
Try to uninstall and reinstall Catalyst 14.4
Before a crash: Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (minecraft/crash-reports/crash-<DATE>-client.txt) here.
After a crash: Please attach the relevant parts of the development console (especially those with " a large negative number")
Attached requested logs.
Less than two days to close a bug as "incomplete" after requesting further information? That's a good way to get your bug count down but a less good way to actually address problems. Do I need to open a new bug report now?
Well, yes, your tickets was prematurely resolved in the daily resolving routing. Sorry about that.
In the crash report is nothing unusual to see.
Some questions:
Does it crash also on single player or only while playing on (modded) server ?
Does it crash with Catalyst 13.12 ?
Do you get a file hs_err_pidXXXX.log (XXXX=numbers) ?
Please provide answers to the last questions asked as well as confirmation this still occurs on the latest snapshot (14w30c as of this moment).
FYI, the problem wasn't solved. I wound back to Catalyst 13.12 (or at least the last WHQL certified version) and the problem didn't go away. Yes, it crashes on (unmodded) single player too. I didn't ever look for a hs_err_pidXXXX.log file.
As there was unlikely to be a fix for the Radeon, when my son wants to play Minecraft we switch to the on-board Intel graphics which works fine.
I'm going to tag this as invalid as it is a tech support thing it would appear, I would suggest using the Mojang Support Center if you do want individual assistance.