mojira.dev
MC-95474

loging in or updating a block cases crash and makes game unplayable

Resolved
Duplicate
0

don't know exactly why it happen it may be RAM overload may not but for me it makes game unplayable "sometimes"

*What I expected to happen was game ran normal as always and be playable

*What actually happened was by updating a block or simply just login in cases a crash

Steps to Reproduce:
1. login to launcher then in world
2. update block and crash
3. or go in world then log out
4. then go back in and world may crash seconds after logging

Linked issues

duplicates 1

Comments 8

Incomplete without a crash report from ([minecraft/crash-reports/crash-<DATE>-client.txt|http://hopper.minecraft.net/help/finding-minecraft-data-folder]). Please attach it to this ticket so that we can diagnose your issue.

all crash report I can find show up from last year and I have had crashes just minutes ago so do u want me to just copy paste all the stuff on the screen it shows in the game out put it has for my player

// if so here is what is shown when I crash hope it is helpful //
Completely ignored arguments: [--nativeLauncherVersion, 286]
[16:04:06] [Client thread/INFO]: Setting user: adh92100
[16:04:06] [Client thread/INFO]: (Session ID is token:a11a725509d84056bbb1784658777943:5502e21fc6744f7ab1e416b0a0f4cb10)
[16:04:08] [Client thread/INFO]: LWJGL Version: 2.9.4
[16:04:08] [Client thread/INFO]: Reloading ResourceManager: Default
[16:04:09] [Client thread/WARN]: Missing sound for event: minecraft:entity.snowman.ambient
[16:04:09] [Client thread/WARN]: Missing sound for event: minecraft:item.bottle.fill_dragonbreath
[16:04:09] [Sound Library Loader/INFO]: Starting up SoundSystem...
[16:04:09] [Thread-5/INFO]: Initializing LWJGL OpenAL
[16:04:09] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[16:04:11] [Thread-5/INFO]: OpenAL initialized.
[16:04:11] [Sound Library Loader/INFO]: Sound engine started
[16:04:12] [Client thread/INFO]: Created: 1024x512 textures-atlas
[16:04:13] [Client thread/ERROR]: Realms module missing
[16:04:22] [Server thread/INFO]: Starting integrated minecraft server version 15w51b
[16:04:22] [Server thread/INFO]: Generating keypair
[16:04:22] [Server thread/INFO]: Preparing start region for level 0
[16:04:24] [Server thread/INFO]: Preparing spawn area: 0%
[16:04:25] [Server thread/INFO]: Preparing spawn area: 28%
[16:04:25] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID 8e6d580e-8157-4f84-b036-91fb1ac2790e
[16:04:25] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 5cc333b6-57a5-45b3-b8c2-7fabcf226269
[16:04:25] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 5ef6b743-d69b-4ba9-8b6c-06afd98ccf34
[16:04:25] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 627a0cb1-7856-4e56-b1f1-6b12eefbca41
[16:04:25] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 289d28f3-2803-4f09-a5fa-736be749d581
[16:04:25] [Server thread/WARN]: Keeping entity EntityHorse that already exists with UUID 4d70fc13-5a4e-4fa5-a673-5a7e6fce7ba0
[16:04:25] [Server thread/WARN]: Keeping entity EntityHorse that already exists with UUID 4d70fc13-5a4e-4fa5-a673-5a7e6fce7ba0
[16:04:26] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID f4252c15-1ead-41ee-8073-ed5d8a300781
[16:04:26] [Server thread/INFO]: Preparing spawn area: 92%
[16:04:26] [Server thread/INFO]: Changing view distance to 12, from 10
[16:04:27] [Server thread/INFO]: adh92100[local:E:3f485af9] logged in with entity id 318 at (808.8607823714269, 70.0, -109.78300794309918)
[16:04:27] [Server thread/INFO]: adh92100 joined the game
[16:04:27] [Server thread/WARN]: Keeping entity Pig that already exists with UUID b1b30edc-554b-4262-b813-b400b50a879f
[16:04:31] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 4478ms behind, skipping 89 tick(s)
[16:04:48] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3042ms behind, skipping 60 tick(s)
[16:05:14] [Server thread/WARN]: adh92100 is sending move packets too frequently (6 packets since last tick)
[16:05:14] [Server thread/WARN]: adh92100 is sending move packets too frequently (7 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (6 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (7 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (8 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (9 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (10 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (11 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (12 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (13 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (14 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (15 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (16 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (17 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (18 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (19 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (20 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (21 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (22 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (23 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (24 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (25 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (26 packets since last tick)
[16:05:16] [Server thread/WARN]: adh92100 is sending move packets too frequently (6 packets since last tick)
#

  1. A fatal error has been detected by the Java Runtime Environment:
    #

  2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffe2182628c, pid=1672, tid=8092
    #

  3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

  4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)

  5. Problematic frame:

  6. C [ig75icd64.dll+0x55628c]
    #

  7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #

  8. An error report file with more information is saved as:

  9. C:\Users\Terry\AppData\Roaming\.minecraft\hs_err_pid1672.log
    #

  10. If you would like to submit a bug report, please visit:

  11. http://bugreport.sun.com/bugreport/crash.jsp

  12. The crash happened outside the Java Virtual Machine in native code.

  13. See problematic frame for where to report the bug.
    #
    AL lib: (EE) alc_cleanup: 1 device not closed
    Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

Outdated and broken Intel graphics card drivers, see MC-32606

having a similar problem wonder if it is same reason hear is what it said when I crashed
Completely ignored arguments: [--nativeLauncherVersion, 286]
[21:25:57] [Client thread/INFO]: Setting user: adh92100
[21:25:57] [Client thread/INFO]: (Session ID is token:121e1e595b254a91906c3cb134318f90:5502e21fc6744f7ab1e416b0a0f4cb10)
[21:25:59] [Client thread/INFO]: LWJGL Version: 2.9.4
[21:26:00] [Client thread/INFO]: Reloading ResourceManager: Default
[21:26:01] [Client thread/WARN]: Missing sound for event: minecraft:entity.snowman.ambient
[21:26:01] [Client thread/WARN]: Missing sound for event: minecraft:item.bottle.fill_dragonbreath
[21:26:01] [Sound Library Loader/INFO]: Starting up SoundSystem...
[21:26:01] [Thread-5/INFO]: Initializing LWJGL OpenAL
[21:26:01] [Thread-5/INFO]: (The LWJGL binding of OpenAL. For more information, see http://www.lwjgl.org)
[21:26:02] [Thread-5/INFO]: OpenAL initialized.
[21:26:02] [Sound Library Loader/INFO]: Sound engine started
[21:26:03] [Client thread/INFO]: Created: 1024x512 textures-atlas
[21:26:05] [Client thread/ERROR]: Realms module missing
[21:26:17] [Server thread/INFO]: Starting integrated minecraft server version 16w02a
[21:26:17] [Server thread/INFO]: Generating keypair
[21:26:18] [Server thread/INFO]: Preparing start region for level 0
[21:26:19] [Server thread/INFO]: Preparing spawn area: 0%
[21:26:19] [Server thread/WARN]: Keeping entity Pig that already exists with UUID db06d3dd-7684-4a48-8420-9e84a689f3e3
[21:26:20] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID d74ec868-11d2-494f-8d12-d6a89cd18ecc
[21:26:20] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID 8e6d580e-8157-4f84-b036-91fb1ac2790e
[21:26:20] [Server thread/INFO]: Preparing spawn area: 28%
[21:26:20] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID 8e6d580e-8157-4f84-b036-91fb1ac2790e
[21:26:20] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 5ef6b743-d69b-4ba9-8b6c-06afd98ccf34
[21:26:21] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 627a0cb1-7856-4e56-b1f1-6b12eefbca41
[21:26:21] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 03d4c2f2-f283-4d0a-b93b-f1b03b5d2dda
[21:26:21] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 289d28f3-2803-4f09-a5fa-736be749d581
[21:26:21] [Server thread/WARN]: Keeping entity Sheep that already exists with UUID 5cc333b6-57a5-45b3-b8c2-7fabcf226269
[21:26:21] [Server thread/WARN]: Keeping entity EntityHorse that already exists with UUID 4d70fc13-5a4e-4fa5-a673-5a7e6fce7ba0
[21:26:21] [Server thread/WARN]: Keeping entity EntityHorse that already exists with UUID 4d70fc13-5a4e-4fa5-a673-5a7e6fce7ba0
[21:26:21] [Server thread/INFO]: Preparing spawn area: 69%
[21:26:21] [Server thread/WARN]: Keeping entity Rabbit that already exists with UUID f4252c15-1ead-41ee-8073-ed5d8a300781
[21:26:22] [Server thread/INFO]: Changing view distance to 12, from 10
[21:26:23] [Server thread/INFO]: adh92100[local:E:d801f829] logged in with entity id 417 at (363.1806202892945, 64.0, 172.30000001192093)
[21:26:23] [Server thread/INFO]: adh92100 joined the game
[21:26:27] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 3778ms behind, skipping 75 tick(s)
#

  1. A fatal error has been detected by the Java Runtime Environment:
    #

  2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffd7da1628c, pid=1252, tid=3896
    #

  3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

  4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)

  5. Problematic frame:

  6. C [ig75icd64.dll+0x55628c]
    #

  7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #

  8. An error report file with more information is saved as:

  9. C:\Users\Terry\AppData\Roaming\.minecraft\hs_err_pid1252.log
    #

  10. If you would like to submit a bug report, please visit:

  11. http://bugreport.sun.com/bugreport/crash.jsp

  12. The crash happened outside the Java Virtual Machine in native code.

  13. See problematic frame for where to report the bug.
    #
    AL lib: (EE) alc_cleanup: 1 device not closed
    Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

also MC-32606

#

  1. A fatal error has been detected by the Java Runtime Environment:
    #

  2. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ff99cfb4fdc, pid=2736, tid=8248
    #

  3. JRE version: Java(TM) SE Runtime Environment (8.0_25-b18) (build 1.8.0_25-b18)

  4. Java VM: Java HotSpot(TM) 64-Bit Server VM (25.25-b02 mixed mode windows-amd64 compressed oops)

  5. Problematic frame:

  6. C [ig75icd64.dll+0x524fdc]
    #

  7. Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
    #

  8. An error report file with more information is saved as:

  9. C:\Users\Terry\AppData\Roaming\.minecraft\hs_err_pid2736.log
    #

  10. If you would like to submit a bug report, please visit:

  11. http://bugreport.sun.com/bugreport/crash.jsp

  12. The crash happened outside the Java Virtual Machine in native code.

  13. See problematic frame for where to report the bug.
    #
    AL lib: (EE) alc_cleanup: 1 device not closed
    Java HotSpot(TM) 64-Bit Server VM warning: Using incremental CMS is deprecated and will likely be removed in a future release

is this same problem

@@unknown: Without fixing the broken Intel drivers you will run over and over again in the same crash. As already said twice, see MC-32606.

austin hartley

(Unassigned)

Unconfirmed

Minecraft 15w51b

Retrieved