There's something pretty funky in that crash report:
UnityForceFeedback.dll caused an Access Violation (0xc0000005)
in module UnityForceFeedback.dll at 0023:703e12d3.
Error occurred at 2014-01-26_193632.
L:\D Series\DSERIESV091.exe, run by KastaRules.
37% memory in use.
0 MB physical memory [0 MB free]. <===================
0 MB paging file [0 MB free].
0 MB user address space [2819 MB free].
Read from location 00000000 caused an access violation.
0 MB physical memory [0 MB free] seems pretty suspicious. Out of memory or bad memory...?
If you're running out of memory when spawning all sorts of things could go wrong.
E.g., the Game Object isn't created and it's null in all actions that use it...
You could add some error checking to the Spawning behavior. E.g., after spawning check that the GameObject isn't null. But if you're really out of memory you're going to have other problems.
Maybe look into object pooling, so you're not making any new objects during gameplay. You make them all at the start of the level then disable/enable them as needed...