Windows .exe Unable to load FTB [fatal error]

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

kickflare

New Member
Jul 29, 2019
1
0
0
Hey, I wasn't sure where to post this but I thought you wonderful people maybe to fix it [I used to play this pack all the time without problem, I'm not sure what's happened since]

Here's the copy out of the console:-

Login complete.
Current: 1.5.2
Required: 1.5.2
Java Path: C:\Program Files\Java\jre7\bin\javaw.exe
Setting MinMemory to 256
Setting MaxMemory to 1024
Loading jars...
Added URL to classpath: file:/I:/minecraft/Unleashed/instMods/MinecraftForge.zip
Added URL to classpath: file:/I:/minecraft/Unleashed/minecraft/bin/minecraft.jar
Added URL to classpath: file:/I:/minecraft/Unleashed/minecraft/bin/lwjgl.jar
Added URL to classpath: file:/I:/minecraft/Unleashed/minecraft/bin/lwjgl_util.jar
Added URL to classpath: file:/I:/minecraft/Unleashed/minecraft/bin/jinput.jar
Loading natives...
Natives loaded...
Loading minecraft class
mc = class net.minecraft.client.Minecraft
field amount: 68
Fixed Minecraft Path: Field was private static java.io.File net.minecraft.client.Minecraft.an
MCDIR: C:\Users\kickflare\AppData\Roaming\.minecraft
Launching with applet wrapper...
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_PRIV_INSTRUCTION (0xc0000096) at pc=0x02209901, pid=12068, tid=12128
#
# 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:
# j java.awt.Component.dispatchEventImpl(Ljava/awt/AWTEvent;)V+144
#
# 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\kickflare\Desktop\hs_err_pid12068.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.sun.com/bugreport/crash.jsp
#

I guess I should include the log it mentions as well...
 

Attachments

  • fatalerrorlog02-09-2014.txt
    14.1 KB · Views: 104