P3Dexe stopped working

[Petermuc3]

Hi, every 2nd flight I get a ntdll.dll error and need to quit P3D4.3. As I haven't seen this error in the forum yet, it might not be
the Bonanza. But in my case it only happens flying the Bonanza. Flying other complex aircrafts like the FSL A319/320 I have no issues.

Thanks for the help
Peter

[email protected], 24,0 GB, Gigabyte 1080ti, Win7/64 Ultimate, P3Dv4.3, Logitech Extreme 3D Pro, ThrustmasterT.1600, Saitek Throttle,
MFG Crosswind Pedals

[Nick - A2A]

Hi Peter - welcome to the A2A forums.

Please can you check the content of past error logs for this event and if possible paste one on the forum here. Probably the easiest way to do this is open the Windows "Reliability Monitor" and select one of the previous reports which should be shown by red x icons.

Thanks,
Nick

[Petermuc3]

Here we go.

Log Name: Application
Source: Application Error
Date: 22-Sep-18 11:41:48
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Peter-PC
Description:
Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263
Faulting module name: ntdll.dll, version: 6.1.7601.24231, time stamp: 0x5b6db5a7
Exception code: 0xc000000d
Fault offset: 0x000000000008b2ad
Faulting process id: 0x6dc
Faulting application start time: 0x01d4524fda30ef6f
Faulting application path: G:\Prepar3D\Prepar3D.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: b91cdc56-be4b-11e8-98f9-7824af43cf7e
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="2018-09-22T09:41:48.000000000Z" />
<EventRecordID>82346</EventRecordID>
<Channel>Application</Channel>
<Computer>Peter-PC</Computer>
<Security />
</System>
<EventData>
<Data>Prepar3D.exe</Data>
<Data>4.3.29.25520</Data>
<Data>5b2c3263</Data>
<Data>ntdll.dll</Data>
<Data>6.1.7601.24231</Data>
<Data>5b6db5a7</Data>
<Data>c000000d</Data>
<Data>000000000008b2ad</Data>
<Data>6dc</Data>
<Data>01d4524fda30ef6f</Data>
<Data>G:\Prepar3D\Prepar3D.exe</Data>
<Data>C:\Windows\SYSTEM32\ntdll.dll</Data>
<Data>b91cdc56-be4b-11e8-98f9-7824af43cf7e</Data>
</EventData>
</Event>

[Nick - A2A]

Thanks Peter.

The error log doesn't show the A2A Accu-Sim dll but there are a couple of general troubleshooting steps you could try.

Delete the shaders folder:

C:\Users\[UserName]\AppData\Local\Lockheed Martin\Prepar3D v4\Shaders

Also delete the Prepar3D.cfg file:

C:\Users\[UserName]\AppData\Roaming\Lockheed Martin\Prepar3D v4\Prepar3D.cfg

Both will be regenerated next time you launch the sim.

If these steps don't help, a general web search for the issue should throw up plenty more troubleshooting threads.

Thanks,
Nick

[Petermuc3]

Thanks Nick,

yes I was about to do that, but thought I try here first as it does not happen with other aircraft.

Peter

[Petermuc3]

Unfortunatelly I still have P3D stopping and it seems that this is always happening when
in ORBX territory, like Germany South or KBZN (ORBX). No problems like KIDA payware or
LOWG payware etc.
Peter

[Petermuc3]

I nailed it down to ORBX airports, being it freeware or payware. As this happens only with the Bonanza
I was hoping to get some help here. Of course I will also ask in the ORBX forums.
Peter

[Nick - A2A]

Okay, thanks for the info Peter.

Please can you confirm if you've tried the two troubleshooting suggestions I mentioned above?

Nick

[Petermuc3]

Yes I did.
Peter

[Petermuc3]

After having installed the latest ORBX libraries at least on 2 ORBX airports the problem is gone.
Need to try some other but it looks good.
Peter

[Nick - A2A]

Okay, thanks for the update Peter. We didn't have any reports of ntdll.dll errors during testing of the Bonanza, so hopefully in your case the Orbx update will have fixed this on your system.

Cheers,
Nick

[Petermuc3]

Unfortunatelly my problem was not solved with the new libraries. Had CTD when approaching Palm Springs ORBX
but also when approaching Digital Design LOWS. It seams that on short flights (40-50nm) there is no problem, doing
100nm or more I get the CTD. I am not 100% sure but the CTD comes when I adjust mixture.
So any further help is much appreciated. Maybe I should reinstall the Bo. But I installed with admin rights, antivir off, but on a separate
drive as my system partition gets full.
Peter

[Nick - A2A]

Maybe I should reinstall the Bo. But I installed with admin rights, antivir off, but on a separate
drive as my system partition gets full.

Hello Peter,

When you say your "system partition gets full" how much space is remaining? Also, is P3D itself installed on this drive or a separate one? Certainly there's no problem installing the Bonanza to a different drive, but I'm wondering if lack of space on your system drive may be related to the CTDs.

Thanks,
Nick

[Petermuc3]

Hi Nick,
my system partition still has 9GB. P3D is installed on a separate drive, Bonanza is on the same drive.
Today I tried the flight KMYF-KPSP again, same problem, on approach around 12 miles out "P3D stopped working".
To make sure that there is no problem with P3D itself or scenery etc. I did the exact same flight with the FSL A320
and everything went fine. So there must be a problem with the Bonanza and my setup.
Do you think that reinstalling the Bonanza on the recommended drive would be a solution?

Thanks Peter

[Nick - A2A]

Hi Peter,

Though reinstalling the Bonanza wouldn't do any harm, you may be better of checking that basic core functionality of your operating system is up to date: thing like graphics card drivers and windows updates for example.

As you'll see if you Google "Prepar3D ntdll.dll error" or similar, there are lots of reports of this with different add-ons.

The general debugging advice on the Prepar3D forum is probably a good place to start with troubleshooting.

If you're able to systematically reproduce this error in the Bonanza, please let us know. In the meantime, I'll check with the coders to see if they have any further ideas.

Thanks,
Nick