billkhalid577 Posted July 31, 2016 Share Posted July 31, 2016 I have put up with this problem for over two years now and I've decided I can't take it any longer. It is so annoying how I can be moments away from a perfect landing and then seconds before touchdown see a big window right in the middle of the screen awaiting a dreadful message for me. I have tried pretty much everything. I have reinstalled over 17 times, I have updated my video card driver (Intel HD Graphics), I have tried the UIAutomationcore.dll fix,I have got the latest version of Direct X installed, I have followed all of the steps on the Microsoft forums but I still face this problem. I am using an Intel Windows 10 64 bit PC with the latest video card installed This situation has seemed to have gotten worse. Before I could easily do 4-5 hour flights but now FSX will crash seconds after I load up my flight Link to comment Share on other sites More sharing options...
mrzippy Posted July 31, 2016 Share Posted July 31, 2016 So what would be the Faulting Module that's creating all of your havoc? Knowing that will give us a clue as to what's going on. Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area. Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting. BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE! General Tab: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: This is what we need to Know! Exception code: 0xc0000005 Fault offset: 0x0000ee3a Faulting process id: 0x748 Faulting application start time: 0x01ce0253dc4b69d4 Faulting application path: R:\FSX\fsx.exe Faulting module path: R:\FSX\window.dll Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1 If there is not one listed: Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000, you will need to do as previously noted No Faulting Module? -> Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test. Be sure to test each thoroughly before moving on to the next Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
mallcott Posted August 1, 2016 Share Posted August 1, 2016 I have put up with this problem for over two years now and I've decided I can't take it any longer. It is so annoying how I can be moments away from a perfect landing and then seconds before touchdown see a big window right in the middle of the screen awaiting a dreadful message for me. I have tried pretty much everything. I have reinstalled over 17 times, I have updated my video card driver (Intel HD Graphics), I have tried the UIAutomationcore.dll fix,I have got the latest version of Direct X installed, I have followed all of the steps on the Microsoft forums but I still face this problem. I am using an Intel Windows 10 64 bit PC with the latest video card installed If you are truly using an onboard graphics card I am actually amazed it loaded at all. FSX requires a proper dedicated GPU. Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 So what would be the Faulting Module that's creating all of your havoc? Knowing that will give us a clue as to what's going on. Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area. Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting. BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE! General Tab: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: This is what we need to Know! Exception code: 0xc0000005 Fault offset: 0x0000ee3a Faulting process id: 0x748 Faulting application start time: 0x01ce0253dc4b69d4 Faulting application path: R:\FSX\fsx.exe Faulting module path: R:\FSX\window.dll Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1 If there is not one listed: Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000, you will need to do as previously noted No Faulting Module? -> Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test. Be sure to test each thoroughly before moving on to the next The Faulting module is: Faulting application name:fsx.exe,version 10.0.61472.0,time stamp: 0x475e17d3 Faulting module name:FSUIPC4.dll, version: 4.5.3.0, time stamp: 0x4a971937 Exception code:0xc0000005 Fault offset:0x0002bdc4 Faulting process id:0x2498 Faulting application start time:0x01d1e8b1605eebc8 Faulting application path:C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path::C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll Report Id:9f154114-54a5-11e6-aa60-d067e521eb84 Faulting package full name: Faulting package relative ID: Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
mrzippy Posted August 1, 2016 Share Posted August 1, 2016 http://forum.simflight.com/topic/81928-fsuipc4dll-error/ You may want to register on this site and ask the "creator" Pete Dowson about your FSUIPC4.dll error. Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
Luke Posted August 1, 2016 Share Posted August 1, 2016 You'll also want to upgrade to 4.955g - Pete won't support old versions. Cheers! Luke Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 http://forum.simflight.com/topic/81928-fsuipc4dll-error/ You may want to register on this site and ask the "creator" Pete Dowson about your FSUIPC4.dll error. I'm no expert but will uninstalling FSUIPC4.dll sort out the problem? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
mrzippy Posted August 1, 2016 Share Posted August 1, 2016 I'm no expert but will uninstalling FSUIPC4.dll sort out the problem? Sent from my iPhone using Tapatalk Unknown! Try it and see. I would uninstall FSUIPC4 rather than just the .dll Still thinking about a new flightsim only computer! Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 Unknown! Try it and see. Before I do will it affect anything? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 Unknown! Try it and see. I would uninstall FSUIPC4 rather than just the .dll It didn't work Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Captain Vodka Posted August 1, 2016 Share Posted August 1, 2016 I believe its not a good idea to have the fsx instal on the C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator have it installed outside of this location Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 I believe its not a good idea to have the fsx instal on the C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator have it installed outside of this location Already tried that Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
mallcott Posted August 1, 2016 Share Posted August 1, 2016 Told you, your graphic card is not up to the task. Surely you have the option to replace the onboard graphics chip with a suitable dedicated card? Also please show contents of FSX.cfg Link to comment Share on other sites More sharing options...
jorgen.s.andersen Posted August 1, 2016 Share Posted August 1, 2016 "Faulting application path:C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe" Nope. It's still there. Jorgen Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 "Faulting application path:C:\Programme Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe" Nope. It's still there. Jorgen I meant I did but as it didn't solve the problem I put it back in the default location Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Luke Posted August 1, 2016 Share Posted August 1, 2016 Told you, your graphic card is not up to the task. Surely you have the option to replace the onboard graphics chip with a suitable dedicated card? That won't cause a crash, just low frame rates. Cheers! Luke Link to comment Share on other sites More sharing options...
evm Posted August 1, 2016 Share Posted August 1, 2016 What kind of error message and/or event log did you get when FSUIPC was not installed? It couldn't have been the same error, if FSUIPC was not even present. Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 1, 2016 Author Share Posted August 1, 2016 What kind of error message and/or event log did you get when FSUIPC was not installed? It couldn't have been the same error, if FSUIPC was not even present. It had something to do with the uiautomationcore.dll located in Windows/System32 Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
evm Posted August 2, 2016 Share Posted August 2, 2016 It had something to do with the uiautomationcore.dll located in Windows/System32 Sent from my iPhone using Tapatalk That is a very well known issue with FSX. Did you google the solution? AFAIK you have to copy a certain version of the uiautomationcore.dll directly into the simulator directory. Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 2, 2016 Author Share Posted August 2, 2016 That is a very well known issue with FSX. Did you google the solution? AFAIK you have to copy a certain version of the uiautomationcore.dll directly into the simulator directory. Yes I know that and already have a new copy of the uiautomationcore.dll. Can you send me a link for me to try too as I don't know if mine might not be good enough plus I was told it fixes a very specific problem - when FSX crashes after a menu bar option is pressed. But I hadn't pressed a menu bar option and yet FSX crashed. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
evm Posted August 2, 2016 Share Posted August 2, 2016 Yes I know that and already have a new copy of the uiautomationcore.dll. Can you send me a link for me to try too as I don't know if mine might not be good enough plus I was told it fixes a very specific problem - when FSX crashes after a menu bar option is pressed. But I hadn't pressed a menu bar option and yet FSX crashed. Sent from my iPhone using Tapatalk Sorry, I never had that problem myself. It is not uncommon that error messages from different modules hide behind each other so to speak. You will have to go through them one by one and fix them. Eventually you will arrive at the root cause of the crashes. Assuming of course that you aren't simply running out of memory when on final approach, which is very common too - but the error message for that is very specific, so I guess you would know if that was the case. Link to comment Share on other sites More sharing options...
mallcott Posted August 2, 2016 Share Posted August 2, 2016 Sorry, I never had that problem myself. It is not uncommon that error messages from different modules hide behind each other so to speak. You will have to go through them one by one and fix them. Eventually you will arrive at the root cause of the crashes. Assuming of course that you aren't simply running out of memory when on final approach, which is very common too - but the error message for that is very specific, so I guess you would know if that was the case. The UIAutomationcore fix only affects a very specific FSX crash. This isn't it. As evm suggests you need to go through everything, one at a time. Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 2, 2016 Author Share Posted August 2, 2016 Sorry, I never had that problem myself. It is not uncommon that error messages from different modules hide behind each other so to speak. You will have to go through them one by one and fix them. Eventually you will arrive at the root cause of the crashes. Assuming of course that you aren't simply running out of memory when on final approach, which is very common too - but the error message for that is very specific, so I guess you would know if that was the case. I have sometimes ran out of memory however that is very common for me. Do you have any suggestions of what it may be? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
evm Posted August 2, 2016 Share Posted August 2, 2016 You mean the causes for running out of memory? Google "FSX OOM". Basically just "too much". Too many, too complex things in the simulator, too much scenery, too much autogen, scenery complexity, complex gauges, high resolution textures, switching between views, AI traffic, LOD distance too high (the list goes on). It is very easy to make your sim run out of memory. Link to comment Share on other sites More sharing options...
billkhalid577 Posted August 2, 2016 Author Share Posted August 2, 2016 You mean the causes for running out of memory? Google "FSX OOM". Basically just "too much". Too many, too complex things in the simulator, too much scenery, too much autogen, complex gauges, high resolution textures, switching between views, AI traffic, LOD distance too high, autogen to high (the list goes on). It is very easy to make your sim run out of memory. I meant causes of why FSX may be crashing Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.