When I turn my minecraft on at 1.74. It was just normal. And when I try to join my own server it bugged. Later I tried and I found that It happens on every world or server I tried to log on and it only happend 1.7( I havent tested before 1.7 but its working ok at 1.8 or 1.9. Here is the things it shows me
---- Minecraft Crash Report ----
// You're mean.
Time: 16-3-19 下午2:17
Description: Ticking screen
java.lang.IndexOutOfBoundsException
at java.nio.Buffer.checkIndex(Buffer.java:540)
at java.nio.DirectIntBufferU.get(DirectIntBufferU.java:253)
at bmt.a(SourceFile:271)
at bmt.a(SourceFile:220)
at azi.a(SourceFile:1674)
at azi.a(SourceFile:1632)
at bjw.a(SourceFile:118)
at gu.a(SourceFile:70)
at gu.a(SourceFile:13)
at ef.a(SourceFile:164)
at bbm.c(SourceFile:85)
at azi.p(SourceFile:1323)
at azi.ah(SourceFile:760)
at azi.f(SourceFile:711)
at net.minecraft.client.main.Main.main(SourceFile:152)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
-- Head --
Stacktrace:
at java.nio.Buffer.checkIndex(Buffer.java:540)
at java.nio.DirectIntBufferU.get(DirectIntBufferU.java:253)
at bmt.a(SourceFile:271)
at bmt.a(SourceFile:220)
at azi.a(SourceFile:1674)
at azi.a(SourceFile:1632)
at bjw.a(SourceFile:118)
at gu.a(SourceFile:70)
at gu.a(SourceFile:13)
at ef.a(SourceFile:164)
at bbm.c(SourceFile:85)
-- Affected screen --
Details:
Screen name: bbm
-- Affected level --
Details:
Level name: MpServer
All players: 0 total; []
Chunk stats: MultiplayerChunkCache: 0, 0
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options:
Level spawn location: World: (8,64,8), Chunk: (at 8,4,8 in 0,0; contains blocks 0,0,0 to 15,255,15), Region: (0,0; contains chunks 0,0 to 31,31, blocks 0,0,0 to 511,255,511)
Level time: 0 game time, 0 day time
Level dimension: 0
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: adventure (ID 2). Hardcore: false. Cheats: false
Forced entities: 0 total; []
Retry entities: 0 total; []
Server brand: ~~ERROR~~ NullPointerException: null
Server type: Non-integrated multiplayer server
Stacktrace:
at bka.a(SourceFile:289)
at azi.b(SourceFile:1952)
at azi.f(SourceFile:720)
at net.minecraft.client.main.Main.main(SourceFile:152)
-- System Details --
Details:
Minecraft Version: 1.7.4
Operating System: Windows 10 (amd64) version 10.0
Java Version: 1.8.0_25, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 357534344 bytes (340 MB) / 488636416 bytes (466 MB) up to 7635730432 bytes (7282 MB)
JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx8G
AABB Pool Size: 18497 (1035832 bytes; 0 MB) allocated, 18497 (1035832 bytes; 0 MB) used
IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0
Launched Version: 1.7.4
LWJGL: 2.9.1
OpenGL: GeForce GTX 980M/PCIe/SSE2 GL version 4.5.0 NVIDIA 361.91, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Anisotropic filtering is supported and maximum anisotropy is 16.
Shaders are available because OpenGL 2.1 is supported.
Is Modded: Probably not. Jar signature remains and client brand is untouched.
Type: Client (map_client.txt)
Resource Packs: []
Current Language: 简体中文 (中国)
Profiler Position: N/A (disabled)
Vec3 Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used
Anisotropic Filtering: Off (1)
Related issues
Comments


How do I solve it.

Turn render distance below 16 using 1.8+ before going pre-1.8

See MC-38527
1.7.4 is outdated, we only accept bugs from the latest releases.
This is most likely the issue in which the render distance is too high for pre-1.8 releases.