I have that installed and FSX still crashes when selecting any aircraft with glass cockpit. I can fly all bloody day in any other aircraft, but anything with garmin G1000 systems kills the computer.

Hi Jim,I am experiencing this same error in msvcr80.dll. I tried installing the Visual C++ 2005 SP1 Redistributable Package as you mentioned but, unfortunately, I still get the error.It only started after I installed SP1. Everything else is running great and the sim is smooth and fast. Unfortunately, this error happens so frequently that it is almost unplayable at this point.I have seen the error with the default planes as well as the RealAir SF260. It seems to be more frequent with the SF260 but does still happen with the default planes.As others have mentioned it seems to be related to changing views but I have not found an absolutely consistent way to reproduce the error.If FSX is in full screen when the problem happens the sim just seems to "freeze" and I get an hourglass cursor. I have to press ctrl-alt-del then press cancel on the "Windows Security" dialog in order to get the error report screen.If FSX is in windowed mode when the problem happens the error report screen comes up normally.I hope the Aces folks see this thread and maybe have some input or suggestions.My Specs:ASUS P5N32-E SLI motherboardIntel Core2Quad Q6600 2.4GHz2Gb ramNVidia GeForce 7800GTKind Regards,Don Bush

I just noticed that those in this thread (including myself) that posted their hardware specs all seem to be running Nvidia GeForce 7 series graphics cards. I wonder if that could be relevant. Has anyone with a different card seen this same problem?I have never had any issues with this card and it still works without any errors in all of my other games. But still, it would be interesting to know if anyone with a different card has seen the problem.Kind Regards,Don Bush

>I just noticed that those in this thread (including myself)>that posted their hardware specs all seem to be running Nvidia>GeForce 7 series graphics cards. I wonder if that could be>relevant. Has anyone with a different card seen this same>problem?>>I have never had any issues with this card and it still works>without any errors in all of my other games. But still, it>would be interesting to know if anyone with a different card>has seen the problem.>>Kind Regards,>Don Bush>----------------------------------------------------Hi, DonMine is a nVidia GeForce FX5600 and I get constant CTDs. Usually no problems in VC and Spot View but when I attempt to use the 2D Cockpit (for instance to set the trim wheel in the Cessna 172), I get a complete white screen and sometimes yellow as well. The white screen will sometimes go away after 5 or 6 seconds but, if it's the yellow one, the sim won't recover. I get the 'Notify Microsoft' message often and I've had several complete system crashes with the message "Windows has recovered from a serious error".My FSX was working rather well considering my gear is more than three years old but, after I installed SP1 over FSX, it was just terrible. Reading this forum, I realized I should have uninstalled FSX before installing SP1 but I did not see this information from Phil when I checked FS Insider and found out SP1 was now available.I just downloaded it, expecting a readme would tell me anything important about the installation. When I realized my error, I uninstalled SP1, the SDK and FSX in that order and re-installed FSX anew, followed by SP1. Nothing doing! The crashes are as bad as ever.I have yet to complete a flight in FSXsp1 so, I went back to FS9 with my hundreds of free and payware addon sceneries, hundreds of free and pay aircraft and my 10-12 free+payware utilities. FS9 works like a charm for me, I don't mind at all having to continue using it. It's just that I miss the beauty of pre-SP1 FSX, and I wish ACES complete success with any workaround they can come up with.I posted on this in a thread started by simmer NotASenator, about a week ago, but I can't find the thread anymore. (I believe the thread was about issues with SP1- it had lots of very interesting info about SP1 and how to make it work properly) Where the heck is that thread... Is it just me having problems navigating the forums? joeveeP-4 2.8Ghz - MSI 6720 board w i685p chipset MSI nVidia G-Force FX5600 Graphics (128 Mb) 1024 DDR Mem - 37-in Viewsonic display

Today I turned off anti alias in the display settings of fsx AND in the driver settings of nvidia. Guess what? The crashes are gone!I'm being careful here to pretend to have THE solution for the crashes... but I've been flying for over an hour now, switching planes and places every few minutes, doing everything I did before, what crashed the sim within seconds and could not bring it down!Without AA the graphic is less nice of course, but I can live with it until someone (microsoft? nvidia?) has a solution. So give it a try, and write some feedback here how it works for you!Greg, Switzerland

Hi Greg,When I get home from work I will try it with anti-aliasing turned off and see what happens. I'll definitely post my results here.I agree that running with no anti-aliasing is not an acceptable long term solution but it would certainly be better than having the sim CTD every few minutes.Thanks for the info and your persistence!

Strange, I've had regular CTD issues in FS9 recently, never had them before. And I can't remember a single CTD in FSX with default planes yet. Thanks to this thread/Greg I found how to elimiante CTDs with one of my payware planes in FSX.

A question for this who are getting this msvcr80.dll CTD. Have you been using MS Intellipoint software? I read somewhere it may be releted (or not)

Hi Greg,I tried your suggestion and turned off anti-aliasing and, sure enough, it appears that I no longer get the msvcr80.dll crash. I tried everything I could think of to induce a crash but FSX remained absolutely stable. I was even able to toggle back and forth between full screen and windowed mode repeatedly with no problems. While in the virtual cockpit I opened the 2D GPS window and moved it to my second monitor and I also tested the 2D panel. Prior to turning off anti-aliasing any of these actions would, more often than not, cause the sim to crash with the msvcr80.dll error.Out of curiosity, I re-enabled anti-aliasing and I got the msvcr80.dll error within a couple of minutes. I turned off anti-aliasing and, once again, FSX was able to run without crashing.It certainly appears that anti-aliasing is the issue. I wonder what is different about our systems that leads to us having this problem when, apparently, most people are not getting this error.In any case, I greatly appreciate your posting because now that the errors are no longer happening I am really enjoying FSX again.

Sayaret,Thanks for the suggestion. I seem to recall reading something about that as well. Unfortunately, I do not use the MS Intellipoint software so that could not be the problem in my case.

Its more like memory issue. Turning AA off may lower number of CTD but soon or later you will get it again. It depends on hardware.I read this thread and i can see many people here reported that after making some changes, other ppl sugested, they got rid of CTD. But later they make another post saying they still get CTD. It looks like memory issue

Finally I have now my fsx very stable even with AA turned on! I can only give you a few hints what I did, without any guarantee...Go to the blog of P. Taylor (http://blogs.msdn.com/ptaylor/default.aspx) and do what he suggest at Stutters on nVidia:- Download and install 'DirectX April 2007 release'; Reboot your PC even if the installation does not require you to do so!- Install the latest video driver for your card. For my GeForce 7800 it's version 94.24, which I got from http://www.guru3d.com/- And finally delete or rename your fsx.cfg file and let fsx generate a new one on startup. This step is really important!Good luck!Next issue for me are the stutters... but there are enough threads already dealing with this...Greg, Switzerland

I have tried all the various fixes for this.I hoped P.Taylors suggestion would fix it but alas no.The only thing which seems 99.9% is no AA which makes FSX look awful.I can't increase resolution above 1280 x1024 on my monitor.Greg are you running your AA within FSX or the Driver app?thanks GH

I have currently AA on in both, the driver settings and fsx configuration.But I just experienced another crash, in the middle of a 4+ hours flight... I just started watching a short video sequence inside my firefox browser, having the fsx in the background, when it crashed...Greg

Thanks for the info.I've just sent another 3 error reports to MS :(