I start the game from the launcher 2.1.1462 and don't even get to the game window appearing before having a game crash with exit code -1073741819.
21:04:33 | launcher | Preparing to launch minecraft client for 1.13.2 |
21:04:33 | launcher | Checking installations. |
21:04:33 | launcher | Minecraft client 1.13.2 is ready to start. |
21:04:34 | launcher | Starting! |
21:04:34 | launcher | Using default game log configuration client-1.12.xml (outputs XML) |
21:04:42 | cft | Setting user: mikeypl0001 |
21:05:18 | cft | LWJGL Version: 3.1.6 build 14 |
21:05:28 | launcher |
|
22:05:28 | monitor | Process crashed with exit code -1073741819 |
Related issues
Attachments
Comments


I'm having exactly this same issue.
1.13.1 and older run just fine. 1.13.2 and 18w43b both crash shortly after pressing play roughly 90% of the time (when it does run, play is normal until I exit). No game log (latest.log) or crash report are created. The launcher game output states:
monitor | Process Monitor | Process crashed with exit code -1073741819 |
The launcher log does contain the error and stops here:
[1025/131816:INFO:GameCallbacks.cpp(199)] game/cft (Client thread) info LWJGL Version: 3.1.6 build 14
[1025/131819:INFO:GameCallbacks.cpp(199)] launcher/launcher (main) info
[1025/131819:INFO:GameCallbacks.cpp(199)] launcher/monitor (Process Monitor) fatal Process crashed with exit code -1073741819
Minecraft IRC support was unable to identify any issues with the computer and is suggesting that I reload Windows. However, Since 1.13.1 and older run without error, I am having difficulty accepting the the issue is with the system when the failure is specific to the last two versions.
EDIT: I've attached the Windows event log, which points to lwjgl.dll

I still get this issue although I've made some progress. I've deleted and reinstalled MC then restarted. I then found it will start as normal for anything the first time I run it, but if I try to play Minecraft 1.13.2+ after that first time without restarting I still get that fatal error.


The same exact thing is happening to me

So, is there a solution to this issue?