CTD when exiting FSX after flight

[WarHorse47]

This has happened several times that I thought I'd report it.

After exiting a An-2 flight and then closing out FSX, I get an error message with FSX that it stopped working. Eventually the message reports a problem and the FSX closes.

If I change aircraft and take another flight before exiting, FSX closes as expected. And I have no problem with closing FSX after flights with other aircraft.

My assumption is that something, perhaps a gauge, is hanging up FSX and interfering it from closing.

This is not a major issue as FSX opens as usual and I can fly the An-2 (which I've been doing a lot of lately )

Here is the application event log:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: swan2.DLL, version: 1.0.156.76, time stamp: 0x51b0e2e7
Exception code: 0xc000041d
Fault offset: 0x0000d1d4
Faulting process id: 0x1e5c
Faulting application start time: 0x01ce64606b702b09
Faulting application path: C:\Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Games\Microsoft Flight Simulator X\GAUGES\swan2.DLL
Report Id: 952181a6-d057-11e2-bf32-9c2a701e23b6
Faulting package full name:
Faulting package-relative application ID:

So it appears that swan2.DLL is the culprit.

--WH

[WarHorse47]

Hi. I'd like to BUMP this topic and see if anyone else is experiencing the same so I can determine if there might be an issue with my install.

Thanks in advance

--WH

[iwn]

I had it several times.

[iwn]

And confirming that ctd comes only after using AN-2. Otherwise sim exits normally.

[rosborne]

Same same I reckon except for the faulting module.

Repro only with the An-2.

App Crash View:

Version=1
EventType=BEX
EventTime=130152528559044090
ReportType=2
Consent=1
ReportIdentifier=3d0b9f7b-d0fc-11e2-8317-10bf48d6aea1
IntegratorReportIdentifier=3d0b9f7a-d0fc-11e2-8317-10bf48d6aea1
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=FSUIPC4.dll_unloaded
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=51862b2f
Sig[6].Name=Exception Offset
Sig[6].Value=0f727d85
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=D:\Flight Simulator X\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem and try to restart the program.
UI[5]=Check online for a solution and restart the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=D:\Flight Simulator X\fsx.exe
---------------
LoadedModule 1-188
---------------
LoadedModule[189]=D:\Flight Simulator X\SibWings\Service\swsc_acc.dll
Sec[0].Key=LCID
Sec[0].Value=1033
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft® Flight Simulator X
AppPath=D:\Flight Simulator X\fsx.exe

Rob Osborne

[rosborne]

Ok...

Successful shutdown (no FSX hang) after closing with the 2.2 update.

Hope that update corrected the "issue".

[WarHorse47]

Ok...

Successful shutdown (no FSX hang) after closing with the 2.2 update.

Hope that update corrected the "issue".

What update? The one being beta tested? I ran the Updater and it indicated that there was none. Got me confused.

--WH

[rosborne]

Yes the beta update.

It's two files, a modified .air and aircraft.cfg.


===================


Drat... spoke too soon... had another one as above.

[WarHorse47]

Ah. I thought so. I'm waiting for the final outcome.

I like the first version and am not having any issues other than this CTD, so I'm reluctant to change the flight dynamics at the moment.

[iwn]

Anything new on this? It doesn´t matter much since it occurs after the flight, but yet there is something wrong somewhere.

[Alex]

Can't repeat it on test PC still.
This happens every time?
May have noticed some patterns?

We change some code in out gauge already, it's we'll be available with update.
Maybe this helps with CTD on shutdown.
If someone want to test, please email me on support@sibwings.com.

[WarHorse47]

Can't repeat it on test PC still.
This happens every time?
May have noticed some patterns?

We change some code in out gauge already, it's we'll be available with update.
Maybe this helps with CTD on shutdown.
If someone want to test, please email me on support@sibwings.com.

Yes, I can test. E-mail sent.

--WH

[iwn]

Cannot comment much on any patterns.

I run almost every time Active Sky and launch FSX from that programme.
Start FSX, choose An-2 and a suitable airfield and go up.
When I finish flight I end up with the starting screen, press x and sim asks if really want to exit, I press yes and screen disappears but the icon stays at system tray. After few seconds I receive an error notification that fatal error occured and FSX restarts.

[heywooood]

I also have this issue - if the An-2 is loaded for flight - or if I have just finished a flight in it...CTD on closing FSX
it goes into fault mode - error reporting - then automatic restart of FSX - I can then change aircraft in the selection pane and confirm the new selection - then close FSX
and it closes as it should

[iwn]

Perhaps we should specify our specs, if the culprit lies there. I checked this forum and it seems that Safir has had similar problems during its development.

My hardware/os is Win7 64bit ultimate, i7 quad at 3,06 (modest overclock from 2,93ghz). 16gb ram. Nvidia gtx680 with 320.18 drivers. Registered fsuipc and a gigatons of addons. Fsx acceleration.

[WarHorse47]

Here are my specs:

FSX Acceleration running under
Win8, 64 bit
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8 CPUs), ~3.4GHz, 16 Gb RAM
AMD Radeon HD 7870, 2 Gb with latest drivers

--WH

[heywooood]

my rig:

Intel core i5-2500k CPU @ 3.30GHz
8 Gigs RAM
Win 7 64 Pro
Nvidia GTX 670 all up to date drivers under Nvidia Inspector settings
FSX GOLD

[iwn]

Nothing suspicious to my eyes...

What about Fsx location, I've had it in default location (x86)Program Files, which is known to cause some errors with some addons.

Or a firewall conflict? I've had heavy issues with Flight1 and FSDT with my Norton.

[Basti_793]

The installation path of FSX should not matter. The hardware as well...

However, I've the following interesting questions for the devs:
1) How are the individual processes of the AN-2 discharged after use this model in FSX?
2) Are there any problems in the response-time behavior with the FSX or the interfaces of SimConnect and/or FSUIPC?

SimConnect is not exactly bug free ...

[musterpilot]

I am having the same problem
were do I find update 2.2

thanks in advance