Jump to content
Sign in to follow this  
Ben3083

Crash to desktop Issue......HELP

Recommended Posts

Hi Guys,

 

I've started having an issue with random crash to desktop and wondered if anyone could help. It all started after i added a few add-ons all at once and now i keep getting an FSX unknown app crash in the event viewer.

 

The add-ons i already had running with no problems was:

 

Active Sky next

Aivlasoft EFB (Display unit on a Separate system)

PMDG 737

FS2 Crew

Aerosoft Airbus X Extended

Dublin Mega Airport

Ground Services X

 

The add-ons i added all in the same day just before the CTD started:

 

FSUICP (Registered Version)

Wide FS

UK2000 Leeds Bradford Extreme

FTX England

smartCARS (Separate system)

 

I know most people are going to say start uninstalling the add-ons which i will but what i did wonder could it be a Duplicate BGL file problem between FTX and UK Extreme? I'm not a whizz kid but its just things I've read in the forums. I've added a couple of screenshots with the duplicate files below. There were numerous more duplicates but i did a dirty shut down of GSX in the scenery library.   

 

Any help would be greatly appreciated.

 

My PC spec is as follows: Windows 8.1 64-bit, i7-4770 CPU @ 3.90GHz (8 CPUs), 16gb Ram, 2TB Hard Drive, AMD Radeon R9 270 (2GB)

 

28k39l0.jpg

 

2qizt02.jpg

 

 

 

Share this post


Link to post
Share on other sites

I know most people are going to say start uninstalling the add-ons which i will but what i did wonder could it be a Duplicate BGL file problem between FTX and UK Extreme?

You do not have to uninstall any of your addons to investigate the scene of the crime (your CTD). Just open up Scenery Library and disable all addons (if you have the FTX Central, return it to its defaults). The AVSIM CTD Guide, located to the right of this forum under Hot Spots, shows how to disable the modules in the dll.xml so they will not load the next time you start up FSX. Once that's completed, you can also rename or move your FSX.cfg to another folder, restart FSX and the config will be rebuilt. If that did not fix the problem, then you can return the old config. Once the scenery addons are disabled in the Scenery Library and the modules in the dll.xml, then your FSX will be almost back to when you first installed it. Start enabling 3-4 scenery at a time until the problem reoccurs. Same with the modules in the dll.xml but reenable them one at a time. Most problems are fixed by rebuilding your FSX.cfg as you might have a bad tweak or your settings are set too high.

 

Your images are way too small for my 30 inch monitor so cannot read them. Duplicate files are common and used by developers for different purposes. You should not remove any duplicate files.

 

Hope this helps.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Try'd everything you suggested but to no avail. looks like i will have to do a clean install and add the programs one by one and run them for a while. This is exactly the same log i keep getting in the event viewer:

 

Log Name:      Application
Source:        Application Error
Date:          06/09/2014 13:14:19
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      BensPC
Description:
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: 0x77961a91
Faulting process ID: 0x18b4
Faulting application start time: 0x01cfc9cb4563cc18
Faulting application path: C:\fsx\fsx.exe
Faulting module path: unknown
Report ID: 53cf56c3-35bf-11e4-8262-9cb654eb7d32
Faulting package full name: 
Faulting package-relative application ID: 
Event Xml:
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-09-06T12:14:19.000000000Z" />
    <EventRecordID>6169</EventRecordID>
    <Channel>Application</Channel>
    <Computer>BensPC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.61472.0</Data>
    <Data>475e17d3</Data>
    <Data>unknown</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>77961a91</Data>
    <Data>18b4</Data>
    <Data>01cfc9cb4563cc18</Data>
    <Data>C:\fsx\fsx.exe</Data>
    <Data>unknown</Data>
    <Data>53cf56c3-35bf-11e4-8262-9cb654eb7d32</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>

</Event> 

Share this post


Link to post
Share on other sites

Before completely uninstalling/reinstalling FSX, I would uninstall SP2, restart system, and then reinstall SP2 with Admin Rights.

 

Again, do not remove any duplicate files or you will run into problems, guaranteed.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I uninstalled the SP2 and re installed like you said but the 'Run as Admin' was grey'd out. I've also put the following lines into my new CFG file and i'm getting loads of missing scenery errors.

 

 

[sCENERY]
// To show alerts or areas, set to = 1  
// To hide alerts or areas, set to = 0   
// Alert for missing textures ShowMissingTextureAlert=1  
// Alert for missing objects MissingLibraryAlert=1  

// Render Trigger areas as visible boxes ShowTriggers=1  

Share this post


Link to post
Share on other sites

I've also put the following lines into my new CFG file and i'm getting loads of missing scenery errors.

Those alerts may be okay. Just because a scenery texture is missing or object does not mean it will cause a crash. For instance, in the Orbx/FTX PNW, it is completely normal for missing textures. Is your problem fixed with the reinstall of SP2?

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I've not really had a chance to do any serious tests flights with all my add-ons running since I reinstalled SP2 but I've had no CDT's doing a few quick take offs and circuits.

 

 As with regards to the graphic textures missing, I get 3 warnings when loading the PMDG 737 and every 5-10 minutes I get one saying EGGB texture failed to load and then get around 20-25 texture errors with just codes and I was at EGNM doing circuits when these occured. Thank you for the help and suggestions you have been giving me so far.

Share this post


Link to post
Share on other sites

As with regards to the graphic textures missing, I get 3 warnings when loading the PMDG 737 and every 5-10 minutes I get one saying EGGB texture failed to load

These are most likely objects being called that the developer forgot to add or removed from their product. I suspect the texture could also be corrupted. AVSIM added the missing texture information in the AVSIM CTD Guide to help you pursue your investigation into your crashes/freezes. Missing textures are very common and 99% of them will not cause a crash. For instance, when loading the PMDG 737 w/o the texture missing parameters in your FSX.cfg, does FSX crash? If so, the PMDG 737 is likely the cause. But you have to think about the thousands of other PMDG 737 users who are able to load FSX w/o any problems even with the warnings. Same goes with the other scenery where you are getting reports of missing textures. In the Seattle area with FTX/Orbx loaded, I can get a lot of errors flying around and have to click OK to continue as it finds each missing texture. Still I can run FSX in this area (w/o the missing texture parameters) w/o any problems. More information about these parameters can be found at the FS Developer Wiki - http://www.fsdeveloper.com/wiki/index.php?title=Missing_textures.

 

Have you ran AppCrashView as suggested by the AVSIM CTD Guide? It shows more information about the crash and maybe other problems with your computer.

 

There's another method for trying to pin down your "unknown" crashes - Run Process Monitor as follows:

 

Setting up the Process Monitor for FSX – Another investigative tool used to pin down a situation where FSX/P3D freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb896645. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the sim froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large. For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are sync’d. Going through one minute of a glitch is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D events. It would be nearly impossible to find a possible glitch if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

Open Process Monitor. Click on the Filter tab and then Filter….

Display entries matching these conditions:

Where it says Architecture, click on that and select “Process Name”

Go next to the blank box and click on that and select FSX or P3D.exe and make sure “Include” is shown (FSX or P3D must be running when you do this!!). Once completed, click on Add and then click OK at the bottom of the form and Go Fly.

 

You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).

 

When the flight is finished, immediately go to the Process Monitor application and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this). Shutdown FSX/P3D and begin your investigating!

 

It is most important that you delete the log when you are finished as an hour flight will create a log as large as 8GB's.

 

Hope this helps.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Just to update your good self. Last night i run a flight from EIDW to EGNM with all my add-ons in windowed mode with no problems what so ever apart from when i went to close FSX from the main screen it said 'FSX has stopped working and needs to close' but i get that most times. Then i just went to do the return leg back to EGNM and it crashed whilst sat on the gate and i wasn't actually doing anything at the time. I downloaded the AppCrashView that you recommended and this is what i got from it. Many thanks again for looking at this for me. 

 

Version=1
EventType=BEX
EventTime=130555309521965881
ReportType=2
Consent=1
UploadTime=130555309523551178
ReportIdentifier=fd30fc44-3f4f-11e4-8264-9cb654eb7d32
IntegratorReportIdentifier=fd30fc43-3f4f-11e4-8264-9cb654eb7d32
WOW64=1
NsAppName=fsx.exe
Response.BucketId=3aed9ac45a7239d3435c5488195078f7
Response.BucketTable=5
Response.LegacyBucketId=81703736300
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_8382
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_03_FROM_mscorwks+0x00254E17
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=8382
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=8382e1269ac9d6a3caa36652e586ed78
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=01e0
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=01e0c2c4360344cd6344071d6b2ac881
UI[2]=C:\fsx\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\fsx\fsx.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\windows\system32\apphelp.dll
LoadedModule[5]=C:\windows\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[11]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[12]=C:\windows\SYSTEM32\MPR.dll
LoadedModule[13]=C:\windows\SYSTEM32\SETUPAPI.dll
LoadedModule[14]=C:\windows\SYSTEM32\sfc.dll
LoadedModule[15]=C:\windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[16]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[17]=C:\windows\SYSTEM32\combase.dll
LoadedModule[18]=C:\windows\SYSTEM32\CFGMGR32.dll
LoadedModule[19]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\windows\SYSTEM32\sfc_os.DLL
LoadedModule[21]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[23]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[24]=C:\windows\AppPatch\AcSpecfc.DLL
LoadedModule[25]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\COMCTL32.dll
LoadedModule[26]=C:\windows\SYSTEM32\mscms.dll
LoadedModule[27]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[28]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[29]=C:\windows\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\windows\SYSTEM32\DDRAW.dll
LoadedModule[31]=C:\windows\SYSTEM32\USERENV.dll
LoadedModule[32]=C:\windows\SYSTEM32\COMDLG32.dll
LoadedModule[33]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[34]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\windows\SYSTEM32\msi.dll
LoadedModule[37]=C:\windows\SYSTEM32\WINMMBASE.dll
LoadedModule[38]=C:\windows\SYSTEM32\DCIMAN32.dll
LoadedModule[39]=C:\windows\SYSTEM32\profapi.dll
LoadedModule[40]=C:\windows\SYSTEM32\SHCORE.DLL
LoadedModule[41]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[42]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[43]=C:\windows\SYSTEM32\DEVOBJ.dll
LoadedModule[44]=C:\windows\SYSTEM32\SortWindows61.dll
LoadedModule[45]=C:\windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[46]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll
LoadedModule[47]=C:\windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[48]=C:\fsx\language.dll
LoadedModule[49]=C:\fsx\API.DLL
LoadedModule[50]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll
LoadedModule[51]=C:\fsx\ablscpt.dll
LoadedModule[52]=C:\fsx\acontain.dll
LoadedModule[53]=C:\fsx\ai_player.dll
LoadedModule[54]=C:\fsx\atc.dll
LoadedModule[55]=C:\fsx\controls.dll
LoadedModule[56]=C:\fsx\demo.dll
LoadedModule[57]=C:\fsx\facilities.dll
LoadedModule[58]=C:\fsx\fe.dll
LoadedModule[59]=C:\fsx\flight.dll
LoadedModule[60]=C:\fsx\fsui.dll
LoadedModule[61]=C:\fsx\g2d.dll
LoadedModule[62]=C:\fsx\g3d.dll
LoadedModule[63]=C:\fsx\gps.dll
LoadedModule[64]=C:\fsx\livingwater.dll
LoadedModule[65]=C:\fsx\main.dll
LoadedModule[66]=C:\fsx\multiplayer.dll
LoadedModule[67]=C:\fsx\panels.dll
LoadedModule[68]=C:\fsx\sim1.dll
LoadedModule[69]=C:\fsx\simprop.dll
LoadedModule[70]=C:\fsx\simscheduler.dll
LoadedModule[71]=C:\fsx\sound.dll
LoadedModule[72]=C:\fsx\symmap.dll
LoadedModule[73]=C:\fsx\terrain.dll
LoadedModule[74]=C:\fsx\fs-traffic.dll
LoadedModule[75]=C:\fsx\ui.dll
LoadedModule[76]=C:\fsx\util.dll
LoadedModule[77]=C:\fsx\visualfx.dll
LoadedModule[78]=C:\fsx\weather.dll
LoadedModule[79]=C:\fsx\window.dll
LoadedModule[80]=C:\fsx\xuipc.dll
LoadedModule[81]=C:\windows\SYSTEM32\MSWSOCK.dll
LoadedModule[82]=C:\windows\SYSTEM32\SHFOLDER.dll
LoadedModule[83]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[84]=C:\windows\SYSTEM32\POWRPROF.dll
LoadedModule[85]=C:\windows\SYSTEM32\DINPUT8.dll
LoadedModule[86]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17227_none_dad9452e5bcb7986\gdiplus.dll
LoadedModule[87]=C:\windows\SYSTEM32\d3dx9_34.dll
LoadedModule[88]=C:\windows\SYSTEM32\d3dx10_34.dll
LoadedModule[89]=C:\windows\SYSTEM32\d3d9.dll
LoadedModule[90]=C:\windows\SYSTEM32\DSOUND.dll
LoadedModule[91]=C:\windows\SYSTEM32\WININET.dll
LoadedModule[92]=C:\windows\SYSTEM32\MSACM32.dll
LoadedModule[93]=C:\windows\SYSTEM32\MSIMG32.dll
LoadedModule[94]=C:\windows\SYSTEM32\iertutil.dll
LoadedModule[95]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[96]=C:\windows\system32\uxtheme.dll
LoadedModule[97]=C:\windows\SYSTEM32\RICHED20.DLL
LoadedModule[98]=C:\windows\SYSTEM32\USP10.dll
LoadedModule[99]=C:\windows\SYSTEM32\msls31.dll
LoadedModule[100]=C:\windows\SYSTEM32\CRYPTSP.dll
LoadedModule[101]=C:\windows\system32\rsaenh.dll
LoadedModule[102]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[103]=C:\windows\SYSTEM32\WINTRUST.dll
LoadedModule[104]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[105]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[106]=C:\windows\SYSTEM32\clbcatq.dll
LoadedModule[107]=C:\windows\system32\wbem\wbemprox.dll
LoadedModule[108]=C:\windows\SYSTEM32\wbemcomn.dll
LoadedModule[109]=C:\windows\system32\wbem\wbemsvc.dll
LoadedModule[110]=C:\windows\system32\wbem\fastprox.dll
LoadedModule[111]=C:\windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[112]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[113]=C:\windows\SYSTEM32\dxgi.dll
LoadedModule[114]=C:\windows\SYSTEM32\d3d10.dll
LoadedModule[115]=C:\windows\SYSTEM32\d3d10core.dll
LoadedModule[116]=C:\windows\SYSTEM32\d3d11.dll
LoadedModule[117]=C:\windows\SYSTEM32\aticfx32.dll
LoadedModule[118]=C:\windows\SYSTEM32\atiu9pag.dll
LoadedModule[119]=C:\windows\SYSTEM32\atiumdag.dll
LoadedModule[120]=C:\windows\SYSTEM32\atiumdva.dll
LoadedModule[121]=C:\windows\SYSTEM32\atiuxpag.dll
LoadedModule[122]=C:\windows\SYSTEM32\atidxx32.dll
LoadedModule[123]=C:\windows\SYSTEM32\D3DCompiler_34.dll
LoadedModule[124]=C:\windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[125]=C:\windows\SYSTEM32\d3d10_1.dll
LoadedModule[126]=C:\windows\SYSTEM32\d3d10_1core.dll
LoadedModule[127]=C:\windows\SYSTEM32\WTSAPI32.DLL
LoadedModule[128]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[129]=C:\Windows\SYSTEM32\gameux.dll
LoadedModule[130]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7\COMCTL32.dll
LoadedModule[131]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[132]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[133]=C:\windows\System32\Wpc.dll
LoadedModule[134]=C:\windows\System32\NETAPI32.dll
LoadedModule[135]=C:\windows\SYSTEM32\Normaliz.dll
LoadedModule[136]=C:\windows\System32\wevtapi.dll
LoadedModule[137]=C:\windows\System32\netutils.dll
LoadedModule[138]=C:\windows\System32\srvcli.dll
LoadedModule[139]=C:\windows\System32\wkscli.dll
LoadedModule[140]=C:\windows\System32\SAMCLI.DLL
LoadedModule[141]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[142]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[143]=C:\Windows\System32\Windows.Web.dll
LoadedModule[144]=C:\windows\SYSTEM32\uiautomationcore.dll
LoadedModule[145]=C:\windows\SYSTEM32\sxs.dll
LoadedModule[146]=C:\windows\System32\MMDevApi.dll
LoadedModule[147]=C:\windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[148]=C:\windows\SYSTEM32\HID.DLL
LoadedModule[149]=C:\windows\SYSTEM32\XInput9_1_0.dll
LoadedModule[150]=C:\windows\SYSTEM32\wdmaud.drv
LoadedModule[151]=C:\windows\SYSTEM32\ksuser.dll
LoadedModule[152]=C:\windows\SYSTEM32\AVRT.dll
LoadedModule[153]=C:\windows\SYSTEM32\msacm32.drv
LoadedModule[154]=C:\windows\SYSTEM32\midimap.dll
LoadedModule[155]=C:\windows\SYSTEM32\dinput.DLL
LoadedModule[156]=C:\windows\SYSTEM32\XInput1_4.dll
LoadedModule[157]=C:\fsx\bglmanx.dll
LoadedModule[158]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[159]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[160]=C:\windows\SYSTEM32\inetmib1.dll
LoadedModule[161]=C:\windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[162]=C:\windows\SYSTEM32\snmpapi.dll
LoadedModule[163]=C:\windows\SYSTEM32\WINNSI.DLL
LoadedModule[164]=C:\fsx\VistaMare\ViMaCoreX.dll
LoadedModule[165]=C:\fsx\VistaMare\bin\VMCX_SP2.dll
LoadedModule[166]=C:\fsx\VistaMare\bin\ViMaNET.dll
LoadedModule[167]=C:\fsx\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[168]=C:\fsx\RAASPRO\RAASPRO.dll
LoadedModule[169]=C:\windows\SYSTEM32\Secur32.dll
LoadedModule[170]=C:\windows\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[171]=C:\windows\SYSTEM32\winhttp.dll
LoadedModule[172]=C:\windows\SYSTEM32\DNSAPI.dll
LoadedModule[173]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[174]=C:\Windows\System32\rasadhlp.dll
LoadedModule[175]=C:\windows\System32\fwpuclnt.dll
LoadedModule[176]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[177]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[178]=C:\windows\SYSTEM32\MSDART.DLL
LoadedModule[179]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[180]=C:\Windows\SYSTEM32\comsvcs.dll
LoadedModule[181]=C:\Windows\SYSTEM32\msjetoledb40.dll
LoadedModule[182]=C:\Windows\SYSTEM32\msjet40.dll
LoadedModule[183]=C:\Windows\SYSTEM32\msjter40.dll
LoadedModule[184]=C:\Windows\SYSTEM32\mswstr10.dll
LoadedModule[185]=C:\Windows\SYSTEM32\MSJINT40.DLL
LoadedModule[186]=C:\windows\SYSTEM32\DPAPI.DLL
LoadedModule[187]=C:\Windows\SYSTEM32\mstext40.dll
LoadedModule[188]=C:\windows\SYSTEM32\mlang.dll
LoadedModule[189]=C:\windows\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[190]=C:\windows\SYSTEM32\X3DAudio1_6.dll
LoadedModule[191]=C:\windows\SYSTEM32\xactengine3_4.dll
LoadedModule[192]=C:\windows\SYSTEM32\XAudio2_4.dll
LoadedModule[193]=C:\fsx\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[194]=C:\windows\SYSTEM32\MSVCR100.dll
LoadedModule[195]=C:\fsx\Modules\FSUIPC4.dll
LoadedModule[196]=C:\windows\SYSTEM32\imagehlp.dll
LoadedModule[197]=C:\windows\SYSTEM32\ncrypt.dll
LoadedModule[198]=C:\windows\SYSTEM32\NTASN1.dll
LoadedModule[199]=C:\windows\SYSTEM32\gpapi.dll
LoadedModule[200]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[201]=C:\windows\SYSTEM32\WLDAP32.dll
LoadedModule[202]=C:\windows\SYSTEM32\PROPSYS.dll
LoadedModule[203]=C:\Windows\SYSTEM32\thumbcache.dll
LoadedModule[204]=C:\fsx\as_srv\as_btstrp.dll
LoadedModule[205]=C:\windows\SYSTEM32\mscoree.dll
LoadedModule[206]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[207]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[208]=C:\windows\assembly\NativeImages_v2.0.50727_32\mscorlib\5bd3374f05d46ba0563f44d032209f08\mscorlib.ni.dll
LoadedModule[209]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[210]=C:\fsx\as_srv\as_connect.dll
LoadedModule[211]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[212]=C:\windows\assembly\NativeImages_v2.0.50727_32\System\a500ec9c4638c6ba200d7b55324709f2\System.ni.dll
LoadedModule[213]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\f6ff4eab6e6bb587d62c3975fcbbca30\System.Drawing.ni.dll
LoadedModule[214]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[215]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[216]=C:\windows\system32\msimtf.dll
LoadedModule[217]=C:\windows\SYSTEM32\d2d1.dll
LoadedModule[218]=C:\windows\SYSTEM32\DWrite.dll
LoadedModule[219]=C:\windows\SYSTEM32\d3d10warp.dll
LoadedModule[220]=C:\fsx\VistaMare\bin\ViMaIScnX.dll
LoadedModule[221]=C:\fsx\GAUGES\PMDG_737NGX.DLL
LoadedModule[222]=C:\windows\SYSTEM32\WSOCK32.dll
LoadedModule[223]=C:\windows\SYSTEM32\MSVCP100.dll
LoadedModule[224]=C:\windows\SYSTEM32\XAudio2_7.dll
LoadedModule[225]=C:\fsx\FS2Crew2010\Versions\PMDG737NGX\Gauges\FS2CrewNGXButton.GAU
LoadedModule[226]=C:\fsx\libcurl.dll
LoadedModule[227]=C:\windows\SYSTEM32\FS2AUDIO.dll
LoadedModule[228]=C:\fsx\GAUGES\XGauge.DLL
LoadedModule[229]=C:\fsx\GAUGES\PMDG_737NGX_3.DLL
LoadedModule[230]=C:\fsx\Gauges\PMDG_737NGX_2.dll
LoadedModule[231]=C:\windows\SYSTEM32\OLEACC.dll
LoadedModule[232]=C:\windows\system32\napinsp.dll
LoadedModule[233]=C:\windows\system32\pnrpnsp.dll
LoadedModule[234]=C:\windows\system32\NLAapi.dll
LoadedModule[235]=C:\windows\System32\winrnr.dll
LoadedModule[236]=C:\windows\SYSTEM32\ntmarta.dll
LoadedModule[237]=C:\windows\SYSTEM32\icmp.Dll
LoadedModule[238]=C:\windows\SYSTEM32\msadp32.acm
LoadedModule[239]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\27dc8e491e32361eaff0b88f0befc197\System.Configuration.ni.dll
LoadedModule[240]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Xml\8006a5df62f0c127d15db16d3a8c68f8\System.Xml.ni.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Flight Simulator®
AppPath=C:\fsx\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5B0B5FEC0FEF5400B720718FE7EBC216

Share this post


Link to post
Share on other sites

You received the infamous StackHash crash. Close FSX in Windowed mode and not in full screen. I had the same issue (and many, many others) when FSX was shutdown. Someone found that closing in Windowed mode allowed FSX to close w/o the StackHash. It's all what we stated in our AVSIM CTD Guide.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I was in Windowed mode as stated in my last post. I come out of the sim (windowed mode) to the main screen but then when i shut down FSX from the main menu it crashes. Should i just close the sim from in the game?  

 

EDIT: I have just closed FSX from inside Windowed mode and then started FSX again as i was going to do a full flight and it crashed while on the ground setting up and i got the same error as last time. Whats more frustrating is i didn't have them before i added the above add-ons and even though i have removed them i'm still getting CTD's now. :(  

Share this post


Link to post
Share on other sites

What was the faulting module? Looks like you will have to reinstall Windows. Only solution I know of. It's what I had to do to get rid of a StackHash when closing FSX. Of course, you could start uninstalling addons one by one and maybe after uninstalling the addon, fsx will work again. It's a shame. I think you are the first one where one of our recommendations or the guidance in the AVSIM CTD Guide did not work (at least this year).

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

I've literally tried most things now apart from uninstalling, I suppose i should of stayed with windows 7 instead of going to 8.1 as it doesn't seem very stable with a lot of programs. The faulting module was exactly the same as before. 

 

Version=1
EventType=BEX
EventTime=130555959204485972
ReportType=2
Consent=1
UploadTime=130555959206375628
ReportIdentifier=4142ae44-3fe7-11e4-8264-9cb654eb7d32
IntegratorReportIdentifier=4142ae43-3fe7-11e4-8264-9cb654eb7d32
WOW64=1
NsAppName=fsx.exe
Response.BucketId=3aed9ac45a7239d3435c5488195078f7
Response.BucketTable=5
Response.LegacyBucketId=81703736300
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_8382
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Offset
Sig[6].Value=PCH_03_FROM_mscorwks+0x00254E17
Sig[7].Name=Exception Code
Sig[7].Value=c0000005
Sig[8].Name=Exception Data
Sig[8].Value=00000008
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.768.101
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=8382
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=8382e1269ac9d6a3caa36652e586ed78
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=01e0
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=01e0c2c4360344cd6344071d6b2ac881
UI[2]=C:\fsx\fsx.exe
UI[3]=Microsoft Flight Simulator® has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\fsx\fsx.exe
LoadedModule[1]=C:\windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\windows\SYSTEM32\KERNEL32.DLL
LoadedModule[3]=C:\windows\SYSTEM32\KERNELBASE.dll
LoadedModule[4]=C:\windows\system32\apphelp.dll
LoadedModule[5]=C:\windows\AppPatch\AcLayers.DLL
LoadedModule[6]=C:\windows\SYSTEM32\msvcrt.dll
LoadedModule[7]=C:\windows\SYSTEM32\USER32.dll
LoadedModule[8]=C:\windows\SYSTEM32\GDI32.dll
LoadedModule[9]=C:\windows\SYSTEM32\SHELL32.dll
LoadedModule[10]=C:\windows\SYSTEM32\SHLWAPI.dll
LoadedModule[11]=C:\windows\SYSTEM32\OLEAUT32.dll
LoadedModule[12]=C:\windows\SYSTEM32\MPR.dll
LoadedModule[13]=C:\windows\SYSTEM32\SETUPAPI.dll
LoadedModule[14]=C:\windows\SYSTEM32\sfc.dll
LoadedModule[15]=C:\windows\SYSTEM32\WINSPOOL.DRV
LoadedModule[16]=C:\windows\SYSTEM32\RPCRT4.dll
LoadedModule[17]=C:\windows\SYSTEM32\combase.dll
LoadedModule[18]=C:\windows\SYSTEM32\CFGMGR32.dll
LoadedModule[19]=C:\windows\SYSTEM32\SspiCli.dll
LoadedModule[20]=C:\windows\SYSTEM32\sfc_os.DLL
LoadedModule[21]=C:\windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[22]=C:\windows\SYSTEM32\sechost.dll
LoadedModule[23]=C:\windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[24]=C:\windows\AppPatch\AcSpecfc.DLL
LoadedModule[25]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\COMCTL32.dll
LoadedModule[26]=C:\windows\SYSTEM32\mscms.dll
LoadedModule[27]=C:\windows\SYSTEM32\ADVAPI32.dll
LoadedModule[28]=C:\windows\SYSTEM32\ole32.dll
LoadedModule[29]=C:\windows\SYSTEM32\WINMM.dll
LoadedModule[30]=C:\windows\SYSTEM32\DDRAW.dll
LoadedModule[31]=C:\windows\SYSTEM32\USERENV.dll
LoadedModule[32]=C:\windows\SYSTEM32\COMDLG32.dll
LoadedModule[33]=C:\windows\SYSTEM32\IMM32.dll
LoadedModule[34]=C:\windows\SYSTEM32\WS2_32.dll
LoadedModule[35]=C:\windows\SYSTEM32\dwmapi.dll
LoadedModule[36]=C:\windows\SYSTEM32\msi.dll
LoadedModule[37]=C:\windows\SYSTEM32\WINMMBASE.dll
LoadedModule[38]=C:\windows\SYSTEM32\DCIMAN32.dll
LoadedModule[39]=C:\windows\SYSTEM32\profapi.dll
LoadedModule[40]=C:\windows\SYSTEM32\SHCORE.DLL
LoadedModule[41]=C:\windows\SYSTEM32\MSCTF.dll
LoadedModule[42]=C:\windows\SYSTEM32\NSI.dll
LoadedModule[43]=C:\windows\SYSTEM32\DEVOBJ.dll
LoadedModule[44]=C:\windows\SYSTEM32\SortWindows61.dll
LoadedModule[45]=C:\windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[46]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll
LoadedModule[47]=C:\windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[48]=C:\fsx\language.dll
LoadedModule[49]=C:\fsx\API.DLL
LoadedModule[50]=C:\windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll
LoadedModule[51]=C:\fsx\ablscpt.dll
LoadedModule[52]=C:\fsx\acontain.dll
LoadedModule[53]=C:\fsx\ai_player.dll
LoadedModule[54]=C:\fsx\atc.dll
LoadedModule[55]=C:\fsx\controls.dll
LoadedModule[56]=C:\fsx\demo.dll
LoadedModule[57]=C:\fsx\facilities.dll
LoadedModule[58]=C:\fsx\fe.dll
LoadedModule[59]=C:\fsx\flight.dll
LoadedModule[60]=C:\fsx\fsui.dll
LoadedModule[61]=C:\fsx\g2d.dll
LoadedModule[62]=C:\fsx\g3d.dll
LoadedModule[63]=C:\fsx\gps.dll
LoadedModule[64]=C:\fsx\livingwater.dll
LoadedModule[65]=C:\fsx\main.dll
LoadedModule[66]=C:\fsx\multiplayer.dll
LoadedModule[67]=C:\fsx\panels.dll
LoadedModule[68]=C:\fsx\sim1.dll
LoadedModule[69]=C:\fsx\simprop.dll
LoadedModule[70]=C:\fsx\simscheduler.dll
LoadedModule[71]=C:\fsx\sound.dll
LoadedModule[72]=C:\fsx\symmap.dll
LoadedModule[73]=C:\fsx\terrain.dll
LoadedModule[74]=C:\fsx\fs-traffic.dll
LoadedModule[75]=C:\fsx\ui.dll
LoadedModule[76]=C:\fsx\util.dll
LoadedModule[77]=C:\fsx\visualfx.dll
LoadedModule[78]=C:\fsx\weather.dll
LoadedModule[79]=C:\fsx\window.dll
LoadedModule[80]=C:\fsx\xuipc.dll
LoadedModule[81]=C:\windows\SYSTEM32\MSWSOCK.dll
LoadedModule[82]=C:\windows\SYSTEM32\SHFOLDER.dll
LoadedModule[83]=C:\windows\SYSTEM32\VERSION.dll
LoadedModule[84]=C:\windows\SYSTEM32\POWRPROF.dll
LoadedModule[85]=C:\windows\SYSTEM32\DINPUT8.dll
LoadedModule[86]=C:\windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17227_none_dad9452e5bcb7986\gdiplus.dll
LoadedModule[87]=C:\windows\SYSTEM32\d3dx9_34.dll
LoadedModule[88]=C:\windows\SYSTEM32\d3dx10_34.dll
LoadedModule[89]=C:\windows\SYSTEM32\d3d9.dll
LoadedModule[90]=C:\windows\SYSTEM32\DSOUND.dll
LoadedModule[91]=C:\windows\SYSTEM32\WININET.dll
LoadedModule[92]=C:\windows\SYSTEM32\MSACM32.dll
LoadedModule[93]=C:\windows\SYSTEM32\MSIMG32.dll
LoadedModule[94]=C:\windows\SYSTEM32\iertutil.dll
LoadedModule[95]=C:\windows\SYSTEM32\kernel.appcore.dll
LoadedModule[96]=C:\windows\system32\uxtheme.dll
LoadedModule[97]=C:\windows\SYSTEM32\RICHED20.DLL
LoadedModule[98]=C:\windows\SYSTEM32\USP10.dll
LoadedModule[99]=C:\windows\SYSTEM32\msls31.dll
LoadedModule[100]=C:\windows\SYSTEM32\CRYPTSP.dll
LoadedModule[101]=C:\windows\system32\rsaenh.dll
LoadedModule[102]=C:\windows\SYSTEM32\bcrypt.dll
LoadedModule[103]=C:\windows\SYSTEM32\WINTRUST.dll
LoadedModule[104]=C:\windows\SYSTEM32\CRYPT32.dll
LoadedModule[105]=C:\windows\SYSTEM32\MSASN1.dll
LoadedModule[106]=C:\windows\SYSTEM32\clbcatq.dll
LoadedModule[107]=C:\windows\system32\wbem\wbemprox.dll
LoadedModule[108]=C:\windows\SYSTEM32\wbemcomn.dll
LoadedModule[109]=C:\windows\system32\wbem\wbemsvc.dll
LoadedModule[110]=C:\windows\system32\wbem\fastprox.dll
LoadedModule[111]=C:\windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[112]=C:\Windows\SYSTEM32\urlmon.dll
LoadedModule[113]=C:\windows\SYSTEM32\dxgi.dll
LoadedModule[114]=C:\windows\SYSTEM32\d3d10.dll
LoadedModule[115]=C:\windows\SYSTEM32\d3d10core.dll
LoadedModule[116]=C:\windows\SYSTEM32\d3d11.dll
LoadedModule[117]=C:\windows\SYSTEM32\aticfx32.dll
LoadedModule[118]=C:\windows\SYSTEM32\atiu9pag.dll
LoadedModule[119]=C:\windows\SYSTEM32\atiumdag.dll
LoadedModule[120]=C:\windows\SYSTEM32\atiumdva.dll
LoadedModule[121]=C:\windows\SYSTEM32\atiuxpag.dll
LoadedModule[122]=C:\windows\SYSTEM32\atidxx32.dll
LoadedModule[123]=C:\windows\SYSTEM32\D3DCompiler_34.dll
LoadedModule[124]=C:\windows\SYSTEM32\WindowsCodecs.dll
LoadedModule[125]=C:\windows\SYSTEM32\d3d10_1.dll
LoadedModule[126]=C:\windows\SYSTEM32\d3d10_1core.dll
LoadedModule[127]=C:\windows\SYSTEM32\WTSAPI32.DLL
LoadedModule[128]=C:\windows\SYSTEM32\WINSTA.dll
LoadedModule[129]=C:\Windows\SYSTEM32\gameux.dll
LoadedModule[130]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7\COMCTL32.dll
LoadedModule[131]=C:\Windows\SYSTEM32\XmlLite.dll
LoadedModule[132]=C:\Windows\SYSTEM32\msxml6.dll
LoadedModule[133]=C:\windows\System32\Wpc.dll
LoadedModule[134]=C:\windows\System32\NETAPI32.dll
LoadedModule[135]=C:\windows\SYSTEM32\Normaliz.dll
LoadedModule[136]=C:\windows\System32\wevtapi.dll
LoadedModule[137]=C:\windows\System32\netutils.dll
LoadedModule[138]=C:\windows\System32\srvcli.dll
LoadedModule[139]=C:\windows\System32\wkscli.dll
LoadedModule[140]=C:\windows\System32\SAMCLI.DLL
LoadedModule[141]=C:\Windows\System32\Windows.Globalization.dll
LoadedModule[142]=C:\Windows\System32\Bcp47Langs.dll
LoadedModule[143]=C:\Windows\System32\Windows.Web.dll
LoadedModule[144]=C:\windows\SYSTEM32\uiautomationcore.dll
LoadedModule[145]=C:\windows\SYSTEM32\sxs.dll
LoadedModule[146]=C:\windows\System32\MMDevApi.dll
LoadedModule[147]=C:\windows\SYSTEM32\AUDIOSES.DLL
LoadedModule[148]=C:\windows\SYSTEM32\HID.DLL
LoadedModule[149]=C:\windows\SYSTEM32\XInput9_1_0.dll
LoadedModule[150]=C:\windows\SYSTEM32\wdmaud.drv
LoadedModule[151]=C:\windows\SYSTEM32\ksuser.dll
LoadedModule[152]=C:\windows\SYSTEM32\AVRT.dll
LoadedModule[153]=C:\windows\SYSTEM32\msacm32.drv
LoadedModule[154]=C:\windows\SYSTEM32\midimap.dll
LoadedModule[155]=C:\windows\SYSTEM32\dinput.DLL
LoadedModule[156]=C:\windows\SYSTEM32\XInput1_4.dll
LoadedModule[157]=C:\fsx\bglmanx.dll
LoadedModule[158]=C:\windows\SYSTEM32\PSAPI.DLL
LoadedModule[159]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[160]=C:\windows\SYSTEM32\inetmib1.dll
LoadedModule[161]=C:\windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[162]=C:\windows\SYSTEM32\snmpapi.dll
LoadedModule[163]=C:\windows\SYSTEM32\WINNSI.DLL
LoadedModule[164]=C:\fsx\VistaMare\ViMaCoreX.dll
LoadedModule[165]=C:\fsx\VistaMare\bin\VMCX_SP2.dll
LoadedModule[166]=C:\fsx\VistaMare\bin\ViMaNET.dll
LoadedModule[167]=C:\fsx\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
LoadedModule[168]=C:\fsx\RAASPRO\RAASPRO.dll
LoadedModule[169]=C:\windows\SYSTEM32\Secur32.dll
LoadedModule[170]=C:\windows\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[171]=C:\windows\SYSTEM32\winhttp.dll
LoadedModule[172]=C:\windows\SYSTEM32\DNSAPI.dll
LoadedModule[173]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[174]=C:\Windows\System32\rasadhlp.dll
LoadedModule[175]=C:\windows\System32\fwpuclnt.dll
LoadedModule[176]=C:\windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[177]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[178]=C:\windows\SYSTEM32\MSDART.DLL
LoadedModule[179]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[180]=C:\Windows\SYSTEM32\comsvcs.dll
LoadedModule[181]=C:\Windows\SYSTEM32\msjetoledb40.dll
LoadedModule[182]=C:\Windows\SYSTEM32\msjet40.dll
LoadedModule[183]=C:\Windows\SYSTEM32\msjter40.dll
LoadedModule[184]=C:\Windows\SYSTEM32\mswstr10.dll
LoadedModule[185]=C:\Windows\SYSTEM32\MSJINT40.DLL
LoadedModule[186]=C:\windows\SYSTEM32\DPAPI.DLL
LoadedModule[187]=C:\Windows\SYSTEM32\mstext40.dll
LoadedModule[188]=C:\windows\SYSTEM32\mlang.dll
LoadedModule[189]=C:\windows\SYSTEM32\RAASAUDIO32.DLL
LoadedModule[190]=C:\windows\SYSTEM32\X3DAudio1_6.dll
LoadedModule[191]=C:\windows\SYSTEM32\xactengine3_4.dll
LoadedModule[192]=C:\windows\SYSTEM32\XAudio2_4.dll
LoadedModule[193]=C:\fsx\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[194]=C:\windows\SYSTEM32\MSVCR100.dll
LoadedModule[195]=C:\fsx\Modules\FSUIPC4.dll
LoadedModule[196]=C:\fsx\as_srv\as_btstrp.dll
LoadedModule[197]=C:\windows\SYSTEM32\mscoree.dll
LoadedModule[198]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[199]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
LoadedModule[200]=C:\windows\assembly\NativeImages_v2.0.50727_32\mscorlib\5bd3374f05d46ba0563f44d032209f08\mscorlib.ni.dll
LoadedModule[201]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll
LoadedModule[202]=C:\windows\SYSTEM32\imagehlp.dll
LoadedModule[203]=C:\windows\SYSTEM32\ncrypt.dll
LoadedModule[204]=C:\windows\SYSTEM32\NTASN1.dll
LoadedModule[205]=C:\windows\SYSTEM32\gpapi.dll
LoadedModule[206]=C:\Windows\SYSTEM32\cryptnet.dll
LoadedModule[207]=C:\windows\SYSTEM32\WLDAP32.dll
LoadedModule[208]=C:\fsx\as_srv\as_connect.dll
LoadedModule[209]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll
LoadedModule[210]=C:\windows\assembly\NativeImages_v2.0.50727_32\System\a500ec9c4638c6ba200d7b55324709f2\System.ni.dll
LoadedModule[211]=C:\windows\SYSTEM32\PROPSYS.dll
LoadedModule[212]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\f6ff4eab6e6bb587d62c3975fcbbca30\System.Drawing.ni.dll
LoadedModule[213]=C:\Windows\SYSTEM32\ieframe.dll
LoadedModule[214]=C:\Windows\SYSTEM32\mshtml.dll
LoadedModule[215]=C:\windows\system32\msimtf.dll
LoadedModule[216]=C:\windows\SYSTEM32\d2d1.dll
LoadedModule[217]=C:\windows\SYSTEM32\DWrite.dll
LoadedModule[218]=C:\windows\SYSTEM32\d3d10warp.dll
LoadedModule[219]=C:\fsx\VistaMare\bin\ViMaIScnX.dll
LoadedModule[220]=C:\fsx\GAUGES\PMDG_737NGX.DLL
LoadedModule[221]=C:\windows\SYSTEM32\WSOCK32.dll
LoadedModule[222]=C:\windows\SYSTEM32\MSVCP100.dll
LoadedModule[223]=C:\windows\SYSTEM32\XAudio2_7.dll
LoadedModule[224]=C:\fsx\FS2Crew2010\Versions\PMDG737NGX\Gauges\FS2CrewNGXButton.GAU
LoadedModule[225]=C:\fsx\libcurl.dll
LoadedModule[226]=C:\windows\SYSTEM32\FS2AUDIO.dll
LoadedModule[227]=C:\fsx\GAUGES\XGauge.DLL
LoadedModule[228]=C:\fsx\GAUGES\PMDG_737NGX_3.DLL
LoadedModule[229]=C:\fsx\Gauges\PMDG_737NGX_2.dll
LoadedModule[230]=C:\windows\SYSTEM32\OLEACC.dll
LoadedModule[231]=C:\windows\system32\napinsp.dll
LoadedModule[232]=C:\windows\system32\pnrpnsp.dll
LoadedModule[233]=C:\windows\system32\NLAapi.dll
LoadedModule[234]=C:\windows\System32\winrnr.dll
LoadedModule[235]=C:\windows\SYSTEM32\ntmarta.dll
LoadedModule[236]=C:\windows\SYSTEM32\icmp.Dll
LoadedModule[237]=C:\windows\SYSTEM32\msadp32.acm
LoadedModule[238]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\27dc8e491e32361eaff0b88f0befc197\System.Configuration.ni.dll
LoadedModule[239]=C:\windows\assembly\NativeImages_v2.0.50727_32\System.Xml\8006a5df62f0c127d15db16d3a8c68f8\System.Xml.ni.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=BEX
AppName=Microsoft Flight Simulator®
AppPath=C:\fsx\fsx.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=5B0B5FEC0FEF5400B720718FE7EBC216

Share this post


Link to post
Share on other sites

A StackHash is a non-module type crash as there is no such module on your computer system. A StackHash just happens when something in your FSX configuration is messed up. Your computer system doesn't like that configuration or bad texture or missing file. FSX was suppose to do something and it couldn't do it so there was a StackHash to shut the program down. Many have Windows 8 working well. There could be some sharing or ownership or trusting issues as Windows 8.1 came with many more security features to keep you safe from evil people on the Internet who want to hack into your system. Unfortunately, you have to run your own investigation as only you can see your computer system and only you can see your configurations. This is why we have the AVSIM CTD Guide. Moving the FSX.cfg, the dll.xml and the exe.xml (if it exists) to a temporary folder and running FSX again will bring FSX back to the basics. It will be like reinstalling FSX. If the problem goes away, it was one of those files that caused your problem.

 

Make sure your USB ports, system bus, and Intel chipset is up-to-date.

 

Hope this helps.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...