Log Name:      Application
Source:        Application Hang
Date:          10/13/2018 8:05:08 PM
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-DS4IA60
Description:
The program fsx.exe version 10.0.61472.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 19b0
 Start Time: 01d4633e52463bc6
 Termination Time: 140
 Application Path: C:\FSX\fsx.exe
 Report Id: 248a72ad-e89e-4c35-9f7b-f358de73f07f
 Faulting package full name: 
 Faulting package-relative application ID: 

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Hang" />
    <EventID Qualifiers="0">1002</EventID>
    <Level>2</Level>
    <Task>101</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2018-10-14T00:05:08.337190700Z" />
    <EventRecordID>10025</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-DS4IA60</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>19b0</Data>
    <Data>01d4633e52463bc6</Data>
    <Data>140</Data>
    <Data>C:\FSX\fsx.exe</Data>
    <Data>248a72ad-e89e-4c35-9f7b-f358de73f07f</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

 

i haven.t had FSX hanging in years........and I just returned to it after flying for months X-PLANE11....any insight would be appreciated!!!

W10  32G I7 8700 GTX1060 6G FSX boxed version

Edited October 14, 20187 yr by enzo64

Your application was shutdown because of one of the modules that loads at startup by the dll.xml.  Most likely the fsuipc.dll since you have not used fsx for months.  The fsuipc.dll is updated frequently.  Based on the very limited information you provided, this is my "assumption".  To fix, I would recommend the procedures starting on page 10, AVSIM CTD Guide to investigate and solve the reason for your apphang.  It is the only way to fix with an apphang. 

Since you mentioned XP11, remember XP11 is a 64-bit game with unlimited resources; FSX is a 32-bit game which has limited resources.

7 hours ago, Jim Young said:

Your application was shutdown because of one of the modules that loads at startup by the dll.xml.  Most likely the fsuipc.dll since you have not used fsx for months.  The fsuipc.dll is updated frequently.  Based on the very limited information you provided, this is my "assumption".  To fix, I would recommend the procedures starting on page 10, AVSIM CTD Guide to investigate and solve the reason for your apphang.  It is the only way to fix with an apphang. 

Since you mentioned XP11, remember XP11 is a 64-bit game with unlimited resources; FSX is a 32-bit game which has limited resources.

********* FSUIPC4, Version 4.974b (14th March 2018) by Pete Dowson *********
Windows 10 Home 64 Bit reported as Build 17134, Release ID: 1803 (OS 10.0)
fsx.exe version = 10.0.61472.0
Reading options from "C:\FSX\Modules\FSUIPC4.ini"
Running inside FSX on Windows 10
Module base=5D7D0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       31 System time = 13/10/2018 17:47:38
       31 FLT path = "C:\Users\enzo6\Documents\Flight Simulator X Files\"
       31 ------ Module Version Check ------
       31        acontain.dll: 10.0.61472.0
       31             api.dll: 10.0.61472.0
       31        controls.dll: 10.0.61472.0
       31      fs-traffic.dll: 10.0.61472.0
       31             G3D.dll: 10.0.61472.0
       31        language.dll: 10.0.61472.0
       31            sim1.dll: 10.0.61472.0
       31        visualfx.dll: 10.0.61472.0
       31         weather.dll: 10.0.61472.0
       31          window.dll: 10.0.61472.0
       31 ----------------------------------
       94 Trying to connect to SimConnect Acc/SP2 Oct07 ...
      109 FS path = "C:\FSX\"
      187 ---------------------- Joystick Device Scan -----------------------
      187 Product= CH FLIGHT SIM YOKE USB 
      187    Manufacturer= CH PRODUCTS
      187    Vendor=068E, Product=00FF (Version 0.0)
      187    GUIDs returned for product: VID_068E&PID_00FF:
      187       GUID= {AEED3A90-F726-11E7-8008-444553540000}
      187       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X255,Y255,Z255
      187 Product= CH PRO PEDALS USB 
      187    Manufacturer= CH PRODUCTS
      187    Vendor=068E, Product=00F2 (Version 0.0)
      187    GUIDs returned for product: VID_068E&PID_00F2:
      187       GUID= {AEED88B0-F726-11E7-8009-444553540000}
      187       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      187 Product= CH THROTTLE QUADRANT
      187    Manufacturer= CH PRODUCTS
      187    Vendor=068E, Product=00FA (Version 0.0)
      187    GUIDs returned for product: VID_068E&PID_00FA:
      187       GUID= {AEEBDB00-F726-11E7-8004-444553540000}
      187       Details: Btns=12, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U255,V255,X255,Y255,Z255
      187 -------------------------------------------------------------------
      187 Device acquired for use:
      187    Joystick ID = 2 (Registry okay)
      187    2=CH FLIGHT SIM YOKE USB
      187    2.GUID={AEED3A90-F726-11E7-8008-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 3 (Registry okay)
      187    3=CH PRO PEDALS USB
      187    3.GUID={AEED88B0-F726-11E7-8009-444553540000}
      187 Device acquired for use:
      187    Joystick ID = 4 (Registry okay)
      187    4=CH THROTTLE QUADRANT
      187    4.GUID={AEEBDB00-F726-11E7-8004-444553540000}
      187 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 ------ Setting the hooks and direct calls into the simulator ------
      203 --- CONTROLS timer memory location obtained ok
      203 --- SIM1 Frictions access gained
      203 --- FS Controls Table located ok
      203 --- Installed Mouse Macro hooks ok.
      203 --- Wind smoothing fix is fully installed
      203 --- G3D.DLL fix attempt installed ok
      203 --- SimConnect intercept for texts and menus option is off
      203 --- All links checked okay
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Trying to use SimConnect Acc/SP2 Oct07
      203 Opened separate AI Traffic client okay
     3016 Running in "Microsoft Flight Simulator X", Version: 10.0.61472.0 (SimConnect: 10.0.61259.0)
     3016 Initialising SimConnect data requests now
     3016 FSUIPC Menu entry added
     3047 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT
     3047 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR
   108516 C:\FSX\SimObjects\Airplanes\PMDG 777-200LR\B777-200LR.AIR
   200625 User Aircraft ID 1 supplied, now being used
   200625 Aircraft loaded: running normally now ...
   226875 Aircraft="PMDG 777-232LR Delta Air Lines"
   226875 System time = 13/10/2018 17:51:24, Simulator time = 17:51:40 (21:51Z)
   232625 Starting everything now ...
   232719 ASN active function link set
   232719 Ready for ActiveSky WX radar with additional data
   235844 Advanced Weather Interface Enabled
   309328 Weather Mode now = Theme
   353297 Sim stopped: average frame rate for last 123 secs = 22.6 fps
   353297    Max AI traffic was 0 aircraft
  5100516 **** Restarting traffic scanning due to non-reception ****
 

Hi Jim,

thank you very much for stepping in...as you can see I'm running the latest FSUIPC module.

As I have said before, in ten years of flying, I have had no more than few hangs within FSX cause the COUATI.dll .

That module and unfortunately GSX is out of the picture now and pretty much the rest is untouched other then the newest model matching for Vpilot.

31 minutes ago, enzo64 said:

thank you very much for stepping in...as you can see I'm running the latest FSUIPC module.

I mentioned this as a possibility.  It is just one of the modules that is loaded at startup.  So, according to the fsuipc, everything loaded so there is no problem with your dll.xml.

So, you followed my suggestion to investigate the apphang starting on page 10, AVSIM CTD Guide?  You still have to do something with your fsx.cfg, the dll.xml, and scenery.cfg.   Apphangs are impossible to fix via forums.  Only you can fix it and the AVSIM CTD Guide tells you how.

1 hour ago, Jim Young said:

 

So, you followed my suggestion to investigate the apphang starting on page 10, AVSIM CTD Guide?  You still have to do something with your fsx.cfg, the dll.xml, and scenery.cfg.   Apphangs are impossible to fix via forums.  Only you can fix it and the AVSIM CTD Guide tells you how.

Working on it now...flying a small hop with the T7 KSJC-KSEA after I made the change to my FSX.cfg just to start...keeping my fingers crossed!!!

Renaming or deleting the FSX.cfg is the number one fix for apphangs/crashes.  You must have had a tweak in the config.

Ok Jim,

The flight went very well, no hang whatsoever, but I have done something to avoid some troubles from the past.

My VA ACARS has the ability to record the flight even if I m disconnected from the server... I have had simulator hangs because the ACARS software...... keeping on testing to make sure that this is the culprit,

Thanks again for your help!!!

Edited October 15, 20187 yr by enzo64