I had GECK for F3 working fine, but replacing the .exe and .dll with the contents of GECK_NV_v1.1 results in a reliable crash whenever I try to fire it up.

In XP I get a pretty huge technical dump, but of course I can't select/highlight any of it to copy...

As luck would have it, I have the same result on my Linux box in wine, both running Steam + F:NV from Steam.

On this one, I get some debug info:

doneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ wine Geck.exe fixme:win:EnumDisplayDevicesW ((null),0,0x33c784,0x00000000), stub!fixme:win:EnumDisplayDevicesW ((null),0,0x33c738,0x00000000), stub!fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x1725b0, dst_window (nil) stub!wine: Unhandled stack overflow at address 0xc0855c (thread 0009), starting debugger...err:seh:setup_exception_record stack overflow 1244 bytes in thread 0009 eip 7efa0371 esp 00240e54 stack 0x240000-0x241000-0x340000Segmentation faultdoneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ winecfgdoneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ wine Geck.exe fixme:win:EnumDisplayDevicesW ((null),0,0x33c784,0x00000000), stub!fixme:win:EnumDisplayDevicesW ((null),0,0x33c738,0x00000000), stub!fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x174e60, dst_window (nil) stub!wine: Unhandled stack overflow at address 0xc0855c (thread 001b), starting debugger...err:seh:setup_exception_record stack overflow 1244 bytes in thread 001b eip 7efa0371 esp 00240e54 stack 0x240000-0x241000-0x340000err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf749a7e6wine client error:1b: write: Bad file descriptor^Cfixme:console:CONSOLE_DefaultHandler Terminating process 1a on event 0fixme:winmm:MMDRV_Exit Closing while ll-driver openerr:mmtime:TIME_MMTimeStop Timer still active?!doneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ wine Geck.exe fixme:win:EnumDisplayDevicesW ((null),0,0x33c784,0x00000000), stub!fixme:win:EnumDisplayDevicesW ((null),0,0x33c738,0x00000000), stub!fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x174e60, dst_window (nil) stub!wine: Unhandled stack overflow at address 0xc0855c (thread 002c), starting debugger...err:seh:setup_exception_record stack overflow 1244 bytes in thread 002c eip 7efa0371 esp 00240e54 stack 0x240000-0x241000-0x340000err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf74b97e6wine client error:2c: write: Bad file descriptor^Cfixme:console:CONSOLE_DefaultHandler Terminating process 2b on event 0fixme:winmm:MMDRV_Exit Closing while ll-driver openerr:mmtime:TIME_MMTimeStop Timer still active?!doneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ wine Geck.exe fixme:win:EnumDisplayDevicesW ((null),0,0x33c784,0x00000000), stub!fixme:win:EnumDisplayDevicesW ((null),0,0x33c738,0x00000000), stub!fixme:d3d9:IDirect3DDevice9ExImpl_CheckDeviceState iface 0x174e60, dst_window (nil) stub!wine: Unhandled stack overflow at address 0xc0855c (thread 003b), starting debugger...err:seh:setup_exception_record stack overflow 1244 bytes in thread 003b eip 7efa0371 esp 00240e54 stack 0x240000-0x241000-0x340000err:seh:raise_exception Unhandled exception code c0000005 flags 0 addr 0xf75627e6wine client error:3b: write: Bad file descriptor^R^Cfixme:console:CONSOLE_DefaultHandler Terminating process 3a on event 0fixme:winmm:MMDRV_Exit Closing while ll-driver openerr:mmtime:TIME_MMTimeStop Timer still active?!doneill@milla:~/.wine-fnv/drive_c/Program Files/Steam/steamapps/common/fallout new vegas$ wine Geck.exe 

and EditorStackTrace.txt has basically nothing useful in it...

00ADE5EB (GECK): (filename not available): (function-name not available)^M(filename not available) (0): (function-name not available)

I don't suppose anybody could offer tips? I could upgrade XP to Win7, I've been looking for an excuse to do that, hehe.

Are you trying to use the NV Geck with Fallout 3 or something? Why are you replacing the F3 Geck with the New Vegas GECK.

The NV GECK should be put in the New Vegas installation folder.

Of course not. I installed the F3 version first, which is the most prevalent download, but the above text clearly shows this:



Also, that I'm running it from the NV directory.

Oh the way you worded that it REALLY sounds like you just replaced your Fallout 3 geck with the NV geck in the Fallout 3 directory. Anywho, I don't know what would cause that. It almost sounds like some kind of large scale hardware incompatability? The geck and game should run fine on Windows XP no problems.