Jump to content

Archived

This topic is now archived and is closed to further replies.

WebMaximus

FSX has stopped working, Faulting module name: Unknown

Recommended Posts

Guess I should consider myself quite lucky because I haven't had many problems lately with FSX but from time to time I still get CTDs, FSX just freezes and I'm presented with a dialog box telling me Microsoft Flight Simulator X has stopped working and all I can do when this happens is to confirm the message and at that time I'm thrown back to the desktop.

 

Looking in the Application log in Windows this is what it says

Faulting application name: fsx.exe, version: 10.0.61472.0, 
time stamp: 0x475e17d3
Faulting module name: unknown, version: 0.0.0.0, time stamp: 
0x00000000
Exception code: 0xc0000005
Fault offset: 0x04246c81
Faulting process id: 0xf0
Faulting application start time: 
0x01ce49c9169d6909
Faulting application path: F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: unknown
Report Id: a65f06b1-b5bc-11e2-9c4b-e954a1240769

Very annoying to say the least and since the faulting module is unknown I don't really know what to look for or how to troubleshoot what it is actually causing these CTDs and would really appreciate some help.

Share this post


Link to post
Share on other sites

Hi. Today my FSX stopped working too,  and im not sure if this is related to the FSUIPC issue issue or not. Cant help you much but personally i had to remove FSX and re install i know its a pain but for me i guess this was the solution after trying other options and this was all before knowing about the FSUIPC issue, Try to reinstall the FSUIPC new version and see what happens.

Share this post


Link to post
Share on other sites

If you are using Sweetfx or ENb series....remove their dll's and try again...had a similar problem with an unknown module crashing my FSX at startup. reinstalling their respective dll's and default settings kept my fsx from crashing again.

Share this post


Link to post
Share on other sites

Hi. Today my FSX stopped working too,  and im not sure if this is related to the FSUIPC issue issue or not. Cant help you much but personally i had to remove FSX and re install i know its a pain but for me i guess this was the solution after trying other options and this was all before knowing about the FSUIPC issue, Try to reinstall the FSUIPC new version and see what happens.

 

Thanks for your input but I've had this problem with random CTDs caused by this "Unknown module" way back before the current FSUIPC issue arised and as for reinstalling FSX as you say that sure is a pain to say the least. If I thought that would cure my problems I might considered going for it but I've already installed a fresh FSX a couple of times the last few years and I've had this (or similar) CTD problems in all those installations.

 

What I was hoping for was to find some way to troubleshoot what is actually causing these CTDs. Would have been great to have some kind of logging or debug tool to trace what is going on "behind the scenes" when this happens and what is actually the culprit.

 

If you are using Sweetfx or ENb series....remove their dll's and try again...had a similar problem with an unknown module crashing my FSX at startup. reinstalling their respective dll's and default settings kept my fsx from crashing again.

 

I am using Sweetfx and I used to use ENB but since ENB would cause lots of problems I was happy when SweetFX came around. But again as said in my previous reply to Toufic I've had these random CTDs long before using both SweetFX and ENB so I honestly don't think they are to blame...at least not in my case but who knows...maybe it could be worth trying some flying without using any of them just to see what happens.

 

Guess I'm not the only one in here wishing we one day will have a new and more stable FS that would not only solve all these kind of weird stability problems but would also make better use or today's hardware and would let all addon developers develop addons not limited by the old and inner workings of FSX.

Share this post


Link to post
Share on other sites

Agreed, FSX is a chore when unstable, but when all the bugs are ironed out, it is very enjoyable. Luckily ive had zero crashes since reinstalling Sweetfx.  Is it always at one location when you CTD or at random? Day/Night? With UTX/GEX?  Also do you ctd every time you use FSX?  

Share this post


Link to post
Share on other sites

Agreed, FSX is a chore when unstable, but when all the bugs are ironed out, it is very enjoyable. Luckily ive had zero crashes since reinstalling Sweetfx.  Is it always at one location when you CTD or at random? Day/Night? With UTX/GEX?  Also do you ctd every time you use FSX?  

 

I fully agree, when all is working FSX sure is a true joy and looking at all great addons we have today both a/c like the NGX I fly but also all other different kinds of great addons like FS2Crew, GTX, Aivlasoft EFB, OpusFSX just to mention a few it's almost like you were in the actual a/c for real. I really love this hobby!

 

Regarding my CTDs they are luckily quite rare, maybe every 10'th flight or so and totally random. Doesn't matter what time of day it is, location or situation. To find out what addons I'm using just click my 'My simulator' link which is up to date and same goes for my 'My PC' link.

Share this post


Link to post
Share on other sites

Exception c0000005 (however many zeroes....) I remember from way back always meant either FSX had run out of RAM, or it had gone on a seek mission on the hard drive for a file/texture/whatever and not found it in time to remain happy.

 

Defragging can sometimes help if the latter, or shutdown/restart to clear out the caches on the hard drive.

 

Share this post


Link to post
Share on other sites

OK, so I decided to try flying for a while without SweetFX but boy FSX became ugly and milky looking without SweetFX when you're used to it!

 

To fix this I thought I would try adjusting my TV (a Samsung 40 inch LED TV) a bit to see if I could come up with a way to compensate for what SweetFX normally does and I'm more than happy to tell you I found two settings on my TV that together looked so good I don't think I will ever need SweetFX nor any other similar utility again :D For anyone with a similar TV (or maybe these settings exist on most TVs today) the settings I changed were

 

Dynamic Contrast from Medium to High

HDMI Blackness from Normal to Low

 

Now I'm very excited both to try flying without SweetFX keeping my fingers crossed this will result in no or at least fewer CTDs but equally much I'm looking forward to do some flying with this great new look in FSX I got by modifying the settings mentioned above!!

Share this post


Link to post
Share on other sites

Exception c0000005 (however many zeroes....) I remember from way back always meant either FSX had run out of RAM, or it had gone on a seek mission on the hard drive for a file/texture/whatever and not found it in time to remain happy.

 

Defragging can sometimes help if the latter, or shutdown/restart to clear out the caches on the hard drive.

 

Ok, thanks for the info. Is there any way I can check if one of the things you mention indeed was the reason for the CTD?

 

I always try to keep my FSX installation very clean so I would like to think all files, textures or whatever should be in place. As for the memory, exactly what memory is it FSX might run out of? I have 8 GB RAM and I'm running 64 bit Win7 and I have a GTX 680 with 2 GB dedicated video memory if my own memory serves :wink: I don't run any highly intense memory consumers like 4096 textures and so on but keep all textures including the cloud textures at the FSX default size of 1024.

 

As for fragmentation problems that shouldn't be an issue since I'm running FSX on it's own dedicated SSD disk.

Share this post


Link to post
Share on other sites

Run Procmon  http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx  while running FSX, when and if you crash it will show if FSX is crashing because of a faulty texture, FX file etc....

 

When you first run procmon you will need to specify to look for FSX only....

 

In the filter screen  http://imageshack.us/photo/my-images/442/result2gq0.jpg/?sa=0

 

select Process name, is, type fsx.exe, include..... Apply then OK

 

Start FSX, and if you have a crash it will show what faulted.

 

Has helped to find buggy files in FSX

Share this post


Link to post
Share on other sites

That's the thing to be clear on: you can have 32GB of system RAM, an 8GB VRAM video card..... but, because FSX is 32-bit, it will only ever see 4GB RAM total.

 

It's good to have the RAM and 64-bit and all to keep that 4GB as clear of the rest of Windows as possible, but it won't increase the amount of Virtual Address Space (4GB) that FSX "sees."

 

The HD thing is mainly a bit shot in the dark; I just defrag frequently, and restart my PC if things start to get wonky (which, fortunately, hasn't been often on my new machine, yay).

 

There are occasions where nothing but full reinstall of both Windows and FSX will do, but I don't think you're there yet.

 

Also make sure you have Simconnect installed (it's the MS equivalent of FSUIPC, inter process communications for add-ons may rely on it), and if you do, doesn't hurt to go to Control Panel and issue a Repair every now and then.

 

Finally, more tricky and mysterious, make sure you have a good install of .NET Framework 3.5SP1 installed, and before going to full reinstall of everything, Google .NET Framework Repair Tool and make sure your 3.5SP1 install is okay; sometimes it, like Simconnect, can get corrupted, and thus also cause mysteries. :)

 

Hey, it's easier than learning to program an FMC!

Steve

Share this post


Link to post
Share on other sites

Thanks guys for all valuable input, will try what has been suggested and keep you posted.

Share this post


Link to post
Share on other sites

Maybe try renaming your fsx.cfg file and build a new one? Some people swear by this since overtweaking on a high end systems places much to much strain on and old operating platform.

You could try just using a few very basic tweaks like highmemfix etc and run it like this for several days

Share this post


Link to post
Share on other sites

 

 



Maybe try renaming your fsx.cfg file and build a new one? Some people swear by this since overtweaking on a high end systems places much to much strain on and old operating platform.
You could try just using a few very basic tweaks like highmemfix etc and run it like this for several days


Thanks Zoran, that's always a good suggestion but in my case I don't think that would help. I don't have that many tweaks in my fsx.cfg, only the ones suggested by Word Not Allowed's FSX guide and I would say these are all pretty good and well proven tweaks. Part from this I've had these kind of CTDs caused by the mysterious unknown module also long before Word Not Allowed's guide was written and without using those tweaks.

For now I think my first step will be to use Process Monitor suggested above. That is actually a really great tip and can't understand why I didn't think of it myself since I already had that utility on my disk. Will be very interesting to see what that gives!

To be honest I would almost even more like to find a way to track down exactly what is happening "behind the scenes" when you get these type of CTDs rather than simply getting rid of the CTDs by doing some changes because then I will still not know what was actually causing them and I do want to find that out once and for all and I'll do my very very best this time to track it down.

So...if your name is 'Unknown module'...watch out :wink: !!

Share this post


Link to post
Share on other sites

 

 


Also make sure you have Simconnect installed (it's the MS equivalent of FSUIPC, inter process communications for add-ons may rely on it), and if you do, doesn't hurt to go to Control Panel and issue a Repair every now and then.Finally, more tricky and mysterious, make sure you have a good install of .NET Framework 3.5SP1 installed, and before going to full reinstall of everything, Google .NET Framework Repair Tool and make sure your 3.5SP1 install is okay


I do have SimConnect installed since I have both XPax and Aivlasoft EFB running on a second computer connecting to my FSX computer via SimConnect, at least I think so if my memory serves. When you suggest I should go to the Control Panel and issue a repair every now and then exactly what repair process are you referring to then?

Then regarding .NET 3.5 SP1 that's interesting because when I checked my installed programs I actaully didn't have that one at all but only .NET Framwork 4 Client Profile. What is it that would be using .NET 3.5 SP1 and would I still need that when I have .NET Framwork 4 Client Profile installed? And if something actually needs .NET 3.5 SP1 specifically I don't understand why I couldn't find it in the list of installed programs since normally all those kind of "extras" get installed automatically by the program relying on them...?

 

Edited to add I now did find .NET 3.5.1 on my system, was found under 'Turn Windows features on and off' rather than in the list of installed programs. However I haven't been able to find any SP1 for .NET 3.5 (or maybe 3.5.1 already indicate SP1 is included...?) Will have to do some reading about this I guess.

Share this post


Link to post
Share on other sites

 

 


Then regarding .NET 3.5 SP1 that's interesting because when I checked my installed programs I actaully didn't have that one at all but only .NET Framwork 4 Client Profile. What is it that would be using .NET 3.5 SP1 and would I still need that when I have .NET Framwork 4 Client Profile installed? And if something actually needs .NET 3.5 SP1 specifically I don't understand why I couldn't find it in the list of installed programs since normally all those kind of "extras" get installed automatically by the program relying on them...?

 

Dotnet is not backwards compatible and FSX requires versions 1.1 thru 4.5 installed (the proper version is installed with the product if not found).  You can check to see what versions you have installed by going to your Windows folder\Microsoft.net\Framework (x86)\the various versions.  To check to see if the versions are installed properly, use this tool - http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx (as suggested by PaulJ here at AVSIM).

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks Jim for the input and the link to the verification tool. Just downloaded and tried it and both .NET 3.5 SP1 and .NET 4 Client was verified successfully so all seems good :smile:

 

Just completed my first flight without SweetFX and all went fine so I will continue flying and keep my fingers crossed!

Share this post


Link to post
Share on other sites

Completed several flights now without any CTDs and even if it might be too soon to say for sure maybe SweetFX was the culprit after all since that is the only thing I removed from my FSX setup.

 

I also tried the Process Monitor utility but since I found it to be incompatible with OpusFSX (which crashed whenever Process Monitor was running) I couldn't use it since I don't want to fly without Opus. I also asked about this in the Opus forum and received an answer it appears Process Monitor is incompatible with any applications using .NET.

 

Will continue keeping my fingers crossed and do more flying...

Share this post


Link to post
Share on other sites

 

 


also asked about this in the Opus forum and received an answer it appears Process Monitor is incompatible with any applications using .NET.

 

Hi Richard,

 

Dotnet is essential for any application/game to function properly - http://en.wikipedia.org/wiki/.NET_Framework.  It even manages memory for the products and any addons such as Opus.  I have used Process Monitor frequently just out of curiosity to see what processes occur when fsx first loads, after loading, during a flight, etc.  Never a crash.   I have heard of some security updates to dotnet have crashed systems but never applications.  Microsoft immediately issues a fix when this happens.  Dotnet is kept up-to-date via Windows Update but, according to NickN, they sometimes make the update an option and it is not always updated unless you go into Windows Update, click on the Options tab and select installing the update.  I have seen this too on occasion but not all of the time.

 

The error report you furnished in OP doesn't really say much.  You should download and run AppCrashView - http://www.nirsoft.net/utils/app_crash_view.html and copy and paste the results of the latest crash here.  This neat little utility interprets the Microsoft crash reports and provides more information about the crash(es). 

 

If you are periodically having crashes, it is most likely a high FSX setting.  It could be a bad tweak too.  No crash report will tell you exactly what caused a crash and that's why we need to investigate each one.  Your crash report in OP is a common one indicating you had a memory_access_violation at an "unknown" module.  This tells me your settings are set too high but it could be something else.  That's why I say we need to investigate.  Wish there was a magic bullet to fix them all.  You just have to remember - when you first installed FSX and ran it for the first time, it started up fast and no problems.  Then you installed SP2 or Acceleration and ran it and still no problem.  FSX started up fast and loaded really fast.  Then, you started installing addons and began to tweak your fsx.cfg and display drivers.  Things started to go downhill after that. 

 

I don't own OPUS and like AS2012 instead but I had major problems with AS2012 when I first installed it.  It was freezing or crashing my computer in mid-flight and I traced it to a bad install of SimConnect (it needs that to update the weather and communicate with FSX).  I reinstalled SimConnect several times and finally no more crashes.  FS Developers.com has a good guide on installing SimConnect and the FSX SDK. 

 

I also had problems with AS2012 when I set my graphics options to 4096 textures and also set my texture_max_load setting to 4096 and LOD_Radius to 6.5 (and higher!).  My system just could not handle that.  So I reduced the textures in AS2012 to 1024 and that fixed that problem.  I let my fsx.cfg handle the resolutions.

 

I see you just have SP2 installed.  Some individuals in the CTD Forum have resolved their problem(s) by uninstalling SP2 and then reinstalling it.  (Click on the SP2.exe and then select uninstall).  Run FSX once after uninstalling then reinstall.

 

Hope this helps.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Many thanks Jim for trying to help but as said in my last post I've done several flights now without any more CTDs and everything is working really smooth and fine so if I'm lucky I might already have gotten rid of what was causing the CTDs in removing SweetFX. But then again I never had constant CTDs but only one here and one there on very few and random occations so I'm not 100% sure until I've done even more flying.

 

What you say is of course true, FSX out of the box with no tweaks nor any addons seldom not to say never causes any problems but then again...what makes FSX what it is today is all great addons and without them FSX wouldn't honestly get much of my attention.

 

Although I have several addons installed I always try to keep my FSX setup (and my Windows installation for that matter) very tidy. Same thing goes for tweaks I'm using...only running a few of them and they are all well documented fsx.cfg tweaks and they are all well tested by the community.

 

Looking at my settings in FSX I do have all sliders to the far right with the exception of Water effects which I have at Low 2.x and Autogen Density which I have at Normal. Also I have Ground scenery shadows, Aircraft casts shadows on itself and Aircraft casts shadows on the ground unchecked and lastly I have all traffic set at 0% since I do all my flying online. This also goes for cars and boats since I only fly to payware addon airports which mostly have their own animated traffic which I don' want to mix up with default FSX traffic. Might also add that I haven't changed any of the default settings in fsx.cfg when it comes to max texture size, cloud density etc...all those settings are at default and I'm only running 1024 textures.

 

To find out what my FSX setup looks like in detail both when it comes to hardware and FSX addons please see the My PC and My Simulator links. I would like to think my hardware should be able to handle the settings I'm using in FSX but if there is something you find questionable in this regard please let me know.

 

For what it's worth below is what my last CTD looks like in AppCrashView.

Version=1EventType=AppHangB1EventTime=130124892180520862ReportType=3Consent=1UploadTime=130124892200882027ReportIdentifier=a4756a63-b7d9-11e2-be17-820aaafe2015IntegratorReportIdentifier=a4756a64-b7d9-11e2-be17-820aaafe2015WOW64=1Response.type=4Sig[0].Name=Application 
NameSig[0].Value=fsx.exeSig[1].Name=Application 
VersionSig[1].Value=10.0.61472.0Sig[2].Name=Application 
TimestampSig[2].Value=475e17d3Sig[3].Name=Hang 
SignatureSig[3].Value=b9e7Sig[4].Name=Hang 
TypeSig[4].Value=0DynamicSig[1].Name=OS 
VersionDynamicSig[1].Value=6.1.7601.2.1.0.256.1DynamicSig[2].Name=Locale 
IDDynamicSig[2].Value=1053DynamicSig[22].Name=Additional Hang Signature 
1DynamicSig[22].Value=b9e7f481b9c32c8c08c124be4ec8168dDynamicSig[23].Name=Additional 
Hang Signature 2DynamicSig[23].Value=bdb9DynamicSig[24].Name=Additional 
Hang Signature 
3DynamicSig[24].Value=bdb9a2ec7def70101abfb3bb2ed15900DynamicSig[25].Name=Additional 
Hang Signature 4DynamicSig[25].Value=b9e7DynamicSig[26].Name=Additional 
Hang Signature 
5DynamicSig[26].Value=b9e7f481b9c32c8c08c124be4ec8168dDynamicSig[27].Name=Additional 
Hang Signature 6DynamicSig[27].Value=bdb9DynamicSig[28].Name=Additional 
Hang Signature 
7DynamicSig[28].Value=bdb9a2ec7def70101abfb3bb2ed15900UI[3]=Microsoft 
Flight Simulator® is not respondingUI[4]=If you close the program, you might 
lose information.UI[5]=Close the programUI[6]=Close the 
programUI[7]=Close the programLoadedModule[0]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\fsx.exeLoadedModule[1]=C:\Windows\SysWOW64\ntdll.dllLoadedModule[2]=C:\Program 
Files\AVAST 
Software\Avast\snxhk.dllLoadedModule[3]=C:\Windows\syswow64\KERNEL32.dllLoadedModule[4]=C:\Windows\syswow64\KERNELBASE.dllLoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLLLoadedModule[6]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dllLoadedModule[7]=C:\Windows\syswow64\msvcrt.dllLoadedModule[8]=C:\Windows\syswow64\GDI32.dllLoadedModule[9]=C:\Windows\syswow64\USER32.dllLoadedModule[10]=C:\Windows\syswow64\ADVAPI32.dllLoadedModule[11]=C:\Windows\SysWOW64\sechost.dllLoadedModule[12]=C:\Windows\syswow64\RPCRT4.dllLoadedModule[13]=C:\Windows\syswow64\SspiCli.dllLoadedModule[14]=C:\Windows\syswow64\CRYPTBASE.dllLoadedModule[15]=C:\Windows\syswow64\LPK.dllLoadedModule[16]=C:\Windows\syswow64\USP10.dllLoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dllLoadedModule[18]=C:\Windows\syswow64\ole32.dllLoadedModule[19]=C:\Windows\system32\apphelp.dllLoadedModule[20]=C:\Windows\AppPatch\AcGenral.DLLLoadedModule[21]=C:\Windows\system32\UxTheme.dllLoadedModule[22]=C:\Windows\system32\WINMM.dllLoadedModule[23]=C:\Windows\system32\samcli.dllLoadedModule[24]=C:\Windows\syswow64\OLEAUT32.dllLoadedModule[25]=C:\Windows\system32\MSACM32.dllLoadedModule[26]=C:\Windows\system32\VERSION.dllLoadedModule[27]=C:\Windows\syswow64\SHELL32.dllLoadedModule[28]=C:\Windows\system32\sfc.dllLoadedModule[29]=C:\Windows\system32\sfc_os.DLLLoadedModule[30]=C:\Windows\system32\USERENV.dllLoadedModule[31]=C:\Windows\system32\profapi.dllLoadedModule[32]=C:\Windows\system32\dwmapi.dllLoadedModule[33]=C:\Windows\syswow64\SETUPAPI.dllLoadedModule[34]=C:\Windows\syswow64\CFGMGR32.dllLoadedModule[35]=C:\Windows\syswow64\DEVOBJ.dllLoadedModule[36]=C:\Windows\syswow64\urlmon.dllLoadedModule[37]=C:\Windows\syswow64\iertutil.dllLoadedModule[38]=C:\Windows\syswow64\WININET.dllLoadedModule[39]=C:\Windows\syswow64\Normaliz.dllLoadedModule[40]=C:\Windows\system32\MPR.dllLoadedModule[41]=C:\Windows\AppPatch\AcLayers.DLLLoadedModule[42]=C:\Windows\system32\WINSPOOL.DRVLoadedModule[43]=C:\Windows\AppPatch\AcSpecfc.DLLLoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dllLoadedModule[45]=C:\Windows\system32\mscms.dllLoadedModule[46]=C:\Windows\system32\DDRAW.dllLoadedModule[47]=C:\Windows\system32\DCIMAN32.dllLoadedModule[48]=C:\Windows\syswow64\COMDLG32.dllLoadedModule[49]=C:\Windows\syswow64\IMM32.dllLoadedModule[50]=C:\Windows\syswow64\MSCTF.dllLoadedModule[51]=C:\Windows\syswow64\WS2_32.dllLoadedModule[52]=C:\Windows\syswow64\NSI.dllLoadedModule[53]=C:\Windows\system32\msi.dllLoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLLLoadedModule[55]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\language.dllLoadedModule[56]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\API.DLLLoadedModule[57]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dllLoadedModule[58]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\ablscpt.dllLoadedModule[59]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\flight.dllLoadedModule[60]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\ai_player.dllLoadedModule[61]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\acontain.dllLoadedModule[62]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\controls.dllLoadedModule[63]=C:\Windows\system32\DINPUT8.dllLoadedModule[64]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\fsui.dllLoadedModule[65]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\atc.dllLoadedModule[66]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\facilities.dllLoadedModule[67]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\demo.dllLoadedModule[68]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\main.dllLoadedModule[69]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\fe.dllLoadedModule[70]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\util.dllLoadedModule[71]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\simprop.dllLoadedModule[72]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\g2d.dllLoadedModule[73]=C:\Windows\system32\d3dx9_34.dllLoadedModule[74]=C:\Windows\system32\d3dx10_34.dllLoadedModule[75]=C:\Windows\system32\d3d9.dllLoadedModule[76]=C:\Windows\system32\d3d8thk.dllLoadedModule[77]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\g3d.dllLoadedModule[78]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\panels.dllLoadedModule[79]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\multiplayer.dllLoadedModule[80]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\ui.dllLoadedModule[81]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\sound.dllLoadedModule[82]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\sim1.dllLoadedModule[83]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\simscheduler.dllLoadedModule[84]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\visualfx.dllLoadedModule[85]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\window.dllLoadedModule[86]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator X\terrain.dllLoadedModule[87]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\weather.dllLoadedModule[88]=C:\Windows\system32\DSOUND.dllLoadedModule[89]=C:\Windows\system32\POWRPROF.dllLoadedModule[90]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\symmap.dllLoadedModule[91]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dllLoadedModule[92]=C:\Windows\system32\MSIMG32.dllLoadedModule[93]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\xuipc.dllLoadedModule[94]=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\livingwater.dllLoadedModule[95]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\fs-traffic.dllLoadedModule[96]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\gps.dllLoadedModule[97]=C:\Windows\system32\MSWSOCK.dllLoadedModule[98]=C:\Windows\system32\SHFOLDER.dllLoadedModule[99]=C:\Windows\system32\RICHED20.DLLLoadedModule[100]=C:\Windows\system32\CRYPTSP.dllLoadedModule[101]=C:\Windows\system32\rsaenh.dllLoadedModule[102]=C:\Windows\syswow64\WINTRUST.dllLoadedModule[103]=C:\Windows\syswow64\CRYPT32.dllLoadedModule[104]=C:\Windows\syswow64\MSASN1.dllLoadedModule[105]=C:\Windows\syswow64\CLBCatQ.DLLLoadedModule[106]=C:\Windows\system32\wbem\wbemprox.dllLoadedModule[107]=C:\Windows\system32\wbemcomn.dllLoadedModule[108]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[109]=C:\Windows\system32\wbem\wbemsvc.dllLoadedModule[110]=C:\Windows\system32\wbem\fastprox.dllLoadedModule[111]=C:\Windows\system32\NTDSAPI.dllLoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLLLoadedModule[113]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\dxgi.dllLoadedModule[114]=C:\Windows\system32\d3d10.dllLoadedModule[115]=C:\Windows\system32\d3d10core.dllLoadedModule[116]=C:\Windows\system32\d3d11.dllLoadedModule[117]=C:\Windows\system32\d3dx10_43.dllLoadedModule[118]=C:\Windows\system32\d3dx11_43.dllLoadedModule[119]=C:\Windows\system32\MSVCR100.dllLoadedModule[120]=C:\Windows\system32\D3DCOMPILER_43.dllLoadedModule[121]=C:\Windows\system32\dxgi.dllLoadedModule[122]=C:\Windows\system32\nvd3dum.dllLoadedModule[123]=C:\Windows\syswow64\PSAPI.DLLLoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dllLoadedModule[125]=C:\Windows\system32\WindowsCodecs.dllLoadedModule[126]=C:\Windows\system32\d3d10_1.dllLoadedModule[127]=C:\Windows\system32\d3d10_1core.dllLoadedModule[128]=C:\Program 
Files (x86)\NVIDIA Corporation\3D 
Vision\nvSCPAPI.dllLoadedModule[129]=C:\Windows\SysWOW64\dxdiagn.dllLoadedModule[130]=C:\Windows\system32\winbrand.dllLoadedModule[131]=C:\Windows\system32\nvapi.dllLoadedModule[132]=C:\Windows\system32\WTSAPI32.DLLLoadedModule[133]=C:\Windows\system32\WINSTA.dllLoadedModule[134]=C:\Windows\SysWOW64\gameux.dllLoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dllLoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dllLoadedModule[137]=C:\Windows\SysWOW64\wer.dllLoadedModule[138]=C:\Windows\System32\Wpc.dllLoadedModule[139]=C:\Windows\System32\wevtapi.dllLoadedModule[140]=C:\Windows\System32\msxml6.dllLoadedModule[141]=C:\Windows\system32\SAMLIB.dllLoadedModule[142]=C:\Windows\system32\netutils.dllLoadedModule[143]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\uiautomationcore.dllLoadedModule[144]=C:\Windows\system32\OLEACC.dllLoadedModule[145]=C:\Windows\System32\MMDevApi.dllLoadedModule[146]=C:\Windows\System32\PROPSYS.dllLoadedModule[147]=C:\Windows\system32\AUDIOSES.DLLLoadedModule[148]=C:\Windows\system32\HID.DLLLoadedModule[149]=C:\Windows\system32\XInput9_1_0.dllLoadedModule[150]=C:\Windows\system32\wdmaud.drvLoadedModule[151]=C:\Windows\system32\ksuser.dllLoadedModule[152]=C:\Windows\system32\AVRT.dllLoadedModule[153]=C:\Windows\system32\msacm32.drvLoadedModule[154]=C:\Windows\system32\midimap.dllLoadedModule[155]=C:\Windows\system32\dinput.DLLLoadedModule[156]=C:\Windows\System32\wshtcpip.dllLoadedModule[157]=C:\Windows\System32\wship6.dllLoadedModule[158]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\bglmanx.dllLoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dllLoadedModule[160]=C:\Windows\system32\inetmib1.dllLoadedModule[161]=C:\Windows\system32\IPHLPAPI.DLLLoadedModule[162]=C:\Windows\system32\WINNSI.DLLLoadedModule[163]=C:\Windows\system32\snmpapi.dllLoadedModule[164]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\PMDG\DLLs\PMDG_HUD_interface.dllLoadedModule[165]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\VistaMare\ViMaCoreX.dllLoadedModule[166]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\VistaMare\bin\VMCX_SP2.dllLoadedModule[167]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\VistaMare\bin\ViMaNET.dllLoadedModule[168]=F:\Program Files 
(x86)\Microsoft Games\Microsoft Flight Simulator 
X\Aerosoft\ASE_DATA\AseData.dllLoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dllLoadedModule[170]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dllLoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dllLoadedModule[172]=F:\Program 
Files (x86)\IVAO\IvAp 
v2\ivap_fsx_bootstrap.dllLoadedModule[173]=C:\Windows\system32\mfc100.dllLoadedModule[174]=C:\Windows\system32\MSVCP100.dllLoadedModule[175]=C:\Windows\system32\MFC100ENU.DLLLoadedModule[176]=C:\Windows\system32\ntmarta.dllLoadedModule[177]=C:\Windows\syswow64\WLDAP32.dllLoadedModule[178]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\Modules\FSUIPC4.dllLoadedModule[179]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\Modules\FSCopilot.dllLoadedModule[180]=C:\Windows\system32\oledlg.dllLoadedModule[181]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[182]=C:\Windows\SysWow64\XAudio2_7.dllLoadedModule[183]=C:\Windows\system32\FS2AUDIO.dllLoadedModule[184]=C:\Windows\system32\X3DAudio1_6.dllLoadedModule[185]=C:\Windows\SysWow64\xactengine3_4.dllLoadedModule[186]=C:\Windows\SysWow64\XAudio2_4.dllLoadedModule[187]=C:\Windows\system32\Secur32.dllLoadedModule[188]=C:\Windows\system32\dnsapi.DLLLoadedModule[189]=C:\Windows\system32\RASAPI32.dllLoadedModule[190]=C:\Windows\system32\rasman.dllLoadedModule[191]=C:\Windows\system32\rtutils.dllLoadedModule[192]=C:\Windows\system32\sensapi.dllLoadedModule[193]=C:\Windows\system32\NLAapi.dllLoadedModule[194]=C:\Windows\system32\rasadhlp.dllLoadedModule[195]=C:\Windows\System32\fwpuclnt.dllLoadedModule[196]=C:\Windows\SysWOW64\ieframe.dllLoadedModule[197]=C:\Windows\SysWOW64\mshtml.dllLoadedModule[198]=F:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\GAUGES\PMDG_737NGX.DLLLoadedModule[199]=C:\Windows\system32\NETAPI32.dllLoadedModule[200]=C:\Windows\system32\srvcli.dllLoadedModule[201]=C:\Windows\system32\wkscli.dllLoadedModule[202]=C:\Windows\system32\WSOCK32.dllLoadedModule[203]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\FS2Crew2010\Versions\PMDG737NGX\Gauges\FS2CrewNGXVoice.GAULoadedModule[204]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\libcurl.dllLoadedModule[205]=F:\Program Files (x86)\Microsoft 
Games\Microsoft Flight Simulator 
X\GAUGES\PMDG_737NGX_3.DLLLoadedModule[206]=C:\Windows\system32\msimtf.dllLoadedModule[207]=C:\Windows\system32\msls31.dllLoadedModule[208]=C:\Windows\system32\d2d1.dllLoadedModule[209]=C:\Windows\system32\DWrite.dllLoadedModule[210]=C:\Windows\system32\D3D10Warp.dllLoadedModule[211]=C:\Windows\system32\MLANG.dllLoadedModule[212]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\Gauges\PMDG_737NGX_2.dllLoadedModule[213]=C:\Windows\system32\napinsp.dllLoadedModule[214]=C:\Windows\system32\pnrpnsp.dllLoadedModule[215]=C:\Windows\System32\winrnr.dllLoadedModule[216]=C:\Windows\system32\icmp.DllLoadedModule[217]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\VistaMare\bin\ViMaIScnX.dllLoadedModule[218]=F:\Program Files 
(x86)\FSFDT\FSCopilot\FSCopGPWS.ocxLoadedModule[219]=C:\Windows\system32\MSVBVM60.DLLLoadedModule[220]=C:\Windows\system32\SXS.DLLLoadedModule[221]=F:\PROGRA~1\FSFDT\FSCOPI~1\FSCOPI~1.OCXLoadedModule[222]=F:\Program 
Files (x86)\FSFDT\FSCopilot\FSCopTimeSync.ocxLoadedModule[223]=F:\Program 
Files (x86)\FSFDT\FSCopilot\FSCopHeadEffects.ocxLoadedModule[224]=F:\Program 
Files (x86)\FSFDT\FSCopilot\FSCopTuner.ocxLoadedModule[225]=F:\Program Files 
(x86)\FSFDT\Control 
Panel\MSCOMCTL.OCXLoadedModule[226]=C:\Windows\system32\wmp.dllLoadedModule[227]=C:\Windows\system32\wmploc.dllLoadedModule[228]=C:\Windows\system32\MFPlat.DLLLoadedModule[229]=C:\Program 
Files\AVAST 
Software\Avast\AhAScr.dllLoadedModule[230]=C:\PROGRA~1\AVASTS~1\Avast\aswCmnBS.dllLoadedModule[231]=C:\PROGRA~1\AVASTS~1\Avast\aswCmnOS.dllLoadedModule[232]=C:\PROGRA~1\AVASTS~1\Avast\aswCmnIS.dllLoadedModule[233]=C:\PROGRA~1\AVASTS~1\Avast\Aavm4h.dllLoadedModule[234]=C:\PROGRA~1\AVASTS~1\Avast\AavmRpch.dllLoadedModule[235]=C:\PROGRA~1\AVASTS~1\Avast\ashBase.dllLoadedModule[236]=C:\PROGRA~1\AVASTS~1\Avast\aswEngLdr.dllLoadedModule[237]=C:\PROGRA~1\AVASTS~1\Avast\ashTask.dllLoadedModule[238]=C:\PROGRA~1\AVASTS~1\Avast\aswAux.dllLoadedModule[239]=C:\PROGRA~1\AVASTS~1\Avast\aswProperty.dllLoadedModule[240]=C:\PROGRA~1\AVASTS~1\Avast\avastIP.dllLoadedModule[241]=C:\Windows\system32\WINHTTP.dllLoadedModule[242]=C:\Windows\system32\webio.dllLoadedModule[243]=C:\Windows\SysWOW64\jscript.dllLoadedModule[244]=C:\Program 
Files\AVAST 
Software\Avast\aswJsFlt.dllLoadedModule[245]=C:\Windows\system32\msadp32.acmLoadedModule[246]=F:\Program 
Files (x86)\Microsoft Games\Microsoft Flight Simulator 
X\Aerosoft\AES\ViMaCli.dllLoadedModule[247]=F:\Program Files 
(x86)\FSFDT\FSInn 
UI\FSCopilotFSInn.ocxLoadedModule[248]=F:\PROGRA~1\FSFDT\FSInn\FSInn.ocxLoadedModule[249]=C:\Windows\system32\DPLAYX.dllFriendlyEventName=Stopped 
responding and was closedConsentKey=AppHangXProcB1AppName=Microsoft 
Flight Simulator®AppPath=F:\Program Files (x86)\Microsoft Games\Microsoft 
Flight Simulator X\fsx.exeReportDescription=A problem caused this program to 
stop interacting with Windows.

Share this post


Link to post
Share on other sites

Your AppCrashView is somewhat confusing and convoluted as it is hard to read but I got through it.  Your Microsoft Visuals are up-to-date and loaded properly.  You had an AppHang rather than a CTD and this "crash" was significantly different from the OP.  There are many reports here in this forum and elsewhere on the Internet regarding issues with FSCoPilot and FSInn (Google: fsinn crashes fsx).  Make sure they are properly configured as they were nearly the last two modules loaded before fsx hung up.  There has also been reported problems with AES.  The AVAST anti-virus program could be creating problems too by not allowing a module in fsx to load.  You can temporarily disable AVAST and run FSX and see if this fixes the problem.  You can disable AES too (through the Scenery Library) to see if this fixes the problem.  I'm not sure about FSInn and FS Co-Pilot but, if you can disable these programs and run FSX just to see if these programs are causing your problem, it would help in the investigation.

 

 

 


Looking at my settings in FSX I do have all sliders to the far right with the exception of Water effects which I have at Low 2.x and Autogen Density which I have at Normal.

 

You have a nice system and surely capable of running FSX. As of right now I think the problem is associated with one of the programs mentioned above.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks Jim for taking your time looking into my crash log and you're right, the problem when it happens is more FSX stops responding rather than crashing to the desktop. It's when I confirm the FSX stopped responding dialog I'm thrown back at the desktop.

 

I could of course try what you suggest and disable the programs you mention but problem is since this issue is very intermittent and I don't know how to reproduce it since it happens very randomly and it only happens maybe 1 of out 10 flights that would mean I would have to fly without these programs for lots of flights and still not knowing if a hang indeed would have occcured if I hadn't removed the programs.

 

At this point and considering I've done maybe 6-7 flights since removing SweetFX from the mix I will go on flying and hopefully I will not have any more problems and if I do have another hang I'll consider doing what you suggest.

 

Now it's time to start preparing for descent into LEBL :wink:

 

Thanks again for your help and input so far!

Share this post


Link to post
Share on other sites

×
×
  • Create New...