# P3D 3.4.14 hangs when using other applications

## Recommended Posts

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

##### Share on other sites
 Help AVSIM continue to serve you!Please donate today!

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

Best regards,

Jim

##### Share on other sites

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.

##### Share on other sites

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

##### Share on other sites

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.

##### Share on other sites

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.

##### Share on other sites

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

##### Share on other sites

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


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.

##### Share on other sites

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

##### Share on other sites

Dear Florian,

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

• 1

##### Share on other sites

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

##### Share on other sites

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.

##### Share on other sites

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

##### Share on other sites

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

##### Share on other sites

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

I just rebuilt my sim and it still happens. I can't imagine it's my setup if LM has already acknowledged it's a bug... I will check logs, but there is nothing that correlates to when it freezes.

##### Share on other sites

I just rebuilt my sim and it still happens. I can't imagine it's my setup if LM has already acknowledged it's a bug... I will check logs, but there is nothing that correlates to when it freezes.

I'm also really sure it is P3D which is causing the issues (or a incompatibility with the latest nvidia drivers or windows updates). I've disabled every add on, config file, tweak, etc. and the problem remains.

As i read in several threads some other users are also facing the same problems but LM seems to be aware of the problems and hopefully they'll fix it soon.

##### Share on other sites

I'm also really sure it is P3D which is causing the issues (or a incompatibility with the latest nvidia drivers or windows updates). I've disabled every add on, config file, tweak, etc. and the problem remains.

As i read in several threads some other users are also facing the same problems but LM seems to be aware of the problems and hopefully they'll fix it soon.

Yeah it's on their forums, they are working on a fix, hopefully it will be out soon..

##### Share on other sites

I just rebuilt my sim and it still happens. I can't imagine it's my setup if LM has already acknowledged it's a bug

Yeah it's on their forums, they are working on a fix, hopefully it will be out soon..

Where does it state on their website that they acknowledge it's a bug?  It is being looked at but that does not mean there is a bug with P3D.  This always happens whenever we upgrade to the latest version and, in that case, it is a bug because other addon developers have not posted updates for the latest version.  I was having freezes at KLAX in Orbx Southern Calif territory in my PMDG 737.  I updated to the latest version of AS16 yesterday and sat at KLAX in my PMDG 737 for over 30 minutes and no freeze when it was almost guaranteed it would freeze.  Because of my success in fixing my problem, it does not mean there is no bug and an updated version will fix your problems.  I'm just saying my problem shown earlier is fixed (where's that icon, knock on wood...).

Best regards,

Jim

##### Share on other sites

Consequently, the more add ons we have installed and the more complex they are, the greater the chances of incompatibility with every upgrade of the simulation platform. LM can't possibly test for these incompatibilities, I guess its down to us to find them. Or hope that developers get early versions of the new sim and correct any flaws with a patch?

I understand Orbx put out amended dll's within hours of the latest P3d.

Happy Simming.

David

##### Share on other sites

Thinking back when I first started up P3D w/the latest version I trusted the error I received about objectflow_P3D.dll not being compatible and then telling me it would disable the module.  I thought that happened but never checked for a day or two then looked at my dll.xml and saw that it was still loading and it had not been disabled.  Perhaps that caused my ntdll.dll errors.  I will never know.  But corrupted modules that are loaded at startup of P3D have caused ntdll.dll errors in the past until updated or disabled.

I hope everyone who is still having the issues find a solution.

Best regards,

Jim

##### Share on other sites

I'm glad to hear that this issues is being looked at at LM.

In the meantime I posted a temporary workaround in another thread. Maybe someone else can enjoy some flights before the problem is fixed.

Although my gpu temps are stable within 60°C, I have adjusted the base clock to -50MHz and the memory clock to -150MHz. Furthermore I have forced P3D to high priority. So far I was able to make 2 flights in around 3h time without any problems. It's not an elegant solution, but considering the countless hours I have spend so far, I'm happy that it's finally running ... at least for now.

##### Share on other sites

Same issue here. At first it does load to the scenerio, when change airports it gets locked at 83%. Than, when I restart again P3D 3.4 it opens, but then closes with no warning or message.

##### Share on other sites

Hi guys,

i finally found what was causing the issues for me: It was the GeForce Experience "Share in-game overlay". This feature was enabled (although i never enabled it - i think this came with an driver update some weeks/months ago, but i'm not totally sure). After i disabled it in the Geforce Experience application everything works well and i'm unable to reproduce the issues. Here you can find some information about how to disable it: http://nvidia.custhelp.com/app/answers/detail/a_id/4228/~/how-to-disable-the-geforce-experience-share-in-game-overlay

Best regards

Florian

##### Share on other sites

Hi all.  I've been following this thread.  I have some issues that I just can't resolve.  I am running P3D with AS16, FTX Global Base and Vector.  I have tons of other addons that I haven't even tried to install due to ongoing AppHangs and freezes.  I use Prosim737.  Last night, I again froze with the AppHangB1 error that Jim Young discussed in another thread. Note that I had already done all of the preventive actions discussed in the CTD guide in an effort to correct this problem. But after last night's freeze along with several others in the past two weeks, I had had enough.  So I updated FSUIPC, AS16 (I really thought this would fix it), reinstalled all three simconnect versions, moved the scenery.cfg, dll.xml and exe.xml files to a temp folder.  Restarted and let P3D rebuild the files.  Fired up Prosim737, AS16 and P3D.  Got two hours into a flight and got the MSVCR120.dll crash.  Below are the Appcrash reports (the second is from last night before the updates and config changes).  I have also seen stackhash errors and api.dll errors.  Any help would be appreciated.  It is obvious that I am missing something in spite of following the CTD guide.  Next stop is a fresh install I guess, but I just did that a month ago and had problems right away.  Thanks!!!

Troy

CRASH REPORT #1 from 2/2/2017

Version=1

EventType=APPCRASH

EventTime=131305597022800485

ReportType=2

Consent=1

ReportIdentifier=e92fb73d-e9b1-11e6-96e1-a0a8cd279a74

IntegratorReportIdentifier=e92fb73c-e9b1-11e6-96e1-a0a8cd279a74

WOW64=1

Response.BucketId=1267663583

Response.BucketTable=25

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=Prepar3D.exe

Sig[1].Name=Application Version

Sig[1].Value=3.4.18.19475

Sig[2].Name=Application Timestamp

Sig[2].Value=5851bfd2

Sig[3].Name=Fault Module Name

Sig[3].Value=MSVCR120.dll

Sig[4].Name=Fault Module Version

Sig[4].Value=12.0.21005.1

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=524f7ce6

Sig[6].Name=Exception Code

Sig[6].Value=40000015

Sig[7].Name=Exception Offset

Sig[7].Value=000a7676

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Value=5165

DynamicSig[23].Value=5165145cb862f57c9ed3e2944b42f2cb

DynamicSig[24].Value=d198

DynamicSig[25].Value=d198fb430461973a744a22157569b6dd

UI[2]=D:\Lockheed Martin\Prepar3D.exe

UI[3]=Prepar3D exe 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

State[0].Key=Transport.DoneStage1

State[0].Value=1

State[1].Key=DataRequest

State[1].Value=Bucket=1267663583/nBucketTable=25/nResponse=1/n

FriendlyEventName=Stopped working

ConsentKey=APPCRASH

AppName=Prepar3D exe

AppPath=D:\Lockheed Martin\Prepar3D.exe

CRASH REPORT #2 from 2/1/2017

Version=1

EventType=AppHangB1

EventTime=131304748934358391

ReportType=3

Consent=1

ReportIdentifier=7328574c-e8ec-11e6-a243-74d435ecf46e

IntegratorReportIdentifier=7328574d-e8ec-11e6-a243-74d435ecf46e

WOW64=1

Response.BucketId=50

Response.BucketTable=5

Response.type=4

Sig[0].Name=Application Name

Sig[0].Value=Prepar3D.exe

Sig[1].Name=Application Version

Sig[1].Value=3.4.18.19475

Sig[2].Name=Application Timestamp

Sig[2].Value=5851bfd2

Sig[3].Name=Hang Signature

Sig[3].Value=5b32

Sig[4].Name=Hang Type

Sig[4].Value=16384

DynamicSig[1].Name=OS Version

DynamicSig[1].Value=6.1.7601.2.1.0.256.48

DynamicSig[2].Name=Locale ID

DynamicSig[2].Value=1033

DynamicSig[22].Value=5b321d9417a2e8066e808d72f4931d41

DynamicSig[23].Value=9fb8

DynamicSig[25].Value=6d38

DynamicSig[26].Value=6d38772d4f8966c533bafff4a1b77765

DynamicSig[27].Value=0a5a

DynamicSig[28].Value=0a5a6d334d102a94d21c789bab96531a

UI[3]=Prepar3D exe is not responding

UI[4]=If you close the program, you might lose information.

UI[5]=Close the program

UI[6]=Close the program

UI[7]=Close the program

State[0].Key=Transport.DoneStage1

State[0].Value=1

State[1].Key=DataRequest

State[1].Value=Bucket=50/nBucketTable=5/nResponse=1/n

FriendlyEventName=Stopped responding and was closed

ConsentKey=AppHangXProcB1

AppName=Prepar3D exe

AppPath=D:\Lockheed Martin\Prepar3D.exe

ReportDescription=A problem caused this program to stop interacting with Windows.

## Create an account

Register a new account

• Tom Allensworth,
Founder of AVSIM Online

• ### Hot Spots

• 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!

$17,895.00 of$36,000.00 goal reached.