I've encountered this before, but that was with modded MC, and resolved it. I've already uninstalled-reinstalled MC. MC has worked just fine before.
Crashlog:
---- Minecraft Crash Report -------- Minecraft Crash Report ----// Don't do that.
Time: 7/10/18 8:10 AMDescription: Initializing game
cdo: Unable to fit: minecraft:blocks/lava_flow - size: 32x32 - Maybe try a lowerresolution resourcepack? at cdn.c(SourceFile:58) at cdp.b(SourceFile:137) at cdp.a(SourceFile:76) at cgb.n(SourceFile:763) at cgb.a(SourceFile:188) at cgc.a(SourceFile:23) at cev.a(SourceFile:100) at bib.aq(SourceFile:530) at bib.a(SourceFile:404) at net.minecraft.client.main.Main.main(SourceFile:123)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Client threadStacktrace: at cdn.c(SourceFile:58) at cdp.b(SourceFile:137) at cdp.a(SourceFile:76) at cgb.n(SourceFile:763) at cgb.a(SourceFile:188) at cgc.a(SourceFile:23) at cev.a(SourceFile:100) at bib.aq(SourceFile:530)
-- Initialization --Details:Stacktrace: at bib.a(SourceFile:404) at net.minecraft.client.main.Main.main(SourceFile:123)
-- System Details --Details: Minecraft Version: 1.12.2 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 90079768 bytes (85 MB) / 201326592 bytes (192 MB) up to 3221225472 bytes (3072 MB) JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 1.12.2 LWJGL: 2.9.4 OpenGL: AMD Radeon(TM) R2 Graphics GL version 4.5.13506 Compatibility Profile Context 23.20.15017.3010, ATI Technologies Inc. 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: 4x AMD E2-7110 APU with AMD Radeon R2 Graphics
I believe this is due to a bug in the game because I've seen it myself (it seems to happen if I use my computer for a few weeks without restarting, which always fixes it) and I traced it down to the way the game gets the maximum texture size that the GPU (supposedly) supports (I was wondering why the game reported a texture size of -1x-1, as Optifine prints out):
public static int getGLMaximumTextureSize()
{
for (int var0 = 16384; var0 > 0; var0 >>= 1)
{
GL11.glTexImage2D(GL11.GL_PROXY_TEXTURE_2D, 0, GL11.GL_RGBA, var0, var0, 0, GL11.GL_RGBA, GL11.GL_UNSIGNED_BYTE, (ByteBuffer)null);
int var1 = GL11.glGetTexLevelParameteri(GL11.GL_PROXY_TEXTURE_2D, 0, GL11.GL_TEXTURE_WIDTH);
if (var1 != 0)
{
return var0;
}
}
return -1;
}
If you change this method (with a mod, of course) to return something like 1024 or the actual maximum texture size the game launches without any issues (also, for some reason the method above claims that the maximum texture size my GPU supports is only 4096 or 8192 when it is actually 16384, as reported by "GL11.glGetInteger(GL11.GL_MAX_TEXTURE_SIZE)". Interestingly enough, allocating 512 MB of memory gives 8192 while 1 GB gives 4096, so this seems to be related to how much native process memory is available to OpenGL, as I have a 32 bit OS and it is limited to 2 GB - even if you have a 64 bit OS try allocating less memory and see if it helps).
Also, it is worth noting that the default size of the flowing water and lava textures is 32x32, and the game places larger textures first, sorted by name, hence lava_flow is the first texture to be placed in the atlas (which means that the maximum reported texture size, and maximum size of the entire texture atlas, is less than 32x32 if it fails; a lower resolution resource pack will not help since even 1x1 textures will require more space):
(from a modded version, all textures are 16x though)
I've encountered this before, but that was with modded MC, and resolved it. I've already uninstalled-reinstalled MC. MC has worked just fine before.
Crashlog:
---- Minecraft Crash Report -------- Minecraft Crash Report ----// Don't do that.
Time: 7/10/18 8:10 AMDescription: Initializing game
cdo: Unable to fit: minecraft:blocks/lava_flow - size: 32x32 - Maybe try a lowerresolution resourcepack? at cdn.c(SourceFile:58) at cdp.b(SourceFile:137) at cdp.a(SourceFile:76) at cgb.n(SourceFile:763) at cgb.a(SourceFile:188) at cgc.a(SourceFile:23) at cev.a(SourceFile:100) at bib.aq(SourceFile:530) at bib.a(SourceFile:404) at net.minecraft.client.main.Main.main(SourceFile:123)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
-- Head --Thread: Client threadStacktrace: at cdn.c(SourceFile:58) at cdp.b(SourceFile:137) at cdp.a(SourceFile:76) at cgb.n(SourceFile:763) at cgb.a(SourceFile:188) at cgc.a(SourceFile:23) at cev.a(SourceFile:100) at bib.aq(SourceFile:530)
-- Initialization --Details:Stacktrace: at bib.a(SourceFile:404) at net.minecraft.client.main.Main.main(SourceFile:123)
-- System Details --Details: Minecraft Version: 1.12.2 Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 90079768 bytes (85 MB) / 201326592 bytes (192 MB) up to 3221225472 bytes (3072 MB) JVM Flags: 8 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx3G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=16M IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0 Launched Version: 1.12.2 LWJGL: 2.9.4 OpenGL: AMD Radeon(TM) R2 Graphics GL version 4.5.13506 Compatibility Profile Context 23.20.15017.3010, ATI Technologies Inc. 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: 4x AMD E2-7110 APU with AMD Radeon R2 Graphics
Do you have a resourcepack installed?
I am an administrator on the Advent of Ascension Wiki.
Why fire trucks are red:
A fire truck has 8 wheels and 4 people inside.
8 + 4 = 12
There are 12 inches in a foot
A Foot is a ruler
Queen Elizabeth was a ruler
Queen Elizabeth was also a ship
The ship sailed at sea
The sea had fish
The fish had fins
The Finns attacked the Russians
The Russians were red
Red has three letters
There are three sides to a triangle...
Reinstall AMD drivers from scratch.
no
that wouldn't work cause it stopped some time later and now it has come up again,
I believe this is due to a bug in the game because I've seen it myself (it seems to happen if I use my computer for a few weeks without restarting, which always fixes it) and I traced it down to the way the game gets the maximum texture size that the GPU (supposedly) supports (I was wondering why the game reported a texture size of -1x-1, as Optifine prints out):
public static int getGLMaximumTextureSize() { for (int var0 = 16384; var0 > 0; var0 >>= 1) { GL11.glTexImage2D(GL11.GL_PROXY_TEXTURE_2D, 0, GL11.GL_RGBA, var0, var0, 0, GL11.GL_RGBA, GL11.GL_UNSIGNED_BYTE, (ByteBuffer)null); int var1 = GL11.glGetTexLevelParameteri(GL11.GL_PROXY_TEXTURE_2D, 0, GL11.GL_TEXTURE_WIDTH); if (var1 != 0) { return var0; } } return -1; }If you change this method (with a mod, of course) to return something like 1024 or the actual maximum texture size the game launches without any issues (also, for some reason the method above claims that the maximum texture size my GPU supports is only 4096 or 8192 when it is actually 16384, as reported by "GL11.glGetInteger(GL11.GL_MAX_TEXTURE_SIZE)". Interestingly enough, allocating 512 MB of memory gives 8192 while 1 GB gives 4096, so this seems to be related to how much native process memory is available to OpenGL, as I have a 32 bit OS and it is limited to 2 GB - even if you have a 64 bit OS try allocating less memory and see if it helps).
Also, it is worth noting that the default size of the flowing water and lava textures is 32x32, and the game places larger textures first, sorted by name, hence lava_flow is the first texture to be placed in the atlas (which means that the maximum reported texture size, and maximum size of the entire texture atlas, is less than 32x32 if it fails; a lower resolution resource pack will not help since even 1x1 textures will require more space):
(from a modded version, all textures are 16x though)
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
So far users with that issue were using AMD graphics, so the issue is most likely with the drivers, hence my advice to completely reinstalling them.