FSX-SE CTDs when selecting F-4E for flight

[endl3ss]

Hi,

I recently bought and installed the entire MilViz F-4 family. The F-4E/J/S and TacPack addon.
Both the F-4J and S works brilliantly, but whenever I choose the F-4E in the selection menu, and press "Fly Now", the flight loads to about 81% and then it CTDs, and restarts FSX-SE.
Normally I never get into the cockpit at all. The only exception was just a couple of minutes ago, when I first flew the J, then the S, and finally switched to the E.
Of course FSUIPC started pinging due to me getting close to VAS-limit, but for just a short few seconds I popped up in the F-4E cockpit before it locked up and I got the fatal error message and CTDed again.

System is:
Windows 10 64-bit
FSX-SE v10.0.62615.0
All running on a ASUS RoG G750JH laptop (not exactly optimal, I know, but it has worked fairly well so far)
NVIDIA GeForce GTX 780M 4Gb
Intel Core i7-4700HQ overclocked to 3.6 GHz.
32 Gb DDR3 SDRAM

FSX-SE (and Windows for that matter) runs off separate partitions on a SSD.

Add-ons for FSX-SE:
ORBX scenery
UTX Terrain
FSUIPC 4.962
VRS TacPack (VRS Superbug and MilViz F-100D works smoothly with TacPack btw)
Steve's DX10 Scenery Fixer v3.2.98
FSX-SE now running in DX10 preview mode.

FSX-SE runs as admin, UAC is off.
UAC and ESET Smart Security was disabled during download and install of all three MilViz F-4 packages (MilViz_F-4_Phantom_II_E_vA1.161120, MilViz_F-4_Phantom_II_S_J_vA1.161120 and MilViz_F-4_Phantom_vA1.161120_E_TP_Addon).
I've re-installed the F-4 packages twice now, but still get the same CTDs whenever I try to fly the F-4E.


Windows Event viewer gives the following:

Log Name: Application
Source: Application Error
Date: 3/23/2017 9:51:35 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: SpectreASUSRoG
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MV_F-4E_Sys.dll, version: 1.4.0.8, time stamp: 0x5831aa4a
Exception code: 0xc0000005
Fault offset: 0x0002c5a8
Faulting process id: 0x3ea0
Faulting application start time: 0x01d2a416d5c7caaf
Faulting application path: E:\SteamLibrary\steamapps\common\FSX\fsx.exe
Faulting module path: E:\SteamLibrary\steamapps\common\FSX\gauges\MV_F-4E_Sys.dll
Report Id: 8063c978-100a-11e7-8e5a-00ade1ac1c1a
Faulting package full name:
Faulting package-relative application ID:

Hoping for some helpful suggestions here

[JonathanBleeker]

Sounds like you might have accidently installed the FSX Acceleration version in the SE path rather than the FSX SE version.

[endl3ss]

If you're talking about choosing the wrong version during the package install dialogue, I'm pretty sure I didn't. I can uninstall and do a third install, but I'm well aware of what version of FSX I have installed, and the choices was easy enough to understand.

[JonathanBleeker]

Just sent you an email.

[endl3ss]

Check!
I'll try it out when back home...still at work right now
...the big "nothing-to-do"-day...

[endl3ss]

I'm very happy to say that Your fix worked brilliantly. Just had my first short flight with the F-4E, and had no issues whatsoever.
Yeah, just a quick and short flight, and not delving too deeply into the various systems, but given that I never even reached the cockpit before it crashed before the fix, I'm pretty much already a happy camper.

Thank You so much for quick assistance!