FTB Crash before it open the game

[diabloripper]

so i got some problems first my windows is causing blue screen of dead with a kinda memory management it says thing and after the second crash my ftb does not want to start anymore here is the crash log i like to hear what i can to do fix both problems

---- Minecraft Crash Report ----
// This is a token for 1 free hug. Redeem at your nearest Mojangsta: [~~HUG~~]

Time: 14-4-13 0:05
Description: Failed to start game

cpw.mods.fml.common.LoaderException: java.lang.RuntimeException: Unknown character ' ' in '/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 '/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.newInstance0(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 7 (amd64) version 6.1
Java Version: 1.7.0_17, Oracle Corporation
Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation
Memory: 160591640 bytes (153 MB) / 259522560 bytes (247 MB) up to 4260102144 bytes (4062 MB)
JVM Flags: 7 total; -Xms256M -Xmx4096M -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+AggressiveOpts -XX:+CMSClassUnloadingEnabled -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 Optifine OptiFine_1.4.6_HD_U_D5 Feed The Beast Mod Pack 2 mods loaded, 0 mods active
mcp [Minecraft Coder Pack] (minecraft.jar)
FML [Forge Mod Loader] (coremods)
LWJGL: 2.4.2
OpenGL: GeForce GTX 660 Ti/PCIe/SSE2 GL version 4.3.0, NVIDIA Corporation
Is Modded: Definitely; Client brand changed to 'forge,fml'
Type: Client (map_client.txt)
Texture Pack: Sphax PureBDCraft 128x MC14.zip
Profiler Position: N/A (disabled)
Vec3 Pool Size: ~~ERROR~~ NullPointerException: null

 

[Velotican]

How much RAM do you actually have?

 

[diabloripper]

How much RAM do you actually have?

i have 16 gb RAM

 

[Velotican]

OK. I needed to rule out the possibility that you'd somehow managed to try to give the game more RAM than you had but obviously not.

A BSOD, especially on Windows 7 is a sign that something in your computer is either seriously faulty or using a faulty driver, so the problem probably isn't FTB at all, it just happened to trigger the faulty part/driver's fault. The only way an application can cause a BSOD on its own is if it's trying to directly access your hardware and doing it very wrong.

If you don't normally have issues when using your system then it's probably one of your RAM chips that's damaged.