TEKKIT LITE IS CRASHING PLEASE HELP!!!!!

[impossibear798]

so it all started last night when  i was playing tekkit lite with my friends, and my computer has this thing where if you put to much pressure on the bottom it restarts and that's what happened, its normal. but then when i turned it on again my computer stated making weird noises so i turned it off.

i left my computer off for about 2 or 3 hours then went online again to play tekkit lite, but when it started up, right after the mojang screen it went to the crash screen.

if you want the file its here please go to very bottom to for a surprise!

 ---- Minecraft Crash Report ----

// Oh - I know what I did wrong!

 

Time: 7/11/14 1:48 PM

Description: Failed to start game

 

cpw.mods.fml.common.LoaderException: java.lang.RuntimeException: Unknown character ' ' in 'C:/Users/jeremy/AppData/Roaming/.technic/modpacks/tekkitlite/config/forge.cfg:1'

at cpw.mods.fml.common.Loader.identifyMods(Loader.java:326)

at cpw.mods.fml.common.Loader.loadMods(Loader.java:470)

at cpw.mods.fml.client.FMLClientHandler.beginMinecraftLoading(FMLClientHandler.java:161)

at net.minecraft.client.Minecraft.a(Minecraft.java:412)

at asq.a(SourceFile:56)

at net.minecraft.client.Minecraft.run(Minecraft.java:746)

at java.lang.Thread.run(Unknown Source)

Caused by: java.lang.RuntimeException: Unknown character ' ' in 'C:/Users/jeremy/AppData/Roaming/.technic/modpacks/tekkitlite/config/forge.cfg:1'

at net.minecraftforge.common.Configuration.load(Configuration.java:613)

at net.minecraftforge.common.Configuration.<init>(Configuration.java:89)

at net.minecraftforge.common.ForgeDummyContainer.<init>(ForgeDummyContainer.java:47)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at cpw.mods.fml.common.Loader.identifyMods(Loader.java:321)

... 6 more

 

 

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

---------------------------------------------------------------------------------------

 

-- System Details --

Details:

Minecraft Version: 1.4.7

Operating System: Windows 8 (amd64) version 6.2

Java Version: 1.7.0_51, Oracle Corporation

Java VM Version: Java HotSpot 64-Bit Server VM (mixed mode), Oracle Corporation

Memory: 98542040 bytes (93 MB) / 171966464 bytes (164 MB) up to 954728448 bytes (910 MB)

JVM Flags: 3 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xmx1024m -XX:MaxPermSize=128m

AABB Pool Size: 0 (0 bytes; 0 MB) allocated, 0 (0 bytes; 0 MB) used

Suspicious classes: FML and Forge are installed

IntCache: cache: 0, tcache: 0, allocated: 0, tallocated: 0

FML: MCP v7.26a FML v4.7.35.556 Minecraft Forge 6.6.2.534 2 mods loaded, 0 mods active

mcp [Minecraft Coder Pack] (minecraft.jar) 

FML [Forge Mod Loader] (coremods) 

LWJGL: 2.9.0

OpenGL: Intel® HD Graphics 4000 GL version 4.0.0 - Build 10.18.10.3379, Intel

Is Modded: Definitely; Client brand changed to 'forge,fml'

Type: Client (map_client.txt)

Texture Pack: Default

Profiler Position: N/A (disabled)

Vec3 Pool Size: ~~ERROR~~ NullPointerException: null 

 

 

 

whoever fixes it becomes an admin on my server!!!

[plowmanplow]

The file configforge.cfg has become corrupted. There may be other files with similar problems but it will stop after the first fatal error. Replace that file with the original file from the server download and try again.

[impossibear798]

plowmanplow how would i do this?

 

[impossibear798]

 

Edited July 11, 2014 by impossibear798

[impossibear798]

The file configforge.cfg has become corrupted. There may be other files with similar problems but it will stop after the first fatal error. Replace that file with the original file from the server download and try again.

how would i do that

[plowmanplow]

In this case it would be sufficient to simply delete that file as it will get recreated when you start the pack.