If I am flying for a while and I click the views and try to change a view, it will crash and lock up. But I am running two monitors on video card and one usb monitor. I put ATC, radio stack, and gps on one monitor, the aircraft panel on one monitor and the cockpit view on the primary monitor. Settings are not all that high as I do a lot of IFR and night flying. That is a lot of stuff and I wonder if I am overloading my memory. I have 2 gigs of ram. I haven't tried it with just one monitor but will try that next time I fly. I don't have any addons except the acceleration pack and FSX. Thanks for any replies.

I have the same setup and my system with 8 gigs of memory will freeze up if I put just the GPS gauge on the secondary monitor especially if I try to move the GPS. That's in Full Screen mode. Don't know the effects in Windowed mode. You only have 2GB's of ram and that's extremely borderline for FSX. On a 32 bit OS, FSX can see up to 3GB's with the /3GB switch but you only have 2GB's so FSX can only use maybe one GB at the most and the OS takes the rest to run Windows. With a 64 bit OS, FSX can see up to 4GB's so it is best to have 6-8 GB's or more installed so that FSX can use the 4GB's and there is memory still left for the OS. Everytime you open up a module like the GPS, the Radio Stack, it takes more memory to make that happen.

 

Best regards,

Jim

Jim, I tried again today and it locked up again. Installed 4 gigs memory and was just running one monitor with one window. Error report files were: cfg.txt dxdiag.txt scenery.cfg fdc.dat dll.xml code 0x0000005 address0x00000000537edd8d Getting very frustrating wasting so much time. Help

Thanks Lewis

Getting very frustrating wasting so much time.

 

Sorry, no solutions. Your error report files mean nothing. Where did they come from? AppCrashView? It would be nice to see the whole error report along with all of the modules that were loaded before the crash occurred. Was there an error reported? Exception Code 0x0000005 means you had a Memory_Access_Violation. Shows up in most CTD's and usually no meaningful information. This means something did not happen when you turned on FSX. FSX was trying to call a texture, a gauge, a sound file, a display driver file, an operating system dll, etc., and it could not find it so FSX crashed. Did you open up cfg.txt and dxdiag.txt and read what was stated in them? The dxdiag.txt file shows DirectX information (problems, etc.). Problems could occur here if your display drivers are not installed correctly. The fdc.dat belongs to FDC Live Cockpit. Maybe you should uninstall it? Of course the scenery.cfg and dll.xml belongs to FSX and they will show no errors so don't know what they came up in any error report. Both files can easily become corrupted though. If there is a problem with the scenery.cfg, you'll see an error about a scenery area when FSX starts up. Do not know where cfg.txt would come from. You can double-click it though and it will open up.

 

Most likely you do not have Microsoft Visual C++ 2005 with SP1 installed. You can tell if you open up the Add/Remove Programs and scroll down to see if it is installed. You can find the package here - http://www.microsoft.com/en-us/download/details.aspx?id=5638. Run Windows Update after installing (if you install the program).

 

You could also be missing Microsoft.net Framework x86 1.1 and version 2. You can check to see if they are installed by opening up Windows Explorer and looking in C:/Windows/Microsoft.net/Framework/the the various versions. You can also go to the following link - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx - and follow the instructions there to verify whether all versions are installed. FSX basic wants to see 1.1 and 2.0. Any addons and it wants to see 3.5 too. Microsoft Visuals and Microsoft.net programs are used by the developers (in your case only Microsoft) to properly install and run your software.

 

I don't know how you are wasting so much time. You are trying to figure out what's wrong with your computer and you are wasting your time? You installed new memory. You got error reports. I know it's frustrating to have FSX crash all of the time. Been there, did that. Just need some patience.

 

Best regards,

Jim

Jim, did what you said, started again and error report in about 15 minutes just doing radio settings etc.

 

How do you copy the error report to post here? Way to long to retype. Thanks

How do you copy the error report to post here? Way to long to retype. Thanks

 

Copy and paste it. Take your cursor and place it at the beginning of the error report. Left click and pull your cursor all the way down to the bottom of the report. It should all be highlighted. Release the left click. While highlighted, right click and select copy. Okay, it has now been placed on your imaginary clipboard. Now come back here and place your cursor on your new post at the beginning. Right click again and select paste. The report should be in your new post.

 

Best regards,

Jim

Jim, tried that , no response. The box on the screen is the error reporting box to open to see error report or send to Microsoft. Should I just uninstall fsx and acceleration and reinstall? I don't use any planes right now except cessna 172 and Mooney Bravo. By wasting time , I mean it is frustrating setting everything up taking off and trying to do a mission and then it locks up and have to start all over. I am not well versed on how to fix problems in software and computers. Appreciate your help and expertise.

Should I just uninstall fsx and acceleration and reinstall?

 

I think that will be the best solution but it's not simple to just uninstall FSX and reinstall it as there are a lot of files left over after the uninstall and you'll probably run into the same problems as before. Here's an excellent guide for uninstalling/reinstalling FSX - http://support.precisionmanuals.com/KB/a87/how-to-uninstall-and-reinstall-fsx.aspx.

 

For some reason I thought you had downloaded and installed AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html. This program interprets the crash report that Microsoft provides whenever your system crashes as it lets the techs know what modules you had running during the operation and it helps to troubleshoot.

 

Best regards,

Jim