FSX SE crashes when exiting a flight with the 737-200

[jfwharton]

Does your system meet the sim's requirements? YES
Did you temporarily disable your anti-virus program during the download process? YES
Before installing did you disable UAC. (User Account Control)? YES
Did you install, and are you running the sim as an admin? YES
Before running the sim did you make sure the FSX/P3D directory is off limits to any AV scanning? YES
Does your system have the required distributables? YES
Is your video card DX11 compatible? YES
If applicable, did you disable any FSX to P3D migration tools (like Estonia) before running the sim? YES
Are you using an aircraft other than a Milviz one as your default aircraft? YES
Have you installed in the root sim directory? YES
Do you have the appropriate SimConnect libraries installed? YES

Aircraft: 737-200c
Sim platform: FSX: Steam Edition
Operating system: Win10 Pro Version 1709 (build 16299-248)
Version: 3.160428
Unique ticket identifier: 67549C0B-A1B2-5764-D62D-FB62CD7E692B

Yesterday I purchased the MILVIZ 737-200 from FSPilotshop. it is version 160428. I am running:
Windows 10 Pro
FSX SE version 10.0.62615
Active Sky Next 1.0.5870.26737
EZDOK V2
DX10fixer- 3 3 103
WX Advantage Radar - 20171207

I can start a flight without any issues. But when I either want to change aircraft or exit a flight that is using the MILVIZ 737-200 I get the message that something has caused a problem with Microsoft Flight Simulator and the program exits to desktop. Sometimes I don't even get the message. There is a long pause and then FSX SE is no longer running. I have tried uninstalling the aircraft and reinstalling, running the installation as administrator. FSX SE is run as administrator as well. I am not able to attached a copy of the windows 10 log file which indicates the issue is in SIM1.DLL. I have re-downloaded the file from FSPilotshop and confirmed it is the latest version and tried reinstalling. I do not have this issue with any other aircraft in FSX SE which include Carenado B1900D, DO 228, Cheyenne III, MILVIZ 310R, Flysimware MU-2, Lear35A, 441 Conquest, Capt Sim L1011, Just Flight L1011, etc.

Since I am not able to attach a text or doc file here is the text from the windows log regarding this error:

Log Name: Application
Source: Application Error
Date: 3/3/2018 9:58:01 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: sim1.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc000041d
Fault offset: 0x0005eb95
Faulting process id: 0x5a0
Faulting application start time: 0x01d3b30f8c5922b8
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\sim1.dll
Report Id: 722779a1-d498-481f-9ce4-88372999c235
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2018-03-03T16:58:01.252893800Z" />
<EventRecordID>40022</EventRecordID>
<Channel>Application</Channel>
<Computer>
<Security />
</System>
<EventData>
<Data>fsx.exe</Data>
<Data>10.0.62615.0</Data>
<Data>559f9a9a</Data>
<Data>sim1.dll</Data>
<Data>10.0.62615.0</Data>
<Data>559f9ab4</Data>
<Data>c000041d</Data>
<Data>0005eb95</Data>
<Data>5a0</Data>
<Data>01d3b30f8c5922b8</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe</Data>
<Data>C:\Program Files (x86)\Steam\steamapps\common\FSX\sim1.dll</Data>
<Data>722779a1-d498-481f-9ce4-88372999c235</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

I have attached a file FSX.rar that contains the crash reports from FSX.

[jfwharton]

I have discovered another issue. After uninstalling and reinstalling the aircraft I have noticed if I go into the configuration manager after FSX SE has crashed, I see the following:

Configuration Manager.jpg (128.92 KiB) Viewed 2041 times

So somehow when FSX crashes it affects the settings in the configuration manager and checks the boxes. How do I fix this? When I go into the configuration manager the checks are locked. I cannot uncheck anything that is checked. I have to uninstall and reinstall the aircraft.

[jfwharton]

Hello. Is there anyone from support?

[N4GIX]

Jon will have to help you. I'll jiggle his elbow and point him here.

[jfwharton]

Thank you. Love the aircraft, just not the crashing.

[JonathanBleeker]

I am at a bit of a loss as to what I can do to fix it until the v4 update is released. Everything has changed considerably so I can't just send you a new gauge dll to try. Bill? how far are we from this one?

[Krazycolin]

This sounds like you're not running it in Administrator mode. Please verify that, after the new installation, you're doing so.

As well, the update will be happening, with luck, in the next two weeks.

Sorry for the delays

[JonathanBleeker]

The crash in the sim1.dll I suspect is an old outdated hook used for the auto brake system. The ACM issue is something else but is due to be replaced entirely with our new AMS system.

[jfwharton]

I rechecked and the MILVIZ Menu Manager short cuts and executables are all set to run as administrator.

[N4GIX]

I am at a bit of a loss as to what I can do to fix it until the v4 update is released. Everything has changed considerably so I can't just send you a new gauge dll to try. Bill? how far are we from this one?

Note that he's not running P3Dv4.2. He's running FSX:SE. Still in all the B737 is next in line on my list of projects.

[JonathanBleeker]

the v4 update still contains improvements for the FSX SE version though.

[jfwharton]

I just finished uninstalling the 737, deleting the MILVIZ folder and verified the 737 aircraft folder was removed. Be advised when you run the installer and select the option to uninstall the aircraft, it does not remove the MILVIZ folder and it's files from FSX. It does remove the aircraft folder from under airplanes. Be advised that while I am running the steam edition of FSX my folder path is C:\Program Files (x86)\Steam\steamapps\common\FSX because I do not have the FSX boxed edition installed. After reinstalling the aircraft, running the installer as administrator I verified the MV_MM.exe and MV_ACM.exe files are set to run as administrator. FSX.exe is also set to run as administrator. I went into the menu manager and configured the each of the aircraft models to start ready for takeoff and exited. Since I also installed using the weather option I modified the aircraft.cfg file adding the _WX extension where indicated in your forum. I have attached the modified aircaft.cfg file. I started a flight with the 737, verified that the wx advantage radar worked and then just exited flight simulator. There were no errors. When I went into the Milviz Menu Manager afterward almost all of the boxes were checked, just like shown above.

[Raptor]

... Be advised when you run the installer and select the option to uninstall the aircraft, it does not remove the MILVIZ folder and it's files from FSX. It does remove the aircraft folder from under airplanes...

I believe that is intended, as is difficult to know if the user has more MILVIZ planes, in which case, the MILVIZ folder would be needed so removing the folder for one plane, would break others.

[jfwharton]

I can understand that. I do have another MILVIZ aircraft, the C310R but it doesn't use that folder. I wanted to mention also that if I uninstall and reinstall the aircraft and do not use the WX option for wx advantage radar the same issue results with the menu manager.

[N4GIX]

I just finished uninstalling the 737, deleting the MILVIZ folder and verified the 737 aircraft folder was removed. Be advised when you run the installer and select the option to uninstall the aircraft, it does not remove the MILVIZ folder and it's files from FSX.

That is intentional. It is always a bad idea to uninstall files that might be in common with other Milviz products. However, that said the new version will be using an entirely different system that is now the de-facto standard for all Milviz products.