Can someone help me diagnose my CTD and a possible solution? I am unfamiliar with the process. I also notice that this event log is not too detailed (long) when compared to others. If it helps, I can get the longer one but will need some direction.

 

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: ntdll.dll, version: 6.1.7601.19135, time stamp: 0x56a1c9c5
Exception code: 0xc000000d
Fault offset: 0x000000000006e042
Faulting process id: 0xc34
Faulting application start time: 0x01d3833a5ee6cc40
Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 0ec3f0ec-ef4a-11e7-aa7b-10c37b9252f4

 

 

Thank you in advance

40 minutes ago, BOEINGMAN07 said:

Exception code: 0xc000000d

Indicates an invalid parameter was passed to a service or function and that could be a parameter you placed in your P3D.cfg.  Messing with the P3d.cfg causes a lot of crashes and renaming it to p3d.cfg.off and restarting P3D usually fixes the problem.  An addon might have been installed too and has a bad parameter.

There are many more suggestions on how to fix this issue in the AVSIM CTD Guide.  Around page 9, there is a procedure for fixing most CTD's and freezes in P3DV4.1.

Happy New Year!

Best regards,

Jim

Thank you so much! I will head over there now. Just reinstalled the sim and still having the issue so Ill take a look. Happy New Year!

How do I determine which addon is created the CTD? I renamed the CFG and still have the error.

1 hour ago, BOEINGMAN07 said:

How do I determine which addon is created the CTD? I renamed the CFG and still have the error.

That's too bad the p3d.cfg did not fix the issue.  As I stated above, your next step as shown in the CTD Guide is to rename the dll.xml to dll.xml.off.  As stated in the guide, there are two, one in the same folder as your P3D.cfg and one in the same folder as your scenery.cfg (which is the default location).  When you disable this one in the scenery.cfg, a new default dll.xml will be build when you restart P3D.  If that does not fix the issue, then you need to open up your addon organizer and disable all scenery listed, restart P3D, and see if this fixes the problem.  If none of these solutions work, then your problem is truly serious but we won't discuss that until that happens.