FSX - Crash on exit caused by FSUIPC

[Lazarus Long]

Hello

 

I want to report that I've experience crash when I exit FSX. Until today everything was okay but I've installed Sibwings An-2 and simulator crashes only when I use this add-on and when I attempt to close sim.

In event viewer problem is linked to fsuipc.dll , I can reproduce this every time with no exceptions. FSX didn't crash after other add-on

 

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: FSUIPC4.dll_unloaded, version: 0.0.0.0, time stamp: 0x52d1eec2
Exception code: 0xc0000005
Fault offset: 0x603e8392
Faulting process id: 0x21f0
Faulting application start time: 0x01cf163896a00914
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: FSUIPC4.dll
Report Id: fb9b8e20-822c-11e3-91ae-74d02bc838fd

 

 

Using newest FSUIPC 4.928(registered)

 

FSUIPC4.ini.txt

FSUIPC4.log.txt

[Pete Dowson]

Faulting module name: FSUIPC4.dll_unloaded

 

As the error shows and the log confirms, FSUIPC is not actually running at the time you got the crash.  The log shows it terminated quite normally.  I can't really fix crashes outside my own code as I have no control over them. I don't know what is using FSUIPC which might be crashing when it closes -- I assume the AN-2 isn't using it for anything?

 

It looks like the "fault offset" is actually the place where a hook from the Weather module is linked to, for use in Wind Smoothing, so it seems for some reason, after installing the AN-2, some weather actions continue after FS is closing? Not seen that before, it is most odd.

 

All I might be able to do is work out a way to unhook this before terminating. Not easy, and may cause more crashes elsewhere because the modules being hooked might be unloaded first.

 

[LATER]

After looking at that I don't think it is possible without making things worse. I think the best I could do would be to keep FSUIPC runnng, somehow, for some seconds more. You could try that yourself. Add

 

ForceTerminateTime=N to the [General] section of the INI file, where N is a number of seconds.

 

Regards

Pete

[Lazarus Long]

 

 You could try that yourself. Add

 

ForceTerminateTime=N to the [General] section of the INI file, where N is a number of seconds.

 

Regards

Pete

Тhis did the trick

ForceTerminateTime=2

 

Checked several times with and without this line and FSX crashes every time when I remove this line. It's strange that sometimes (with this add-on) I have nvwgf2um.dll errors (Faulting module name: nvwgf2um.dll_unloaded, version: 0.0.0.0, time stamp: 0x52b32680) which is (as I see on internet) Nvidia DX10 renderer library 

And all this after installing An-2 on perfectly stable simulator and system.

 

I've contacted developer of An-2 and they promised update. Other folks, users of Sibwings, have similar FSUIPC "errors" with their add-ons (I've seen this on their forums)

 

Thank you very much

[Pete Dowson]

Тhis did the trick

ForceTerminateTime=2

 

Checked several times with and without this line and FSX crashes every time when I remove this line.

 

Good. However, I've also worked out some code to "unhook" the weather DLL before FSUIPC is unloaded. If you'd like to test that for me (without the ForceTerminateTime parameter) I'd be grateful. Let me know, and if okay I'll upload the amended version.

 

Regards

Pete

[Lazarus Long]

Good. However, I've also worked out some code to "unhook" the weather DLL before FSUIPC is unloaded. If you'd like to test that for me (without the ForceTerminateTime parameter) I'd be grateful. Let me know, and if okay I'll upload the amended version.

 

Regards

Pete

Short answer is  - OK

 

I'm familiar with imaging programs like Acronis and Ghost so testing&restoring system and files is easy for me. Please post link for download

[Pete Dowson]

Short answer is  - OK

 

I'm familiar with imaging programs like Acronis and Ghost so testing&restoring system and files is easy for me. Please post link for download

 

FSUIPC4928a.zip

 

To test, just put this version into the Modules folder, replacing 4.928, and remove the ForceTerminateTime parameter. Hopefully the undoing of the Hooks will solve the problem in a tidier way than using a delay.

 

If not, well, it was worth a try! ;-)

 

Thanks,

Pete

[Lazarus Long]

 

 and remove the ForceTerminateTime parameter. Hopefully the undoing of the Hooks will solve the problem in a tidier way than using a delay.

No success. Now, without line I have g3d.dll errors/crashes every time 

(Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58) and I have one crash related to panels. dll (

Faulting module name: panels.dll, version: 10.0.61637.0, time stamp: 0x46fadb59

)

 

Adding back ForceTerminateTime=2 on 4928a resolves issue again. 

 

To be honest this is not a problem with fsuipc but with  poorly written add-on or some part of add-on aircraft. Finally, it is good that we have a solution

If you have some other idea or even more *.dll-s for testing let me know.

 

btw

I didn't use external weather programs. Testing was performed with default weather teme >> Fair Weather <<<

 

[Pete Dowson]

No success. Now, without line I have g3d.dll errors/crashes every time 

(Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58) and I have one crash related to panels. dll (

Faulting module name: panels.dll, version: 10.0.61637.0, time stamp: 0x46fadb59

 

Very odd, because the change I made is nothing at all to do with G3D nor PANELS.DLLs. These crashes are on shutdown, I take it?  There's been no change except for the hook removal at shutdown.

 

FSUIPC does have a hook in G3D.DLL -- its the patch to cure some of the well-known G3D crashes. There's also one in PANELS.DLL in order to implement "mouse macros". I can only think that your aircraft add-on is somehow managing to continue on, using FS facilities to execute itself, long after FSUIPC has been told to close down.

 

I've never encoutered anything quite as strange. I might take a look at those two hooks, to see if they can be easily undone before FSUIPC disappears, but I won't promise anything. It looks best if you retain that Terminate time fiddle.

 

Adding back ForceTerminateTime=2 on 4928a resolves issue again. 

 

Okay. The removal of the hooks I've already done will still be occurring, before this delay, in any case -- so this at least proves that change is working. It is just insufficient.

 

To be honest this is not a problem with fsuipc but with  poorly written add-on or some part of add-on aircraft. Finally, it is good that we have a solution

If you have some other idea or even more *.dll-s for testing let me know.

 

 

 

Okay. I might do, but not as a top priority. I'll add to this thread if I do.

 

Regards

Pete

 

[flightcheck]

Very odd, because the change I made is nothing at all to do with G3D nor PANELS.DLLs. These crashes are on shutdown, I take it?  There's been no change except for the hook removal at shutdown.

 

FSUIPC does have a hook in G3D.DLL -- its the patch to cure some of the well-known G3D crashes. There's also one in PANELS.DLL in order to implement "mouse macros". I can only think that your aircraft add-on is somehow managing to continue on, using FS facilities to execute itself, long after FSUIPC has been told to close down.

 

I've never encoutered anything quite as strange. I might take a look at those two hooks, to see if they can be easily undone before FSUIPC disappears, but I won't promise anything. It looks best if you retain that Terminate time fiddle.

 

 

Okay. The removal of the hooks I've already done will still be occurring, before this delay, in any case -- so this at least proves that change is working. It is just insufficient.

 

 

 

Okay. I might do, but not as a top priority. I'll add to this thread if I do.

 

Regards

Pete

 

I am having this problem with hanging on exit, and a g3d.dll error

 

I will add the forceterminatetime line to the ini file. This started after updating to the latest version, 4.937b and ASN

 

I run fsx acceleration, win7 64bit, active sky next, pmdg 777x, latest nvidia drivers. registered fsuipc.

[Pete Dowson]

I am having this problem with hanging on exit, and a g3d.dll error

 

I will add the forceterminatetime line to the ini file. This started after updating to the latest version, 4.937b and ASN

 

I run fsx acceleration, win7 64bit, active sky next, pmdg 777x, latest nvidia drivers. registered fsuipc.

 

Some add-on is causing the problem. You would need to go through a process of elimination on the assorted additions to find it. Bear in mind that many add-on aircraft, not just PMDG ones, have their own DLLs loading. Sometimes the order of them is important. You can check this and change it in the DLL.XML file.

 

Pete

[flightcheck]

Some add-on is causing the problem. You would need to go through a process of elimination on the assorted additions to find it. Bear in mind that many add-on aircraft, not just PMDG ones, have their own DLLs loading. Sometimes the order of them is important. You can check this and change it in the DLL.XML file.

 

Pete

 

It is asn, adding the line ForceTerminateTime=2 fixes it but then asn never diconnects after exiting fsx.

[Pete Dowson]

It is asn, adding the line ForceTerminateTime=2 fixes it but then asn never diconnects after exiting fsx.

 

Hmm. I'm using ASN with no such problems. How are you loading it? 

 

I just checked, and I use FSUIPC to start ASN, and also KILL it forcibly when FS is closed. Here is the line in my [Programs] section:

 

RunIF1=KILL,"C:\Program Files (x86)\HiFi\ASNext_FSX\ASNext.exe"

 

This works fine for me.

 

Regards

Pete

[flightcheck]

 

Hmm. I'm using ASN with no such problems. How are you loading it? 

 

I just checked, and I use FSUIPC to start ASN, and also KILL it forcibly when FS is closed. Here is the line in my [Programs] section:

 

RunIF1=KILL,"C:\Program Files (x86)\HiFi\ASNext_FSX\ASNext.exe"

 

This works fine for me.

 

Regards

Pete

 

 

How do I setup ASN to start thru fsuipc? And is that line added under the general section? I submitted a ticket to hifi, maybe they can help me fix this. I have removed all other dll files from the xml's that are not used, it must be some conflict between PMDG 777X, ASN and FSUIPC

[Pete Dowson]

How do I setup ASN to start thru fsuipc? 

 

As I just showed you!

 

And is that line added under the general section?

 

No, as I certainly stated it goes into a section called [Programs]. Please see FSUIPC docs for more info, if needed (which you don't really as I gave you the answer already)..

 

it must be some conflict between PMDG 777X, ASN and FSUIPC

 

So why did you say it was ASN?  Now it might be the 777?

 

I doubt it, really, as all these add-ons are very frequently used by many folks. Maybe your FSX installation is corrupted someplace? In your earlier message you said it hangs on exit AND a G3D error. How can it be both? Either it hangs or it crashes, it can't do both. If it's a crash in G3D it is likely to be down to corrupted textures or medel files, related to scenery and aircraft visuals. There's nothing in FSUIPC which interacts in any way with G3D.

 

Pete

[flightcheck]

It crashes with a G3D error on exit when using FSX normally. When I add the line about force terminating, ASN hangs after exiting FSX and still says "FSX Connected"

 

I just added what addons I use so you may see if there is a conflict somewhere.

[Pete Dowson]

It crashes with a G3D error on exit when using FSX normally

 

Okay. In that case I think you have a corrupted file -- whether an aircraft or scenery file I couldn't say. I expect when you solve that it will also fix the hang. Corrupted graphics files can result in other corruption in memory and give other results which depend on memory usage and layout at the time.. There's probably no conflict at all between your add-ons, just the basic fault you need to find and fix.

 

Pete

[flightcheck]

Okay. In that case I think you have a corrupted file -- whether an aircraft or scenery file I couldn't say. I expect when you solve that it will also fix the hang. Corrupted graphics files can result in other corruption in memory and give other results which depend on memory usage and layout at the time.. There's probably no conflict at all between your add-ons, just the basic fault you need to find and fix.

 

Pete

 

If adding the terminate time line fixes the crash on exit, that means it is a fault with the scenery or airplane?

 

I really do not want to reinstall, any idea when you get a chance what I might look for?

[Ian P]

Out of interest, what happens if, rather than exiting the sim directly, you return to the Create a Flight screen, then wait a while and exit from there.

 

I have some add-ons which take a while to unload after ending a flight and, if you exit before the sim has unloaded all the code/textures/whatever it's doing in the background, then it crashes on exit. If, however, I exit to the "Create a Flight" screen, leave it for a couple of minutes and then close the sim down, it exits properly.

 

Might be worth trying? I don't know how you exit the sim at present.

 

Cheers,

 

Ian P.

[Pete Dowson]

If adding the terminate time line fixes the crash on exit, that means it is a fault with the scenery or airplane?

 

It just means that whatever corruption is causing the crash or hang is affecting something with less of an outcome due to timing.

 

Problems caused by minor timing differences are notoriously difficult to track down. To fix it at all you need a consistent result, which sounds like the G3D crash you get 'normally'.

 

I really do not want to reinstall, any idea when you get a chance what I might look for?

 

Sorry, no. It could be any one or more of the assorted graphics items loaded and processed whilst you were using FS.  It'll be a process of elimination.  A friend of mine recently had a similar problem which eventually turned out to be due to one corrupted bitmap file in just one livery of one of the many AI planes being used by his add-on traffic package. Once it was identified a simple reinstall of that one aircraft livery fixed it.

 

Sometimes re-installation is quicker, but if you aren't getting crashes whilst using FS, only when you've finished, you might not think it worth the hassle.

 

Pete

[flightcheck]

Thank you for the help I believe it is fixed now. I installed fsx on another computer, and copied over everything from the main texture and effects folders. Now no more crashes on exit!

[Drover]

Hi Pete,

i've been having fsui.dll issues CTD on exit of FSX

and the force terminate works for me as well

 

I have 4.938f

 

Dwayne

[Pete Dowson]

i've been having fsui.dll issues CTD on exit of FSX

and the force terminate works for me as well

 

 

 

 "FSUI.DLL?  That's a standard part of FSX. It is nothing to do with FSUIPC. You are in the wrong forum.

 

Regards

Pete

[joelpacheco]

I now this is a very old post but it fixed my FSX crashing every time I exit FSX.

I added ForceTerminateTime=5

Thank you!

The crash report in my case also showed fsui.dll as the culprit

[Pete Dowson]

6 hours ago, joelpacheco said:

I now this is a very old post but it fixed my FSX crashing every time I exit FSX.

I added ForceTerminateTime=5

Do you have any Lua plug-in scripts running? That's the usual problem fixed this way.

6 hours ago, joelpacheco said:

The crash report in my case also showed fsui.dll as the culprit

That/s the Sim's "user interface", mainly used for menus, so it's a bit odd.

Pete