Anyone with any idea why my MD-11F should all of a sudden completely freeze and lock up FSX.Did an EGLL-EHAM flight and was descending into EHAM to pick up the STAR,when I had it lock-up and freeze FSX,yet was only using 24% CPU(Quad Core+12Gb).But,when I tried the very same flight with the 747,no issues.Strange? And all this after re-installing FSX,then other aircraft and scenery add-ons followed last by the 747 first,then by the J4100,and then the MD-11.Thanks for any advice.

I know the MD-11 draws more resources on the system than the 747 does. In FSX I also can suffer similar events with the MD-11 out of the blue, which is why I normally prefer to use it in FS9 where is very stable. Your system right off the bat is better than mine with that processor, but that dosent mean you won't have any issues. One thing that seems to be consistent with those who experience this is when switching views. Although my problems are not isolated to switching views, I have to be VERY careful when doing so in the MD-11 or its almost certain to lock up and crash.

Rick, The problem could be anything really. Have you checked your event logs? Is this just a one time crash? Were you actually in the FMC(cdu) selecting the approach when it crashed (Known issue for some)? How was it only 24% CPU load? What I mean was, did it lock up and then you checked task manager or a monitor of some kind? Or did you just happen to be looking at it when it crashed? I can't imagine many circumstances where my CPU load would be so low in FSX personally, unless FSX is already hung up or crashed that is.How long have you been flying the MD-11 (had it installed and using it)?I wouldn't lose sleep over it if it's just a one time thing. Check the event logs and if it happens again, try and gather more info to exactly what was going on when it crashed.*Also, it would be wise to list your complete computer specs or as much as you can for assistance in these type of issues. That's why so many people add their specs to their sig,,, hmmm, that reminds me I need to update my sig :(

Thank you Bill and Dan for your responses.Matter of fact,very early on in my FSX+SP1+SP2,I did experience the CTD when cycling through the different views but that was soon resolved as I use Win7 Pro 64-bit to make use of the full 12Gb RAM,by modifying the UIAutomationCore.dll,which soon put an end to those particular CTDs.But this latest issue is new,and furthermore,checking Task Manager does not show the 4 cores running at 100% when locked up.And yes,Dan,the very first place I routinely go to check any CTD is the Event Log.And no,I had already set up my MD-11F FMC with the arrival STAR inputted and was following the heading for that STAR descending just off the Belgium coast,when all off a sudden the MD-11 just froze although I could still hear the engines running,and FSX reporting 'Not Running' in Task Manager.The same happened on a day/night KSFO-EGLL flight using the same aircraft,when off the coast of Ireland,it froze and locked up FSX.I've been flying the whole gamut of PMDG products in FS2004 and the MD-11 since it first came out in FS2004 version before migrating to the FSX version,so am well-versed in its usage.And for the last 2-3 months have had no issues logging upto 500 hours with it alone,asides from the other high-level aircraft such as the Level-D,Simcheck's A300-B400,until I decided to add a repaint,which immediately caused me to have visualfx.dll issues,which I was not able to resolve,which is why I ended up doing a complete re-install,and in doing so lost my Logbook.Comp Specs:Intel Core2Quad Q6600 o/c stable to 3.4GHz,Antec 900/2 case,OCZ 8500 12Gb,XFX HD5770,Samsung 500Gb with FSX in its own directory,Be Quiet! PSU

Thanks for the additional info Rick, I never assume to know more than the poster but its of course hard to visualise someones issue without more detail :wink:The oddest part of this is FSX crashing and you don't have it in task manager. I remember long ago I had a somewhat similar experience but it wasn't locking up or crashing, but after I closed it the sounds remained. The app was gone in the first tab of TM (Applications) but the process was still running. I think new sound drivers cleared it but of course it was a different issue.The only thing that comes to mind (and this may be a long shot) is that something is either starting in FSX or altering your window count. The MD-11 uses near max windows and if its exceeded FSX will crash with nothing in the logs. The only way I found the issue was because FSP had a log and noticed window errors in it. So if your running various other addons or even one could cause this if it has window frames of any kind, it may be it.Again though this would have to be something you started or maybe is attempting to open a message dialog box of some kind later in your flight.If you don't fly FSX missions or use the mission compas you could just remove two files from your FSX/Gauges folder and test. I am at work right and don't remember the exact names, but the files start with "Mission". Just cut and paste them to your desktop next time you fly and see if you see anymore issues.I know its a long shot, but otherwise I'm stumped.

Dan,I read your posts often in Avsim Forums,and the one thing I love about your posts is the positive help you always render.Nice one Dan.Thanks a lot for all your tips/suggestions.The odd bit is when the MD-11 locks up,and the sounds of the engines are still running,whilst the memory and CPU monitor I have running in the background reports around 1.3Gb of RAM being used by FSX with just one core going high but not quite 100% while the other three are all low,but with 12Gb spare I know I have no resources issues there.What really baffles me is that I then fly the exactly the same route with another high-end PMDG aircraft,the 747-400F,albeit not as intensive as the MD-11,---which I must admit is my favourite aircraft because PMDG have with that aircraft managed to so successfully replicate almost everything as in the real world MD-11 other than the weather radar,and there is so much for the end-user to get involved in just preparing the aircraft for a flight,never mind the actual flying even without FS2Crew,---I have no locking-up or FSX freezing issues. As I have just done a complete FSX reinstall,the only add-on scenery I have is the Aerosoft EGLL,and the Level-D 767-300ER,and the three PMDG aircraft,i.e.744,J4100,and the MD-11,so as far as add-ons go,it should not really in theory tax FSX,or I'd have thought so.Somebody may correct me.I've not got around to flying missions as yet as I want to accumulate as many hours on the 'heavies' before going for the Aerosoft F-16 or a Tomcat to give me a break from my obsession of long-haul flights.That makes two of us stumped.I really loved the FS2004 versions,where I had no issues whatsover even running an ancient single-core Skt939 AMD but now that I've reluctantly at first switched over to FSX,I cannot somehow go back to FS2004

Thanks for the kind words Rick, I'm glad I have an occasional fan and good to see it's not just enemies :wink:Anywho, thanks for the kind words.If you're not running any addons such as FS2Crew, FSPassengers, or addon gauges (anything at all that has a window like explained above), then the only thing I can think of is rerunning the install (repair), or installing the latest .Net framework or C++ runtimes.Just for shins and tins, you could cut and paste your fsx.cfg somewhere else and let fsx build a new one. I have so many edits to mine I hate the thought of re-editing it sometimes, but just long enough to test. Atleast then it can be ruled out and many times have seen that be the issue in the long run.Hearing the sound like you mentioned again is something I have seen many times and by itself isn't much of an issue and when I had that problem it was after I closed it and not accompanied by your main issue of FSX crashing.Last but not least, if you tried all of the above, including the fsx.cfg temporary relocation then I would just say no matter how many times I try to understand programs and Windows, some times something just gets screwed up on install. New install after new install I now have an exact order where 99& of the time things run great, but there is that 1% where I can only write it off as a Windows hiccup. I hate not knowing but sometime just have to cut my losses and try, try again.Hopefully you won't get to that point though. Try removing those files I mentioned too. Just temporarily. As said in the movie War Games, "I'd pizz on a spark plug if I thought it would do any good" :(

Thanks for the kind words Rick, I'm glad I have an occasional fan and good to see it's not just enemies :wink:Anywho, thanks for the kind words.If you're not running any addons such as FS2Crew, FSPassengers, or addon gauges (anything at all that has a window like explained above), then the only thing I can think of is rerunning the install (repair), or installing the latest .Net framework or C++ runtimes.Just for shins and tins, you could cut and paste your fsx.cfg somewhere else and let fsx build a new one. I have so many edits to mine I hate the thought of re-editing it sometimes, but just long enough to test. Atleast then it can be ruled out and many times have seen that be the issue in the long run.Hearing the sound like you mentioned again is something I have seen many times and by itself isn't much of an issue and when I had that problem it was after I closed it and not accompanied by your main issue of FSX crashing.Last but not least, if you tried all of the above, including the fsx.cfg temporary relocation then I would just say no matter how many times I try to understand programs and Windows, some times something just gets screwed up on install. New install after new install I now have an exact order where 99& of the time things run great, but there is that 1% where I can only write it off as a Windows hiccup. I hate not knowing but sometime just have to cut my losses and try, try again.Hopefully you won't get to that point though. Try removing those files I mentioned too. Just temporarily. As said in the movie War Games, "I'd pizz on a spark plug if I thought it would do any good" :(

Thanks for your latest input,Dan.Not a fan or anything like that--I just appreciate anybody who'll take their time out to assist others,coz without the likes of you giving up their time,guys like me would be up a creek without a paddle.Oddly enough I had been thinking on the same C++ Runtimes as the ones that came with the MD-11 and the 744 are 2008 versions.I'd have thought there is a more up-to-date version but was reluctant to download and install in case I screwed up the PMDG installs.Tried that FSX.cfg trick--made no difference.I love your brand of humour,Dan.Your last piece after your Labor Day was brill.I'll give your suggestion of a complete wipe-clean/re-install a try.Luckily I have not added to many add-ons.I'm just hoping that MS dont throw me out when I try to re-activate.

Hi RickDid you have any error message after closing FSX down? I just had a freeze again with the md11 and after ctrl-alt-del i get an error message: 0xc000014bI have done a search on this error but my pc-knowledge is not good enough to enterpret it all. I did notice, though, that it could be related to .net that has to be updated as Dan already stated.At the time of the freeze I was running: PMDG MD11 with FS2CREW, REX 2.0 overdrive, RC4. The freeze happened 2 hours after FSX startup. I have had this kind of freeze before but it happens randomly.Has anybody else experienced this error?By the way, it is a flightsimmers worst nightmare: Girlfriend away for 2 days, everything setup for a nice long flight in my favorite aircraft, a nice cup of hot coffee, every chart for the route setup on laptop and then... CTD!

Hi RickDid you have any error message after closing FSX down? I just had a freeze again with the md11 and after ctrl-alt-del i get an error message: 0xc000014bI have done a search on this error but my pc-knowledge is not good enough to enterpret it all. I did notice, though, that it could be related to .net that has to be updated as Dan already stated.At the time of the freeze I was running: PMDG MD11 with FS2CREW, REX 2.0 overdrive, RC4. The freeze happened 2 hours after FSX startup. I have had this kind of freeze before but it happens randomly.Has anybody else experienced this error?By the way, it is a flightsimmers worst nightmare: Girlfriend away for 2 days, everything setup for a nice long flight in my favorite aircraft, a nice cup of hot coffee, every chart for the route setup on laptop and then... CTD!

Hi HeinoNo,I do not see any of the error messages as the one you have described.All I get is the engine sound still running,but the plane is not moving against the background and I cannot click on any of the hotspots on the 2D Panel.FSX just locks up.I have to then shut it down from the Task Manager,and when I do check the Event Log,it does not point to any error message,which makes it all the more baffling.But then mind you,I do not run REX,RC4 or anything like that,so mine is not an error related to those particular add-ons.But the error message you are getting I think is the kind of error you would have seen in the good old days of the BSOD(Blue Screen of Death).I'm sure somebody out there in Avsimland will decode that error string for you.My guess is it is a hardware-related error.You are lucky to have a girlfriend away so that you can indulge in your hobby.I wish my late wife was still around then I would not have to kill time flying long-haul routes.

Rick,were you flying at dawn or at dusk ?

Rick,were you flying at dawn or at dusk ?

Hi Stefitt.No,actually it was a plain ole daytime flight from EGLL-EHAM Martinair Cargo return to base.What beats me is that I had done the night flight from VABB-EGLL without a hitch,from t/o to auto-landing using an FSC generated flightplan with SID/STAR,so this glitch had me scratching my head.I know these sorts of aircraft are far more complex than the usual fare available,but they are rock-steady normally.Just makes me wonder if it is FSX or the aircraft behaving oddly. I have not flown the plane since,as I'm busy building time on my 747 having lost my Logbook.Once I get back to the MD-11,and if I get this same scenario again,I'll inform.Will try your Highmemfix tip,David.Thanks.

Update on the last issue I had.Flew a long-haul flight from VABB-LSZH.No issues filling-in the FMC,no issues with any en route lock-ups,etc as previously encountered with an approach to EHAM.Even had no probs when changing the pre-loaded STAR for Rwy16 to Rwy34 after reading the ATIS info and verifying with an ATC vector.However,despite being at the correct FL to intercept the GS,and getting the required ILS freq captured,I could not auto-land,so had to do a GA,and the very same happened again,so I chose to hand-land it instead,again with no issues.I know I have full autoland when I see G/S and Dual but on both these occasions did not see Dual.Only a small niggle as the main one experienced previously did not manifest itself again.Maybe someone has a pointer for the autoland?

I must have tempted fate! There was me routinely flying between LSZH to EGKK in my Swissair MD-11 minding my business at 36k when I last posted then returned to get ready for my descent to EGKK.But as the FMC-input flightplan was an FSBuild f/p,I wanted to add some more waypoints to the flightplan before landing at Rwy26L,so used the Map to check the intersections,etc,before Rwy26L,when all of a sudden FSX crashed with sim1.dll error(Events Log).Have done a search here but to no avail.Anyone with any idea what this DLL error is or what triggers it to crash FSX?Thanks.

Rick, there are only two solutions that I have personally used and can say they worked for me:-1. HIGHMEMFIX=1 ( put in FSX cfg. under graphics)2. UIAUTOMATIONCORE.dll Put in the FSX folder.....use the Vista 32 version)Since using 1, I have had very few CTD's.So I have now removed 2, from the FSX folder. HIGHMEM simply sorted it!FSX never runs with any high degree of consistency, In My Humble Opinion! Regards.David Harrison

Hi David Thanks for that.In fact I did have my UIAutomationCore.dll in my FSX Modules folder and had removed it from the system32 folder,until I read another thread in another forum suggesting moving it to the FSX root folder,which I have done.I'll get around to your HighMemFix next.Then I'll try another MD-11 escapade.Cheers.