Nah, they're getting a different error.
The old splitter code caused TFTD to throw this every single time
the "split" geoscape.exe exited:
XCOM crashed at 0x0 with error 0xC0000005 trying to access 0x00000000
... though that particular form
of the error was only visible with Extender running. Otherwise you only got a generic "TFTD has encountered a problem and needs to close" message (as provided by Windows itself). Whenever the game crashes with Extender running, for just about any
reason, you'll get something that looks like that rather then the traditional crash report.
The equivalent code for EU doesn't have that specific crash trigger at all, though it does collide with Extender's intro-skip to trigger the following:
XCOM crashed at 0x45E6A5 with error 0xC0000005 trying to access 0x000000
Beats me as to why those functions would interfere; if you don't already have it, here's a diff of the values involved in the split:
geoscape patch.txt 5.04K
Mind you, you will still sometimes get random crashes when you go to start combat, but these are unrelated - they happen regardless as to whether you're using a "split" EXE or not (or even any mods at all). In fact, using the "split" version makes things a little more "stable" in that the batch file that jumps between the two game engines is perfectly happy to carry on and start combat even if the geoscape engine happened to crash at that exact point.