Good morning Larry,

I did some quick checks on your code and I'm pretty sure what causes the problem (not that you're able to solve it, but at least it should be a good hint for jcl).

Started your level from WED and it crashed - as you said.
Started the level from SED and it worked perfect.

==> Checked the different parameters for the engine with -diag.
Paramters when running from WED: -nx 300 -diag -wnd
Parameters when running from SED: -diag -wnd -ta -debug

==> Removed -debug & -ta from the command line / did not change anything
==> Added -nx 300 to the command line ==> crash
==> Removed -nx 300 from the WED commandline ==> no crash

The -nx statement for its own does not cause the crash (-nx40 is working smoothly) - but it seems as if the high value leads to the crash.

As the error seems to happend randomly on different computer-settings I would suggest you to check if the crash is in relation to the height of the nexus value (e.g. if it doesn't crash, just set a value like -nx 1200 ).

Greetings,
Timo Stark

PS: just saw that this problem was already reported - so it might be the magical number 300 aaand
PS2: pretty amazing, but it don't seem to stand in any relationship to the available memory

System specs:
Windows XP (SP3)
Genuine Intel CPU 585, 2.16 GHZ
2 GB ram
Mobile Intel (R) 4 Series Express Chipset Family (yeah integrated gpus rocks )