Hi all,

 

Flying either the NGX or Majestic Q400, I am getting occasional freeze ups. Usually happens only after an hour or more and not on every flight. Sound can still be heard but screen stays as if paused. I can hit Cntl+Alt +Delete to enter the Task Manager and the sim immediately unfreezes and I can continue flying. The problem seems to occur when I go into spot view and / or when I re-enter the cockpit after spot view. My FSX settings are quite high but I have played with the cfg settings for texture resolution 4096/1024 and the loading distance 4.5 vs 6.5. Also tried adding and deleting BufferPools / UsePools=0 in the cfg.

 

Any ideas on where to look to eliminate this? Also, given that the sim is only freezing, not crashing, is there a log file somewhere I can view to see what was happening in the moments leading up to and during the crash?

 

Flying with REX Essential ( not overdrive), My Traffic 5.4c (possible suspect?). Sim runs ultra smooth at 30fps locked, even at addon airports. DX9.

Any ideas on where to look to eliminate this? Also, given that the sim is only freezing, not crashing, is there a log file somewhere I can view to see what was happening in the moments leading up to and during the crash?

 

The following is a quote from the AVSIM CTD Guide under the heading "Actions to take after a crash is encountered": 

 

"AppCrashView - usually, when you get a CTD, a Windows Error Report (WER) is generated by Windows.  This report is not very detailed and Microsoft did not make it easy for you to find or interpret the report.  After a crash you should download and run a neat utility called AppCrashView (click on AppCrashView to go to the website to download this program).  It interprets the Microsoft WER reports and provides more details.  If you post a CTD or problem, you should copy and paste the report in your topic.  Along with this, include your system specifications."   There is also information in the guide on accessing the Event Viewer in case a Windows Error Report was not generated.

 

I see you have your system specs which are the same as mine and I see you might have been reading some other topics.  MTX 5.4c removal fixed my ntdll/StackHash problems.  You can simply disable in the Scenery Library and see if this fixes your problem.  Freezing/locking up is usually a StackHash error.  When I was getting my freezes though and went into Task Manager, FSX would still not respond and I had to shut it down. I advised another member the following procedures on troubleshooting these types of errors:

 

"The way I found my problem (MyTrafficX) was to run Process Monitor (freeware from the Internet).  I start it up just before takeoff.  You have to turn it on after FSX is at least at the Startup screen so it can "see" it.  Once open, you need to click on Filter.  Change Architecture to Process Name and then go to the blank space and scroll down to FSX.exe then click on Add and then OK.  Process Monitor should now be showing only FSX stuff loading.  Now go to full screen and go fly.  During the flight I wrote down the time I saw a "glitch" in the flight, like a one or two second stutter.  Of course, if it freezes or CTD's, you need to get to the Process Monitor and click Ctrl+E.  This will capture all the events that occurred during your flight session.  Now you can scroll through to the time(s) you saw a glitch or FSX froze up or crashed.  There will be hundreds of thousands of entries for each minute but you can get an idea or see what was loading during that minute.  Maybe you'll see a lot of TCP receive/send entries which indicates something in FSX was going on the Internet and sending/receiving info.  Most likely be a weather program.  You will see where it sends/receives product licensing info too (it will so state).  If that is occurring in that "minute" you saw the glitch, maybe it was having a hard time finding the server or getting the data.  Just remember this program is not going to tell you "here's the glitch".  You have to figure that out yourself.  An hour flight will create about a 6-7GB log file so I would not run it much longer than that.  It creates a ton of data.  For instance you can right click on each piece of date that occurred in a nanosecond and get the properties of that entry.  It will show you every program on your computer that was used to load that nanosecond.  It will show you the memory stack addresses.  Way too much stuff.  But you can delete the log file after you analyze the report and get your 6 or 7 GB's back.  Now, when I saw my fps going from 50-60 fps to suddenly 6 fps, I wrote the time down.  I think you'll be able to see what's a major glitch and what is not.  See what was loading and suspect that product.  Disable that product and see if it occurs again."

 

Hope this helps.

 

Best regards,