FSUIPC Loading Issues After Installing Acceleration Pack

[gotjackson]

First, I'm a long time user of FS, but fairly new to FSX. I am getting a "Fatal Error" about 80% of time after installing the FSX Acceleration Pack.

 

I installed FSX Gold Edition about 2 weeks ago and had no problems with FSUIPC (which I installed because I was using Air Hauler. Everything has been working fine. However, a couple of days ago, I installed the Acceleration Pack and when I ran Air Hauler, it told me I needed to update to the latest version of FSUIPC. I believe I already had the latest version (downloaded just a couple of weeks ago), but I downloaded and installed (as administrator) the latest FSUIPC yesterday.

 

After the screen loads following the pressing of "Fly Now", I can look really quick before it crashes on the menu under Addons and I can see that FSUIPC is not there. Within a few seconds, it crashes. There are a few times, however, when FSUIPC does show under Addons and FS doesn't crash.

 

I've tried loading different aircraft, different weather, different airports and I can't seem to find any common denominator as to why FSUIPC doesn't show up most of the time after "Fly Now".

 

If I act quick before it crashes, I can sometimes re-load an aircraft (sometimes the same one, sometimes a different one) from the FS menu and then suddently FSUIPC appears under Addons. It doesn't always work and I sometimes have to persist through 3 or 4 crashes before I can finally fly. It's a workaround, but a frustrating one.

 

If you have any ideas for me, please keep in mind that I am not very technically savvy with computers, so simple is good.

 

I am running Windows 8, 64 bit, FSX Gold Edition with Acceleration Pack now installed.

 

Thanks for any help you can offer.

 

Bryan

[Pete Dowson]

First, I'm a long time user of FS, but fairly new to FSX. I am getting a "Fatal Error" about 80% of time after installing the FSX Acceleration Pack.

 

I installed FSX Gold Edition about 2 weeks ago and had no problems with FSUIPC (which I installed because I was using Air Hauler. Everything has been working fine. However, a couple of days ago, I installed the Acceleration Pack and when I ran Air Hauler, it told me I needed to update to the latest version of FSUIPC. I believe I already had the latest version (downloaded just a couple of weeks ago), but I downloaded and installed (as administrator) the latest FSUIPC yesterday.

 

Sounds like a corrupted install of FSX Acceleration. But I need more details to determine what might be going on.

 

When a program crashes there will be details in the Windows event logs. Check the Applications log in the event viewer. Give me all the details -- module, offset, error code.

 

Additionally, show me the FSUIPC4 log file for the attempts when it crashes, and also the whole of the Install log. both logs will be found in the FSX Modules folder.

 

After the screen loads following the pressing of "Fly Now", I can look really quick before it crashes on the menu under Addons and I can see that FSUIPC is not there. Within a few seconds, it crashes. There are a few times, however, when FSUIPC does show under Addons and FS doesn't crash.

 

SimConnect doesn't create an Addons menu until something asks to add an entry, so what entries are already there? Maybe it's a clash with some other add-in you have?

 

Regards

Pete

[gotjackson]

HI Pete. Thanks for the quick response. It took some digging around Windows 8 to find the error logs, but it looks like you're second thought may be the problem. I have EZDok Camera installed from Flight1 and it looks like that is what is causing the problem with FSUIPC. Here are the repeated error messages:

 

- <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="2014-02-02T06:02:58.000000000Z" />

  <EventRecordID>3108</EventRecordID>

  <Channel>Application</Channel>

  <Computer>Inspiron</Computer>

  <Security />

  </System>

- <EventData>

  <Data>EZCA.exe</Data>

  <Data>1.1.5.0</Data>

  <Data>2a425e19</Data>

  <Data>unknown</Data>

  <Data>0.0.0.0</Data>

  <Data>00000000</Data>

  <Data>c0000005</Data>

  <Data>f3ac0000</Data>

  <Data>32c</Data>

  <Data>01cf1fdc6a980630</Data>

  <Data>C:\Program Files (x86)\EZCA\EZCA.exe</Data>

  <Data>unknown</Data>

  <Data>a994c46a-8bcf-11e3-be7a-3423874074c0</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

 

All of the error messages seem to have slightly different lines in them, but they are all similar to this.

[Pete Dowson]

HI Pete. Thanks for the quick response. It took some digging around Windows 8 to find the error logs, but it looks like you're second thought may be the problem. I have EZDok Camera installed from Flight1 and it looks like that is what is causing the problem with FSUIPC. Here are the repeated error messages:

 

- <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="2014-02-02T06:02:58.000000000Z" />

  <EventRecordID>3108</EventRecordID>

  <Channel>Application</Channel>

  <Computer>Inspiron</Computer>

  <Security />

  </System>

- <EventData>

  <Data>EZCA.exe</Data>

  <Data>1.1.5.0</Data>

  <Data>2a425e19</Data>

  <Data>unknown</Data>

  <Data>0.0.0.0</Data>

  <Data>00000000</Data>

  <Data>c0000005</Data>

  <Data>f3ac0000</Data>

  <Data>32c</Data>

  <Data>01cf1fdc6a980630</Data>

  <Data>C:\Program Files (x86)\EZCA\EZCA.exe</Data>

  <Data>unknown</Data>

  <Data>a994c46a-8bcf-11e3-be7a-3423874074c0</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

 

All of the error messages seem to have slightly different lines in them, but they are all similar to this.

 

I also use EZCA so it isn't a specific incompatibility between that and FSUIPC. Neither are dependent on each other either.

 

Try loading EZCA.EXE after FSX has fully started. You could even have FSUIPC load it.

 

Pete

[gotjackson]

Okay, that seems to work. I disabled EZCA on startup and put the EZCA.EXE on my taskbar so I can get to it easy. Tried it several times and I've had no fatal errors.

 

If I wanted to try it, how do I get FSUIPC to load EZCA for me?

[Pete Dowson]

Okay, that seems to work. I disabled EZCA on startup and put the EZCA.EXE on my taskbar so I can get to it easy. Tried it several times and I've had no fatal errors.

 

If I wanted to try it, how do I get FSUIPC to load EZCA for me?

 

You put its pathname into a [Programs] section in the FSUIPC4.INI file, like:

 

[Programs]

Run1=CLOSE,"<full path to EXCA exe file>"

 

The CLOSE should make EZCA close when FS is closed. Alternatively you could let it keep running, but use RunIf1="<path>" so it is only loaded if not already running. If CLOSE doesn't manage to close it you can try KILL instead. Less tidy but stronger in action.

 

If that creates a problem you can use Run1= (or RunIf1=) with READY as a keyword (as well as CLOSE or KILL), so:

 

Run1=KILL,READY,"<path>"

 

Then it won't start it till FS is ready to fly.

 

There's a section about all this in the FSUIPC advanced user's guide -- it has its own chapter listed in the Contents.

 

Pete

[gotjackson]

So, problem not totally solved. I'm still having issues when launching from Air Hauler. Works fine when launching FSX direct. Tried twice, got the following from the event logs:

 

First one

Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000230b3

Faulting process id: 0x18e4

Faulting application start time: 0x01cf2045ed44aaf8

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSX.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL

Report Id: 48e7f052-8c39-11e3-be7a-3423874074c0

Faulting package full name:

Faulting package-relative application ID:

 

Second one:0

Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000230b3

Faulting process id: 0x1ac8

Faulting application start time: 0x01cf2046268e4e83

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSX.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL

Report Id: 7ebf25dc-8c39-11e3-be7a-3423874074c0

Faulting package full name:

Faulting package-relative application ID:

 

 

[Pete Dowson]

So, problem not totally solved. I'm still having issues when launching from Air Hauler. Works fine when launching FSX direct. Tried twice, got the following from the event logs:

 

First one

Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000230b3

Faulting process id: 0x18e4

Faulting application start time: 0x01cf2045ed44aaf8

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSX.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL

Report Id: 48e7f052-8c39-11e3-be7a-3423874074c0

Faulting package full name:

Faulting package-relative application ID:

 

Second one:0

Faulting application name: FSX.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: API.DLL, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000230b3

Faulting process id: 0x1ac8

Faulting application start time: 0x01cf2046268e4e83

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FSX.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLL

Report Id: 7ebf25dc-8c39-11e3-be7a-3423874074c0

Faulting package full name:

Faulting package-relative application ID:

 

 

 

Ok. I'm sorry, then, but I think you've got some serious problems which aren't really specifically to do with FSUIPC at all. Evidently something got severely messed up when you installed Acceleration. None of the crashes you've had have been in or directly related to FSUIPC, they have been in other unrelated areas. I think you are really looking at an FSX repair job, maybe even a reinstall from scratch.

 

Regards

Pete