The Dreaded Return of ntdll.dll

[seanlister1]

Hello all,

It's happened after a good year of no crashing, it's returned and I'm at a loss. Was just exiting my NAT track on EGLL - CYUL and boom P3D just closes. Here's the event from event viewer.

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x74bed8b0
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x33e8
Faulting application start time: 0x01d4d8e150fdfff7
Faulting application path: I:\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e2b4de58-26c9-40b2-a2df-c93fcaa60958
Faulting package full name:
Faulting package-relative application ID:

[Martyson]

Hello all,

It's happened after a good year of no crashing, it's returned and I'm at a loss. Was just exiting my NAT track on EGLL - CYUL and boom P3D just closes. Here's the event from event viewer.

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x74bed8b0
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x33e8
Faulting application start time: 0x01d4d8e150fdfff7
Faulting application path: I:\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e2b4de58-26c9-40b2-a2df-c93fcaa60958
Faulting package full name:
Faulting package-relative application ID:

Which aircraft?

[sw34669]

did you see this ..... https://www.prepar3d.com/forum/viewtopi ... 2&t=129041

[seanlister1]

Hello all,

It's happened after a good year of no crashing, it's returned and I'm at a loss. Was just exiting my NAT track on EGLL - CYUL and boom P3D just closes. Here's the event from event viewer.

Faulting application name: Prepar3D.exe, version: 4.4.16.27077, time stamp: 0x5bfdbb35
Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x74bed8b0
Exception code: 0xc0000374
Fault offset: 0x00000000000f479b
Faulting process id: 0x33e8
Faulting application start time: 0x01d4d8e150fdfff7
Faulting application path: I:\Prepar3D v4\Prepar3D.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: e2b4de58-26c9-40b2-a2df-c93fcaa60958
Faulting package full name:
Faulting package-relative application ID:

Which aircraft?

This one happened in the QW 787, I've had another one today int the PMDG 747-8

[KUB10]

[/quote]
This one happened in the QW 787, I've had another one today int the PMDG 747-8
[/quote]

Let me guess, your system is overclocked. This happens now every flight to me, since version 4.4, nerver had that ever before. It is bloody anoying, every new version comes with new hickups.

[Martyson]

This one happened in the QW 787, I've had another one today int the PMDG 747-8
[/quote]

Let me guess, your system is overclocked. This happens now every flight to me, since version 4.4, nerver had that ever before. It is bloody anoying, every new version comes with new hickups.
[/quote]

Does the problem happen at or near the same location?

How to recreate your crash?

[seanlister1]

This one happened in the QW 787, I've had another one today int the PMDG 747-8

Let me guess, your system is overclocked. This happens now every flight to me, since version 4.4, nerver had that ever before. It is bloody anoying, every new version comes with new hickups.
[/quote]

Does the problem happen at or near the same location?

How to recreate your crash?
[/quote]
My system isn't overclocked one bit, I crashed between greenland and canada. Then the same somewhere over Russia.