Minecraft will not create a new world.

raylee_1

Prominent
Jul 20, 2017
1
0
510
I've recently have been in the mood to play minecraft which has worked perfectly in the past, but every time i try to create a new world on single player it loads for a few seconds and then crashes. I have uninstalled minecraft plenty of times I have even tried the older launcher to see if that was the case. I have also completely removed java and re installed it (current version Jre1.8.0-141) and i have also completely updated my graphic cards, turned off my firewall,and disabled and lan creators (hamchie,evolve ect.). But i still get crashes. can anyone help... here is my crash report.
---- Minecraft Crash Report ----
// I let you down. Sorry :(

Time: 7/20/17 5:59 PM
Description: Updating screen events

java.lang.IllegalStateException: failed to create a child event loop
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:88)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:58)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:47)
at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:58)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:77)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:72)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:59)
at ox$1.a(SourceFile:61)
at ox$1.b(SourceFile:58)
at rf.c(SourceFile:10)
at ox.a(SourceFile:152)
at bhz.a(SourceFile:2209)
at bog.a(SourceFile:212)
at bli.a(SourceFile:334)
at bog.a(SourceFile:352)
at bli.k(SourceFile:397)
at bli.q(SourceFile:374)
at bhz.t(SourceFile:1625)
at bhz.az(SourceFile:1000)
at bhz.a(SourceFile:419)
at net.minecraft.client.main.Main.main(SourceFile:123)
Caused by: io.netty.channel.ChannelException: failed to open a new selector
at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:157)
at io.netty.channel.nio.NioEventLoop.<init>(NioEventLoop.java:149)
at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:127)
at io.netty.channel.nio.NioEventLoopGroup.newChild(NioEventLoopGroup.java:36)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:84)
... 20 more
Caused by: java.io.IOException: Unable to establish loopback connection
at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source)
at sun.nio.ch.PipeImpl$Initializer.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at sun.nio.ch.PipeImpl.<init>(Unknown Source)
at sun.nio.ch.SelectorProviderImpl.openPipe(Unknown Source)
at java.nio.channels.Pipe.open(Unknown Source)
at sun.nio.ch.WindowsSelectorImpl.<init>(Unknown Source)
at sun.nio.ch.WindowsSelectorProvider.openSelector(Unknown Source)
at io.netty.channel.nio.NioEventLoop.openSelector(NioEventLoop.java:155)
... 24 more
Caused by: java.net.ConnectException: Connection timed out: connect
at sun.nio.ch.Net.connect0(Native Method)
at sun.nio.ch.Net.connect(Unknown Source)
at sun.nio.ch.Net.connect(Unknown Source)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at java.nio.channels.SocketChannel.open(Unknown Source)
at sun.nio.ch.PipeImpl$Initializer$LoopbackConnector.run(Unknown Source)
... 33 more


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

-- Head --
Thread: Client thread
Stacktrace:
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:88)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:58)
at io.netty.util.concurrent.MultithreadEventExecutorGroup.<init>(MultithreadEventExecutorGroup.java:47)
at io.netty.channel.MultithreadEventLoopGroup.<init>(MultithreadEventLoopGroup.java:58)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:77)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:72)
at io.netty.channel.nio.NioEventLoopGroup.<init>(NioEventLoopGroup.java:59)
at ox$1.a(SourceFile:61)
at ox$1.b(SourceFile:58)
at rf.c(SourceFile:10)
at ox.a(SourceFile:152)
at bhz.a(SourceFile:2209)
at bog.a(SourceFile:212)
at bli.a(SourceFile:334)
at bog.a(SourceFile:352)
at bli.k(SourceFile:397)
at bli.q(SourceFile:374)

-- Affected screen --
Details:
Screen name: blg
Stacktrace:
at bhz.t(SourceFile:1625)
at bhz.az(SourceFile:1000)
at bhz.a(SourceFile:419)
at net.minecraft.client.main.Main.main(SourceFile:123)

-- System Details --
Details:
Minecraft Version: 1.12
Operating System: Windows 10 (x86) version 10.0
Java Version: 1.8.0_141, Oracle Corporation
Java VM Version: Java HotSpot(TM) Client VM (mixed mode), Oracle Corporation
Memory: 116097640 bytes (110 MB) / 278421504 bytes (265 MB) up to 523501568 bytes (499 MB)
JVM Flags: 6 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:-UseAdaptiveSizePolicy -Xmn128M
IntCache: cache: 0, tcache: 0, allocated: 13, tallocated: 95
Launched Version: 1.12
LWJGL: 2.9.4
OpenGL: GeForce GTX 980/PCIe/SSE2 GL version 4.5.0 NVIDIA 384.76, NVIDIA Corporation
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: Yes
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)
CPU: 12x Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
 

Dylaann

Prominent
Jul 18, 2017
9
0
510
Not trying to be mean or anything, but this may not be the best place to post this. I don't think there are any Minecraft experts on this forum, so maybe try reporting this directly with Mojang? You can email them and I'm sure they'll be happy to help.