• Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines
  1. Interesting, I tried the same thing and got same results running the sim for about 5 min at the gate before shutdown.
  2. Hi Kyle, I'm not sure where the problem is, all I know it happens only with PMDG747 QoS II. Having PMDG 737/777 and Aerosoft Airbuses this issue does not exist. So it leads me to believe that there is something with 747 QoS II that is causing this. As per topic "appcrash kernel32.dll when exiting FSX" it was there every time with initial release and latest build 3.00.8189 (Released 2017-03-13). But before the latest update, I ran with build 3.00.8186 (Released 2017-03-10) for entire week and the problem did not exist. Regards, Michael
  3. Well, I did about 6 flights after the first update last week - no issues on exit. But, another update which I installed today BUILD 3.00.8189 (Released 2017-03-13), the same problem is back. Michael
  4. Looks like it's solved by the new update just released, I tested after the update and no more crash on exit from main menu. PMDG 747-400 Queen of the Skies II - BUILD 3.00.8186 (Released 2017-03-10) Cheers, Michael
  5. I have the same problem in FSX-SE only with PMDG B747 v3, I don't think it's OOM, simconnect must be closing successfully cause my FSUIPC log indicates clean exit: 8295915 System time = 04/03/2017 22:42:44, Simulator time = 20:03:50 (18:03Z) 8295915 *** FSUIPC log file being closed Minimum frame rate was 7.6 fps, Maximum was 739.3 fps Minimum available memory recorded was 1013Mb Average frame rate for running time of 7743 secs = 22.7 fps Maximum AI traffic for session was 132 aircraft Memory managed: 3479 Allocs, 3479 Freed ********* FSUIPC Log file closed *********** And the way I stop the sim is always end flight to main menu and from there exit. Looking at task manager I see memory being released but at around 400MB remaining this error happens - every time.
  6. Updating FSUIPC – no change Updated with SP1b – no change Also, deleting fsx.cfg and having a fresh one – no change (so I restored it) Additionally, loading a saved flight like 20nm before T/D when message usually shows “Initializing system…” it crashes every time. To make long story short, this problem CTD ending flight after landing or loading saved flight, appears to be related to only one particular saved flight that I created after SP1. I have created new flight with different livery but I loaded same panel state and there was CTD again after landing and ending flight. So I tried bunch of other saved flights with ready for takeoff, before T/D and 30nm before landing and they were fine. No CTD. I even used instant replay of 120 sec after landing then ended replay and ended flight normally. FYI, in case someone has missed readme version info for SP1 ; ************************************************************ VERY IMPORTANT: Due to the huge number of changes we made to the 777, we were not able to maintain backward compatibiltiy with any saved flights. We recommend that you delete all of your 777 saved flights and panel state files in order to prevent accidentally loading one of them. ************************************************************ I had deleted all saved flights and panel states on initial SP1 as per instructions but had a problem on one of the newly saved ones – now it’s gone. So I think there was something wrong with that panel state when the flight was saved from the beginning and any subsequent flight saves must have carried the bug with it.
  7. Same here, after SP1 and I don’t have 300. It is the same when ending flight with engines running or cold and dark after completion of the flight. I have unregistered FSUIPC v4.928, I’ll try 4.934. Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: kernel32.dll Fault Module Version: 6.1.7601.18409 Fault Module Timestamp: 53159a85 Exception Code: c0000005 Exception Offset: 00011359 OS Version: 6.1.7601. Locale ID: 1033