Probably O/C related.

You have the uianimationcore.dll file in your main fsx directory?

 

Delete the fsx.cfg file and let it rebuild. Don't make any tweaks manually to the file except adding the highmemfix line

 

Do you get the same problems?

Gentlemen, I'm grateful to each one of you. I know how this wonderful community works, so a great big Thank You from me. Each one of you is a credit to Avsim.

 

I've been there when I've either helped somebody or tried my best to help somebody. Now the boot's on the other foot.

 

I reckon, I'll take a sabbatical, watch some Airliner DVDs, then as Srdan has opined, start afresh. Let's see where we go. I only wish my hardware stockist would be able to lay his hands on that 560Ti GS 1Gb card soon. For now, it's time-out for me.

 

Will update as and when.

MD-11 was made for FS2004 yes?

 

Just wondering does the same thing happen to you with one of the newer addons that werent ported eg the NGX or the Turbine Duke?

 

I ask this because I only have problems in FSX when using old addons like the Dornier Do-27. Flights are fine for short hops but if I do a tour or even use time acceleration sometimes things can happen, bad things..

MD-11 was made for FS2004 yes?

 

Yes, and for FSX too. It is not a port.

MD-11 was made for FS2004 yes?

 

Just wondering does the same thing happen to you with one of the newer addons that werent ported eg the NGX or the Turbine Duke?

 

I ask this because I only have problems in FSX when using old addons like the Dornier Do-27. Flights are fine for short hops but if I do a tour or even use time acceleration sometimes things can happen, bad things..

 

The MD-11 is pure 100% unadulterated FSX code, nothing was ported from the FS2004 version because FSX version came first, then it was adapted for FS9. Seems there´s still quite some confusion about this point, and i wonder how it influences/influenced the product´s sales. You don´t get this confusion with their later products so dropping FS9 may have been worthwile for them.

 

Not arguing with you btw, just commenting on something that caught my attention some time ago (the belief that the MD-11 is a port).

My q6600 also o/c to 3.2ghz for many months and I keep getting blue screen and program crash every few weeks. I now run the cpu at 3.0ghz and all problems gone. Try run your q6600 at default 2.4ghz and see if the problem persist.

The MD-11 is pure 100% unadulterated FSX code, nothing was ported from the FS2004 version because FSX version came first, then it was adapted for FS9. Seems there´s still quite some confusion about this point, and i wonder how it influences/influenced the product´s sales. You don´t get this confusion with their later products so dropping FS9 may have been worthwile for them.

 

Not arguing with you btw, just commenting on something that caught my attention some time ago (the belief that the MD-11 is a port).

 

That's ok I'm not picking up the wrong tone :)

 

I don't think I picked up on the confusion around this because I never followed the MD-11 at all as I have no interest in it. The only airliners I'm interested in are the ones common in Australia i.e. 737, 747, Dash 8.

 

It was just an assumption based on the fact it's been a few years now it's not the newest addon.

 

It won't affect sales from me since I'm still not buying it even if it only just came out, but I did buy the 737 and soon the new 747 (when it comes).

 

Soo.. I guess that rules out the instability there.

 

Problem with computers is there are so many possible causes, since there are so many components and software parts all working together.

Now that you have mentioned VM, I had the pagefile moved to another partition. Could that have caused something like this?

 

I believe so if it wasn't done right or as suggested by the real 'experts'. Here's an article I refer to often and think you need to read. It's about understanding the Windows Page File System - http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disable-it. The author does not recommend moving it to a different partition but instead to another HHD, and agrees with me, it should be set to system managed size. FSX is an old application and uses the CPU more than the GPU (whereas it was the reverse for FS9 and earlier versions of FS). FSX is a memory intensive application and is power hungry and needs a lot of juice to run. I really think this is your problem. I know of one other individual in the CTD forum who had the exact problem as yours and I recommended changing his page file to system managed size and that was the fix.

 

Best regards,

Jim

Thanks for that input Jim.

 

I had in fact set the Pagefile as a Custom Set-up of 2.5 times the installed RAM, which is what various tweakers had recommended when using WinXP SP3 32-bit, so I just did the same here with the current Win7 64-bit OS.

 

I will now do what you have suggested and set it to system-managed size. Unfortunately, until I get an SSD,----- and the current rig is due for a much-needed hardware upgrade, as soon as I get that GPU that I'm awaiting for,---- I will not be able to put that Pagefile to another HDD.

 

Will report back on your 'fix'.

hmmm, got me wondering now about moving the page to my secondary hard drive. About the only thing I haven't tried to get that one last boost to make me happy. :)

Wow, sounds like what I had with FSX a few months ago. I would be flying nicely for about an hour or so and bang!, The dreaded "Black Screen of Death", but with sounds still playing in the background. Very weird.

 

Anyway, I did a fresh install of FSX and removed those two UIAutomationCore from sys32 and syswow64 in the windows directory. This did the trick for me. No more black screen. Granted, it took a while to fix but I did do a lot of research here lurking around and reading lots of post from just about everyone here! and it paid off. Thanks AVSIM!

 

I just figured out another problem I was having recently too. FSX was hanging/crashing on me everytime I quit running FSX. I had this "SmartAssembly" error poping up and it was bugging the hell out of me. Then remember I installed Ultimate Traffic 2 and later on I purchased F1's Audio Environment - Airlines. I removed Audio Environment to see if that was the culpirt...and it was!...no more SmartAssembly errors. I guess UT2 and AE don't like being together!..lol

 

Anyway, so far so good. Sometimes is just as well to leave FSX alone and just add only a few addons. I think the more you add, the more problems surfaces.

 

Just wanted to reply since the OP is experincing the same issues I had.

 

peace

"Will report back on your 'fix'."

 

Not really MY fix. I'm not that smart. But there are some really smart people across the Internet (and here on AVSIM). Hope it works.

 

Best regards,

Jim

Thank you Jim + egguzman

Did it turn out well or is it still a mystery, Rick?