nor969

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

Yes, I do have that update. I'll try the fixes listed and see how it goes. Thanks again for the help, Chris Herner

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

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

I only got the Introduction and the Tutorial, but none of the other manuals downloaded when I bought the plane. What happened? How do I submit a trouble ticket?

I only got the Introduction and the Tutorial, but none of the other manuals downloaded when I bought the plane. What happened? How do I submit a trouble ticket?

I do have the registered version of FSUIPC. How, exactly, do I do that? I am excited that there is a solution out there! Chris

Thanks for that. Is there a way to do it FSUIPC? Or are there settings within the MD-11 itself that will allow me to assign all 3 throttles to 2 throttles on the joystick? Chris

I can't seem to figure out how to assign all 3 throttles to my 2 throttle joystick. I always ends up with only controlling 2 of the throttles, and the third one doesn't move. Can somebody help me with this? Thanks, Chris

No, I never mess with the clock. It started after installed the Superbug by Vertical Reality, so I removed it but the problem persists. Chris

Has nobody else experienced this problem? Any ideas?

The time to next waypoint in the navigation display (upper right hand corner) just keeps changing at a really fast rate. It never settles down and just keeps running through the numbers. Any ideas on how to fix this? Chris Herner

Ok, I just tried turning down the drivers and it had exactly zero effect. So, now I will try the next suggestion and see if that makes a difference. thanks again and keep it coming! Chris Herner

Ok, I'll try and turn down the sliders and see what happens. Thanks for the help and if anyone else has any other clever ideas I am all ears. Chris Herner

Yea I tried that. I have also followed all the directions in the ngx manual for how to set up fsx and also the directions offered here for how to set up my nvidia drivers (I have a gtx 285). Anything else I can try? Again, any help is appreciated. Chris Herner

I have a problem with FSX, which is that when I run it in dx9 mode it consistently does strange things with the graphics (black screen, skeleton planes, etc); in other words, I can't use the simulation in dx9. In dx10, however, it works just fine. I can switch between full screen and windowed without any problems, and, generally, there are few if any problems. Can anybody help me with this? I read everywhere that I should never run fsx in dx10 because it is buggy and slow, but I find that dx9 is buggy, although it looks prettier when it works, which typically isn't for very long. Any suggestions?? Thank you in advance. Chris Herner

Yeah, I have tried reinstalling. I also used the guide for installing, and all my drivers are up to date. I have tried deleting fsx.cfg. Nothing seems to work.

I give up! No matter what I do the stupid thing either freezes, says I am out of memory, looses half of the graphics so the cockpit is see through. I have a nice new system (i7, 6gig, gtx 285, vista premium 64bit, ASUS P6TSE) and ASA installed. The only air plane I run is the PMDG MD-11. Something always goes wrong and I basically cannot play the game. Does anyone know if there are any fixes coming from Microsoft?chris

I am not sure about actual rules about autoland. On vatsim, however, I find that I can fly manually even on approach as long as I have the radio freq's programmed ahead of time. I also turn off a/t and just set n1 to something that approximates the speed I want. If there is turb the speed bounces up and down but no big deal. Even if I have to let go of controls for a few seconds to change freq's or even enter a freq the plane more or less continues in the direction I left it in, so long as you are trimmed properly and also have proper power settings. At least for me that works.christoffer

Hi everybody, great product! I have only one problem. When I first click on the before taxi checklist, I get the following error on the desktop: creation failed: check if sound file is available. I already uninstalled fs2crew, copied the original aircraft.cfg files, installed the update that allows the pmdg 600-700 virtual cockpit to be clickable then reinstalled fs2crew. Still same error. I happens on both the 700 and 800. I can keep going by cancelling the error then go back into fs and continue clicking the green box for my responses. Any ideas? Christoffer Herner