FSX Fatal Error FSUIPC

[Sam Carstairs]

Hi Pete,

 

I have been having a few issues with FSUIPC and FSX. I get about 10 minutes into a flight then I get a fatal error. I had this issue before so i did a clean install of fsx without FSUIPC and all was good then today i decided to reinstall it and first flight gave a fatal error.

I am running the latest FSUIPC, downloaded today FSx with SP2, pmdg aircraft, ezdok,asnext,rex testures and the usual scenery stuff

Below is the Event viewer logs and FSUIPC log

 

Hope you can help because i love using FSUIPC besides this hickup

 

Sam

 

********* FSUIPC4, Version 4.936 by Pete Dowson *********

Reading options from "P:\FSX\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=516E0000

User Name="Sam Carstairs"

User Addr="sam.carstairs@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

      140 System time = 20/08/2014 14:18:55

      140 FLT path = "C:\Users\Sam\Documents\Flight Simulator X Files\"

      187 Trying to connect to SimConnect Acc/SP2 Oct07 ...

      203 FS path = "P:\FSX\"

      343 LogOptions=00000000 00000001

      343 SIM1 Frictions access gained

      343 Wind smoothing fix is fully installed

      343 G3D.DLL fix attempt installed ok

      343 SimConnect_Open succeeded: waiting to check version okay

      343 Trying to use SimConnect Acc/SP2 Oct07

     4103 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

     4103 Initialising SimConnect data requests now

     4103 FSUIPC Menu entry added

     4134 P:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

     4134 P:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

    27347 System time = 20/08/2014 14:19:22

    27347 *** FSUIPC log file being closed

G3D fix: Passes 1101, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 4 Allocs, 4 Freed

********* FSUIPC Log file closed ***********

 

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: mscorlib.ni.dll, version: 2.0.50727.5483, time stamp: 0x530efe95

Exception code: 0xc0000005

Fault offset: 0x00aa1810

Faulting process id: 0x1928

Faulting application start time: 0x01cfbc3c0c258436

Faulting application path: P:\FSX\fsx.exe

Faulting module path: C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\f8be9e33457f57805b4068f90099e428\mscorlib.ni.dll

Report Id: bcb5ce5b-2831-11e4-b48c-e84a10dbe9c0

 

Fault bucket 50, type 5

Event Name: BEX

Response: Not available

Cab Id: 0

 

Problem signature:

P1: fsx.exe

P2: 10.0.61472.0

P3: 475e17d3

P4: mscorlib.ni.dll

P5: 2.0.50727.5483

P6: 530efe95

P7: 00aa1810

P8: c0000005

P9: 00000008

P10: 

 

Attached files:

C:\Users\Sam\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt

C:\Users\Sam\AppData\Roaming\Microsoft\FSX\dxdiag.txt

C:\Users\Sam\AppData\Roaming\Microsoft\FSX\scenery.cfg

C:\Users\Sam\AppData\Roaming\Microsoft\FSX\fdr.dat

C:\Users\Sam\AppData\Roaming\Microsoft\FSX\dll.xml

C:\Users\Sam\AppData\Local\Temp\WER2F.tmp.WERInternalMetadata.xml

 

These files may be available here:

C:\Users\Sam\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_ab528a441eeee96482dbcf466244bf3e0b8ad66_12122a1c

 

Analysis symbol: 

Rechecking for solution: 0

Report Id: bcb5ce5b-2831-11e4-b48c-e84a10dbe9c0

 

 

[Pete Dowson]

I have been having a few issues with FSUIPC and FSX. I get about 10 minutes into a flight then I get a fatal error. I had this issue before so i did a clean install of fsx without FSUIPC and all was good then today i decided to reinstall it and first flight gave a fatal error.

I am running the latest FSUIPC, downloaded today FSx with SP2, pmdg aircraft, ezdok,asnext,rex testures and the usual scenery stuff

Below is the Event viewer logs and FSUIPC log

********* FSUIPC4, Version 4.936 by Pete Dowson *********

Reading options from "P:\FSX\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=516E0000

User Name="Sam Carstairs"

User Addr="sam.carstairs@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

      140 System time = 20/08/2014 14:18:55

      140 FLT path = "C:\Users\Sam\Documents\Flight Simulator X Files\"

      187 Trying to connect to SimConnect Acc/SP2 Oct07 ...

      203 FS path = "P:\FSX\"

      343 LogOptions=00000000 00000001

      343 SIM1 Frictions access gained

      343 Wind smoothing fix is fully installed

      343 G3D.DLL fix attempt installed ok

      343 SimConnect_Open succeeded: waiting to check version okay

      343 Trying to use SimConnect Acc/SP2 Oct07

     4103 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

     4103 Initialising SimConnect data requests now

     4103 FSUIPC Menu entry added

     4134 P:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

     4134 P:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

    27347 System time = 20/08/2014 14:19:22

    27347 *** FSUIPC log file being closed

G3D fix: Passes 1101, Null pointers 0, Bad pointers 0, Separate instances 0

Memory managed: 4 Allocs, 4 Freed

********* FSUIPC Log file closed ***********

 

 

FSUIPC has not crashed, nor is it causing the crash. In fact the log you supply shows FSUIPC terminating normally, no problems. However, it isn't actually starting -- it isn't supplying any services at all -- at least in the first 27 seconds. .You might have a corrupted Flight or Weather file. Without FSUIPC loaded, try selecting a different default flight. However, that doesn't explain the crash you have logged which is in nothing used by either FSX or FSUIPC.

 

Whether the system is crashing with or without add-ons such as FSUIPC is often to do with timing differences and memory arrangements affecting other parts.

 

The module which is crashing is mscorlib.ni.dll, of which I know nothing. In fact it doesn't even exist on my system, so I suspect it is installed and used by another add-on you are using within FSX. You may need to do a process of elimination to find out which.

 

Googling that module I find:

 

Description: Mscorlib.ni.dll is not essential for Windows and will often cause problems. mscorlib.ni.dll is located in a subfolder of C:\Windows. Known file sizes on Windows 7/XP are 11,486,720 bytes (33% of all occurrences), 11,490,816 bytes and 7 more variants.  

A .dll file (Dynamic Link Library) is a special type of Windows program containing functions that other programs can call. This .dll file can be injected to all running processes and can change or manipulate their behavior. The program is not visible. There is no detailed description of this service. It can change the behavior of other programs or manipulate other programs. The file is not a Windows system file. Therefore the technical security rating is 66% dangerous, however also read the users reviews.

Recommended: Identify mscorlib.ni.dll related errors

Important: Some malware camouflages itself as mscorlib.ni.dll. Therefore, you should check the mscorlib.ni.dll process on your PC to see if it is a threat. 

 

 

Hope this helps,

 

Pete

[Sam Carstairs]

Thanks for the quick reply Pete. I just tried running FSX again and this is the error that came up this time

Maybe they are more familiar to you??

 

********* FSUIPC4, Version 4.936 by Pete Dowson *********

Reading options from "P:\FSX\Modules\FSUIPC4.ini"

Running inside FSX on Windows 7

Module base=50190000

User Name="Sam Carstairs"

User Addr="sam.carstairs@gmail.com"

FSUIPC4 Key is provided

WIDEFS7 not user registered, or expired

      281 System time = 20/08/2014 19:50:29

      281 FLT path = "C:\Users\Sam\Documents\Flight Simulator X Files\"

      328 Trying to connect to SimConnect Acc/SP2 Oct07 ...

      344 FS path = "P:\FSX\"

      468 LogOptions=00000000 00000001

      468 SIM1 Frictions access gained

      484 Wind smoothing fix is fully installed

      484 G3D.DLL fix attempt installed ok

      484 SimConnect_Open succeeded: waiting to check version okay

      484 Trying to use SimConnect Acc/SP2 Oct07

     4556 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)

     4556 Initialising SimConnect data requests now

     4556 FSUIPC Menu entry added

     4587 P:\FSX\FLIGHTS\OTHER\FLTSIM.FLT

     4587 P:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR

    37815 P:\FSX\SimObjects\Airplanes\PMDG 777-300ER\B777-300ER.AIR

    93710 System time = 20/08/2014 19:52:03, Simulator time = 10:50:34 (03:50Z)

    93710 Aircraft="PMDG 777-3U3ER Garuda Indonesia"

    98624 Starting everything now ...

    98624 AES Link established

    99482 Weather Mode now = Theme

    99607 Ready for ASN WX radar

    99966 Advanced Weather Interface Enabled

   113600 AES version 2.30 active at airport WIII (default vehicles deleted)

 

 

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: mshtml.dll, version: 11.0.9600.17239, time stamp: 0x53d26078

Exception code: 0xc0000005

Fault offset: 0x00417c45

Faulting process id: 0x1b24

Faulting application start time: 0x01cfbc6cd68accfc

Faulting application path: P:\FSX\fsx.exe

Faulting module path: C:\Windows\SysWOW64\mshtml.dll

Report Id: 25451e68-2861-11e4-a20c-bb124a2504ca

 

- EventData

      fsx.exe       10.0.61472.0       475e17d3       mshtml.dll       11.0.9600.17239       53d26078       c0000005       00417c45       1b24       01cfbc6cd68accfc       P:\FSX\fsx.exe       C:\Windows\SysWOW64\mshtml.dll       25451e68-2861-11e4-a20c-bb124a2504ca

[Pete Dowson]

 

Thanks for the quick reply Pete. I just tried running FSX again and this is the error that came up this time

Maybe they are more familiar to you??

 

 

...

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: mshtml.dll, version: 11.0.9600.17239, time stamp: 0x53d26078

Exception code: 0xc0000005

Fault offset: 0x00417c45

Faulting process id: 0x1b24

Faulting application start time: 0x01cfbc6cd68accfc

Faulting application path: P:\FSX\fsx.exe

Faulting module path: C:\Windows\SysWOW64\mshtml.dll

 

No, this is still nothing related specifically to FSUIPC. "mshtml.dll" is used by Internet Explorer and other browsers. FSUIPC doesn't touch the Internet and has nothing to do with HTML.

 

Your problems are from other add-ins you are running. You need to go through a process of elimination.  If you find your DLL.XML and EXE.XML files and paste those here I can point out how to do this for those programs loading automatically.

 

Pete

 

 

 

Pete

[Sam Carstairs]

Here are the 2 files

 

Thanks again

 

<?xml version="1.0" encoding="Windows-1252"?>

 

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Name>ObjectFlow_YBAS.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>P:\FSX\ORBX\FTX_AU\FTXAA_YBAS\Scenery\ObjectFlow_YBAS.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>ObjectFlow_YMML.dll</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>P:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll</Path>

  </Launch.Addon>

  <Launch.Addon>

<Name>Addon Manager</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>bglmanx.dll</Path>

</Launch.Addon>

  <Launch.Addon>

<Name>Object Placement Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>

</Launch.Addon>

  <Launch.Addon>

<Name>Traffic Toolbox</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>

</Launch.Addon>

  <Launch.Addon>

<Name>Visual Effects Tool</Name>

<Disabled>True</Disabled>

<ManualLoad>False</ManualLoad>

<Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>

</Launch.Addon>

  <Launch.Addon>

<Name>PMDG Interface</Name>

<Disabled>False</Disabled>

<Path>PMDG\DLLs\PMDG_Interface.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

  <Launch.Addon>

<Name>RAASPRO</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>.\RAASPRO\RAASPRO.dll</Path>

<DllStartName>module_init</DllStartName>

<DllStopName>module_deinit</DllStopName>

</Launch.Addon>

  <Launch.Addon>

<Name>VistaMare Core</Name>

<Disabled>False</Disabled>

<ManualLoad>False</ManualLoad>

<Path>VistaMare\ViMaCoreX.dll</Path>

</Launch.Addon>

  <Launch.Addon>

    <Name>PMDG HUD interface</Name>

    <Disabled>False</Disabled>

    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>

    <DllStartName>module_init</DllStartName>

    <DllStopName>module_deinit</DllStopName>

  </Launch.Addon>

  <Launch.Addon>

        <Name>FSUIPC 4</Name>

        <Disabled>False</Disabled>

        <Path>Modules\FSUIPC4.dll</Path>

    </Launch.Addon>

  <Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp.dll</Path>

  </Launch.Addon>

</SimBase.Document>

 

 

 

 

 

<?xml version="1.0" encoding="windows-1252"?>

<SimBase.Document Type="Launch" version="1,0">

  <Descr>Launch</Descr>

  <Filename>dll.xml</Filename>

  <Disabled>False</Disabled>

  <Launch.ManualLoad>False</Launch.ManualLoad>

  <Launch.Addon>

    <Name>Couatl</Name>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Path>fsdreamteam\couatl\couatl.exe</Path>

  </Launch.Addon>

  <Launch.Addon>

    <Name>EZdok camera addon</Name>

    <Disabled>false</Disabled>

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

  </Launch.Addon>

  <Launch.Addon>

    <Disabled>False</Disabled>

    <ManualLoad>False</ManualLoad>

    <Name>UT2</Name>

    <Path>P:\FSX\\Flight One Software\Ultimate Traffic 2\UT2Services.exe</Path>

    <NewConsole>True</NewConsole>

  </Launch.Addon>

</SimBase.Document>

 

[Sam Carstairs]

Just realised you probably want the whole file :)

dll.xml

exe.xml

[Pete Dowson]

Here are the 2 files

 

Okay. So the DLLs and EXE's being loaded are:

DLLs:

P:\FSX\ORBX\FTX_AU\FTXAA_YBAS\Scenery\ObjectFlow_YBAS.dll
P:\FSX\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dll
P:\FSX\bglmanx.dll
P:\FSX\PMDG\DLLs\PMDG_Interface.dll
P:.\RAASPRO\RAASPRO.dll
P:\FSX\VistaMare\ViMaCoreX.dll
P:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
P:\FSX\Modules\FSUIPC4.dll
P:\FSX\as_srv\as_btstrp.dll


EXEs:


P:\FSX\fsdreamteam\couatl\couatl.exe
C:\Program Files (x86)\EZCA\EZCA.exe
P:\FSX\\Flight One Software\Ultimate Traffic 2\UT2Services.exe

Now I don't think the EXE's are likely to be responsible as then the crash would more likely be in their process, not in FSX's.

 

Of the DLLs I have no idea which try to use the internet (and hence "mshtml.dll"), but there are two ways to stop them running. Easiest is probably simply to rename them -- change the DLL ending to, say, DLX. Try doing this initially with all except FSUIPC4 (no need to change that one as you've already tried without). If you get no crash, enable each in turn, testing after each one.

 

I use several of those listed -- AS_BTSTRP (part of ASN), BGLMANX, VIMACOREX and RAASPRO. I've a feeling BGLMANX might access the internet in order to check for updates. Not sure about the others.

 

Pete

 

 

[Sam Carstairs]

It seems it was an issue with AS Next. I after a lomg process of elimination i ended up doing a fresh install of AS Next and FSUIPC and the problem seems to have gone away. Thanks for you promt help Pete, much appreciated