August 15, 201213 yr Hi AVSIM gang! So I spent some time putting my comp specs, so please take a look and tell me how the heck I get FSX to run as smoothly as I truly believe it can on the beast that I built. I have Win7 64 bit PRO and when FSX is installed without any add ons except accellerator. It runs beautifully. I tested out a few flights, short, medium and long haul with default aircraft..no problems. Today I added Just Flight F-Lite A320, it loaded without a problem, I do have FSX installed in it's own directory (learned that the hard way) and I input a flight plan, short haul, SFO-LAX. Had a smooth push back, start up, taxi out and got to the end of the runway, switched views a few times back and fourth and on about the 3rd or 4th view switch, I got the fatal error CTD screen of death :(. This computer was just built and by all accounts has nothing else on it except FSX and it was built for this purpose. I read many forms that said win7 gives many problems and you can partition your hard drive and run FSX back on XP which im considering because it just seems that once I add anything to FSX (just flight aircraft are simple add-on's in my opinion) and I just cannot get FSX to remain stable past it's default install. Frustrated to say the least but I recall with 2004 how long it took me to get it just right and that was with a machine 1/3 of the power of the one I just made so I am at a loss to why I can't get this thing to run well. I am not a scenery hog and I am not trying to see the menu at the mcdonalds a TBIT at LAX, so I just want basic but decent scenery, my interests more lie in having beautiful aircraft and excellent airline traffic near me. This is what I envision my simulator to have, REX 2.0, PMDG 747-400 and NGX, just flight A320 and MD-81/82, and Ultimate Traffic 2. I would like to eventually add the 757, 767 and 777 from either wilco, captain sim or just flight. That being said, with the specifics of my system, am I being realistic that I can run those first few items without a lot of drama? I realize there are many variables involved with FSX so I could use some help in getting my beautiful computer in the right direction. I am curious to any AMD 8 core users out there, how are you getting great performance out of this processor? I know intel is the preferred CPU and Nvidea the preferred graphics card but I feel my system is more than adequate to handle FSX but I am open to suggestions. While I don't want to hear using AMD 8 core was a death sentence for FSX, I'll listen to it, just be kind, I dropped close to 1800 bucks on this beast. Sorry to be so long but I know when people post here they can be really vague and you geniuses need as much info as possible to try and help... Can I run FSX with REX, UT2, the PMDG family of products and a couple other aircraft add ons, again, not huge on airport scenery or seeing foxes in the hills of the ozarks, I just want my airplanes and traffic to fly smoothly from major airports to other major airports. I am getting constant crashing once I install an aircraft add on, any suggestions? I read as many posts as I could before posting this but I see that most people are using a system quite different from mine so I thought I should finally put it out here and see what you guys all think. Is Windows 7 the problem for me? Or did I go wrong with my CPU/graphics card which I would be heart broken but it is what it is and I am having issues keeping FSX running for longer than 20 30 minutes once I bring outside items in. Would love to hear what everyone thinks my ideal settings for FSX should be as far as scenery density, mesh, graphics all that. Any help is deeply appreciated! I'll check regularly for replies and answer any specifics I can to see what a solution could be. Thanks everyone!
August 15, 201213 yr Author Also, when it crashes, and I pull down the specifics page, this is what I get. Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional information about the problem: LCID: 1033 Maybe this will help some of you figure out why it's crashing so much for me....Thanks!
August 15, 201213 yr Something is not compatible with your FSX installation. I checked a review of the F-Lite A320 and the reviewer had a crash after installing this aircraft because of an error with the jf_a320.gau - http://www.avsim.com...light/A320.html. He went to Just Flight and they provided him with an update. So, first of all, make sure you have the latest update to this product. Have you checked the Just Flight page for any issues with this aircraft? http://www.justfligh...olution-upgrade I would uninstall the A320 and see if the crashes continue. If not, you have pinpointed the problem. When you install the A320, did you make sure you installed it as the Administrator by right clicking the .exe and selecting 'run as administrator'? Did you disable any running anti-virus program and disable UAC? Sometimes these programs do not like anyone making changes to the system registry and this could mess up the installation and create problems. When you first started FSX after installing the A320, did you trust the gauges and any other requests to trust this product? These are security warnings to warn you of an application or gauge that wants to run on your system. You should trust these all of these items. BEX indicates something is not compatible and most of the time this error occurs when someone installs third party software made from versions prior to FS9. Many FS9 products were made for FS2K2 then updated to work with FS9. If they were not modified further for FSX, there could be an incompatibility. Exception code c0000005 indicates you had a Memory_Access_Violation. This is a common issue when FSX crashes. It basically means FSX was trying to call a module, couldn't find it or it was corrupted and your system crashed. So, the only solution you have now is to investigate this and make sure the A320 is fully compatible and has all the updates. You have to make sure it was installed properly. And you must trust the program to run in your FSX system. FSX is more compatible with nVidia cards in that when FSX was first released, so was Vista. Nvidia was the first video card developer that came up with drivers for Vista and FSX. ATI took several months to come up with compatible drivers and they acted like they just weren't going to support Vista or FSX at all. It was all mind-boogling to me as I had an ATI card for XP and I really thought they were great. So FSX developers worked with the Nvidia techs to come up with the best drivers for their product. Today, ATI has great cards and great drivers and they should be able to run FSX just as well as nvidia. You have an excellent system and you should be able to run FSX very well. You should not think though that you can turn your FSX settings and display driver settings up to the max and not have issues. Sure, it will work okay for a few flights but eventually you will have a crash. Hope this helps! Best regards, Jim
August 15, 201213 yr Author Hi Jim, Thank you for taking the time to write me back! I do appreciate it. So I completely uninstalled A320 jetliner, went to just flight and saw they have some updates for the product. Before I did that though I decided to test the sim again to see if uninstalling the add on helped FSX run without crashing and now unfortunately it's crashing within minutes of it being on. I am still receiving the same crash event posted below: Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: unknown Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 00000000 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional information about the problem: LCID: 1033 I am the full administrator on the computer and when I ran the install for FSX I did with full permissions and all of that. Originally when I installed FSX I had a bunch of problems since I assumed it would run well, I went ahead and installed a few programs and then realized I had some issues so I did a full and complete uninstall of FSX, cleaned everything out and started over. That seemed to help let it run a few days without a problem. Now currently I have the settings pretty high and will adjust them but what would you think is the appropriate frame rate setting for what I have? I just find this mind boggling lol, to say the least. Should I consider installing XP on half of my hard drive (I've got ample room for both) and put FSX on that and try it out? I just cannot get it remain stable with or without add ons. Still not sure what I am doing so wrong and do forgive me I am not computer programer or coder so I do not mess with files or configurations of files, I am happy to just have it run smoothly with a few add ons. Being a real world pilot for the A320, seeing it glitch along would make me insane hehe :) How can I investigate the memory access violation now that A320 has been removed, again forgive me, what exactly is that telling me? Also, kind of a crazy question too...I still have FS 2004 and all of the great add ons, would they even work on this thing? I'd be willing to kiss FSX goodbye since when I was a 2004 junkie, I had a beautifully running thing and it almost NEVER crashed on me and I don't care if the jetbridge pulls up or not, I can pretend, after all it is a game :-D. Thanks again for your time, I really appreciate your help! Jeremy Uiautomationcore.dll installed in your FSX folder? I did a search in FSX folder for that file name and nothing came up, what is that file?
August 15, 201213 yr what would you think is the appropriate frame rate setting for what I have? I would say 30 fps if you want to limit frames. I have mine set to unlimited. No need to install XP because you can right click fsx.exe or the desktop Icon and select properties, then select the Compatibility Tab. On there you can select compatibility with XP or any previous OS but that won't really solve your problem. Your problem now appears related to memory. You need to get that fixed before you reinstall the A320. Do you have the ENB Series module installed. That has had a lot of compatibility problems with Windows 7, especially the 64 bit version. My next suggestion for investigating your problem is to rename your FSX.cfg to fsx.orig, restart FSX and let the config rebuild. Don't touch any of the scenery, AI, weather, or aircraft settings. See if you can reproduce the problem. If not, then it's most likely caused by your fsx settings being too high. If you still get the error, then it has to be system related (FSX is an intense program that can bring many computers down). You can go back and rename your fsx.orig back to fsx.cfg and you'll have your original settings. Again, the memory_access_violation occurred when FSX was trying to call a module, let's say a gauge, or a texture but there was a glitch as it couldn't find the module or texture where it is suppose to be located or it's corrupt or it's not compatible. Here's a better explanation - http://www.updatexp.com/0xC0000005.html. It's for XP but it's for Windows 7 too. Who overclocked your system? A lot of memory access violations are caused by wrong frequency, timings, and voltage settings in the BIOS. You can also get crashes if your CPU voltage is too high or too low based on your overclock. To test all of this, you can return your BIOS settings back to the default and see if this fixes the problem. If it does, then it has to be a wrong memory or CPU voltage setting. Memory frequency, timing, and voltages should be the same as one of the listed settings shown in the freeware CPU-Z under the SPD tab. That's what your memory can handle. Some individuals here have fixed memory access violations by simply changing the virtual memory (page file) settings. I have found that 'System Managed Size' is the best setting for FSX. To get to this program, click on the Start button and type Virtual Memory in the search bar then look up in the Menu and click on How to change Virtual Memory settings. The default for Windows 7 systems is the top option or "automatically manage page file settings for all drives". That one is not good. Click on the drive FSX is on and select System Managed Size. Of course, overheating will cause crashes like this too. Lastly, you need to check your Event Viewer. That can be found by clicking on the Start button and typing Event Viewer in the search bar then looking up in the Menu and clicking on Event Viewer. Once open, select Applications then, over in the search bar on the right, type in FSX and it will show you all the errors for FSX. An 'event' is recorded for every FSX crash. You want the latest one. On the right column you will see Copy and then copy as text. You want to copy as text then paste it into your post here. The uiautomationcore.dll referred to by Rendi is part of one of the Microsoft.net framework packages. It's a system .dll and located in C:\Windows\Microsoft.net\Framework. Some people have been successful fixing their system by downloading the Vista version of the dll and dropping it into the main FSX directory. When you installed FSX/Acceleration, you installed the first ever Microsoft.net packages - Version 1. This was for Vista. But since then, the latest version is 4 and that's automatically installed with Windows 7. So you need to search on Google for uiautomationcore.dll for vista and download it and put it in your main fsx folder. Microsoft.net is used by Microsoft to run FSX and it also has a function to manage the memory. Again, the likelihood of it working for your issue is remote but no harm, no file if you try. Hope this helps, Best regards, Jim
August 20, 201213 yr Author Hi Jim, Thanks again for your reply. I was on a trip and didn't have a chance to play my sim :). I tried to locate the fsx.cfg file but couldn't find anything named that, I did find fsx.scenery.cfg , fsx.aircraft.cfg and fsx.elumans (I'm not sure of the correct spelling) etc. I dpn't want to change the incorrect thing and create even more problems for myself. So the last time I did get a chance to play the game, it crashed and it gave me this reason below: Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: uiautomationcore.dll Fault Module Version: 7.0.0.0 Fault Module Timestamp: 4a5bdb1d Exception Code: c0000005 Exception Offset: 0000e52a OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional information about the problem: LCID: 1033 I see that it stated the uia file was the cause. That's the first time I have had it tell me that was the cause. I have a feeling this is a memory based problem seeing as how when I change views that is when it crashes and from memory I believe FS is using memory to refresh the views. I researched my memory sticks and they do not appear to be the ENB series you mentioned. The brand is listed below: G.SKILL Ripjaws Z Series 16GB (4 x 4GB) 240-Pin DDR3 SDRAM DDR3 2133 (PC3 17000) Desktop Memory Model F3-17000CL11Q-16GBZL My brother physically built the computer and set up the CPU in the BIOS. That's an area I know little about, so I am not sure what I would be looking for as far as proper timing and frequencies but I can always research it :), gotta love google. I will try to get another event to happen so I can post it here and see if there are consistencies with the crashes. Thanks again for your time, you have already been a major help! Have a great weekend! Jeremy Hi Jim, I went back and did an event view..here was what the last crash event stated: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61637.0 P3: 46fadb14 P4: uiautomationcore.dll P5: 7.0.0.0 P6: 4a5bdb1d P7: c0000005 P8: 0000e52a P9: P10: Attached files: C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dll.xml These files may be available here: C:\Users\Jeremy\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_9960c49efe74893b7b87c489bef439761cdb932_096800dc Analysis symbol: Rechecking for solution: 0 Report Id: ea1f88bd-e74d-11e1-904d-c86000c051b6 Report Status: 0 And the one before that one was this: Fault bucket , type 0 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61637.0 P3: 46fadb14 P4: unknown P5: 0.0.0.0 P6: 00000000 P7: 00000000 P8: c0000005 P9: 00000008 P10: Attached files: C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dll.xml These files may be available here: C:\Users\Jeremy\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_ea9ff82bb13cb93b6d0aa572a7088cf4d63aeaa_05fa3e28 Analysis symbol: Rechecking for solution: 0 Report Id: 2f4f4047-e6b1-11e1-98fb-c86000c051b6 Report Status: 0
August 20, 201213 yr Author So I had a chance to run it again, just basic stuff, not even a flight plan and got this crash: Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: uiautomationcore.dll Fault Module Version: 7.0.0.0 Fault Module Timestamp: 4a5bdb1d Exception Code: c0000005 Exception Offset: 0000e52a OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 1033 Additional information about the problem: LCID: 1033 this is what the event viewer stated: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61637.0 P3: 46fadb14 P4: uiautomationcore.dll P5: 7.0.0.0 P6: 4a5bdb1d P7: c0000005 P8: 0000e52a P9: P10: Attached files: C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dll.xml These files may be available here: C:\Users\Jeremy\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_9960c49efe74893b7b87c489bef439761cdb932_02809d1b Analysis symbol: Rechecking for solution: 0 Report Id: 6123dd65-ea7d-11e1-96e9-c86000c051b6 Report Status: 0
August 20, 201213 yr So I had a chance to run it again, just basic stuff, not even a flight plan and got this crash: This app crash indicates you had a crash with uiautomationcore.dll as the cause. Some people have had success in fixing this error by downloading the Vista version of this dll and dropping it in your FSX main directory. Based on a Google search, I have not seen much success in this 'fix'. But, if you're interesting in trying, here's the link regarding this 'sometimes it works' fix: http://forum.avsim.net/topic/273341-heres-the-apparent-fix-to-fsx-crashing-win-7-x64/. I tried to locate the fsx.cfg file but couldn't find anything named that, I did find fsx.scenery.cfg , fsx.aircraft.cfg and fsx.elumans (I'm not sure of the correct spelling) etc. I dpn't want to change the incorrect thing and create even more problems for myself. Jeremy, if you look in the previous post you sent above and look in the error report, you'll see the exact location of the FSX.cfg - C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fsx.CFG. If you cannot find this directory (it's hidden), you have to use the following procedure to see the directory and the files: Go to the Start menu and click on Windows Explorer (if you have the Computer Icon on your desktop, just double-click that to open up Windows Explorer. Once open, look at the Menu options at the top and click on Tools, then Folder Options. Once Folder Options is open click on the View tab then look down at the Advanced settings. Under Files and Folders, click on Hidden files and folders and click on 'Show hidden files, folders, or drives'. Click Apply. Now look in the left column of Internet Explorer and click on C:\ then look down for the Users directory. Now you can go to the directory where FSX.cfg is located. Deleting or renaming the FSX.cfg fixes most crashes and is the preferred method other than uninstalling FSX and reinstalling it. Deleting the FSX.cfg and restarting FSX will rebuild the config back to where it was when you first installed FSX. Make sure, when asked immediately upon restarting FSX that you trust a module or gauge, or whatever message pops up. I still think your issue is with the A320 and I think the A320 install program installed a bad version of Microsoft Visual C++ Redistributable 2005. FSX and FSX addons will install Microsoft Visual C++ 2005 if it does not find the version on your computer. Microsoft Visuals are used by developers of FSX and FSX addons to properly install their product on your computer. There was a SP1 to the Microsoft Visual 2005 which a lot of developers never had when FSX or their product was first released. Here is the link to that update - http://www.microsoft.com/en-us/download/details.aspx?id=5638. Hope this helps. Best regards, Jim
August 28, 201213 yr Author Hi Jim, So I was able to remane the fsx.cfg file to fsx.orig. Unfortunately the system still crashes after about 45 minutes of flying. I have the A320 completely uninstalled and I am just trying to run basic flight sim flights without any add ons. The latest event said the crash was due to the follow: Fault bucket , type 0 Event Name: BEX Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61637.0 P3: 46fadb14 P4: unknown P5: 0.0.0.0 P6: 00000000 P7: 00000000 P8: c0000005 P9: 00000008 P10: Attached files: C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Jeremy\AppData\Roaming\Microsoft\FSX\dll.xml These files may be available here: C:\Users\Jeremy\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_ea9ff82bb13cb93b6d0aa572a7088cf4d63aeaa_0a596426 Analysis symbol: Rechecking for solution: 0 Report Id: 7e5fbe5c-e696-11e1-9873-c86000c051b6 Report Status: 0 Still not sure what is going on, I continue to be appreciative of all your help. I have some great add ons waiting to be used but I wont install anything until the system is stable. I'm not sure what other direction to take, I still just have a hard time believing FSX can't be run on this machine. I just can't figure out why it's crashing so much. I can check the bios for the clocking and memory but I wouldn't know what I am looking for to be the correct settings. Anyway, thanks again for any help you can provide. Jeremy
August 29, 201213 yr Hi Jeremy, Sorry to hear you're still having issues. The above error report gives me no clues as to what happened but I see in post #7 above you had the same error. My recommendation now is to go to the following website - http://www.nirsoft.net - and download this neat little program called AppCrashView (it's free). It will provide you more details of every FSX crash. Did you try the uiautomationcore.dll fix I suggested in the previous post? That's the faulting module I have seen in a couple of your error reports. It doesn't hurt trying at least as it has worked for some. The link I provided above has the link to download the correct version and how to install it. I think the solution to your problem is in post #6 above. I have seen a lot of crash reports and it turns out the memory settings in the bios were incorrect. A few times it's because the voltage for the CPU is too high or too low. Anything above 1.5 voltage for the CPU may cause problems. I had major issues with my system memory when I first built my system and put my memory settings in the bios on Auto. Worked great for a long time then FSX put more stress on the system and it crashed. Turned out ASUS motherboard makers just don't know how to properly configure memory in the BIOS so the auto setting was causing the problem. My system had passed several stress tests and never showed a problem until FSX brought the system down. I'm running out of ideas or suggestions. Just hope one of the one's above will work. Best regards, Jim
Create an account or sign in to comment