Here I am finally on the upside of the curve after another almost full day of troubleshooting.By the way, I am running FSX SP2, Windows 7 64 bit Home Premium , 4 Gigs of Ram, etc etc,,.IT all started after a few hours spent spring cleaning the computer. You know, the Defrag, The clean out the registry of junk .. all those normal utilities and service operations we all do from time to time. Finished this housekeeping operaton on Friday night and went to bed.Saturday lunchtime. Hmmm new skins for the SMS Airbus ..Admittedly FS2004, but should work fine in FSX. Download, install and kick off FSX. Intro screen, switch to quick flight. Uh-oh - aircraft preview screen is black. Next minute " A fatal error has occurred".QUick wipe of the sweaty hands, steady, steady...Should be able to recover from this.First, uninstall the last skins, change back the Aircraft config files and reboot. Nada, Same error.Ok, delete FSX.CFG file. Starts ok, requesting permissions to use add on modules, click yes and get back to Music and intro screen.Switch to quick flight - CTDOkkkkk....Last time this happened got a quick flash of assembly something error. Peruse the Interent. Gold mine of faults relating to this and something called Uiautomativecore.dll causing issues with Win 7 64 bit, could it be? Who knows, but to give it a try. Follow recommended steps. Reboot, Reset FSX,CFG Launch. Not even load screen this time, CTD before welcome.Perspiration on Brow now. Really starting to sweat it. The first black thoughts creep in.I have a lot of add-ons, payware aircraft with Machine code keys... lots of modified textures, scenery etcl... Where are those serial numbers? did I store them in the right place?I know, go back to System restore before yesterday's operation. Whoops, forgot, Fine tuning recommendations have been to turn of System Restore. So no rescue there.OK I am stumped. Reinstallation? No, first lets try a repair.... So in goes the master disk 1. Repair underway, takes forever. Then SP1, then uninstall SP2 and restinall SP2. Launch FSX - CTD ------ ARRRGGGGHHHHH!It looks like a total reinstallation - Oh my god - not again!!! (This would be, I think, the 5th or 6th time for a full reinstall over the past 4 years.) Thinking now of all the work involved...cripes it could take a couple of days.Back on the Internet first, just in case. Hello, whats this ? sage and timely advice from another user. Look at your System error reports. Good idea. (Why didn't I think of that first?)Went into reports and found some alerts under application failures.D93d.dll seemed to be a problem - and yes - it was occurring as I launched FSX. Perhaps that was it?Remove D93d.dll, Remove the Enbseries file. REboot - and yes - NO CTDFSX starts normally!!!! Hurray. relief. Everything works apart from Victoria scenery, which requires a quick reinstall, as does EZdock and UT2 - but it works without a major reinstallation. Put D93d file back into FSX, reboot, Crash. So yes, this somehow became corrupted. But wait, wasn't there a modification in the Config files you needed to include? So Use a past FSX config file and reboot. Same - Still CTD. So leave out D93d.dll and it works.Pity. No doubt I have't totally got to the bottom of this, but for now it works.I probably could have avoided all of the above had I looked at the system error files first.Moral of the story - I obviously use FSX too much as it has taken on a whole big dimension of importance that I would want to reinstall it all again. Most simulations I suspect I would have long ago given up on...Still , a good outcome in the end and to celebrate a quick flight with my new skins on the SMS A320 (Condor and AIr NZ) -very nice even though designed for FS2004.Thanks for reading

You could have simply restored the last healthy image you made with a program like Acronis. This might take 15 - 20 minutes. :( This is how I recover from such kind of problems. :(

You could have simply restored the last healthy image you made with a program like Acronis. This might take 15 - 20 minutes. :( This is how I recover from such kind of problems. :(

Yes, I suppose I could have instituted some sort of localized back up like that - I have sometimes backed up the whole hard drive, but that is compressed and I have not specifically backed up just FSX. I have sort of failed at backing up on a regular basis, so I only have my self to blame. I guess my point ought to have been that this product called FSX is still a tempremental beast, made more so by our constant need to make it go better.We are long overdue for a consolidated FSX product which includes the two patches and some more fine tuning, but as that is not going to happen, we all tweak away (well, at least I do), in my quest for the holy grail of peformance and visual excellence. In doing so, we ride that curve of danger and are reminded of it abruptly every now and then....My file is actually over 81Gbs of data and still climbing.Thanks for the response

I always thought that this involved the FSX compabilities with such products!

In doing so, we ride that curve of danger and are reminded of it abruptly every now and then....My file is actually over 81Gbs of data and still climbing.

No risk, no fun! :( I save C: with OS, Applications, FSX and Add-ons in one image. C: is 62.2 GB, the corrsponding image is 37.8 GB. I would not feel comfortable without this tool. Make once a week an image and you can always feel good. :(

No risk, no fun! :( I save C: with OS, Applications, FSX and Add-ons in one image. C: is 62.2 GB, the corrsponding image is 37.8 GB. I would not feel comfortable without this tool. Make once a week an image and you can always feel good. :(

I use Norton Ghost #15 to do the same thing every week and keep the last 3 backup images on an internal disk + two monthly backup images on an external SATA disk.Disk space is cheap and I rather be flying than pulling my hair out (there's too little left) with frustration.Backup up images = peace of mind & the warm and fuzzy feeling of a security blanket.