---- Minecraft Crash Report ----
// Surprise! Haha. Well, this is awkward.

Time: 08/09/13 17:02
Description: Sending packet

java.lang.NullPointerException
	at cm.b(SourceFile:116)
	at cm.a(SourceFile:41)
	at jz.b(SourceFile:421)
	at hm.b(SourceFile:648)
	at hm.a(SourceFile:82)
	at bkz.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:488)
	at net.minecraft.server.MinecraftServer.s(SourceFile:405)
	at bkw.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:339)
	at hh.run(SourceFile:582)


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

-- Head --
Stacktrace:
	at cm.b(SourceFile:116)
	at cm.a(SourceFile:41)

-- Packet being sent --
Details:
	Packet ID: 4
	Packet class: fw
Stacktrace:
	at jz.b(SourceFile:421)
	at hm.b(SourceFile:648)
	at hm.a(SourceFile:82)
	at bkz.b(SourceFile:73)
	at net.minecraft.server.MinecraftServer.t(SourceFile:488)
	at net.minecraft.server.MinecraftServer.s(SourceFile:405)
	at bkw.s(SourceFile:124)
	at net.minecraft.server.MinecraftServer.run(SourceFile:339)
	at hh.run(SourceFile:582)

-- System Details --
Details:
	Minecraft Version: 1.6.2
	Operating System: Windows XP (x86) version 5.1
	Java Version: 1.7.0_11, Oracle Corporation
	Java VM Version: Java HotSpot(TM) Client VM (mixed mode, sharing), Oracle Corporation
	Memory: 256268880 bytes (244 MB) / 518979584 bytes (494 MB) up to 518979584 bytes (494 MB)
	JVM Flags: 2 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx512M
	AABB Pool Size: 16568 (927808 bytes; 0 MB) allocated, 16568 (927808 bytes; 0 MB) used
	Suspicious classes: No suspicious classes found.
	IntCache: cache: 0, tcache: 0, allocated: 1, tallocated: 63
	Profiler Position: N/A (disabled)
	Vec3 Pool Size: 1839 (102984 bytes; 0 MB) allocated, 1839 (102984 bytes; 0 MB) used
	Player Count: 0 / 8; []
	Type: Integrated Server (map_client.txt)
	Is Modded: Probably not. Jar signature remains and both client + server brands are untouched.