Anybody ever Have FSX Freeze when "Ending Flight"? Happens every time for me. See Pic below.

 

Can we safely assume that it didn't do this until recently?  Any new installs to report?  I

 

have never gotten a freeze, just the occasional fake "fatal error" after FSX closes.

You probably have an addon or another program that is running in the background and not shutting down properly so FSX is waiting for it to happen. Next time it happens, go into the Task Manager and see what is running. If it's an addon, shut it down and see if FSX closes too.

 

Best regards,

You probably have an addon or another program that is running in the background and not shutting down properly so FSX is waiting for it to happen. Next time it happens, go into the Task Manager and see what is running. If it's an addon, shut it down and see if FSX closes too.

 

Best regards,

 

UT2 is still running

So, did FSX close down properly after ending the UT2 task in the Task Manager. If so, you may have to reinstall UT2. I think it could be a texture in UT2 that is still trying to render and causing the program to remain open. It could be a flightplan that an AI aircraft cannot find too and the program is looking for it.

 

Best regards,

So, did FSX close down properly after ending the UT2 task in the Task Manager. If so, you may have to reinstall UT2. I think it could be a texture in UT2 that is still trying to render and causing the program to remain open. It could be a flightplan that an AI aircraft cannot find too and the program is looking for it.

 

Best regards,

 

Closed UT2 in "Task Manager" FSX shows "Running" but nothing happens.

Check the Event Viewer to see if there are any error messages. The AVSIM CTD Guide located to the right of this forum under Hot Spots shows how to open the Event Viewer and what section to look in. You can also try to run AppCrashView (link in AVSIM CTD Guide) and see if there are any errors. If that does not work then I would run Process Monitor as follows (this will be in a future update of the AVSIM CTD Guide)(This setup will ensure only FSX and FSX addons are monitored. When FSX freezes, you will want to shutdown the Process Monitor and look around the time of your freeze to see what was running):

 

Setting up the Process Monitor for FSX – Another investigative tool used to pin down a situation where FSX/P3D freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb896645. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the sim froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

 

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large. For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are sync’d. Going through one minute of a glitch is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D events. It would be nearly impossible to find a possible glitch if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

 

Open Process Monitor. Click on the Filter tab and then Filter….

 

Display entries matching these conditions:

 

Where it says Architecture, click on that and select “Process Name”

 

Go next to the blank box and click on that and select FSX or P3D.exe and make sure “Include” is shown (FSX or P3D must be running when you do this!!). Once completed, click on Add and then click OK at the bottom of the form and Go Fly.

 

You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).

 

Best regards,

Check the Event Viewer to see if there are any error messages. The AVSIM CTD Guide located to the right of this forum under Hot Spots shows how to open the Event Viewer and what section to look in. You can also try to run AppCrashView (link in AVSIM CTD Guide) and see if there are any errors. If that does not work then I would run Process Monitor as follows (this will be in a future update of the AVSIM CTD Guide)(This setup will ensure only FSX and FSX addons are monitored. When FSX freezes, you will want to shutdown the Process Monitor and look around the time of your freeze to see what was running):

 

Setting up the Process Monitor for FSX – Another investigative tool used to pin down a situation where FSX/P3D freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb896645. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the sim froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

 

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large. For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are sync’d. Going through one minute of a glitch is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D events. It would be nearly impossible to find a possible glitch if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

 

Open Process Monitor. Click on the Filter tab and then Filter….

 

Display entries matching these conditions:

 

Where it says Architecture, click on that and select “Process Name”

 

Go next to the blank box and click on that and select FSX or P3D.exe and make sure “Include” is shown (FSX or P3D must be running when you do this!!). Once completed, click on Add and then click OK at the bottom of the form and Go Fly.

 

You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).

 

Best regards,

 

Thanks, I will try that.

I get that screen often but it doesn't freeze.  If i click on the minimize button upper right, it clears to the normal opening menu and I can usually close down fine.  I have noticed that some programs, like Multicrew and others, can sometimes interfere with shutting down FSX. 

 

Randall