Jump to content
The simFlight Network Forums

FSX CTD with FSUIPC.DLL (inflight)


Recommended Posts

Hello!

 

Today I had FSX CTD during my flight. Log said that faulting module is FSUIPC. 

Can you please check logs and tell me any suggestions?

 
Fault bucket , type 0
 
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: fsx.exe
P2: 10.0.61637.0
P3: 46fadb14
P4: FSUIPC4.dll
P5: 4.9.2.7
P6: 52b0eeeb
P7: c0000005
P8: 00013691
P9: 
P10: 
 
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: FSUIPC4.dll, version: 4.9.2.7, time stamp: 0x52b0eeeb
Exception code: 0xc0000005
Fault offset: 0x00013691
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
 
With best regards, Alex.
Link to comment
Share on other sites

I forgot to add that I'm using FSUIPC 4.927a and ASN with latest Hotifx installed.

 

Today I installed 4.927b and will check it later.

 

With best regards, Alex.

 

P.S. thank you for your message, Paul. It's nice to see that I'm not only one who has this problem.

Edited by Flightoff27
Link to comment
Share on other sites

I forgot to add that I'm using FSUIPC 4.927a and ASN with latest Hotifx installed.

 

Today I installed 4.927b and will check it later.

 

With best regards, Alex.

 

P.S. thank you for your message, Paul. It's nice to see that I'm not only one who has this problem.

 

There are now three threads on the same subject -- see for example http://forum.simflight.com/topic/75975-ctd-fsuipc4/ not very far below this one!

 

I'm working on it, but I'm reasonably sure there's a work -around -- I just need confirmation. I may be able to supply a test version soon, but no one replies to my requests for information. No one suffering this has supplied any logs and no one has tried the parameter change I suggested. :-(

 

Pete

Link to comment
Share on other sites

Please download FSUIPC 4.927f and try it for me. I'm anxious to get to the bottom of this because I cannot reproduce it here.

 

Please add these lines to the [General] section of the FSUIPC.INI file:

 

Debug=Please

TestOptions=x8000

 

This version may not actually crash, but it may well get the same error -- I've tried to trap the error before the crash occurs so I can log the details instead. So after using 4.927f whether you get a crash or not, please paste the log here. If no crash, by all means carry on using it but show me the log after each session for a while, please. If the log is too big to paste here, ZIP it an email to petedowson@btconnect.com.

 

Once I know exactly why it is happening I'll fix it properly -- then you'd just need to remove those two added INI lines.

 

Thanks,

Pete

Link to comment
Share on other sites

Hello Pete,

 

thank you very much for your answer.

 

I will download 4.927f and will try it. Also, I added 2 lines to FSUIPC.ini file.

I will try to make a flight today in evening and will write about results after it.

 

One more thing (not sure if it has to do anything with our problem, but anyway):

my friend is using FSUIPC 4.927a and ASN with latest hotfix and he never had CTDs. We decided to compare fsx.cfg and dll.xml. And we noticed one interesting thing - following lines somehow disappeared from my dll.xml:

 
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>

 

I checked backups of dll.xml and I'm sure it was there.

But, as I said, I'm not sure that it can be part of our problem. However, I never had any CTDs before yesterday and was able to complete a lot of flights with ASN and 4.927a.

 

Anyway, will write later.

Thank you for your help, Pete.

 

With best regards, Alex.

Link to comment
Share on other sites

One more thing (not sure if it has to do anything with our problem, but anyway):

my friend is using FSUIPC 4.927a and ASN with latest hotfix and he never had CTDs. We decided to compare fsx.cfg and dll.xml. And we noticed one interesting thing - following lines somehow disappeared from my dll.xml:

 
<Launch.Addon>
<Name>as_connect</Name>
<Disabled>False</Disabled>
<Path>as_srv\as_btstrp.dll</Path>
</Launch.Addon>

 

I checked backups of dll.xml and I'm sure it was there.

 

It needs to be there for ASN to work correctly. Without it ASN canot perform many of its operations, including smoothing.

 

I've been checking the FSUIPC code exactly where the FSUIPC crashes occur, and I know it isn't anything to do with ASN. There's another SimConnect application which is making some calls which are causing FSUIPC to have a headache. I know how to work-around it but I want a proper solution.

 

But, as I said, I'm not sure that it can be part of our problem. However, I never had any CTDs before yesterday and was able to complete a lot of flights with ASN and 4.927a.

 

Have you added anything else recently? Another installer probably lost the as_connect entry in the DLL.XML and may be responsible for FSUIPC's confusion too.

 

One more thing - can you please tell which log do you need?

 

Is it FSUIPC text document in Modules folder?

 

Yes, it will be. It sounds like you have Windows hiding filenames from you -- see the notes in the FSUIPC documentation about that, it's a folder option in Explorer. You should be able to see the correct filenames, like

 

FSUIPC4.DLL  (the program)

FSUIPC4.INI  (the configuration settings)

FSUIPC4.LOG (the run time log file)

FSUIPC4 Install.LOG (the log showing the installation actions)

FSUIPC4.KEY (registration details)

 

With Windows left to hide the correct filenames all you see is its classification according to what program it thinks you should use with it. Text files like Logs and INI and CFG files, which can be opened with Notepad will say Text Files or similar, but that might change if you use some other program for looking at these. Best to turn that annoying option off. In earlier versions of Windows it defaulted off, which was much more sensible.

Link to comment
Share on other sites

 

 

Have you added anything else recently? Another installer probably lost the as_connect entry in the DLL.XML and may be responsible for FSUIPC's confusion too.

 

Actually, I added Wilco Airbuses (for some tests) and I also started to use AI Smooth.

 

CTD occurred on first flight with A330 from Wilco.

 

With AI Smooth I was able to complete 1 flight only (with 737NGX, on second flight I had CTD with Wilco A330), so it's hard to say if AI Smooth can be a problem.

 

 

 

 

Yes, it will be. It sounds like you have Windows hiding filenames from you...

 

Actually, before I always turned off this option (Hide extensions of known file types)... I forgot to do it this time.

Thank you for advice!

Link to comment
Share on other sites

Hello again Pete.

 

Well, I made a flight and this time I had different error. Now problem is g3d.dll.

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58
Exception code: 0xc0000005
Fault offset: 0x000122fa
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
 
FSUIPC log is too big, so, I uploaded it. Please check following link (log file is 64MB).
One more thing - please notice that I continued to use sim for 14 minutes after error window appeared (I'm using pseudo fullscreen, so, it was possible for me).
 
If you need anything else, please inform me.
 
With best regards, Alex.
Link to comment
Share on other sites

Well, I made a flight and this time I had different error. Now problem is g3d.dll.

 

That error is nothing whatsoever to do with FSUIPC -- it is one of the well known G3D crashes which occur in FSX with some sceneries and textures. Take a look through the FSX CTD forum on AVSIM.

 

FSUIPC log is too big, so, I uploaded it. Please check following link (log file is 64MB)..

 

It is a TEXT file. A zipped version would have been small. Why do you think I asked for it to be Zipped and emailed? I even gave my email address!

 

Anyway, it shows nothing useful. You didn't encounter anything which would have resulted in the original FSUIPC crash.

 

Regards

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.