mojira.dev
MC-209343

Minecraft crashing with exit code 1

My Minecraft crashes when I try to play it. It crashes either when it is loading or after the game has loaded and I've only played for a few seconds. I had the 107374091 crash and fixed it before; now its saying it out of memory and it can't keep up. I have allocated 4gb out of 8gb to Minecraft.

 
 
 
12:41:02.937
aar
Render thread
Preparing spawn area: 72%
12:41:03.592
aar
Render thread
Preparing spawn area: 82%
12:41:03.728
aar
Render thread
Preparing spawn area: 86%
12:41:04.970
aar
Render thread
Preparing spawn area: 86%
12:41:04.970
aar
Render thread
Preparing spawn area: 86%
12:41:05.074
aar
Render thread
Time elapsed: 12854 ms
12:41:05.347
eng
Server thread
Changing view distance to 14, from 10
12:41:06.722
acu
Server thread
HoneyHalo[local:E:7b48a48c] logged in with entity id 223 at (-120.5, 71.0, -5.5)
12:41:06.790
net.minecraft.server.MinecraftServer
Server thread
HoneyHalo joined the game
12:41:07.921
eng
Server thread
Saving and pausing game...
12:41:08.006
net.minecraft.server.MinecraftServer
Server thread
Saving chunks for level 'ServerLevel[test 25]'/minecraft:overworld
12:41:08.254
z
Render thread
Loaded 0 advancements
12:41:09.739
net.minecraft.server.MinecraftServer
Server thread
Saving chunks for level 'ServerLevel[test 25]'/minecraft:the_nether
12:41:09.740
net.minecraft.server.MinecraftServer
Server thread
Saving chunks for level 'ServerLevel[test 25]'/minecraft:the_end
12:41:09.806
net.minecraft.server.MinecraftServer
Server thread
Can't keep up! Is the server overloaded? Running 2041ms or 40 ticks behind
12:42:13.960
del
Render thread
OpenGL debug message, id=0, source=API, type=ERROR, severity=HIGH, message=Unknown internal debug message. The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (pid=4444 javaw.exe 64bit)
12:42:13.960
del
Render thread
OpenGL debug message, id=1285, source=API, type=ERROR, severity=HIGH, message=GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer object.
12:42:13.961
del
Render thread
OpenGL debug message, id=0, source=API, type=ERROR, severity=HIGH, message=Unknown internal debug message. The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (pid=4444 javaw.exe 64bit)
 12:42:13.961
del
Render thread
OpenGL debug message, id=1285, source=API, type=ERROR, severity=HIGH, message=GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer object.
12:42:13.962
del
Render thread
OpenGL debug message, id=0, source=API, type=ERROR, severity=HIGH, message=Unknown internal debug message. The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (pid=4444 javaw.exe 64bit)
12:42:13.962
del
Render thread
OpenGL debug message, id=1285, source=API, type=ERROR, severity=HIGH, message=GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer object.
12:42:13.963
del
Render thread
OpenGL debug message, id=0, source=API, type=ERROR, severity=HIGH, message=Unknown internal debug message. The NVIDIA OpenGL driver has encountered an out of memory error. This application might behave inconsistently and fail. (pid=4444 javaw.exe 64bit)
12:42:13.963
del
Render thread
OpenGL debug message, id=1285, source=API, type=ERROR, severity=HIGH, message=GL_OUT_OF_MEMORY error generated. Failed to allocate memory for buffer object.
12:42:16.734
launcher
main

  1. # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd938b21b0, pid=4444, tid=4540 # # JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16) # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops) # Problematic frame: # C [nvoglv64.dll+0x7a21b0] # # Failed to write core dump. Minidumps are not enabled by default on client versions of Windows # # An error report file with more information is saved as: # C:\Users\macke\AppData\Roaming\.minecraft\hs_err_pid4444.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # AL lib: (EE) alc_cleanup: 1 device not closed
    12:42:16.735
    monitor
    Process Monitor
    Process crashed with exit code 1

Comments 2

Hey there!

This report is invalid, as this is a technical support issue and the bug tracker is unable to help you, as the team do not have access to the appropriate resources. I'd recommend looking through the "Potential Fix" in MCL-6550 to see if this fixes the problem. After following the given advice, if the issue still persists, the bug tracker is unable to provide you with assistance so please contact Community Support.

Or please try updating your graphics card drivers.

Mackenzie jilbert

(Unassigned)

Unconfirmed

(Unassigned)

1.16.4

Retrieved