So P3D has been crashing since today mid flight, I honestly don't know why does it keep crashing all I know is i'm suddenly flying and it freezes after that Windows tells me the usual Prepar3D is not responding.

 

Specs:

• I5 6600K (Not oc'd)
• 8 GB DDR4 RAM
• Gigabyte GTX 1060 6GB
• ASUS Z170 Pro Gaming MB

 

Here is the event viewer log:

 

Log Name:      Application

Source:        Application Hang

Date:          12/27/2016 12:48:10 AM

Event ID:      1002

Task Category: (101)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Alessandros-PC

Description:

The program Prepar3D.exe version 3.4.14.18870 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.

 Process ID: 25e8

 Start Time: 01d25ff514d20958

 Termination Time: 62

 Application Path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

 Report Id: a644c654-cbef-11e6-a6ad-38d5470f454b

 Faulting package full name: 

 Faulting package-relative application ID: 

 

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Hang" />

    <EventID Qualifiers="0">1002</EventID>

    <Level>2</Level>

    <Task>101</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-12-27T04:48:10.912559500Z" />

    <EventRecordID>1754</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Alessandros-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>Prepar3D.exe</Data>

    <Data>3.4.14.18870</Data>

    <Data>25e8</Data>

    <Data>01d25ff514d20958</Data>

    <Data>62</Data>

    <Data>C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe</Data>

    <Data>a644c654-cbef-11e6-a6ad-38d5470f454b</Data>

    <Data>

    </Data>

    <Data>

    </Data>

    <Binary>55006E006B006E006F0077006E0000000000</Binary>

  </EventData>

</Event>

 

 

Let me know if you guys need anything else.

Apparently I submitted two times, you guys can delete one of the posts, sorry for the problems caused.

Sigh, when you install it in it's default location you absolutely need run prepar3d.exe as an administrator. Never install it in it's default location. 

Sigh, when you install it in it's default location you absolutely need run prepar3d.exe as an administrator. Never install it in it's default location. 

So just run Prepar3D.exe as an admin program and all my crashes are gone? The thing with running P3D as an admin program is that then I cannot talk on vPilot in VATSIM or TeamSpeak

The default program files location is a read only location. Since some addons place files there that they need to write to, running as admin is one way to acquire the permission to write there. Another "less obvious" way is to provide the actual permission - right-click on the folder in explorer, click "Properties" on the popup menu, choose "Security" tab, click "Edit", select "Users" group, check "Modify", click OK, OK. We do that once. Now any time we or any addon wants to modify a file within that folder tree we have permission. Whether this is the root of the problem mentioned here I'm not sure. But there's certainly nothing wrong with accepting the *recommended installation path* defaulted by P3D, although it might help to know how certain addons work. On top of that; some addons may actually need to by run as admin since they modify admin only areas of the registry and that's to do with acquiring Priveleges, not permissions - it's worth understanding the difference. If these type of addons are started up by P3D exe.xml then P3D must be started as admin to accommodate those.

 

And there lies the irony. Even if we installed into a custom folder, we may still need to run as admin for an addon that updates the system. But if we do we gain permission to write to it since we made the folder - we own it. Therein lies another irony, if anything happens to our user profile we may lose access to it, and admins don't ordinarily have permission to those custom folders. Sigh.

The default program files location is a read only location. Since some addons place files there that they need to write to, running as admin is one way to acquire the permission to write there. Another "less obvious" way is to provide the actual permission - right-click on the folder in explorer, click "Properties" on the popup menu, choose "Security" tab, click "Edit", select "Users" group, check "Modify", click OK, OK. We do that once. Now any time we or any addon wants to modify a file within that folder tree we have permission. Whether this is the root of the problem mentioned here I'm not sure. But there's certainly nothing wrong with accepting the *recommended installation path* defaulted by P3D, although it might help to know how certain addons work. On top of that; some addons may actually need to by run as admin since they modify admin only areas of the registry and that's to do with acquiring Priveleges, not permissions - it's worth understanding the difference. If these type of addons are started up by P3D exe.xml then P3D must be started as admin to accommodate those.

 

And there lies the irony. Even if we installed into a custom folder, we may still need to run as admin for an addon that updates the system. But if we do we gain permission to write to it since we made the folder - we own it. Therein lies another irony, if anything happens to our user profile we may lose access to it, and admins don't ordinarily have permission to those custom folders. Sigh.

Thanks!! I'll try this and do a some flights and see if this fixes the program, thank you very much!

Well, could be anything at this stage. Run as admin and set the permission, belts and braces so to speak, won't hurt and will prove if it's any of that soon enough. Other things to check are that you have the latest updates to addons since your last hotfix. If you've recently installed anything check the setup, dll.xml, exe.xml. Try renaming the Prepar3D.cfg, check setup of AI traffic addons - unmap certain aircraft folders and so on for testing.

Well, could be anything at this stage. Run as admin and set the permission, belts and braces so to speak, won't hurt and will prove if it's any of that soon enough. Other things to check are that you have the latest updates to addons since your last hotfix. If you've recently installed anything check the setup, dll.xml, exe.xml. Try renaming the Prepar3D.cfg, check setup of AI traffic addons - unmap certain aircraft folders and so on for testing.

Well I installed the IVAO models and it has been crashing since then, do you recommend reinstalling them and see if they make a difference?

 

 

 

Try renaming the Prepar3D.cfg

What you mean by this is so that Prepar3D can create a new CFG?

Could very well be one of those models - map out the folder so they are not used and retest - reinstalling wont make any difference usually because it simply recreates the same setup. see C:\ProgramData\Lockheed Martin\Prepar3D v3\SimObjects.cfg

 

if you rename those files they will be re-created freshly, but you still have your original you can rename back.

Could very well be one of those models - map out the folder so they are not used and retest - reinstalling wont make any difference usually because it simply recreates the same setup. see C:\ProgramData\Lockheed Martin\Prepar3D v3\SimObjects.cfg

 

if you rename those files they will be re-created freshly, but you still have your original you can rename back.

I honestly don't understand what you want me to do, if it's not a problem can you elaborate or expand? Thanks  :smile:

Hi, if you're not familiar with those files then you could try uninstalling those models to check if they have any effect. But for example in SimObjects.cfg there would be sections that define the locations of your planes so you could temporarily remove whatever section to guarantee none of those models appear while you test.

The default program files location is a read only location. Since some addons place files there that they need to write to, running as admin is one way to acquire the permission to write there. Another "less obvious" way is to provide the actual permission - right-click on the folder in explorer, click "Properties" on the popup menu, choose "Security" tab, click "Edit", select "Users" group, check "Modify", click OK, OK. We do that once. Now any time we or any addon wants to modify a file within that folder tree we have permission. Whether this is the root of the problem mentioned here I'm not sure. But there's certainly nothing wrong with accepting the *recommended installation path* defaulted by P3D, although it might help to know how certain addons work. On top of that; some addons may actually need to by run as admin since they modify admin only areas of the registry and that's to do with acquiring Priveleges, not permissions - it's worth understanding the difference. If these type of addons are started up by P3D exe.xml then P3D must be started as admin to accommodate those.

 

And there lies the irony. Even if we installed into a custom folder, we may still need to run as admin for an addon that updates the system. But if we do we gain permission to write to it since we made the folder - we own it. Therein lies another irony, if anything happens to our user profile we may lose access to it, and admins don't ordinarily have permission to those custom folders. Sigh.

This solved everything, when I selected the NGX and clicked start flight it told me it couldn't generate its work files just before everything started to load, I guess the NGX needed a work file and it couldn't find it because it had no perms to the Prepar3D folder, after I modified those perms it didn't give me that warning anymore and it hasn't crashed since. Thanks for you help!

Good work Alessandro! When we log into Windows we become a member of the Users group and so we get access that way to write files and stay within the security. The PMDG manual recommends that we install the sim in a private folder so we automatically get access to it since we own it, but that way can fail down the road if something happens to the profile - it's way more effective to set the permission, and a simple job for any Windows installer routine.