P3D 3.4.14 hangs when using other applications

[busychild 0]

Hi guys,

 

i've a really strange issue with P3D 3.4.14 (i updated P3D and my graphic card drivers):

 

Prepar3D Client: 3.4.14

NVidia Drivers: Latest (375.95)

Windows 10

i7-6900k

GTX1080

 

Everytime i open up a document in photoshop (and sometimes after closing photoshop) Prepar3D hangs (it's not directly crashing, just not responding. I still hear the sound but can't interact anymore). If i click on the P3D screen it says that P3D isn't responding anymore and the only opportunity i have is to close and restart it. It happens every time when i'm using Photoshop. I've testet several other programs and could reproduce the issue also with the Software "Wirecast" (which is a broadcasting software) but until now not with other programs.

 

There is no crash log in the event viewer (just one after i close P3D manually that says that Prepar3D.exe couldn't run on windows anymore, but with no further information). 

 

My guess is, that it has something to do with applications which are also using the graphic card (but i'm not totally sure).

 

I tried the following to make sure it isn't related to add ons or settings:

- Completely removed all entries from the exe.xml and dll.xml files (in both directories)

- Removed all other simobject entries from the simobject.cfg file

- Removed the prepar3d.cfg file and let P3D generate a new one

- Made a fresh install of the P3D Client

 

After that i also removed all of the following files (as suggested in another thread):

 

- %PROGRAMDATA%\Lockheed Martin\Prepar3D v3

- %LOCALAPPDATA%\Lockheed Martin\Prepar3D v3

- %APPDATA%\Lockheed Martin\Prepar3D v3

- %USERPROFILE%\Documents\Prepar3D v3 Files

 

Nothing has helped yet.

 

Any ideas?

 

Best regards

 

Florian

[Jim Young 2,356]

 

 

Everytime i open up a document in photoshop (and sometimes after closing photoshop) Prepar3D hangs (it's not directly crashing, just not responding.

 

I thought PhotoShop is a resource intensive application.  Anytime it is open it uses a lot of resources.  P3D is just as resource intensive as Photoshop.  It's just like if you have your web browser open while using P3D and you have several tabs open with different websites (like me)(makes it quick and easy to check on news stories, etc. and do AVSIM chores at the same time.  The tabs do not have to be open, just loaded.  Some websites will literally bring your computer down to its knees as it loads videos and graphics and makes constant updates to the sites so you have the latest and greatest information.  I'll be playing one of the Microsoft games like Solitaire once in a while and have my web browser open too and suddenly I can hardly move my cursor.  There are other things running in the background too like any anti-virus or anti-malware program to stop any attacks.  Microsoft Essentials does it too in addition to any anti-virus or anti-malware program you might have installed.  So that's what is happening.  I do not know of any solutions other than to run your P3D by itself on your main computer and use a laptop (a very powerful laptop) to look at Photoshop stuff.

 

Best regards,

Jim

[Jimm 437]

I thought PhotoShop is a resource intensive application.  Anytime it is open it uses a lot of resources.  P3D is just as resource intensive as Photoshop.  It's just like if you have your web browser open while using P3D and you have several tabs open with different websites (like me)(makes it quick and easy to check on news stories, etc. and do AVSIM chores at the same time.  The tabs do not have to be open, just loaded.  Some websites will literally bring your computer down to its knees as it loads videos and graphics and makes constant updates to the sites so you have the latest and greatest information.  I'll be playing one of the Microsoft games like Solitaire once in a while and have my web browser open too and suddenly I can hardly move my cursor.  There are other things running in the background too like any anti-virus or anti-malware program to stop any attacks.  Microsoft Essentials does it too in addition to any anti-virus or anti-malware program you might have installed.  So that's what is happening.  I do not know of any solutions other than to run your P3D by itself on your main computer and use a laptop (a very powerful laptop) to look at Photoshop stuff.

 

Best regards,

Jim

Jim, if I may.  Photoshop, is in fact, very resource intesive from the standpoint that it uses a "scratch disk" for writing historical data to once a session is initiated.  Ther eis a very good chance that the OP's Photoshop scratch disk is the same as where the sim is.  Photoshop will carve out a good percentage of disk space for scratch space, if it isn't manually controlled by the user.  Aside from the scratch disk, Photoshop also likes to communicate constantly online, so there is that load to contend with, especially if users are running Photoshop CC.

 

If I were the OP, I would check that wonderful systray for apps running, as well as checking the task manager, which I am sure is chock full of Adobe processes while P3D is running.

[busychild 0]

Thanks guys but please don't focus on photoshop too much (i'm totally aware of the fact that photoshop is using much resources) - as i said i could easily reproduce the issue with a sofware called "Wirecast" and i assume i could reproduce it with other applications as well. There is another topic at the p3d forums which may be the same issue that i'm facing (http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=122335).

 

Currently i think one of these things messes it up:

• Windows Update
• NVidia Driver Update

Yesterday i tried to downgrade from 3.4.14 to 3.5 but the issue remains (so i would assume it has nothing to do with the p3d version).

[toprob 105]

Currently i think one of these things messes it up:

• Windows Update
• NVidia Driver Update

 

 

I think you may be right, I've had the same problem with P3D3.4, using my normal scenery development tools -- Whisplacer etc. Sooner or later I find that P3D is not responding, never struck that with any previous version.

But recent NVidia updates have caused all sorts of little issues, which come with one update and go with the next, so I wouldn't be surprised if this was related.

[Korundar 12]

I have the same issue with 3.3.5. Suddenly P3D stops responding and simply closes without errors. I always have only Chrome running and I think it's something related with the nVidia drivers too, in my case 372.90

 

I'm able to complete 1 flight out of 4... don't know what to do. 

[Jim Young 2,356]

Thanks guys but please don't focus on photoshop too much (i'm totally aware of the fact that photoshop is using much resources) - as i said i could easily reproduce the issue with a sofware called "Wirecast" and i assume i could reproduce it with other applications as well. There is another topic at the p3d forums which may be the same issue that i'm facing (http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=122335).

 

Currently i think one of these things messes it up:

• Windows Update
• NVidia Driver Update

Yesterday i tried to downgrade from 3.4.14 to 3.5 but the issue remains (so i would assume it has nothing to do with the p3d version).

Whenever you update P3D, it requires updates to certain add-ons before it will work properly.  Orbx, FSDT, and FSUIPC are three I know for sure that requires updates (and they have been updated).  Not sure what happens if you go back to a previous version (you can do that?) and the previous version required previous version updates for Orbx, FSDT, and FSUIPC.  There is a lot of software that is not fully compatible with P3Dv3 so if you have any addons that were not made for P3Dv3, then you might want to disable those programs temporarily until you can get this issue fixed.

 

I have the latest version of P3D and had problems with Orbx ObjectFlow and FSDT stuff but not with FSUIPC.  I also could not use AS16 until they updated that program.  I have updated to the latest Nvidia driver (as I do not use SLI) and Windows has updated since I installed the update.  If there was a "bad" Windows Update I would expect everyone who updated to the latest version to also get crashes.

 

Whenever you have a crash or freeze, you need to check out page 10 of the AVSIM CTD Guide where it explains how to fix most crashes/freezes in FSX and P3D.  The guide explains you need to rename the P3D.cfg and the dll.xml, restart P3D and the P3D.cfg will be rebuilt (but not the dll.xml as it is not a default P3D program).  There are two dll.xml's in P3D for most.  One where the P3D.cfg is located and one where the scenery.cfg is located.  Both should be renamed or moved to a temporary directory just to see if this fixes the problem.  If it does, then there is a problem with one of the modules loaded by the dll.xml into P3D (most likely cause).

 

Best regards,

Jim

[busychild 0]

Whenever you update P3D, it requires updates to certain add-ons before it will work properly.  ...

 

Hi Jim,

 

thanks for your feedback - i already removed all configuration files (exe.xml, dll.xml, prepar3d.cfg and all folders which are containing files related to add ons) to try it with some kind of a "vanilla" p3d. So there were no add ons and no tweaks running at the time of my testings. Also there were no sceneries, simobjects or other additional stuff running.

 

Unfortunately the ctd guide doesn't helped in my case (i went through the "freezes" section already). Also p3d doesn't crash directly, it's just not responsing anymore. There is also no error log entry in the event viewer as long as i don't close p3d manually. Then the event viewer just shows an error "AppHang" and no information about why the app freezes. Here is my log from AppCrashView:

Version=1
EventType=AppHangB1
EventTime=131242466461455841
ReportType=3
Consent=1
UploadTime=131242466474738592
ReportIdentifier=2e6b3713-b047-11e6-8400-80a589a07173
IntegratorReportIdentifier=2e6b3714-b047-11e6-8400-80a589a07173
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=00004808-0001-0033-4886-62ce5344d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//10//27:17:31:14!6cc50!Prepar3D.exe
BootId=4294967295
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=3.4.14.18870
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=581239e2
Sig[3].Name=Absturzsignatur
Sig[3].Value=a258
Sig[4].Name=Absturztyp
Sig[4].Value=134217984
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=10.0.14393.2.0.0.768.101
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=1031
DynamicSig[22].Name=Zusätzliche Absturzsignatur 1
DynamicSig[22].Value=a258262b01b9d7943c8ef7caac5cff02
DynamicSig[23].Name=Zusätzliche Absturzsignatur 2
DynamicSig[23].Value=ece9
DynamicSig[24].Name=Zusätzliche Absturzsignatur 3
DynamicSig[24].Value=ece94ec14701a1b57b2a7446e1763af0
DynamicSig[25].Name=Zusätzliche Absturzsignatur 4
DynamicSig[25].Value=a258
DynamicSig[26].Name=Zusätzliche Absturzsignatur 5
DynamicSig[26].Value=a258262b01b9d7943c8ef7caac5cff02
DynamicSig[27].Name=Zusätzliche Absturzsignatur 6
DynamicSig[27].Value=ece9
DynamicSig[28].Name=Zusätzliche Absturzsignatur 7
DynamicSig[28].Value=ece94ec14701a1b57b2a7446e1763af0
UI[3]=Prepar3D exe reagiert nicht
UI[4]=Wenn Sie das Programm schließen, gehen möglicherweise Informationen verloren.
UI[5]=Programm schließen
UI[6]=Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=E:\Prepar3D\Prepar3D.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\AcGenral.DLL
LoadedModule[6]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[7]=C:\WINDOWS\System32\sechost.dll
LoadedModule[8]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[9]=C:\WINDOWS\System32\SspiCli.dll
LoadedModule[10]=C:\WINDOWS\System32\CRYPTBASE.dll
LoadedModule[11]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[12]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[13]=C:\WINDOWS\System32\combase.dll
LoadedModule[14]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[15]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[16]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[17]=C:\WINDOWS\System32\USER32.dll
LoadedModule[18]=C:\WINDOWS\System32\win32u.dll
LoadedModule[19]=C:\WINDOWS\System32\ole32.dll
LoadedModule[20]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[21]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[22]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[23]=C:\WINDOWS\System32\cfgmgr32.dll
LoadedModule[24]=C:\WINDOWS\System32\windows.storage.dll
LoadedModule[25]=C:\WINDOWS\System32\powrprof.dll
LoadedModule[26]=C:\WINDOWS\System32\advapi32.dll
LoadedModule[27]=C:\WINDOWS\System32\kernel.appcore.dll
LoadedModule[28]=C:\WINDOWS\System32\shcore.dll
LoadedModule[29]=C:\WINDOWS\System32\profapi.dll
LoadedModule[30]=C:\WINDOWS\SYSTEM32\UxTheme.dll
LoadedModule[31]=C:\WINDOWS\SYSTEM32\WINMM.dll
LoadedModule[32]=C:\WINDOWS\SYSTEM32\samcli.dll
LoadedModule[33]=C:\WINDOWS\SYSTEM32\MSACM32.dll
LoadedModule[34]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\USERENV.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\dwmapi.dll
LoadedModule[37]=C:\WINDOWS\SYSTEM32\urlmon.dll
LoadedModule[38]=C:\WINDOWS\SYSTEM32\WINSPOOL.DRV
LoadedModule[39]=C:\WINDOWS\SYSTEM32\MPR.dll
LoadedModule[40]=C:\WINDOWS\SYSTEM32\WINMMBASE.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\iertutil.dll
LoadedModule[42]=C:\WINDOWS\SYSTEM32\bcrypt.dll
LoadedModule[43]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[44]=E:\Prepar3D\api.dll
LoadedModule[45]=C:\WINDOWS\SYSTEM32\MSVCP120.dll
LoadedModule[46]=C:\WINDOWS\SYSTEM32\MSVCR120.dll
LoadedModule[47]=C:\WINDOWS\SYSTEM32\Cabinet.dll
LoadedModule[48]=C:\WINDOWS\System32\WS2_32.dll
LoadedModule[49]=C:\WINDOWS\SYSTEM32\MSWSOCK.dll
LoadedModule[50]=C:\WINDOWS\SYSTEM32\WINHTTP.dll
LoadedModule[51]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[52]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.14393.447_none_5507ded2cb4f7f4c\COMCTL32.dll
LoadedModule[53]=E:\Prepar3D\acontain.dll
LoadedModule[54]=E:\Prepar3D\ai_player.dll
LoadedModule[55]=E:\Prepar3D\atc.dll
LoadedModule[56]=C:\WINDOWS\System32\MSASN1.dll
LoadedModule[57]=E:\Prepar3D\controls.dll
LoadedModule[58]=E:\Prepar3D\demo.dll
LoadedModule[59]=C:\WINDOWS\System32\SETUPAPI.dll
LoadedModule[60]=E:\Prepar3D\DIS.dll
LoadedModule[61]=E:\Prepar3D\facilities.dll
LoadedModule[62]=E:\Prepar3D\fe.dll
LoadedModule[63]=E:\Prepar3D\flight.dll
LoadedModule[64]=E:\Prepar3D\fs-traffic.dll
LoadedModule[65]=E:\Prepar3D\g2d.dll
LoadedModule[66]=E:\Prepar3D\g3d.dll
LoadedModule[67]=E:\Prepar3D\gps.dll
LoadedModule[68]=E:\Prepar3D\livingwater.dll
LoadedModule[69]=E:\Prepar3D\main.dll
LoadedModule[70]=E:\Prepar3D\menus.dll
LoadedModule[71]=E:\Prepar3D\multiplayer.dll
LoadedModule[72]=C:\WINDOWS\System32\COMDLG32.dll
LoadedModule[73]=E:\Prepar3D\pdk.dll
LoadedModule[74]=E:\Prepar3D\panels.dll
LoadedModule[75]=E:\Prepar3D\sim1.dll
LoadedModule[76]=E:\Prepar3D\simscheduler.dll
LoadedModule[77]=E:\Prepar3D\simprop.dll
LoadedModule[78]=E:\Prepar3D\sound.dll
LoadedModule[79]=E:\Prepar3D\symmap.dll
LoadedModule[80]=E:\Prepar3D\terrain.dll
LoadedModule[81]=E:\Prepar3D\util.dll
LoadedModule[82]=E:\Prepar3D\visualfx.dll
LoadedModule[83]=E:\Prepar3D\weather.dll
LoadedModule[84]=C:\WINDOWS\System32\WLDAP32.dll
LoadedModule[85]=E:\Prepar3D\window.dll
LoadedModule[86]=C:\WINDOWS\SYSTEM32\HID.DLL
LoadedModule[87]=C:\WINDOWS\SYSTEM32\DINPUT8.dll
LoadedModule[88]=C:\WINDOWS\SYSTEM32\DSOUND.dll
LoadedModule[89]=E:\Prepar3D\audiere.dll
LoadedModule[90]=E:\Prepar3D\mplEasyBlendSDKDX11.dll
LoadedModule[91]=C:\WINDOWS\SYSTEM32\MFReadWrite.dll
LoadedModule[92]=C:\WINDOWS\SYSTEM32\MFPlat.DLL
LoadedModule[93]=C:\WINDOWS\SYSTEM32\dxgi.dll
LoadedModule[94]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[95]=C:\WINDOWS\SYSTEM32\d3d11.dll
LoadedModule[96]=E:\Prepar3D\D3DCOMPILER_47.dll
LoadedModule[97]=C:\WINDOWS\SYSTEM32\OPENGL32.dll
LoadedModule[98]=C:\WINDOWS\SYSTEM32\GLU32.dll
LoadedModule[99]=C:\WINDOWS\SYSTEM32\d3dx9_43.dll
LoadedModule[100]=C:\WINDOWS\SYSTEM32\d3dx11_43.dll
LoadedModule[101]=E:\Prepar3D\d3dcsx_47.dll
LoadedModule[102]=C:\WINDOWS\SYSTEM32\D3DCOMPILER_43.dll
LoadedModule[103]=C:\WINDOWS\SYSTEM32\DDRAW.dll
LoadedModule[104]=C:\WINDOWS\SYSTEM32\DCIMAN32.dll
LoadedModule[105]=C:\WINDOWS\SYSTEM32\RTWorkQ.DLL
LoadedModule[106]=E:\Prepar3D\language.dll
LoadedModule[107]=C:\WINDOWS\SYSTEM32\MSXML6.DLL
LoadedModule[108]=C:\WINDOWS\SYSTEM32\ntmarta.dll
LoadedModule[109]=E:\Prepar3D\uiInterface.dll
LoadedModule[110]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[111]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[112]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
LoadedModule[113]=C:\WINDOWS\SYSTEM32\MSVCR120_CLR0400.dll
LoadedModule[114]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\40571abae9422cd2ca6fafbbde1c3cdc\mscorlib.ni.dll
LoadedModule[115]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll
LoadedModule[116]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\08da6b6698b412866e6910ae9b84f363\System.ni.dll
LoadedModule[117]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationCore\051a282e157a228405b2e0d867c3ce1d\PresentationCore.ni.dll
LoadedModule[118]=C:\WINDOWS\SYSTEM32\CRYPTSP.dll
LoadedModule[119]=C:\WINDOWS\system32\rsaenh.dll
LoadedModule[120]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatio5ae0f00f#\5272cb4aeec65bec2fffb45e9cb22910\PresentationFramework.ni.dll
LoadedModule[121]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Core\f6ebd52be27fe627fed0d185c6a9c0d5\System.Core.ni.dll
LoadedModule[122]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\WindowsBase\5751e969e4789e60d3ad463cb6024006\WindowsBase.ni.dll
LoadedModule[123]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xaml\04c4f83e0b62ff553abff98943e45f42\System.Xaml.ni.dll
LoadedModule[124]=C:\WINDOWS\SYSTEM32\dwrite.dll
LoadedModule[125]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\wpfgfx_v0400.dll
LoadedModule[126]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\WPF\PresentationNative_v0400.dll
LoadedModule[127]=C:\WINDOWS\SYSTEM32\PROPSYS.dll
LoadedModule[128]=C:\WINDOWS\SYSTEM32\iphlpapi.dll
LoadedModule[129]=C:\WINDOWS\System32\NSI.dll
LoadedModule[130]=C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[131]=C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL
LoadedModule[132]=C:\WINDOWS\SYSTEM32\ondemandconnroutehelper.dll
LoadedModule[133]=C:\WINDOWS\System32\MSCTF.dll
LoadedModule[134]=C:\WINDOWS\SYSTEM32\secur32.dll
LoadedModule[135]=C:\WINDOWS\SYSTEM32\DNSAPI.dll
LoadedModule[136]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[137]=C:\WINDOWS\System32\fwpuclnt.dll
LoadedModule[138]=C:\Windows\System32\rasadhlp.dll
LoadedModule[139]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\Presentatioaec034ca#\def8702c6e883330fb8cb8e3f5c5e665\PresentationFramework.Aero2.ni.dll
LoadedModule[140]=C:\WINDOWS\SYSTEM32\WindowsCodecs.dll
LoadedModule[141]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_410e5247be0e5f00\nvd3dum.dll
LoadedModule[142]=C:\WINDOWS\system32\nvspcap.dll
LoadedModule[143]=C:\WINDOWS\System32\PSAPI.DLL
LoadedModule[144]=C:\WINDOWS\SYSTEM32\WTSAPI32.dll
LoadedModule[145]=C:\WINDOWS\system32\nvapi.dll
LoadedModule[146]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\c2abcda8f96d67fa6ff5665fd21dddff\System.Drawing.ni.dll
LoadedModule[147]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\c02fbf560e52a1aab432a90d4c613af4\System.Windows.Forms.ni.dll
LoadedModule[148]=C:\WINDOWS\SYSTEM32\WINSTA.dll
LoadedModule[149]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\aa9c29b70b4cceab890eb841f89d73e9\System.Configuration.ni.dll
LoadedModule[150]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\7532301b00fac8def2f526ca8b480e11\System.Xml.ni.dll
LoadedModule[151]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[152]=C:\WINDOWS\system32\dataexchange.dll
LoadedModule[153]=C:\WINDOWS\system32\dcomp.dll
LoadedModule[154]=C:\WINDOWS\system32\twinapi.appcore.dll
LoadedModule[155]=C:\WINDOWS\system32\msctfui.dll
LoadedModule[156]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\UIAutomationTypes\75ed56cf95fe6228472b5e57ac7a76b7\UIAutomationTypes.ni.dll
LoadedModule[157]=C:\WINDOWS\SYSTEM32\UIAutomationCore.dll
LoadedModule[158]=C:\WINDOWS\SYSTEM32\sxs.dll
LoadedModule[159]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Runteb92aa12#\213003369298faf75651a6b8981dce12\System.Runtime.Serialization.ni.dll
LoadedModule[160]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.321_none_baab3cb4359688b4\gdiplus.dll
LoadedModule[161]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\SMDiagnostics\1b144b0155aa14719ac0b83f038abbd5\SMDiagnostics.ni.dll
LoadedModule[162]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Servd1dec626#\d842ac6dc0b94d7516b2d43a62b8f4d7\System.ServiceModel.Internals.ni.dll
LoadedModule[163]=C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_410e5247be0e5f00\nvwgf2um.dll
LoadedModule[164]=C:\WINDOWS\SYSTEM32\DEVOBJ.dll
LoadedModule[165]=C:\WINDOWS\System32\WINTRUST.dll
LoadedModule[166]=C:\Program Files (x86)\Dropbox\Client\DropboxExt.3.0.dll
LoadedModule[167]=C:\WINDOWS\system32\ntshrui.dll
LoadedModule[168]=C:\Program Files\TortoiseGit\bin\TortoiseGitStub32.dll
LoadedModule[169]=C:\Program Files\TortoiseGit\bin\TortoiseGit32.dll
LoadedModule[170]=C:\Program Files\TortoiseGit\bin\libgit232_tgit.dll
LoadedModule[171]=C:\Program Files\TortoiseGit\bin\gitdll32.dll
LoadedModule[172]=C:\WINDOWS\SYSTEM32\SHFOLDER.dll
LoadedModule[173]=C:\Program Files\TortoiseGit\bin\zlib132_tgit.dll
LoadedModule[174]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.447_none_89c64d28dafea4b9\Comctl32.dll
LoadedModule[175]=C:\WINDOWS\system32\srvcli.dll
LoadedModule[176]=C:\WINDOWS\SYSTEM32\cscapi.dll
LoadedModule[177]=C:\WINDOWS\system32\netutils.dll
LoadedModule[178]=C:\WINDOWS\System32\coml2.dll
LoadedModule[179]=C:\WINDOWS\system32\mssprxy.dll
LoadedModule[180]=C:\WINDOWS\SYSTEM32\LINKINFO.dll
LoadedModule[181]=C:\WINDOWS\system32\Windows.Storage.Search.dll
LoadedModule[182]=C:\WINDOWS\System32\StructuredQuery.dll
LoadedModule[183]=C:\WINDOWS\SYSTEM32\edputil.dll
LoadedModule[184]=C:\Windows\System32\ActXPrxy.dll
LoadedModule[185]=C:\WINDOWS\system32\NetworkExplorer.dll
LoadedModule[186]=C:\WINDOWS\System32\ntlanman.dll
LoadedModule[187]=C:\WINDOWS\System32\drprov.dll
LoadedModule[188]=C:\WINDOWS\System32\davclnt.dll
LoadedModule[189]=C:\WINDOWS\System32\DAVHLPR.dll
LoadedModule[190]=C:\WINDOWS\system32\zipfldr.dll
LoadedModule[191]=C:\WINDOWS\System32\MMDevApi.dll
LoadedModule[192]=C:\WINDOWS\SYSTEM32\AUDIOSES.DLL
LoadedModule[193]=C:\WINDOWS\SYSTEM32\wintypes.dll
LoadedModule[194]=C:\WINDOWS\SYSTEM32\avrt.dll
LoadedModule[195]=C:\WINDOWS\SYSTEM32\XInput9_1_0.dll
LoadedModule[196]=C:\WINDOWS\SYSTEM32\wdmaud.drv
LoadedModule[197]=C:\WINDOWS\SYSTEM32\ksuser.dll
LoadedModule[198]=C:\WINDOWS\SYSTEM32\msacm32.drv
LoadedModule[199]=C:\WINDOWS\SYSTEM32\midimap.dll
LoadedModule[200]=E:\Prepar3D\radar.dll
LoadedModule[201]=E:\Prepar3D\VirtualReality.dll
LoadedModule[202]=E:\Prepar3D\openvr_api.dll
LoadedModule[203]=E:\Prepar3D\ControllableCamera.dll
LoadedModule[204]=E:\Prepar3D\SimDirector.dll
LoadedModule[205]=E:\Prepar3D\BGLCompLib.dll
LoadedModule[206]=E:\Prepar3D\simpropext.dll
LoadedModule[207]=E:\Prepar3D\Gauges\TargetInfo.dll
LoadedModule[208]=E:\Prepar3D\Gauges\Fury_1500.dll
LoadedModule[209]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\PresentationUI\fa9bc06d50d0f6facee221caeca59282\PresentationUI.ni.dll
LoadedModule[210]=C:\WINDOWS\SYSTEM32\XInput1_4.dll
LoadedModule[211]=C:\WINDOWS\system32\wbem\wbemprox.dll
LoadedModule[212]=C:\WINDOWS\SYSTEM32\wbemcomn.dll
LoadedModule[213]=C:\WINDOWS\system32\wbem\wbemsvc.dll
LoadedModule[214]=C:\WINDOWS\system32\wbem\fastprox.dll
LoadedModule[215]=C:\WINDOWS\SYSTEM32\mscms.dll
LoadedModule[216]=C:\WINDOWS\SYSTEM32\WindowsCodecsExt.dll
LoadedModule[217]=C:\WINDOWS\SYSTEM32\icm32.dll
LoadedModule[218]=C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Web\b5bd1926660d2d17f74fd4ee135f4c4b\System.Web.ni.dll
LoadedModule[219]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\webengine4.dll
LoadedModule[220]=C:\Windows\System32\ieframe.dll
LoadedModule[221]=C:\Windows\System32\NETAPI32.dll
LoadedModule[222]=C:\Windows\System32\WKSCLI.DLL
LoadedModule[223]=C:\Windows\System32\mshtml.dll
LoadedModule[224]=C:\Windows\System32\srpapi.dll
LoadedModule[225]=C:\WINDOWS\SYSTEM32\WININET.dll
LoadedModule[226]=C:\WINDOWS\SYSTEM32\XmlLite.dll
LoadedModule[227]=C:\Windows\System32\vaultcli.dll
LoadedModule[228]=C:\WINDOWS\SYSTEM32\MLANG.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Beendet und geschlossen.
ConsentKey=AppHangXProcB1
AppName=Prepar3D exe
AppPath=E:\Prepar3D\Prepar3D.exe
ReportDescription=Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren.
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=EAB9CE02337CBAC29C0A4C84CDDE4BF3
MetadataHash=-1566366343

It seems that toprob and Korundar are facing the same issue. I have no idea how to fix this - maybe i should try to roll back the nvidia drivers.

[Jim Young 2,356]

 

 

I have no idea how to fix this - maybe i should try to roll back the nvidia drivers.

 

You did install Microsoft.net 4.6 before installing the latest update?

 

I do not see where simconnect.dll 10.0.60905.0 or 10.0.61259.0 loaded (this may be due to the fact you had no modules loaded that had to connect via simconnect).

 

I do not seee where Microsoft Visual C++ 2005 with SP1 loaded (MSVCR80.dll v8.0.50727.6195).  In all of my P3D crash reports with the latest version, Microsoft Visual 2005 is loaded.

 

You should NOT remove the simobjects.cfg folder as it is not rebuilt and is a default folder.

 

Make sure you are moving or deleting the P3D.cfg and scenery.cfg.  There is a P3D.txt file that looks the same as the P3D.cfg.  It was created when you had a crash or freeze as Microsoft had visions of having you send them a text version of your config so they could figure out FSX (now P3D) failed.

 

Best regards,

Jim

[MachTwo 386]

Dear Florian,

 

LM are aware of this issue - I have brought this thread to their attention. 

[busychild 0]

Dear Florian,

 

LM are aware of this issue - I have brought this thread to their attention. 

 

Hi Andrew,

 

wow - thanks - that's great!

 

And by the way: You guys are awesome - keep up the unbelievable work with the A320 (i can't wait to fly it in P3D)!

 

Best regards

 

Florian

[Korundar 12]

Good news! Hope that LM will solve this issue once for all.

 

Florian, I don't think it's related with using other applications, it's an issue that happens when you move the focus out of the P3D window. I tried to make some flights without moving the focus and I've been able to complete them all the times. While flying the same routes in the same conditions and with the same aircraft but moving focus between applications has caused P3D to crash 3 times out of 4.

 

It's definitely something wrong with the focus change, but it's very hard to understand as P3D closes without errors.

[vonmar 123]

The same topic was posted in the P3D forum with some additional responses:

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=122675


 

[codylv 0]

Same exact thing happens to me, it keeps "not responding" for no good reason.

[Jim Young 2,356]

Same exact thing happens to me, it keeps "not responding" for no good reason.

You need to post your crash report - see AVSIM CTD Guide for link to AppCrashView and directions for posting here.

 

It is not P3D that is causing the crashes.  It's an addon or tweak and LM is not responsible for addons or bad tweaks.  This is why you must rebuild your p3d.cfg, remove the dll.xml/exe.xml, and rebuild your scenery.cfg as shown on page 10, AVSIM CTD Guide.  If there are no crashes, then it was caused by the p3d.cfg, the dll.xml or scenery.cfg.  I updated to AS16 and my crashes have stopped but I know for a fact, if I remove the dll.xml, I will not get a crash.  Unfortunately, whenever you update P3D, some addon developers have to update their addon too and I think this is the cause of these crashes and why some have gone back to a previous version of P3D and it suddenly works with no crashes.

 

Best regards,

Jim