Minecraft vanilla crashes on world load?

minecraft-java-editiontechnical-issues

For about 2 weeks now my copy of Minecraft crashes on world load/create. The launcher starts correctly but when I click Singleplayer and load a world (or create one) it freezes on generating terrain and crashes.

I've tried deleting everything under the .minecraft folder, reinstalling java, nothing works.

Crash report (pastebin): Click here

If it doesn't work here's the crash report:

---- Minecraft Crash Report ----
// I just don't know what went wrong :(

Time: 3/06/15 09:37 PM
Description: Updating screen events

java.lang.IllegalStateException: failed to create a child event loop
    at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:68)
    at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:49)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:61)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:52)
    at ll$1.a(SourceFile:44)
    at ll$1.b(SourceFile:41)
    at no.c(SourceFile:10)
    at ll.a(SourceFile:121)
    at ave.a(SourceFile:1941)
    at axb.a(SourceFile:210)
    at axu.a(SourceFile:350)
    at axb.a(SourceFile:350)
    at axu.k(SourceFile:413)
    at axu.p(SourceFile:390)
    at ave.s(SourceFile:1497)
    at ave.av(SourceFile:888)
    at ave.a(SourceFile:325)
    at net.minecraft.client.main.Main.main(SourceFile:124)
Caused by: io.netty.channel.ChannelException: failed to open a new selector
    at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:128)
    at io.netty.channel.nio.NioEventLoop.<init>(NioEventLoop.java:120)
    at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:87)
    at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:64)
    ... 17 more
Caused by: java.io.IOException: Unable to establish loopback connection
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:101)
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:68)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.nio.ch.PipeImpl.<init>(PipeImpl.java:170)
    at sun.nio.ch.SelectorProviderImpl.openPipe(SelectorProviderImpl.java:50)
    at java.nio.channels.Pipe.open(Pipe.java:155)
    at sun.nio.ch.WindowsSelectorImpl.<init>(WindowsSelectorImpl.java:127)
    at sun.nio.ch.WindowsSelectorProvider.openSelector(WindowsSelectorProvider.java:44)
    at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:126)
    ... 20 more
Caused by: java.net.ConnectException: Connection timed out: connect
    at sun.nio.ch.Net.connect0(Native Method)
    at sun.nio.ch.Net.connect(Net.java:457)
    at sun.nio.ch.Net.connect(Net.java:449)
    at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:647)
    at java.nio.channels.SocketChannel.open(SocketChannel.java:189)
    at sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(PipeImpl.java:130)
    at sun.nio.ch.PipeImpl$Initializer.run(PipeImpl.java:83)
    ... 28 more


A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------

-- Head --
Stacktrace:
    at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:68)
    at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:49)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:61)
    at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:52)
    at ll$1.a(SourceFile:44)
    at ll$1.b(SourceFile:41)
    at no.c(SourceFile:10)
    at ll.a(SourceFile:121)
    at ave.a(SourceFile:1941)
    at axb.a(SourceFile:210)
    at axu.a(SourceFile:350)
    at axb.a(SourceFile:350)
    at axu.k(SourceFile:413)
    at axu.p(SourceFile:390)

-- Affected screen --
Details:
    Screen name: aya
Stacktrace:
    at ave.s(SourceFile:1497)
    at ave.av(SourceFile:888)
    at ave.a(SourceFile:325)
    at net.minecraft.client.main.Main.main(SourceFile:124)

-- System Details --
Details:
    Minecraft Version: 1.8.6
    Operating System: Windows 8.1 (amd64) version 6.3
    CPU: 2x Intel(R) Celeron(R) CPU 847 @ 1.10GHz
    Java Version: 1.8.0_25, Oracle Corporation
    Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
    Memory: 125741144 bytes (119 MB) / 336470016 bytes (320 MB) up to 1060372480 bytes (1011 MB)
    JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
    IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
    Launched Version: 1.8.6
    LWJGL: 2.9.4
    OpenGL: Intel(R) HD Graphics GL version 3.1.0 - Build 9.17.10.3517, Intel
    GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.

    Using VBOs: No
    Is Modded: Probably not. Jar signature remains and client brand is untouched.
    Type: Client (map_client.txt)
    Resource Packs: []
    Current Language: English (US)
    Profiler Position: N/A (disabled)

Best Answer

Judging from your stacktrace (The list of all the event that lead up the error) , your Java or possibly minecraft is having an issue with your network. It cannot access something it needs to continue.

At this point there are a few things that could cause it. But tt is hard to narrow it down from this point because minecraft's code is obfuscated and the error report is cut off by the crash handler.

  1. Troubleshooting your firewall or if you have a proxy, tinkering with that.
  2. Verifying your Java is installed correctly may help also.
  3. Another alternative could be that this is caused by Minecraft attempting to open the world to LAN as soon as it is created. And this would be an issue with your router/modem not having a properly setup LAN network.
  4. You have launch options that are interfering with the connection information, such as a proxy for your minecraft client. You can disable these in the minecraft launcher if you have them set.