Minecraft Forums

Hello. Whenever I launch Minecraft, it crashes as soon as it hits the title screen. Occasionally it lasts a couple of seconds before crashing. This occurs in both 1.8.9 (which is what I am trying to play in) and 1.12.2. Well, 1.12.2 does work, but only for the first time after deleting the .minecraft folder. Before you make suggestions, I have tried reinstalling multiple times, deleting the .minecraft folder multiple times, changing the render distance to <16, using the old launcher, and updating my graphics driver. I have never linked my Mojang account to my Twitch account and as such I don't have the option to unlink it. I am running no mods, not even Optifine. I have no idea how to fix this, and cannot play Minecraft until it is. I would immensely appreciate any help someone can give. If you need more information to diagnose the problem, just let me know. Thanks in advance.

Below are the logs for 1.8.9 and 1.12.2, with the session ID redacted, of course. Emphasis added.

*** 1.8.9 ***

13:23:25
launcher
main
info
Preparing to launch minecraft client for 1.8.9

13:23:25
launcher
main
info
Checking installations.

13:23:25
launcher
main
info
Minecraft client 1.8.9 is ready to start.

13:23:25
launcher
main
info
Starting!

13:23:26
launcher
main
info
Using default game log configuration client-1.7.xml (outputs XML)

13:23:27
ave
Client thread
info
Setting user: goocube129

13:23:27
ave
Client thread
info
(Session ID is token:********)

13:23:28
ave
Client thread
info
LWJGL Version: 2.9.4

13:23:29
bnn
Client thread
info
Reloading ResourceManager: Default

06:23:29
game
error
If on Windows, make sure to provide all of the necessary dll's as specified in the twitchsdk README. Also, make sure to set the PATH environment variable to point to the directory containing the dll's.
<log4j:Event logger="ave" timestamp="1530995009284" level="ERROR" thread="Client thread">
<log4j:Message><![CDATA[Couldn't initialize twitch stream]]></log4j:Message>
</log4j:Event>

06:23:29
monitor
Process Monitor
error
expected <

13:23:29
bpx
Sound Library Loader
info
Starting up SoundSystem...

13:23:29
bpx
Thread-6
info
Initializing LWJGL OpenAL

13:23:29
bpx
Thread-6
info
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)

13:23:30
bpx
Thread-6
info
OpenAL initialized.

13:23:30
bpx
Sound Library Loader
info
Sound engine started

*** 1.12.2 ***

13:30:51
launcher
main
info
Preparing to launch minecraft client for 1.12.2

13:30:51
launcher
main
info
Checking installations.

13:30:51
launcher
main
info
Minecraft client 1.12.2 is ready to start.

13:30:51
launcher
main
info
Starting!

13:30:51
launcher
main
info
Using default game log configuration client-1.12.xml (outputs XML)

13:30:53
bib
Client thread
info
Setting user: goocube129

13:30:54
bid
Client thread
warn
Skipping bad option: lastServer:

13:30:54
bib
Client thread
info
LWJGL Version: 2.9.4

13:30:55
cev
Client thread
info
Reloading ResourceManager: Default

13:30:55
chm
Sound Library Loader
info
Starting up SoundSystem...

13:30:56
chm
Thread-3
info
Initializing LWJGL OpenAL

13:30:56
chm
Thread-3
info
(The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)

13:30:57
chm
Thread-3
info
OpenAL initialized.

13:30:57
chm
Sound Library Loader
info
Sound engine started

13:30:59
cdp
Client thread
info
Created: 1024x512 textures-atlas

13:31:01
com.mojang.text2speech.NarratorWindows
Client thread
info
Narrator library for x64 successfully loaded

I note that for 1.12.2, there are no errors. The warning for lastServer: is, I presume, because there was no server previously played on due to all of these shenanigans.

- see point 2 here https://www.minecraftforum.net/forums/support/java-edition-support/2827415-1-12-faqs-read-before-posting

- shut down discord

- run scans with malwarebytes and adwcleaner

Thank you for your help. It was in fact Discord--I killed it through Task Manager and Minecraft worked fine. Funnily enough though, the error messages still come up but don't affect anything, and after reopening Discord I can still run Minecraft. Sooo I really don't know what happened or how it was fixed, but I'm not going to question it.

I feel a bit silly now for not thinking to try with no other apps running. Oh well. Cheers!

Edit: Now how do I mark this thread as "Resolved"?