nor969

Prepar3d V3.4 Crashing with PMDG

Recommended Posts

Prepar3d V3.4 (I have the most recent version) crashes every time I try and load a PMDG product.  The simulator works fine with any other plane, just not the PMDG ones.  I have tried uninstalling everything, including the simulator (EZDOK 2.0, GEX World Edition 1.1, UTX Europe and USA, Active Sky 2016) and reinstalling it and the same results.  My NVIDIA display driver is updated, and I run windows 10.  Any suggestions?

 

Thanks,

Chris Herner 

Share this post


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

1. Yes, I run it as adminstrator

2. Event log:  (I have never looked at the event log before, so I hope this is the correct information; there were 5 events, 3 errors and 2 information events.  I copied and pasted all 5 below)

Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 08C8DD00
Stack:
   at MS.Win32.UnsafeNativeMethods.IntGetMessageW(System.Windows.Interop.MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32)
   at MS.Win32.UnsafeNativeMethods.GetMessageW(System.Windows.Interop.MSG ByRef, System.Runtime.InteropServices.HandleRef, Int32, Int32)
   at System.Windows.Threading.Dispatcher.GetMessage(System.Windows.Interop.MSG ByRef, IntPtr, Int32, Int32)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at Views.AlertBox.P3DAlertBox.ProcessPendingWorkItems()
   at Views.AlertBox.P3DAlertBox.OnProgressPercentChanged(System.Object)
   at MenuModels.AlertBox.AlertData.set_ProgressCurrent(Double)
   at <Module>.P3DAlert.SetCurrent(P3DAlert*, Int32)
   at <Module>.P3DAlertSystem.UpdateModeless(Void*, Int32)
 

Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x08c8dd00
Faulting process id: 0x193c
Faulting application start time: 0x01d33a18a7d23437
Faulting application path: E:\Prepar3D v3\Prepar3D.exe
Faulting module path: unknown
Report Id: 31bbd34d-f5f2-43e9-a781-f6e4911471ce
Faulting package full name: 
Faulting package-relative application ID: 

 

Fault bucket 116444676767, type 5
Event Name: BEX
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 3.4.22.19868
P3: 588f7cbf
P4: StackHash_ef7a
P5: 0.0.0.0
P6: 00000000
P7: PCH_AE_FROM_ntdll+0x000722CC
P8: c0000005
P9: 00000008
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCA0A.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBB1.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBBF.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERCBC0.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_7362d03ffb2ce6d1618bdcdaa61c470dbd9c37b_d937b49f_3710ee8a

Analysis symbol: 
Rechecking for solution: 0
Report Id: 31bbd34d-f5f2-43e9-a781-f6e4911471ce
Report Status: 268435456
 

Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc000041d
Fault offset: 0x08c8dd00
Faulting process id: 0x193c
Faulting application start time: 0x01d33a18a7d23437
Faulting application path: E:\Prepar3D v3\Prepar3D.exe
Faulting module path: unknown
Report Id: ae5417eb-6088-422b-8391-9546f502ccbf
Faulting package full name: 
Faulting package-relative application ID: 

 

Fault bucket 109055744440, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 3.4.22.19868
P3: 588f7cbf
P4: StackHash_ae2d
P5: 0.0.0.0
P6: 00000000
P7: c000041d
P8: PCH_0B_FROM_USER32+0x0002FA49
P9: 
P10: 

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF64.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0EC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0ED.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERF0FE.tmp.txt

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_fd327612f9a693d1aebff5ed963b21dd8d1b77d_d937b49f_18510463

Analysis symbol: 
Rechecking for solution: 0
Report Id: ae5417eb-6088-422b-8391-9546f502ccbf
Report Status: 268435456
 

Thanks for helping,

Chris Herner

Share this post


Link to post
Share on other sites

Yes, I do have that update.  I'll try the fixes listed and see how it goes.

 

Thanks again for the help,

Chris Herner

Share this post


Link to post
Share on other sites

Hah ditto on issue - thanks for the point in the right direction...

Regards,

Scott

Share this post


Link to post
Share on other sites

So, I tried all the various suggestions in the prepar3d forum, short of removing the Windows update, and I am having the same issue.  At this point, I am hopeful that the next update will fix the problem, unless there are other suggestions out there, which I am very interested in.

 

Thanks,

Chris

Share this post


Link to post
Share on other sites
14 hours ago, nor969 said:

So, I tried all the various suggestions in the prepar3d forum, short of removing the Windows update, and I am having the same issue.  At this point, I am hopeful that the next update will fix the problem, unless there are other suggestions out there, which I am very interested in.

 

Thanks,

Chris

Chris check if you have KB4040724 as well. This also have been reported to cause issues. Also after removing it make sure that you hide both of these updates so that they do not reinstall automatically.

 

 

Share this post


Link to post
Share on other sites

Maybe you have reached the max amount of sceneries installed (in my case this happenend with ca. 210 sceneriies installed) and that causes the CDT. Try to disable some of your sceneries you do not need. In my case this helped I can load any PMDG AC again.

 

Rgds Roland

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now