Great GSX Frustration

[KKamradt]

Hello, I posted in late August below

http://www.fsdreamteam.com/forum/index.php/topic,14251.0.html

To recap, my Flight sim (all the sim and computer specs in the previous post Aug 24 titled GSX Crashes) had been crashing so much that I did a fresh install of FSX and all add ons, through that process I found GSX was the program causing the crash.  (The crash by the way has no error message, just the blue time out circle, and if you click it says program not responding must shut down).

I sent you error logs and your advice was:

So, as in all threads related to antivirus problems, installs as follows:

- Download and install the latest Stand-Alone Addon Manager or GSX, with the antivirus DISABLED

- Configure it to exclude the whole FSX from the antivirus scanning before trying to start FSX.


I mentioned though that since that last string I found  my antivirus had blocked bglmanx.dll as a Trojan, and I restored that.  Since then I flew a few trips in a GA aircraft, and two trips of less than 300 miles in the default 737 with one crash.  

The I flew the Captain Sim 767 from Dublin to BOS with my virus scan disabled.  I used GSX and departed, made it out to the ocean beyond Ireland (about 30 minutes flying) and it crashed.  Restarted, and crashed again after about 15 minutes.

I then did exactly what your instructions stated, excluded from virus the entire folder my FSX is in (which makes me a little nervous as I will add free ware add on in there, but for now wanted to see)  I disabled my virus scan the entire time I loaded GSX, and all the time I flew the sim.  I tried to re-start the saved flight (I save flights about every 15 minutes due to this crash problem), and it crashed again in about 5 minutes.  I figured that probably this crash was because the files changed with the reinstall of GSX, so I then started a new flight from the Dublin runway (no use of GSX), if I went to the add on menu it said GSX product active, but didn't say it was loaded, however cntrl shift F12 brought up the menu so it looked ok (though I didn't use it).      Flew about 50 minutes (real time, had sim set to 4 times real time so about mid ocean) and it crashed again.  I restarted the computer, and I reloaded the add on manager, then I loaded GSX (I think loading GSX loads the add on manager but to be sure), and restarted.   Then again did a new flight from the runway.  This time went with 8 times acceleration, got about half way across the ocean and it crashed.  Reloaded and got an instant crash.  Tried one more time, but this time started the flight as default, then disabled the add on manager and GSX in your add on menu, restarted, loaded the flight, instant crash.  One other thing I note, when I first install GSX and start it, it says nothing about the airport cache.  Every time I re-start the sim after the first GSX reload gives me the green bar, airport cache reloading.  I think you said that shouldn't happen in another post.  But every time it happens to me except the first time I install GSX.  Sometimes the sim works fine  despite that cache message.  It also seems I have to fly some distance before this crash, like the crash occurs due to a change in the scenery or nearby airports.  It may be a problem with GSX and the Captain Sim plane, as on the shorter flights the default 737 or GA didn't crash it, but in prior battles with this problem the 737 at least did.  I have also used the Captain Sim 767 with your GSX for about two years problem free, prior to these troubles last summer and the Captain Sim hasn't been updated, so if it is part of the problem something has changed to make it so (likely your update, but willing to consider something else).

As I said in my last post, what is so incredibly frustrating (aside from doing a complete reinstall of FSX trying to figure out what was wrong, and spending now the better part of two days trying to nudge my machine into working) is that for almost two years your GSX program worked wonderfully (with Captain sim), with no crashes or problems.  You keep pushing these upgrades and changes, and now I can't use my sim.  And I agree it is probably an interaction between the virus scan and your machine somehow, but my Virus scan is Norton Anti Virus, one of the most popular virus scans.  It has served me well, my computer has never been damaged by a virus, and several have been stopped (at least that's what they say).  I know it isn't your fault if the virus scan doesn't play well with your program, but really I think you have to design a solution to that.  What I can't say enough though is that things worked fine for two years, I just wish I could get the old GSX back but you guys keep forcing changes and now I can't fly my sim.  No other flight sim developer does this (they update, but you can undo them and have a choice to load them), and  this is the first program anywhere that didn't get along with my virus scan.  For these newer downloads it gives a message about Sode manager, I don't really know what this is, I didn't need it before, don't think I need it now but it installs (I think it has something to do with certain jetways).  Of course my Virus scan also receives updates, so could be something changed there.

That I have invested so much time into battling this is an endorsement of how much I like your program, it adds a lot to flight sim.  But if I can't fly my sim with it I will have to do with out.  And since I don't know if it is just GSX or the downloader, and since you have GSX built into your FSdream team airports I am terribly worried I will have to do without your airports as well.  And even a little nervous I might need to do without Flightbeam because they use your add on tool.  So that's a lot to lose, and you guys (and possibly flightbeam) will lose a future customer.

So I would ask for two things to start.  

1) do you have a fix for my problem?  Below are the error logs.  The ones from windows don't say much to me.  Your system didn't generate a panic log, but I attached the log which shows my final upload of GSX.

2) Can you tell me how to uninstall GSX?  There doesn't seem to be a way that I know. to do a clean uninstall of that program, disable doesn't seem to do much.

3) Please give serious consideration to what I suggested about not forcing upgrades, and making it possible to roll back to previous versions.

I'm not super computer savy, but like any FSX die hard I've had to invest time getting smarter on this then I wanted to, and I've already invested a ton of time on this problem.   And I don't envy you guys, having to deal with hundreds of configurations of sims, computers, add ons, and so much potential for something difficult to find to cause it all to crash while other machines work fine.  But for every guy like me who puts time into solving the problem there are probably folks who just say, it doesn't work and moves on.  That to me is a good reason not to force changes once you have something that works.

Of course I hope you can fix it, but I'm not optimistic.  I then really hope you can help me uninstall GSX and somehow leave the airports intact, and that this solves the problem.  The worst for me is to again do another  clean install of FSX and leave GSX out, (this will take me two days) then I'd also have to think about leaving your airports out, it will be a tough decision.

After this weekend real life will keep me away from the Sim for a couple of weeks, but whatever advice you offer I will implement in a month or so.

Thank you for your help.

I will post my error logs in a second message as I exceeded the character count.

[KKamradt]

APPLICATION ERROR LOG
Log Name:      Application
Source:        Application Hang
Date:          9/17/2016 4:21:09 PM
Event ID:      1002
Task Category: (101)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Kevin-PC
Description:
The program fsx.exe version 10.0.61637.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: af4
 Start Time: 01d211188c04a738
 Termination Time: 238
 Application Path: F:\FSX DVD 2016\fsx.exe
 Report Id: 05e509a0-7d14-11e6-bc4a-bc5ff41c01a6

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="2016-09-17T20:21:09.000000000Z" />
    <EventRecordID>163175</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Kevin-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>af4</Data>
    <Data>01d211188c04a738</Data>
    <Data>238</Data>
    <Data>F:\FSX DVD 2016\fsx.exe</Data>
    <Data>05e509a0-7d14-11e6-bc4a-bc5ff41c01a6</Data>
    <Binary>55006E006B006E006F0077006E0000000000</Binary>
  </EventData>
</Event>

      -   Provider
         [ Name]    Application Hang

      -   EventID   1002
         [ Qualifiers]    0

         Level   2

         Task   101

         Keywords   0x80000000000000

      -   TimeCreated
         [ SystemTime]    2016-09-17T20:21:09.000000000Z

         EventRecordID   163175

         Channel   Application

         Computer   Kevin-PC

         Security

-   EventData
         fsx.exe
         10.0.61637.0
         af4
         01d211188c04a738
         238
         F:\FSX DVD 2016\fsx.exe
         05e509a0-7d14-11e6-bc4a-bc5ff41c01a6
         55006E006B006E006F0077006E0000000000
________________________________________
Binary data:
In Words
0000: 006E0055 006E006B 0077006F 0000006E
0008: 0000
In Bytes
0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..
Log Name:      Application
Source:        Windows Error Reporting
Date:          9/17/2016 4:21:07 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Kevin-PC
Description:
Fault bucket 586852556, type 5
Event Name: AppHangB1
Response: Not available
Cab Id: 0

Problem signature:
P1: fsx.exe
P2: 10.0.61637.0
P3: 46fadb14
P4: a1bc
P5: 0
P6:
P7:
P8:
P9:
P10:
WINDOWS ERROR LOG
Attached files:
C:\Users\Kevin\AppData\Local\Temp\WER9C6E.tmp.appcompat.txt
C:\Users\Kevin\AppData\Local\Temp\WER9D59.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_fsx.exe_ef9a0cbc44656487c23ae3d6955026fb884319_11c0a0f1

Analysis symbol:
Rechecking for solution: 0
Report Id: 05e509a0-7d14-11e6-bc4a-bc5ff41c01a6
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-09-17T20:21:07.000000000Z" />
    <EventRecordID>163174</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Kevin-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>586852556</Data>
    <Data>5</Data>
    <Data>AppHangB1</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>46fadb14</Data>
    <Data>a1bc</Data>
    <Data>0</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\Kevin\AppData\Local\Temp\WER9C6E.tmp.appcompat.txt
C:\Users\Kevin\AppData\Local\Temp\WER9D59.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_fsx.exe_ef9a0cbc44656487c23ae3d6955026fb884319_11c0a0f1</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>05e509a0-7d14-11e6-bc4a-bc5ff41c01a6</Data>
    <Data>0</Data>
  </EventData>
</Event>
- System

  - Provider

   [ Name]  Windows Error Reporting
 
  - EventID 1001

   [ Qualifiers]  0
 
   Level 4
 
   Task 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2016-09-17T20:21:07.000000000Z
 
   EventRecordID 163174
 
   Channel Application
 
   Computer Kevin-PC
 
   Security
 

- EventData

   586852556
   5
   AppHangB1
   Not available
   0
   fsx.exe
   10.0.61637.0
   46fadb14
   a1bc
   0
    
    
    
    
    
   C:\Users\Kevin\AppData\Local\Temp\WER9C6E.tmp.appcompat.txt C:\Users\Kevin\AppData\Local\Temp\WER9D59.tmp.WERInternalMetadata.xml
   C:\Users\Kevin\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppHang_fsx.exe_ef9a0cbc44656487c23ae3d6955026fb884319_11c0a0f1
    
   0
   05e509a0-7d14-11e6-bc4a-bc5ff41c01a6
   0

[KKamradt]

Virtuali Log (no error log created)
Python 2.7.6 Stackless 3.1b3 060516 (default, Feb 19 2015, 15:56:51) [MSC v.1800 32 bit (Intel)] wxPython 3.0.2.0
couatl v3.1 (build 3536)
log started on Sat Sep 17 15:21:15 2016

connecting to SimConnect...
connected to SimConnect
bglmanx non ready yet, waiting.
connected to bglmanx
Running in mode: FSX (bglmanx setting)
Loading addons
Loading addon common
Added Menu Item "Couatl settings" (id 67)
Addon common loaded
Loading addon LiveUpdate
Added Menu Item "Couatl Live Update" (id 69)
Added Menu SubItem "Disable Addon" (parentId 69, id 70)
Addon LiveUpdate loaded
requesting AddOn list to bglmanx
Added Menu SubItem "Restart Couatl" (parentId 67, id 71)
Added Menu SubItem "Restart Couatl and rebuild airport cache" (parentId 67, id 72)
Added Menu SubItem "Key Mappings..." (parentId 67, id 73)
Added Menu SubItem "Show YouControl™ Menu        Ctrl+F12" (parentId 67, id 77)
Current locale is English_United States.1252
Initializing audio...
Available devices:
  Generic Software on Speakers (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e20537065616b65727320285265616c74656b204869676820446566696e6974696f6e20417564696f29)
  Generic Software on Realtek Digital Output (Realtek High Definition Audio) (47656e6572696320536f667477617265206f6e205265616c74656b204469676974616c204f757470757420285265616c74656b204869676820446566696e6974696f6e20417564696f29)
Created OpenAL device: Generic Software on Speakers (Realtek High Definition Audio)

Device info:
   Major version: 1
   Minor version: 1
   Frequency: 44100
   Refresh: 40
   Sync: 0
   Mono sources: 255
   Stereo sources: 1
   Extensions: ALC_ENUMERATE_ALL_EXT ALC_ENUMERATION_EXT ALC_EXT_CAPTURE ALC_EXT_EFX

Context info:
   Vendor: Creative Labs Inc.
   Version: 1.1
   Renderer: Software
   Extensions: EAX EAX2.0 EAX3.0 EAX4.0 EAX5.0 EAX3.0EMULATED EAX4.0EMULATED AL_EXT_OFFSET AL_EXT_LINEAR_DISTANCE AL_EXT_EXPONENT_DISTANCE

Using EFX 1.0 extension, with 1 auxiliary send(s)
Using EAX reverb
Added Menu SubItem "Check Live Update" (parentId 69, id 81)
bglmanx list contains 24 AddOn(s)
Loading addon ENBR
Addon ENBR not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named ENBR
Loading addon OHareX
Addon OHareX loaded
Loading addon KDFW
Addon KDFW loaded
Loading addon LSGG
Addon LSGG not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named LSGG
Loading addon f18ag
Addon f18ag not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named f18ag
Loading addon GSX
Current sim directory is F:/FSX DVD 2016
Looking for scenery.cfg in "C:\ProgramData\Microsoft/FSX/scenery.cfg"
  using "Scenery\World\scenery" (layer 1)
  using "Scenery\BASE\scenery" (layer 2)
  using "Scenery\0000\scenery" (layer 3)
  using "Scenery\0001\scenery" (layer 4)
  using "Scenery\0002\scenery" (layer 5)
  using "Scenery\0003\scenery" (layer 6)
  using "Scenery\0004\scenery" (layer 7)
  using "Scenery\0005\scenery" (layer
  using "Scenery\0006\scenery" (layer 9)
  using "Scenery\0007\scenery" (layer 10)
  using "Scenery\0100\scenery" (layer 11)
  using "Scenery\0101\scenery" (layer 12)
  using "Scenery\0102\scenery" (layer 13)
  using "Scenery\0103\scenery" (layer 14)
  using "Scenery\0104\scenery" (layer 15)
  using "Scenery\0105\scenery" (layer 16)
  using "Scenery\0106\scenery" (layer 17)
  using "Scenery\0107\scenery" (layer 18)
  using "Scenery\0200\scenery" (layer 19)
  using "Scenery\0201\scenery" (layer 20)
  using "Scenery\0202\scenery" (layer 21)
  using "Scenery\0203\scenery" (layer 22)
  using "Scenery\0204\scenery" (layer 23)
  using "Scenery\0205\scenery" (layer 24)
  using "Scenery\0206\scenery" (layer 25)
  using "Scenery\0207\scenery" (layer 26)
  using "Scenery\0300\scenery" (layer 27)
  using "Scenery\0301\scenery" (layer 28)
  using "Scenery\0302\scenery" (layer 29)
  using "Scenery\0303\scenery" (layer 30)
  using "Scenery\0304\scenery" (layer 31)
  using "Scenery\0305\scenery" (layer 32)
  using "Scenery\0306\scenery" (layer 33)
  using "Scenery\0307\scenery" (layer 34)
  using "Scenery\0400\scenery" (layer 35)
  using "Scenery\0401\scenery" (layer 36)
  using "Scenery\0402\scenery" (layer 37)
  using "Scenery\0403\scenery" (layer 38)
  using "Scenery\0404\scenery" (layer 39)
  using "Scenery\0405\scenery" (layer 40)
  using "Scenery\0406\scenery" (layer 41)
  using "Scenery\0407\scenery" (layer 42)
  using "Scenery\0500\scenery" (layer 43)
  using "Scenery\0501\scenery" (layer 44)
  using "Scenery\0502\scenery" (layer 45)
  using "Scenery\0503\scenery" (layer 46)
  using "Scenery\0504\scenery" (layer 47)
  using "Scenery\0505\scenery" (layer 48)
  using "Scenery\0506\scenery" (layer 49)
  using "Scenery\0507\scenery" (layer 50)
  using "Scenery\0600\scenery" (layer 51)
  using "Scenery\0601\scenery" (layer 52)
  using "Scenery\0602\scenery" (layer 53)
  using "Scenery\0603\scenery" (layer 54)
  using "Scenery\0604\scenery" (layer 55)
  using "Scenery\0605\scenery" (layer 56)
  using "Scenery\0606\scenery" (layer 57)
  using "Scenery\0607\scenery" (layer 58)
  using "Scenery\0700\scenery" (layer 59)
  using "Scenery\0701\scenery" (layer 60)
  using "Scenery\0702\scenery" (layer 61)
  using "Scenery\0703\scenery" (layer 62)
  using "Scenery\0704\scenery" (layer 63)
  using "Scenery\0705\scenery" (layer 64)
  using "Scenery\0706\scenery" (layer 65)
  using "Scenery\0707\scenery" (layer 66)
  using "Scenery\0800\scenery" (layer 67)
  using "Scenery\0801\scenery" (layer 68)
  using "Scenery\0802\scenery" (layer 69)
  using "Scenery\0803\scenery" (layer 70)
  using "Scenery\0804\scenery" (layer 71)
  using "Scenery\0805\scenery" (layer 72)
  using "Scenery\0806\scenery" (layer 73)
  using "Scenery\0807\scenery" (layer 74)
  using "Scenery\0900\scenery" (layer 75)
  using "Scenery\0901\scenery" (layer 76)
  using "Scenery\0902\scenery" (layer 77)
  using "Scenery\0903\scenery" (layer 78)
  using "Scenery\0904\scenery" (layer 79)
  using "Scenery\0905\scenery" (layer 80)
  using "Scenery\0906\scenery" (layer 81)
  using "Scenery\0907\scenery" (layer 82)
  using "Scenery\1000\scenery" (layer 83)
  using "Scenery\1001\scenery" (layer 84)
  using "Scenery\1002\scenery" (layer 85)
  using "Scenery\1003\scenery" (layer 86)
  using "Scenery\1004\scenery" (layer 87)
  using "Scenery\1005\scenery" (layer 88)
  using "Scenery\1006\scenery" (layer 89)
  using "Scenery\1007\scenery" (layer 90)
  using "Scenery\1100\scenery" (layer 91)
  using "Scenery\1101\scenery" (layer 92)
  using "Scenery\1102\scenery" (layer 93)
  using "Scenery\1103\scenery" (layer 94)
  using "Scenery\1104\scenery" (layer 95)
  using "Scenery\1105\scenery" (layer 96)
  using "Scenery\1106\scenery" (layer 97)
  using "Scenery\1107\scenery" (layer 98)
  using "Scenery\AFRI\scenery" (layer 99)
  using "Scenery\ASIA\scenery" (layer 100)
  using "Scenery\AUST\scenery" (layer 101)
  using "Scenery\EURE\scenery" (layer 102)
  using "Scenery\EURW\scenery" (layer 103)
  using "Scenery\NAMC\scenery" (layer 104)
  using "Scenery\NAME\scenery" (layer 105)
  using "Scenery\NAMW\scenery" (layer 106)
  using "Scenery\OCEN\scenery" (layer 107)
  using "Scenery\SAME\scenery" (layer 108)
  using "Scenery\Cities\Oshkosh\scenery" (layer 109)
  using "Scenery\Cities\StMaarten\scenery" (layer 110)
  using "Scenery\Cities\Rio\scenery" (layer 111)
  using "Scenery\Cities\LasVegas\scenery" (layer 112)
  using "Scenery\Global\scenery" (layer 113)
  using "Scenery\Props\scenery" (layer 114)
  using "Addon Scenery\scenery" (layer 116)
  using "Scenery\Cities\Reno\scenery" (layer 117)
  using "Scenery\Cities\Istanbul\scenery" (layer 118)
  using "Scenery\Cities\Longleat\scenery" (layer 119)
  using "Scenery\Cities\Berlin\scenery" (layer 120)
  using "Scenery\Cities\Edwards_AFB\scenery" (layer 121)
  using "F:\FSX DVD 2016\Just Flight\WA3\KATL Atlanta\scenery" (layer 122)
  using "F:\FSX DVD 2016\Just Flight\WA3\KCLT Charlotte\scenery" (layer 123)
  using "F:\FSX DVD 2016\Just Flight\WA3\KCVG Cincinnati\scenery" (layer 124)
  using "F:\FSX DVD 2016\Just Flight\WA3\MYNN Nassau\scenery" (layer 125)
  using "F:\FSX DVD 2016\Just Flight\WA3\TJSJ San Juan\scenery" (layer 126)
  using "..\FLL road trip\FSX Steam\steamapps\common\FSX\Addon Scenery\PDX\scenery" (layer 127)
  using "FsDreamTeam\KLAX_V2\scenery" (layer 128)
  using "FsDreamTeam\PHNL\scenery" (layer 129)
  using "..\My Traffic X Professional\MyTraffic\scenery" (layer 115)
  using "F:\FSX DVD 2016\SimMarket\KSEA-T2G FSX\data\KSEA-TERRAIN\scenery" (layer 130)
  using "F:\FSX DVD 2016\SimMarket\KSEA-T2G FSX\data\KSEA\scenery" (layer 131)
  using "FsDreamTeam\OHareX\scenery" (layer 132)
  using "F:\FLL road trip\FSX Steam\steamapps\common\FSX\SimMarket\KSEA-T2G FSX\data\KSEA-TERRAIN\scenery" (layer 133)
  using "F:\FLL road trip\FSX Steam\steamapps\common\FSX\SimMarket\KSEA-T2G FSX\data\KSEA\scenery" (layer 134)
  using "FsDreamTeam\KDFW\scenery" (layer 135)
  using "FsDreamTeam\KFLL\scenery" (layer 137)
  using "Addon Scenery\Bushflight Northwest\scenery" (layer 138)
  using "aerosoft\Mega Airport Dublin\scenery" (layer 139)
  using "aerosoft\Mega-Airport-London-Heathrow-Xtended_Terrain\scenery" (layer 140)
  using "aerosoft\Mega-Airport-London-Heathrow-Xtended_Airport\scenery" (layer 141)
  using "FlightBeam\KPHX\scenery" (layer 144)
  using "Addon Scenery\KPHL_SunSkyJet\scenery" (layer 157)
  using "aerosoft\Anchorage-Terrain\scenery" (layer 143)
  using "aerosoft\Anchorage-Airport\scenery" (layer 145)
  using "F:\FSX DVD 2016\aerosoft\Gibraltar X\1_GIB_FSX_Terrain\scenery" (layer 146)
  using "F:\FSX DVD 2016\aerosoft\Gibraltar X\1_GIB_FSX_Airport\scenery" (layer 147)
  using "Just Flight\WA3\KLGA La Guardia\scenery" (layer 148)
  using "Addon Scenery\Flushing Meadows\scenery" (layer 149)
  using "Addon Scenery\KORF\scenery" (layer 150)
  using "Addon Scenery\WashDCX\scenery" (layer 151)
  using "Addon Scenery\Green Bay X HD\scenery" (layer 152)
  using "Addon Scenery\honoycht\scenery" (layer 153)
  using "F:\FSX DVD 2016\Addon Scenery\WCI Narita X\scenery" (layer 154)
  using "F:\FLL road trip\FSX Steam\steamapps\common\FSX\Addon Scenery\WCI Narita X\scenery" (layer 155)
  using "Addon Scenery\RJNS-X\RJNS\scenery" (layer 156)
  using "aerosoft\USCitiesX-LosAngeles\scenery" (layer 142)
  using "Addon Scenery\Manns\scenery" (layer 158)
  using "OZx_World\Grand_Canyon_KGCN\scenery" (layer 159)
  using "Addon Scenery\West_Palm_Beach_FL\KPBI\scenery" (layer 136)
  using "Addon Scenery\MYXG Norman Cay, Bahamas\scenery" (layer 160)
  using "F:\FSX DVD 2016\Addon Scenery\FlyTampa-Boston\scenery" (layer 162)
  using "Addon Scenery\Google Earth Boston Scenery\scenery" (layer 161)
  using "Addon Scenery\eddt-lightx\scenery" (layer 163)
airportCacheOptimizeSearch enabled, excluding files larger than 2000000 bytes
Airport cache loaded successfully
SharedMemInterface connected
Added Menu Item "GSX" (id 82)
Added Menu SubItem "Disable Addon" (parentId 82, id 83)
Addon GSX loaded
Loading addon HAWAII1
Addon HAWAII1 not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named HAWAII1
Loading addon HAWAII2
Addon HAWAII2 not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named HAWAII2
Loading addon PHNL
Addon PHNL loaded
Loading addon JFK
Addon JFK not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named JFK
Loading addon JFK2
Addon JFK2 not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named JFK2
Loading addon KFLL
Addon KFLL loaded
Loading addon KIAH
Addon KIAH not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KIAH
Loading addon KLAS
Addon KLAS not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KLAS
Loading addon KLAX
Addon KLAX loaded
Loading addon KMEM
Addon KMEM not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KMEM
Loading addon CYVR
Addon CYVR not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named CYVR
Loading addon XPOI
Addon XPOI not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named XPOI
Loading addon ZurichX
Addon ZurichX not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named ZurichX
Loading addon KSFO
Addon KSFO not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KSFO
Loading addon KPHX
Addon KPHX loaded
Loading addon KIAD
Addon KIAD not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KIAD
Loading addon KDEN
Addon KDEN not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KDEN
Loading addon KSFOHD
Addon KSFOHD not installed or missing one or more files, skipping.
Traceback (most recent call last):
  File "<string>", line 78, in loadAddons
  File "<string>", line 36, in importAndCreateInstance
ImportError: No module named KSFOHD
Starting system monitors
Added Menu SubItem "Settings..." (parentId 82, id 91)
Added Menu SubItem "Customize aircraft..." (parentId 82, id 92)
Added Menu SubItem "Show GSX Menu by-passing YouControl™        Shift+Ctrl+F12" (parentId 82, id 94)
Loading aircraft data from Airplanes\CS_B767-300
Airplane major/minor version: 767 700
aircraftDb.py provides aircraft data with priority 2
Using aircraft data from aircraftDb.py
Slew mode False
User collision geometries reloaded
Loading airport KDBN from F:\FSX DVD 2016\Scenery\0302\scenery\APX25200.bgl
Added Menu SubItem "Customize airport positions..." (parentId 82, id 99)
Loading airport EIDW from F:\FSX DVD 2016\aerosoft\Mega Airport Dublin\scenery\AF2_EIDW.BGL
Loading user customizations from C:\Users\Kevin\AppData\Roaming\Virtuali/GSX\eidw-blfdhx.ini
Deleted Menu SubItem (parentId 82, id 99)
Added Menu SubItem "Customize airport positions..." (parentId 82, id 99)
User collision geometries reloaded
User collision geometries reloaded
User collision geometries reloaded
User collision geometries reloaded
User collision geometries reloaded
Deleted Menu SubItem (parentId 82, id 99)
User collision geometries reloaded
User collision geometries reloaded

[virtuali]

To recap, my Flight sim (all the sim and computer specs in the previous post Aug 24 titled GSX Crashes) had been crashing so much that I did a fresh install of FSX and all add ons, through that process I found GSX was the program causing the crash.  (The crash by the way has no error message, just the blue time out circle, and if you click it says program not responding must shut down).

Nothing your error log ever indicates that GSX is the cause of the crash, or it's even crashing itself. The Couatl.LOG file shows that GFSX started correctly.

None of the errors in your Windows Event Viewer logs are showing any problems in any of the GSX modules. What your  Windows Event Viewer log shows, is that FSX is crashing ITSELF, but it's entirely unrelated to GSX.

[KKamradt]

As I mentioned, when these crashes started happening earlier this summer I did a clean install of everything, and when I got to GSX that was when the crashes returned.  When I brought it up last time we agreed that the virus scan had corrupted your file.  Now after excluding the FSX folder from scan per your advice it is not showing that in the log file but it is the same type of crash.  Of course it could be something else, with windows update and virsus scan updates something else could damage the process, but the reinstall process I went through makes GSX a likely suspect.

You I believe in replying to someone else said that if the airport cache keeps reloading everytime you start GSX that is a sign that something is wrong, well I have that going on (and as mentioned though it doesn't always crash when that happens).  Could that be related to the crashes?  What is the fix for that?  That never happened in most of the two years I ran your program, I can't say for sure it started the same time as the crashes but it was around the same time.

But your response falls into my expectation of not being optimistic about your helping me solve the problem (and I realize it is partly because the interaction of all the pieces of what makes an FSX with add ons so complicated it is probably really hard to figure out what is going wrong so it is easy to say no evidence of our program causing it (and you may be right, just that my evidence with the clean install of FSX points in the direction of GSX)).

So then my next option is to uninstall GSX and see if that helps, so can you tell me is there away to do a clean uninstall of GSX?, I didn't see any uninstaller icons in any of your folders.  If none is there a manual way to uninstall it and make sure the traces are gone (preferably while keeping your airports).

And lastly I hope you will consider my suggestion of making updates optional and reversible.  So many developers put out programs that take several updates to get working properly, you guys had a program that worked brilliantly and I believe it works less well as a result of the updates (even if it is not causing the crashes, the airport cache load makes me nervous, and there have been times when the pushback doesn't work for some unknown reasons, and other minor things, not worth complaining about actually but I would have preferred to get a version running as well as it was and leave it alone).

[virtuali]

As I mentioned, when these crashes started happening earlier this summer I did a clean install of everything, and when I got to GSX that was when the crashes returned.

That's just coincidental. You probably installed something else too, but since you might also installed GSX at that time, you are mislead thinking GSX could be a problem.

When I brought it up last time we agreed that the virus scan had corrupted your file.  Now after excluding the FSX folder from scan per your advice it is not showing that in the log file but it is the same type of crash.

It's not the same crash. Which is why, I replied here in a different way than I replied to your earlier post.

The post you made in August indicated a crash in Couatl.exe and that you had an old version, which is why suggested to be sure the antivirus didn't interfere with it.

THIS crash is entirely different, and doesn't show ANY crashes in either Couatl.exe or bglmanx.dll (our two software modules), which is why, I told you THIS crash doesn't have anything to do with our software.

Of course it could be something else, with windows update and virsus scan updates something else could damage the process, but the reinstall process I went through makes GSX a likely suspect.

Yes, it's something else, and your Windows Event Viewer log shows exactly that.

You I believe in replying to someone else said that if the airport cache keeps reloading everytime you start GSX that is a sign that something is wrong, well I have that going on (and as mentioned though it doesn't always crash when that happens).  Could that be related to the crashes?

Your Couatl.LOG doesn't show the cache regeneration happened. If it didn't happened in that session, it seems you are not in the situation that the cache keeps reloading *everytime*, so it might just be that you (or some kind of other product accessing it) are really doing changes to the Scenery Library, which is normal.

However, even if you had the issue of the cache regeneration at each startup, the worse it would happen (if the regeneration didn't complete, usually because of a corrupted .BGL), is that GSX won't work, but it will NOT crash the sim.

it is easy to say no evidence of our program causing it (and you may be right, just that my evidence with the clean install of FSX points in the direction of GSX)).

The evidence, which is the Windows Event Viewer log, shows this new crash you are having, is not related to GSX.

So then my next option is to uninstall GSX and see if that helps, so can you tell me is there away to do a clean uninstall of GSX?, I didn't see any uninstaller icons in any of your folders.

Like every standard Windows program out there, GSX can be uninstalled from the "Programs and Features" section of the Windows Control Panel.

If you reply YES to the questions "Do you want to remove the Addon Manager ?" and the Couatl scripting engine, the uninstaller will also remove the modules from starting.

So many developers put out programs that take several updates to get working properly, you guys had a program that worked brilliantly and I believe it works less well as a result of the updates

We fixed a ton of bugs with the update, it's just that you were just lucky to not have found them.

(even if it is not causing the crashes

It's not.

the airport cache load makes me nervous

This doesn't have anything to do with GSX, and it's always caused by some external issue, which is either a corrupted .BGL on your system, or the use of external utilities that change the scenery.cfg at each startup. But it would have been exactly the same with each previous versions (the cache is there since GSX was released), just it would be slower, because the latest version is way faster, because it skips files that are surely not AFCADs.

and there have been times when the pushback doesn't work for some unknown reasons

There no such thing as "unknown reasons". Everything happens for a reason. If the pushback didn't happen, it's because there was a problem with the scenery, or because there was something you had to do on the airplane (for example, removing wheelchocks, etc.)

Not possible to say if you don't CLEARLY report the WHOLE situation, the airplane used, the airport used, the gate used, etc. so I could explain to you why it didn't happen in that particular case.

, and other minor things, not worth complaining

Since nothing in your report ever indicates a problem with GSX (but please report an example of the pushback issue), I'd say please indicate the minor things, so we might have a look at them.

[KKamradt]

The type of crash I am having now is exactly the same type as I was having before I did the clean install of FSX, and after installing FSX and testing, I added back the add ons one by one and this exact same type of crashed returned when I added GSX.  It is also the same type of crash that happened when we opened this discussion.  The error log now points to no reason for the crash whereas before it was pointing to GSX.  By same type I mean the computer behaves the same, it goes into thinking mode (blue circle) and if you click again it says program not responding with no error message.

I suspect the error logs aren't perfect, I mean this error log is saying FSX crashed for no reason whatsoever that it could identify, to paraphrase what you said you said nothing happens for no reason.

I am absolutely willing to believe that it is a coincidence that the crash returned after I reinstalled GSX to my clean install, I am a little frustrated you aren't willing to consider it isn't, even if not directly perhaps it corrupted a file somewhere.

This is why I am anxious to try the sim without GSX installed.  If that doesn't resolve then I can try a few more tweaks ((deleting FSX config file and letting FSX build a new config file and trying the uiautomationcore.dll fix which I haven't needed before) I'm back to the very time consuming clean reinstall of everything and this time test GSX more fully to rule it in or out.

At any rate back to the uninstall, if I use windows to uninstall I uninstall the program Virtualli Add on ManagerX FSX correct?  Did GSX make any changes to any files that won't be un-done by using the windows add on manager?  Will removing the add on manager also disable all of the airports I purchased from your company?

Thank You.

[virtuali]

The type of crash I am having now is exactly the same type as I was having before

No, it's not. It LOOKS similar, but the Windows Event viewer logs you posted clearly indicates they are two entirely different kind of crashes.

I added back the add ons one by one and this exact same type of crashed returned when I added GSX.

As I've said, it's only a coincidence. You should have tried this, instead:

- Installing GSX FIRST.

- Installing the other addons, one by one.

That might have helped to find, for example, an unknown conflict between GSX and another addon.

The error log now points to no reason for the crash whereas before it was pointing to GSX

It points to FSX.EXE having crashed by itself. The OTHER log pointed to Couatl.exe crashing, that's why it was different.

By same type I mean the computer behaves the same, it goes into thinking mode (blue circle) and if you click again it says program not responding with no error message.

That's what I mean when I said "It LOOKS similar". Most crashes will look like that, although they might happen for many different reasons.

I suspect the error logs aren't perfect, I mean this error log is saying FSX crashed for no reason whatsoever that it could identify, to paraphrase what you said you said nothing happens for no reason.

No error log ever points to a "reason", it would be too good if they did. The error log points to WHAT PROGRAM CRASHED.

In the old error log, Couatl.exe crashed, so it WAS an issue related to GSX in some way.

In the new error log, FSX.EXE crashed, so it's NOT an issue related to GSX in any way.

I am absolutely willing to believe that it is a coincidence that the crash returned after I reinstalled GSX to my clean install, I am a little frustrated you aren't willing to consider it isn't, even if not directly perhaps it corrupted a file somewhere.

A clean reinstall would get rid of corrupted files, unless:

1) You have an hardware failure

OR

2) Your antivirus is still interfering.

At any rate back to the uninstall, if I use windows to uninstall I uninstall the program Virtualli Add on ManagerX FSX correct? 

I already confirmed the correct way to entirely remove it.

Will removing the add on manager also disable all of the airports I purchased from your company?

Of course. That's precisely what the uninstaller tells you too.

[KKamradt]

Is there a way to uninstall GSX and retain the airports?  In my tests the crash didn't happen when I installed your airports, but when I added GSX.  I imagine if I uninstall all and then reinstall just the airports I would achieve that, though since GSX is built into your airports maybe not.

[virtuali]

Is there a way to uninstall GSX and retain the airports?

You can try removing the fsdreamteam\Couatl\GSX folder. However, it won't change anything to your crashes.

In my tests the crash didn't happen when I installed your airports, but when I added GSX.

As I've said, it was just a coincidence. As I've said, the one and only module we make that could *theoretically* crash FSX, is the Addon Manager, since it's an in-process .DLL with access to the FSX memory space.

Since all the sceneries requires the Addon Manager (and Couatl too), fact you said yourself that with "just" the sceneries installed there were no crash, it's a clear indication that the crash doesn't have anything to do with GSX, since the sceneries requires EXACTLY the SAME installed modules as GSX.

GSX, as seen alone, it's JUST a Python program being run in the Couatl interpreter. It doesn't have any direct access to FSX, which is why it CANNOT cause crashes.

Unless, an otherwise perfectly legal and 100% SDK compliant object created by *FSX*, on behalf of GSX, is crashing, because you have some kind of issue with video driver settings and/or video driver tweaks and/or FSX.CFG tweaks that don't work well with your setup. So, the REAL cause in this case would be those settings, but you can easily mislead thinking "it's a GSX problem", when it's not.

However, if this was the case, I doubt the airports would work flawlessly, since scenery objects might be even more complex and demanding than GSX vehicles.