November 11, 201312 yr Hi guys, Left the PMDG777 cruising at FL330 alone for an hour today and when I came back FSX was not responding anymore. Came with "Microsoft FSX has stopped working" and I choose the option to close it rather than checking for a solution. I downloaded "Appcrashview" but I can do nothing with the data it spits out :-( I can post the Appcrashview report here, but it is quite long, so I am looking for something a little more user friendly. Like..."FSX has stopped working.....this or that driver/app/etc caused the problem" (Ps I realize the 777 might not be the cause, but I am active almost only on this Forum so I hope its ok to ask for help here.) Rob Robson
November 11, 201312 yr Author The module that caused the crash usually isn't far down the report. Eric W Ok, here is the first ooh....20% Version=1 EventType=APPCRASH EventTime=130286691029382208 ReportType=2 Consent=1 UploadTime=130286729714784445 ReportIdentifier=5f666042-4b01-11e3-96fd-3085a990ba55 IntegratorReportIdentifier=5f666041-4b01-11e3-96fd-3085a990ba55 WOW64=1 Response.BucketId=3884761380 Response.BucketTable=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61637.0 Sig[2].Name=Application Timestamp Sig[2].Value=46fadb14 Sig[3].Name=Fault Module Name Sig[3].Value=ntdll.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.18247 Sig[5].Name=Fault Module Timestamp Sig[5].Value=521ea8e7 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=0002e41b DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.256.48 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=fb8b DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=fb8bd1bf7dcc44d047c58f37f56ad727 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=fa63 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=fa63c80ebf2b9d98cfa9fc211d9a92ad UI[2]=C:\Flight Simulator X\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working UI[4]=Windows can check online for a solution to the problem. UI[5]=Check online for a solution and close the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program Rob Robson
November 11, 201312 yr Ok that's the ntdll.dll crash and that's a tough one. that's a windows module. google "ntdll.dll" crash and you will see its faulty software usually, but can also be a corrupt driver or such. Occasionally its a bad memory module or video card. I had ntdll.dll crashes quite frequently and found it was MyTraffic 5.4c. I cleaned it out and reinstalled up to 5.4b and I am all ok there.
November 11, 201312 yr Author Ok that's the ntdll.dll crash and that's a tough one. that's a windows module. google "ntdll.dll" crash and you will see its faulty software usually, but can also be a corrupt driver or such. Occasionally its a bad memory module or video card. I had ntdll.dll crashes quite frequently and found it was MyTraffic 5.4c. I cleaned it out and reinstalled up to 5.4b and I am all ok there. Ok thanks, that is very helpfull....I recently updated to Mytraffic 5.4C as well. How did you find out that Mytraffic caused the problem? Have you told the developer so they can provide a fix? Rob Robson
November 11, 201312 yr Its a scheduling bug or something. there are a few threads on the forum about it. I was on the case when I had the problem in a Cessna . So I completely uninstalled it, deleted the folder and started over with 5.4b. Incidentally I now get the freeze where the sim just locks up for 30 seconds up to 10 minutes then continues almost every flight if not 4 times a flight. Wonder if I stumbled into something because I never had that before . I am going to try removing AI all together and see if that helps.
November 11, 201312 yr Author Ok hmmm I will see first if this happens more often to me. I would be interested in your results though! Rob Robson
November 11, 201312 yr Happened to me earlier with 5.4C and the 2013 schedule. Switched to 2012 schedule and that fixed it for me!
November 12, 201312 yr Author Happened to me earlier with 5.4C and the 2013 schedule. Switched to 2012 schedule and that fixed it for me! Ok that sounds easier. How does one switch?Is that an option or do I have to import new schedules for that? Rob Robson
November 12, 201312 yr Ok that sounds easier. How does one switch?Is that an option or do I have to import new schedules for that? Open up MyTraffic Communicator and use the Select Schedules menu. Barry Friedman
November 12, 201312 yr Author Open up MyTraffic Communicator and use the Select Schedules menu. Cool thx have you downloaded a new AMD driver by any chance? Nope, I have Nvidia. but thx Rob Robson
November 14, 201312 yr just a suggestion search you tube for a guy named ...fsx genius...he has a video out about this exact problem..rgds hope this helps
November 14, 201312 yr Author just a suggestion search you tube for a guy named ...fsx genius...he has a video out about this exact problem..rgds hope this helpsAbout what problem? The ntdll crash? or Mytraffic 2013 problem? I will search and take a look though, thx. For what it is worth, FSX has not crashed on the subsequent 3 flights and I have not changed anything yet. (might have been a one time thing, we shall see) Rob Robson
November 14, 201312 yr Hi Rob, Post your problem here: http://forum.avsim.net/forum/262-crash-to-desktop-ctd-forum/ I had a lot of problem to a view months ago! Firehawk44 / Jim is always willing to help you with your problem. Never had any problems before and then of the blues all sorts of crashes. Sometime I wonder if it has something to do with the Windows Updates? Good luck! Regards Robert
Create an account or sign in to comment