Space Siege crashes

[Digital-fol]

Hello, I'm trying to use the Space Siege NoDVD fix, but it crashes while it's loading. I can see the white dots, but after a few milliseconds after the curser is visible it has a 'Exception Detected' - MessageBox.

Does anybody else have that problem - (or better a solution)?
My OS is WindowsXP SP2.

Here is the entire crash log:
http://rafb.net/p/9NJZ2E94.html
Seems to be something with a NULL-Poiner perhaps?

-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-
-== App : Space Siege (G:\SpieleArchiv\Gas Powered Games\Space Siege\SpaceSiege.exe - Retail)
-== Log category : Crash Report
-== Session : 9/1/2008 08:55:12 PM
-== Build : Win2k (1.00.0.2063)
-== Failures : 0 warnings, 0 errors, 0 SEH's
-==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==-

--==<< Top-level exception filter report >>==--


[Game]

time: system = 7.964687, global = 7.964685

[Modules]

name = 'G:\SpieleArchiv\Gas Powered Games\Space Siege\SpaceSiege.exe', crc = 0x93879C1A, extra = 0x00FCBFA5

[Trace]

*** Report for process 0x00000AB0

Process command line : "G:\SpieleArchiv\Gas Powered Games\Space Siege\SpaceSiege.exe"
Process priority class : 32
Process priority boosted: no

*** Report for thread Main ***

Exception code: access violation (continuable) - attempted to write data at 0x00000000
Occurred at IP: 0x004034F8

Thread traits:

Thread priority : 0
Last error : 0x000000CB (Das System konnte die eingegebene Umgebungsoption nicht finden.)
Thread priority boosted: no
Thread creation time : 09/01/2008,20:55:12.0
Thread kernel mode time: 00:08:4.375
Thread user mode time : 01:40:46.875

CPU registers:

eax=108A7900 cs=001B eip=004034F8 eflags=00010202
ebx=1027438C ss=0023 esp=0012F964 ebp =00000014
ecx=0012FBFC ds=0023 esi=00000000 fs =003B
edx=101A0190 es=0023 edi=00000000 gs =0000

FPU registers:

st0= 0.000000 st4= 0.000000 ctrl=0C7F
st1= 0.000000 st5= 0.000000 stat=0120
st2= 0.000000 st6= -0.000000 tags=FFFF
st3= 0.000000 st7= 0.000000

Stack trace:

0x004034F8 SpaceSiege.exe: UIShell::ShowInterface + 1016 bytes

*** Report for thread SiegeLoad ***

Thread traits:
... see the nopaste link

[Joe Forster/STA]

And does it work without a crack?

[Digital-fol]

Sorry seems to be a bug in the original game.
I thought it may be the crack because I read in another forum that it also didn't work.
I wonder if I can return that game. I read that it sucks anyways, which is pretty sad because I'd love a space hack&slay game ;-)

[nando2002]

I see smoke in the air. lol.

The "bug" in the original game doesn't crash it. Instead it ask you for the DVD when in fact it was on the drive. GPG released a fix days ago. The problem was caused by the protection.

In fact, in some PC the game crashes when using the crack but in others works fine. If the games crashes on your PC using a crack why are you going to return it. Use you original DVD or create your own image to prevent damages on your original one.

[DABhand]

"Exception code: access violation (continuable) - attempted to write data at 0x00000000
"

Is usually a good sign of RAM problems.

[TippeX]

well, not necessarially ram problems, more like a virtualalloc failed, returning zero and the game never bothered to check before writing to it

if you had ram problems, they'd usually result in a bsod or some other more 'serious' error, system wide, not in just 1 process

[DABhand]

Not totally though, there is more than 1 type of RAM problem, and more than one type of RAM :P

It could be RAM on a Graphic Card or Sound Card. Or just plain SDRAM/DDR/DDR2.

Besides ive seen plenty of RAM problems which results in a general protection fault or Exception's when running software. So not all have to be BSOD's

[Digital-fol]

Thank you for your opinions! I'll run a memtest, and try to move my swap file to another partition.

[TippeX]

no real point in that.. unless similar crashes happen in other programs too

Exception code: access violation (continuable) - attempted to write data at 0x00000000
Occurred at IP: 0x004034F8

it 100% happened in the process code.. write data at 0x00000000 is most definately a failed memory allocation.. which is typically caused by a VirtualAlloc call failing

.004034F0: E8DBBB6C00 call .000ACF0D0 --↓1
.004034F5: 83C404 add esp,4
.004034F8: C70648127602 mov d,[esi],002761248
.004034FE: 5E pop esi
.004034FF: C3 retn

so it has to be esi = NULL... strange thing is that code xreferenced from this reads the dword from esi.. so perhaps the memory isn't writable... very odd.. but i'm pretty certain its a game bug / issue.. and not a system one...

[DABhand]

Dont get why ESI reg has been null'd. But the pop makes me assume its been push'd elsewhere.

Still strange.