I get APP crashes all the time with FSX.For me FSX is installed in a different directory (different than the usual program files etc etc), UAC is disabled, AND I am the administrator. Somehow the PC still thinks I'm not admin.So what I've done, and I think is the only real workaround to this problem (other than running as admin in the program shortcut - which should be grayed out if UAC is already disabled), is to create a task using the task scheduler, pointing it to FSX.exe, and running it at highest privileges in Win 7 mode.Instructions are in this link, it seems to have worked for me:http://www.sevenforums.com/tutorials/11949-elevated-program-shortcut-without-uac-prompt-create.htmlPrior to enabling the way FSX.exe starts up I have G510 gauge errors, d3d.dll errors, and other fsx-related APP CRASH errors all day long. Especially with the Mustang And ES Citation. The second I touch the MFD controller for the G1000 my FSX would CTD.I've tested this new shortcut and I've changed FP's on my mustang, no problems, no crashes.Hope it helps you too!

I've tested this new shortcut and I've changed FP's on my mustang, no problems, no crashes.

Jim Rhoads might make you a VIP member at the Mustang forums, if this cuts down on some of the postings?Reminds me, I must learn how to fly the Mustang, one of these days... :(

Jim Rhoads might make you a VIP member at the Mustang forums, if this cuts down on some of the postings?Reminds me, I must learn how to fly the Mustang, one of these days... :(

Used to be a cert pro... just didn't have the time to commit anymore...And the fix wasn't mine, just a link I found :(

Used to be a cert pro... just didn't have the time to commit anymore...

Small world, isn't it? :( And don't forget your version #, PLEASE! :(

I will clarify a few things I've learned. If you right click the exe, and select run as admin, it should do the same thing. There's two reasons I needed an alternative to this:1) I didn't want to have to right click everytime I ran FSX2) I run an external limiter so I'm not actually clicking the fsx.exe shortcut, I'm clicking the .bat file, which runs the .exe file... Also, devs have been telling people from day 1 to disable UAC. However, by doing this, some programs will have the "run as admin" option greyed out under the shortcut properties. FSX's is greyed out and if you don't want to right click ->run as admin everytime, the way I linked is the perfect way to fix it for good. Only takes about 3-5 minutes to set up.

Disregard the entire post... I'm uspset!!I thought I had the fix but I had another Garmin 510 gauge crash again with the mustang!!!Nooooooo, it's so mean to me, trixy flight sim!!! DANG IT!

I've been fighting the g3d.dll crash for weeks now, even after a complete reinstall. I swear it's something after REX2 textures but am not 100% sureI just rebuilt my fsx.cfg file, I'd suggest you try that too, and only put in a few tweaks at first. Let me know if you get another one! What nvidia drivers do you have? I have the beta 270.51's

I've had that error too.... I actually haven't had that one recently however, only the Mustang-related Garmin gauge error.It is very random though like you say. I was confident I had the fix after creating that task to run at highest privs, and went without a crash for about 6 hrs, flying the Mustang, pressing all the buttons, no problems. Uggh, frustrating. Other people have the errors too. Some say it can be fixed to run as administrator but it's weird because I am the administrator on my box. Also, I'd like to not have to go through the process every time I play FSX. Unfortunately my option to continously run as admin is greyed out (I presume because UAC is disabled - hey, could you check yours to see if its greyed out as well?)Right click FSX->properties->shortcut tab->advancedThanks!edit: I'm at a spot where I can reproduce the Mustang CTD... all day every day. It's so weird though... maybe it's a database thing argh!

Try this, just make a shortcut of the fsx.exe file, don't check run as administrator.Remove the fsx sdk lines in the dll.xml filerebuild fsx.cfg file and see if you get any errors

I actually just got another d3d dll crash tonight :(I'm guessing it has to do with the factory OC on my GTX 570. On my old PC I had a 8800GT and it was factory overclocked. It always crashed Battlefield 2 on OC settings. So I took it back to reference settings. I've done the same with this evga card, checking with Precision, hopefully that will solve it.

I've been fighting the g3d.dll crash for weeks now

Yeah, I've been getting those errors too lately, mostly in Orbx NA Blue area. I suspected almost all addons so far but when I removed them (I have just too many stuff to test everything) I still got the g3d.dll crash.. even worse, it looks like it's semi-random.. in general I get this CTD every 10th flight, it's totally annoying and I'd be a very happy person if I'd know what's causing those crashes. I'm not sure it's REX since I don't get this error if I fly in Europe, ever, and REX is everywhere so I should get this error there too... I lowered the OC, the FSX settings,.... nothing helped. It's really frustrating when you don't know when it's going to crash next.

Yeah, I'm afraid I'll be in the middle of a flight on vatsim (like I was last night GRRR) when I press the magic button and boom lol!I thought it was my OC but I remembered I was getting this error right after I installed vanilla FSX.*sigh*I just think it's dirty Windows 7...I'm starting to long for XP again :(

I've been fighting the g3d.dll crash for weeks now, even after a complete reinstall. I swear it's something after REX2 textures but am not 100% sureI just rebuilt my fsx.cfg file, I'd suggest you try that too, and only put in a few tweaks at first. Let me know if you get another one! What nvidia drivers do you have? I have the beta 270.51's

-------------------------------------------------------------------------------------------------------Last week, I was getting consistent g3d.dll CTD's when flying over and around Portland and/or Seattle. No matter what altitude. No matter. Reading on another post that it might be due to a video driver issue, whether by the actual driver set or in how you chose to install it, (over another prior set, or the nVidia 'clean install' option....well, I reinstalled my driver set with the 'clean install' tagged and I have flown over those two offenders, with no further g3d.dll generated by those locations. I hope this helps you. Reinstall using the 'clean install' and report back if you too have cleared up your CTD.

When I built my system I just installed the latest drivers from the nvidia web site. I'm not sure how else to do it - you'd think the latest drivers would be correct for a GTX 570 since it's a fairly new card.Are there other drivers that work better?

I just started getting the g3dll errors after an install of w7 sp1, not sure if it is a coincident or not..