[LemonSkull]

- 27 Sep 2014 02:14 #137977 Hi, I've been getting this problem on pixelmon whenever I launch it, does anyone know a solution?
[00:10:47] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Using primary tweak class name cpw.mods.fml.common.launcher.FMLTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLTweaker
[00:10:47] [main/INFO] [FML]: Forge Mod Loader version 7.10.18.1180 for Minecraft 1.7.10 loading
[00:10:47] [main/INFO] [FML]: Java is Java HotSpot(TM) Client VM, version 1.7.0_51, running on Windows Vista:x86:6.0, installed at C:\Program Files\Java\jre7
[00:10:47] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Loading tweak class name cpw.mods.fml.common.launcher.FMLDeobfTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLInjectionAndSortingTweaker
[00:10:47] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper
[00:10:50] [main/INFO] [FML]: Found valid fingerprint for Minecraft Forge. Certificate fingerprint e3c3d50c7c986df74c645c0ac54639741c90a557
[00:10:50] [main/INFO] [FML]: Found valid fingerprint for Minecraft. Certificate fingerprint cd99959656f753dc28d863b46769f7f8fbaefcfc
[00:10:50] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.relauncher.CoreModManager$FMLPluginWrapper
[00:10:50] [main/INFO] [LaunchWrapper]: Calling tweak class cpw.mods.fml.common.launcher.FMLDeobfTweaker
[00:10:50] [main/INFO] [LaunchWrapper]: Launching wrapped minecraft {net.minecraft.client.main.Main}
[00:10:51] [main/INFO]: Setting user: 424wither
[00:10:52] [Client thread/INFO]: LWJGL Version: 2.9.1
[00:10:54] [Client thread/INFO] [MinecraftForge]: Attempting early MinecraftForge initialization
[00:10:54] [Client thread/INFO] [FML]: MinecraftForge v10.13.0.1180 Initialized
[00:10:54] [Client thread/INFO] [FML]: Replaced 182 ore recipies
[00:10:54] [Client thread/INFO] [MinecraftForge]: Completed early MinecraftForge initialization
[00:10:55] [Client thread/INFO] [FML]: Searching C:\Users\Josh (Owner)\AppData\Roaming\.minecraft\mods for mods
[00:10:58] [Client thread/INFO] [FML]: Forge Mod Loader has identified 3 mods to load
[00:10:59] [Client thread/INFO]: Reloading ResourceManager: Default, FMLFileResourcePack:Forge Mod Loader, FMLFileResourcePack:Minecraft Forge
[00:10:59] [Client thread/INFO] [FML]: Processing ObjectHolder annotations
[00:10:59] [Client thread/INFO] [FML]: Found 341 ObjectHolder annotations
[00:10:59] [Client thread/INFO] [FML]: Configured a dormant chunk cache size of 0
[00:10:59] [Client thread/INFO] [FML]: Applying holder lookups
[00:10:59] [Client thread/INFO] [FML]: Holder lookups applied
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x4c7d3e22, pid=4112, tid=8668
#
# JRE version: Java(TM) SE Runtime Environment (7.0_51-b13) (build 1.7.0_51-b13)
# Java VM: Java HotSpot(TM) Client VM (24.51-b03 mixed mode windows-x86 )
# Problematic frame:
# C [ig4icd32.dll+0x43e22]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Josh (Owner)\AppData\Roaming\.minecraft\hs_err_pid4112.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

[error occurred during error reporting , id 0xc0000005]

[Cheesey2223]

- 28 Sep 2014 13:48 #138052 Are you running any other mods other than pixelmon?

I cant tell, is this the error report with more information? If not could you please post it.


Furthermore if this is a bug, this should not be here, you need to report it to the Issue Tracker.

Just some helpful guy...