Jump to content
Sign in to follow this  
raymond66

FSXSE crash after using Shadowplay then in FSX Pressing Alt+Enter

Recommended Posts

Hi,

In the last few days, after using Nvidia Shadowplay (even for a few seconds) to record a video of FSX SE, if then I press Alt+Enter (to go from full screen to a window of FSX, a back to full screen...) a few times (usually 3 times), FSX starts going into a window, but it is all black, the sounds cuts for less than a second, then after ~20 seconds FSX SE crashes.

I have Windows 7, and FSX SE is in a dedicated drive D: (so not C:).

This never happened until the last few days: I could use shadowplay, and switch from full screen to a window and back, many many times without problems. I do this to go to the PC and use other applications, change music, answer emails, etc...

If I don't use shadowplay, I can use alt+enter many times without problems.

There was a Nvidia Geforce experience recently, but Nvidia Geforce experience won't allow the use of a previous version, and when in a previous version, if there is a new version, launching Nvidia Geforce experience will update it to the new version!

I wonder if there is a solution to this problem. Has anybody experienced it?

 

Here are the errors I had so far:

1.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x59ac
Faulting application start time: 0x01d4e721e8e01a75
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: 10f0fb74-531f-11e9-b22d-28c2dd8eb0ae

 

2.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ntdll.dll, version: 6.1.7601.24387, time stamp: 0x5c7f3802
Exception code: 0xc0000005
Fault offset: 0x00033b4e
Faulting process id: 0x4df4
Faulting application start time: 0x01d4e740332e817c
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b2b9fb4d-533e-11e9-b22d-28c2dd8eb0ae

 

3.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.6195, time stamp: 0x4dcddbf3
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0xf18
Faulting application start time: 0x01d4e7c399bdbd45
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
Report Id: ca701545-53ea-11e9-bf5b-28c2dd8eb0ae

 

4.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: ai_player.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x0003621c
Faulting process id: 0x1760
Faulting application start time: 0x01d4e7f9cff37234
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\ai_player.dll
Report Id: 8d1f8d09-53ed-11e9-9304-28c2dd8eb0ae

 

5.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x16b0
Faulting application start time: 0x01d4e7fafb137b35
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: cef2500f-53ee-11e9-9304-28c2dd8eb0ae

 

6.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x25e8
Faulting application start time: 0x01d4e7fc3dfeb737
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: 3bacac89-53f0-11e9-9304-28c2dd8eb0ae

 

7.

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x2374
Faulting application start time: 0x01d4e7ff2735064a
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: 63eab3b0-53f3-11e9-9304-28c2dd8eb0ae

Share this post


Link to post
Share on other sites

The AVSIM CTD Guide provides some possible solutions to your faulting modules.  The terrain.dll error usually is called when you have Autogen set too high for your simulator/system.  The ai_player is associated with AI textures.  Perhaps you have AI installed that have textures not compatible with DX10 Preview (or made for earlier versions of FS)?  The MSVCR80.dll error indicates something was not installed properly.  The MSVCR80.dll is part of the Microsoft Visual C++ 2005 package and Microsoft uses it to make sure your application is installed correctly.  If not, it will throw an error. 

For the ntdll.dll error, there are literally thousands of possibilities but mostly you have your settings FSX/Display driver settings set too high.  See the AVSIM FSX Configuration Guide for suggested settings.

 


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

Hi Jim,

Thank you for your reply. The AVSIM CTD guide is indeed good! I did try most things until page 11. In the process of testing, I got 4 crashes, all involving terrain.dll: started FSX SE, started a flight, pressed alt+enter about 10 times, no crash, then used shadowplay for a few seconds, pressed alt+enter up to 4 times (sometimes I needed to use shadowplay a 2nd time for a few seconds), and the crash happened: first in full screen, then in a maximised window but all black, sounds cut for < 1 second, then still black with sound of the aircraft, then after ~20 secs, CTD. So, crash only after using shadowplay; a few days ago doing the same was fine!

To me though, the problem must come from the Nvidia GeForce experience update in late March 2019, as I hadn't changed anything in the FSX SE, and I use it in the same way as before with Nvidia Share/shadowplay. It didn't happen before that update. But GeForce experience won't allow to reinstall the previous version!

SFC /scannow found no problem.

I removed FSX.cfg, crash still happened

I removed scenery.cfg, crash still happened (I put both my originals back of course)

I don't have any AI aircraft software, no FSDT, no big airliners, but several ORBX add-ons (last Orbx addons installed about 3 months ago!), a few other scenery add-onds, a few planes addons, but no new ones in the last month either. I don't have FSUIPC. I have Microsoft .NET Framework 4.6.1 .

As AV, I use Security Essentials, which never caused problems.

 

My system: built by Chillblast, January 2016

- Intel Core i7 5960X Haswell-E 8-Cored 3.50GHz Processor (Overclocked to 4.3 GHz, stable)
- Corsair Hydro Series H100i GTX Extreme Performance Liquid CPU Cooler
- Asus Rampage V Extreme Intel X99 Motherboard
- 64GB Crucial DDR4 2133MHz Memory (8 x 8GB sticks)
- Asus GeForce GTX 980 TI 6GB STRIX OC Direct CU II
- 512GB Samsung 850 Pro Solid State Drive: OS and programs
- 2TB Samsung 850 Pro Solid State Drive: sims
- 2 Western Digital BLACK SERIES 3TB 3.5" 7200RPM Internal Hard Drive in RAID 1 Configuration
- Corsair AX 1200i 80 PLS Platinum Modular 1200W PSU
- Creative Sound Blaster ZX Gaming Soundcard
- Windows 7 Professional 64 bit
 

What I did:

1. DxDiag

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
        Sound Tab 2: No problems found.
        Sound Tab 3: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

I later ran dxdiag and all fine, no errors.

 

2. AppCrashView, for my latest crash:

Version=1
EventType=APPCRASH
EventTime=131986240447012844
ReportType=2
Consent=1
UploadTime=131986240448022901
ReportIdentifier=8eaf357f-54bc-11e9-9b1f-28c2dd8eb0ae
IntegratorReportIdentifier=8eaf357e-54bc-11e9-9b1f-28c2dd8eb0ae
WOW64=1
Response.BucketId=123571580
Response.BucketTable=25
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.62615.0
Sig[2].Name=Application Timestamp
Sig[2].Value=559f9a9a
Sig[3].Name=Fault Module Name
Sig[3].Value=terrain.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.62615.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=559f9ab4
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00058122
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=0a9e
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=0a9e
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789
UI[2]=D:\Steam\steamapps\common\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]=D:\Steam\steamapps\common\FSX\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[18]=D:\Steam\steamapps\common\FSX\steam_api.dll
LoadedModule[19]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[20]=C:\Windows\syswow64\ole32.dll
LoadedModule[21]=C:\Windows\system32\apphelp.dll
LoadedModule[22]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[23]=C:\Windows\system32\UxTheme.dll
LoadedModule[24]=C:\Windows\system32\WINMM.dll
LoadedModule[25]=C:\Windows\system32\samcli.dll
LoadedModule[26]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[27]=C:\Windows\system32\MSACM32.dll
LoadedModule[28]=C:\Windows\system32\VERSION.dll
LoadedModule[29]=C:\Windows\system32\sfc.dll
LoadedModule[30]=C:\Windows\system32\sfc_os.DLL
LoadedModule[31]=C:\Windows\syswow64\USERENV.dll
LoadedModule[32]=C:\Windows\syswow64\profapi.dll
LoadedModule[33]=C:\Windows\system32\dwmapi.dll
LoadedModule[34]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[35]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[36]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[37]=C:\Windows\syswow64\urlmon.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[43]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[44]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[45]=C:\Windows\syswow64\iertutil.dll
LoadedModule[46]=C:\Windows\syswow64\WININET.dll
LoadedModule[47]=C:\Windows\system32\MPR.dll
LoadedModule[48]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[49]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[50]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[51]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[52]=C:\Windows\system32\mscms.dll
LoadedModule[53]=C:\Windows\system32\DDRAW.dll
LoadedModule[54]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[55]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[56]=C:\Windows\syswow64\IMM32.dll
LoadedModule[57]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[58]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[59]=C:\Windows\syswow64\NSI.dll
LoadedModule[60]=C:\Windows\system32\msi.dll
LoadedModule[61]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[62]=D:\Steam\steamapps\common\FSX\language.dll
LoadedModule[63]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[64]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[65]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[66]=C:\Windows\system32\WINNSI.DLL
LoadedModule[67]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[68]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[69]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[70]=C:\Windows\system32\Secur32.dll
LoadedModule[71]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.DLL
LoadedModule[72]=C:\Windows\System32\wshtcpip.dll
LoadedModule[73]=C:\Program Files (x86)\Steam\Steam2.dll
LoadedModule[74]=C:\Windows\system32\DbgHelp.dll
LoadedModule[75]=C:\Program Files (x86)\Steam\CSERHelper.dll
LoadedModule[76]=C:\Program Files (x86)\Steam\gameoverlayrenderer.dll
LoadedModule[77]=D:\Steam\steamapps\common\FSX\API.DLL
LoadedModule[78]=D:\Steam\steamapps\common\FSX\ablscpt.dll
LoadedModule[79]=D:\Steam\steamapps\common\FSX\flight.dll
LoadedModule[80]=D:\Steam\steamapps\common\FSX\ai_player.dll
LoadedModule[81]=D:\Steam\steamapps\common\FSX\acontain.dll
LoadedModule[82]=D:\Steam\steamapps\common\FSX\controls.dll
LoadedModule[83]=C:\Windows\system32\DINPUT8.dll
LoadedModule[84]=D:\Steam\steamapps\common\FSX\fsui.dll
LoadedModule[85]=D:\Steam\steamapps\common\FSX\atc.dll
LoadedModule[86]=D:\Steam\steamapps\common\FSX\facilities.dll
LoadedModule[87]=D:\Steam\steamapps\common\FSX\demo.dll
LoadedModule[88]=D:\Steam\steamapps\common\FSX\main.dll
LoadedModule[89]=D:\Steam\steamapps\common\FSX\fe.dll
LoadedModule[90]=D:\Steam\steamapps\common\FSX\util.dll
LoadedModule[91]=D:\Steam\steamapps\common\FSX\simprop.dll
LoadedModule[92]=D:\Steam\steamapps\common\FSX\g2d.dll
LoadedModule[93]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[94]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[95]=C:\Windows\system32\d3d9.dll
LoadedModule[96]=C:\Windows\system32\d3d8thk.dll
LoadedModule[97]=D:\Steam\steamapps\common\FSX\g3d.dll
LoadedModule[98]=D:\Steam\steamapps\common\FSX\panels.dll
LoadedModule[99]=D:\Steam\steamapps\common\FSX\multiplayer.dll
LoadedModule[100]=D:\Steam\steamapps\common\FSX\sdkencryptedappticket.dll
LoadedModule[101]=D:\Steam\steamapps\common\FSX\ui.dll
LoadedModule[102]=D:\Steam\steamapps\common\FSX\sound.dll
LoadedModule[103]=D:\Steam\steamapps\common\FSX\sim1.dll
LoadedModule[104]=D:\Steam\steamapps\common\FSX\simscheduler.dll
LoadedModule[105]=D:\Steam\steamapps\common\FSX\visualfx.dll
LoadedModule[106]=D:\Steam\steamapps\common\FSX\window.dll
LoadedModule[107]=D:\Steam\steamapps\common\FSX\terrain.dll
LoadedModule[108]=D:\Steam\steamapps\common\FSX\weather.dll
LoadedModule[109]=C:\Windows\system32\DSOUND.dll
LoadedModule[110]=C:\Windows\system32\POWRPROF.dll
LoadedModule[111]=D:\Steam\steamapps\common\FSX\symmap.dll
LoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.24385_none_5c0ad4dfa00a8e0a\gdiplus.dll
LoadedModule[113]=C:\Windows\system32\MSIMG32.dll
LoadedModule[114]=D:\Steam\steamapps\common\FSX\xuipc.dll
LoadedModule[115]=D:\Steam\steamapps\common\FSX\livingwater.dll
LoadedModule[116]=D:\Steam\steamapps\common\FSX\fs-traffic.dll
LoadedModule[117]=D:\Steam\steamapps\common\FSX\gps.dll
LoadedModule[118]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[119]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[120]=C:\Windows\system32\rsaenh.dll
LoadedModule[121]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[122]=C:\Windows\system32\dxgi.dll
LoadedModule[123]=C:\Windows\system32\d3d11.dll
LoadedModule[124]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[125]=C:\Windows\system32\nvd3dum.dll
LoadedModule[126]=C:\Windows\system32\bcrypt.dll
LoadedModule[127]=C:\Windows\system32\ncrypt.dll
LoadedModule[128]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[129]=C:\Windows\system32\nvspcap.dll
LoadedModule[130]=C:\Windows\system32\ntmarta.dll
LoadedModule[131]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[132]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[133]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[134]=C:\Windows\system32\d3d10_1.dll
LoadedModule[135]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[136]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[137]=C:\Windows\system32\GPAPI.dll
LoadedModule[138]=C:\Windows\system32\cryptnet.dll
LoadedModule[139]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[140]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[141]=C:\Windows\system32\wbemcomn2.dll
LoadedModule[142]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[143]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[144]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[145]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[146]=C:\Windows\system32\winbrand.dll
LoadedModule[147]=C:\Windows\system32\nvapi.dll
LoadedModule[148]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[149]=C:\Windows\system32\WINSTA.dll
LoadedModule[150]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[151]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.24380_none_2b2053e245779417\COMCTL32.dll
LoadedModule[152]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[153]=C:\Windows\SysWOW64\wer.dll
LoadedModule[154]=C:\Windows\System32\Wpc.dll
LoadedModule[155]=C:\Windows\System32\wevtapi.dll
LoadedModule[156]=C:\Windows\System32\msxml6.dll
LoadedModule[157]=C:\Windows\system32\SAMLIB.dll
LoadedModule[158]=C:\Windows\system32\netutils.dll
LoadedModule[159]=D:\Steam\steamapps\common\FSX\uiautomationcore.dll
LoadedModule[160]=C:\Windows\system32\OLEACC.dll
LoadedModule[161]=C:\Windows\System32\MMDevApi.dll
LoadedModule[162]=C:\Windows\System32\PROPSYS.dll
LoadedModule[163]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[164]=C:\Windows\system32\RICHED20.DLL
LoadedModule[165]=C:\Windows\system32\HID.DLL
LoadedModule[166]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[167]=C:\Windows\system32\wdmaud.drv
LoadedModule[168]=C:\Windows\system32\ksuser.dll
LoadedModule[169]=C:\Windows\system32\AVRT.dll
LoadedModule[170]=C:\Windows\system32\msacm32.drv
LoadedModule[171]=C:\Windows\system32\midimap.dll
LoadedModule[172]=C:\Windows\system32\dinput.DLL
LoadedModule[173]=C:\Windows\System32\wship6.dll
LoadedModule[174]=D:\Steam\steamapps\common\FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[175]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[176]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[177]=C:\Windows\system32\DNSAPI.dll
LoadedModule[178]=C:\Windows\System32\netprofm.dll
LoadedModule[179]=C:\Windows\System32\nlaapi.dll
LoadedModule[180]=C:\Windows\system32\dhcpcsvc6.DLL
LoadedModule[181]=C:\Windows\System32\npmproxy.dll
LoadedModule[182]=C:\Windows\system32\dhcpcsvc.DLL
LoadedModule[183]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[184]=C:\Windows\system32\rasadhlp.dll
LoadedModule[185]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[186]=C:\Windows\system32\credssp.dll
LoadedModule[187]=C:\Windows\SysWOW64\schannel.dll
LoadedModule[188]=C:\Windows\system32\SensApi.dll
LoadedModule[189]=C:\Windows\system32\WINHTTP.dll
LoadedModule[190]=C:\Windows\system32\webio.dll
LoadedModule[191]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[192]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[193]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[194]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[195]=C:\Windows\system32\msimtf.dll
LoadedModule[196]=C:\Windows\system32\msls31.dll
LoadedModule[197]=C:\Windows\system32\d2d1.dll
LoadedModule[198]=C:\Windows\system32\DWrite.dll
LoadedModule[199]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[200]=C:\Windows\system32\MLANG.dll
LoadedModule[201]=C:\Windows\system32\SXS.DLL
LoadedModule[202]=C:\Windows\SysWOW64\jscript9.dll
LoadedModule[203]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[204]=D:\Steam\steamapps\common\FSX\gauges\Bendix_king_radio.dll
LoadedModule[205]=D:\Steam\steamapps\common\FSX\gauges\Cessna172.dll
LoadedModule[206]=D:\Steam\steamapps\common\FSX\gauges\Cessna.dll
LoadedModule[207]=D:\Steam\steamapps\common\FSX\gauges\Cessna182s.dll
LoadedModule[208]=D:\Steam\steamapps\common\FSX\gauges\CessnaWAlpha.dll
LoadedModule[209]=D:\Steam\steamapps\common\FSX\gauges\Bell_206B.dll
LoadedModule[210]=C:\Windows\system32\msadp32.acm
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=123571580/nBucketTable=25/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Flight Simulator®
AppPath=D:\Steam\steamapps\common\FSX\fsx.exe
 

3. Windows 7 Events viewer

Log Name:      Application
Source:        Application Error
Date:          01/04/2019 21:27:24
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      raymond-PC
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x4f0
Faulting application start time: 0x01d4e8c8ea4cd5a5
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: 8eaf357e-54bc-11e9-9b1f-28c2dd8eb0ae
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-04-01T20:27:24.000000000Z" />
    <EventRecordID>100641</EventRecordID>
    <Channel>Application</Channel>
    <Computer>raymond-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9a9a</Data>
    <Data>terrain.dll</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9ab4</Data>
    <Data>c0000005</Data>
    <Data>00058122</Data>
    <Data>4f0</Data>
    <Data>01d4e8c8ea4cd5a5</Data>
    <Data>D:\Steam\steamapps\common\FSX\fsx.exe</Data>
    <Data>D:\Steam\steamapps\common\FSX\terrain.dll</Data>
    <Data>8eaf357e-54bc-11e9-9b1f-28c2dd8eb0ae</Data>
  </EventData>
</Event>

 

Any suggestion?

Regards, 

 

Share this post


Link to post
Share on other sites

As mentioned earlier, the terrain.dll error is caused mostly by high settings when using FSX.  Of course, you could have a texture belonging to an incompatible scenery installed or an incompatible object but mostly it is caused by high settings in FSX.  Shadowplay is part of Nvidia and you will have to go to their forums to resolve that issue.  I found the following video regarding using Shadowplay with FSX -

 

1 hour ago, raymond66 said:

To me though, the problem must come from the Nvidia GeForce experience update in late March 2019, as I hadn't changed anything in the FSX SE, and I use it in the same way as before with Nvidia Share/shadowplay. It didn't happen before that update. But GeForce experience won't allow to reinstall the previous version!

When you uninstall your Nvidia display drivers, GEForce Experience should be removed too.  Then you can install a previous version of the Nvidia display drivers.  However, I doubt GE Force Experience is the problem.


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

Hi Jim,

Thank you for your help: you are the only one, so priceless.

So I tried to lower the FSX SE settings:

Global texture resolution: to the left, so basically none

Aircraft: very low

Scenery settings: ALL to the left: So a World of blurries.

And the crash after shadowplay, then alt+enter still occurs, terrain.dll!

I can't get any lower in settings, I think, and the crash still occurs. It can't be settings.

I think next step is to uninstall GE force and Nvidia drivers with Display Driver Uninstaller DDU, as advised 2 years ago by my PC manufacturer, Chillblast. At the time it did the trick for another problem.

 

I send a feedback to Nvidia via GeForce, let's see...

 

Have you got any idea?

 

Events viewer:

Log Name:      Application
Source:        Application Error
Date:          02/04/2019 21:48:09
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      raymond-PC
Description:
Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: terrain.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00058122
Faulting process id: 0x9d0
Faulting application start time: 0x01d4e99505493949
Faulting application path: D:\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: D:\Steam\steamapps\common\FSX\terrain.dll
Report Id: 9f0834d2-5588-11e9-8c02-28c2dd8eb0ae
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2019-04-02T20:48:09.000000000Z" />
    <EventRecordID>100770</EventRecordID>
    <Channel>Application</Channel>
    <Computer>raymond-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>fsx.exe</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9a9a</Data>
    <Data>terrain.dll</Data>
    <Data>10.0.62615.0</Data>
    <Data>559f9ab4</Data>
    <Data>c0000005</Data>
    <Data>00058122</Data>
    <Data>9d0</Data>
    <Data>01d4e99505493949</Data>
    <Data>D:\Steam\steamapps\common\FSX\fsx.exe</Data>
    <Data>D:\Steam\steamapps\common\FSX\terrain.dll</Data>
    <Data>9f0834d2-5588-11e9-8c02-28c2dd8eb0ae</Data>
  </EventData>
</Event>

Share this post


Link to post
Share on other sites
1 hour ago, raymond66 said:

And the crash after shadowplay, then alt+enter still occurs, terrain.dll!

I can't get any lower in settings, I think, and the crash still occurs. It can't be settings.

Well, it certainly does not look like it but there may be other external factors that is taking up resources.  FSX is a 32-bit application and it has a hard time managing resources sometimes.  I really have no other suggestions as they are all in the CTD Guide.  Maybe someone who also uses shadowplay will come on and assist.


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

Hi Jim,

Well, after uninstalling then reinstalling the Nvidia drivers + GeForce Experience, the CTD still happens.

As low settings in FSX SE don't solve it, I am at a loss to what is the cause... maybe the GeForce Experience version itself, so of course the latest version gets installed, so the problem remains.

 

Regards,

Edited by raymond66

Share this post


Link to post
Share on other sites

Don't load the GeForce Experience. There have been reports of it causing some CTD's.  Try one thing at a time and I'm sure you will find the culprit.

One question, however. Why are you using Alt-Enter? 

 


Thank you.

Rick

 $Silver Donor

EAA 1317610   I7-7700K @ 4.5ghz, MSI Z270 Gaming MB,  32gb 3200,  Geforce RTX2080 Super O/C,  28" Samsung 4k Monitor,  Various SSD, HD, and peripherals

 

 

Share this post


Link to post
Share on other sites
1 minute ago, 188AHC said:

Don't load the GeForce Experience. There have been reports of it causing some CTD's.  Try one thing at a time and I'm sure you will find the culprit.

One question, however. Why are you using Alt-Enter? 

But without GeForce Experience there is no recording capability from my Nvidia GPU, recording is now called Share, former shadowplay. So, no GeForce Experience = no Share/shadowplay. A few days ago, all was fine. Nvidia Geforce experience was updated recently; Nvidia Geforce experience won't allow the use of a previous version, and when there is a new version, launching Nvidia Geforce experience will update it to the new version! So I can't put the previous version back! Nvidia website doesn't have older versions of GeForce Experience; the only older versions the give are older drivers versions!

Alt+Enter toggles from full screen to window, and vice versa.

Share this post


Link to post
Share on other sites

I don't use GeForce Experience so I'm not familiar with its recording function. 

I still think you should try to run without it to see if it is the problem.

I also know what alt-enter does and it has always been a problem for some users in FSX. 


Thank you.

Rick

 $Silver Donor

EAA 1317610   I7-7700K @ 4.5ghz, MSI Z270 Gaming MB,  32gb 3200,  Geforce RTX2080 Super O/C,  28" Samsung 4k Monitor,  Various SSD, HD, and peripherals

 

 

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...