I've been having constant issues with the pre-releases crashing when I open the Pause menu, however this is where I draw the line.
I downloaded the newest PR, everything runs normal, but the game window goes crazy then crashes, leaving no logs for me to use or anything of that nature.
I have ensured that EVERYTHING is up to date (Graphics, Java, everything), and that nothing runs in the background that shouldn't be, and have tested using system optimization software, same result.
As he said, no crash log nor error message. Weird how Log4j handle logging. Maybe check the logfile?
Oh, sorry. Must have missed that bit. The best bet to finding out why the issue is happening is to enable the output log in the launcher and causing the crash to happen again.
I found some Java error files, but I fear they may be too long to paste in without tripping something, even in a spoiler. No actual crash reports to be found.
You could try updating Java, I'm not sure what version that is, but I don't think it's the one bundled with Minecraft. Have you changed the Java version Minecraft uses?
Rollback Post to RevisionRollBack
D_B
To tell them how to live is to prevent them living.
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
Stick to full releases or report the bug to mojang.
Rollback Post to RevisionRollBack
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
I can confirm this happens in 1.13 full release, I reported in the past and it was written off, stating that I should update drivers and whatnot, now I can't even access the report.
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
Wait for a new update or until a solution is found.
Rollback Post to RevisionRollBack
Say something silly, Laugh 'til it hurts, Take a risk, Sing out loud, Rock the boat, Shake things up, Flirt with disaster, Buy something frivolous, Color outside the lines, Cause a scene, Order dessert, Make waves, Get carried away, Have a great day!
This is an access violation, which means something is trying to get from a stack before it is written to. It is an issue with the pre-release, you'll have to wait for it to be fixed.
[EDIT] Lucky for you, the new version was released today.
I've been having constant issues with the pre-releases crashing when I open the Pause menu, however this is where I draw the line.
I downloaded the newest PR, everything runs normal, but the game window goes crazy then crashes, leaving no logs for me to use or anything of that nature.
I have ensured that EVERYTHING is up to date (Graphics, Java, everything), and that nothing runs in the background that shouldn't be, and have tested using system optimization software, same result.
Who needs alarms when you have geese?
There isn't enough information here to tell you why it is crashing. Can you provide a crash log or a screenshot of the output log?
As he said, no crash log nor error message. Weird how Log4j handle logging. Maybe check the logfile?
I'm a programmer. I use C/C++, BASIC, Assembly, and Python. If i sound too technicial, that's because it's the way i think.
My Suggestions
Oh, sorry. Must have missed that bit. The best bet to finding out why the issue is happening is to enable the output log in the launcher and causing the crash to happen again.
I've dug around, and found what seems to be the launcher's output log, but it does not seem to show any information of use:
[06:23:06] [Client thread/INFO]: Setting user: tywilburn16GDEV
[06:23:10] [Client thread/INFO]: LWJGL Version: 3.1.6 build 14
[06:23:12] [Client thread/INFO]: Reloading ResourceManager: Default
[06:23:34] [Sound Library Loader/INFO]: Starting up SoundSystem...
[06:23:34] [Thread-2/INFO]: Initializing No Sound
[06:23:34] [Thread-2/INFO]: (Silent Mode)
[06:23:34] [Thread-2/INFO]: OpenAL initialized.
[06:23:34] [Sound Library Loader/INFO]: Preloading sound minecraft:sounds/ambient/underwater/underwater_ambience.ogg
[06:23:34] [Sound Library Loader/INFO]: Sound engine started
[06:23:39] [Client thread/INFO]: Created: 1024x512 textures-atlas
[06:23:43] [Client thread/INFO]: Narrator library for x64 successfully loaded
[06:23:43] [Client thread/ERROR]: Realms module missing
I found some Java error files, but I fear they may be too long to paste in without tripping something, even in a spoiler. No actual crash reports to be found.
Who needs alarms when you have geese?
Insert the crash log into a code block.
If you mean the java thing, here goes:
Who needs alarms when you have geese?
This is an access violation. It's a bug within Minecraft itself. You'll have to wait for it to be patched.
Great. Guess I'll have to wait 1.13 out, then.
Who needs alarms when you have geese?
You could try updating Java, I'm not sure what version that is, but I don't think it's the one bundled with Minecraft. Have you changed the Java version Minecraft uses?
D_B
To tell them how to live is to prevent them living.
That's the bundled Java. Never saw the need to change it, should I change it to the regular version and see if that does something?
Who needs alarms when you have geese?
Reinstall latest AMD drivers from scratch.
Just did that, no effect.
Who needs alarms when you have geese?
Stick to full releases or report the bug to mojang.
I can confirm this happens in 1.13 full release, I reported in the past and it was written off, stating that I should update drivers and whatnot, now I can't even access the report.
Who needs alarms when you have geese?
Reinstall Minecraft from scratch.
Done so multiple times over the course of this issue, stays open until I click something on the menu options before doing as it did before.
Who needs alarms when you have geese?
Having the same issue, pretty lame that half the population of the community has this error with their game and it's not known why it's happening.
Wait for a new update or until a solution is found.
This is an access violation, which means something is trying to get from a stack before it is written to. It is an issue with the pre-release, you'll have to wait for it to be fixed.
[EDIT] Lucky for you, the new version was released today.