P3d CTD

Hey I have a problem with my simulator it keeps on crashing when it reaches a 100%.

And my other problem is that i keep on getting error creating child window is there any way to fix this.

I also did a fresh install of v3.4.22 all stock

PC Specs

CPU: Inetl i7 4790 3.6ghz (4.0ghz Turbo) Unparked

HDD: #1 2.5TB 7200rpm #2 1.5TB 7200rpm #3 1tb 5400rpm

OS: Win10 Home Insider Preview Builds (1703 version 16275.1000)

GPU: EVGA GTX 970 4gb ACX 2.0 SSC

RAM: 16gb 1600mhz Duel Channel

PSU; EVGA Supernova 850w P2 Platinum

Display: LG 42' 1080p TV

Peripherals: MSI DS-502 7.1 SURROUND Gaming Head Set Logitech M301 Wireless Keyboard and mouse Thrust master Tflight X HOTAS

P3d CTD

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: 0x0410ba00

Faulting process id: 0x35dc

Faulting application start time: 0x01d3195ec929e6b4

Faulting application path: C:\Lockheed Martin\Prepar3D V3.4.22\Prepar3D.exe

Faulting module path: unknown

Report Id: 150ed2dc-f3c9-420b-85a4-f73a633e6eb1

Faulting package full name:

Faulting package-relative application ID:

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: 0x0cf45590

Faulting process id: 0x14f0

Faulting application start time: 0x01d31ee36e2fb9fa

Faulting application path: C:\Lockheed Martin\Prepar3D V3.4.22\Prepar3D.exe

Faulting module path: unknown

Report Id: bec1bc41-0a0e-4a98-8b32-f91e70d7c618

Faulting package full name:

Faulting package-relative application ID:

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 0CF45590

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 .P3DAlert.SetCurrent(P3DAlert*, Int32)

at .P3DAlertSystem.UpdateModeless(Void*, Int32)

I probably will not be able to help u with P3D technical issues but I advise u to post an explanation of:

What do u mean by simulator reaching %100?

What do u mean by child window? R u trying to create a new view?

Good luck.

Sent from my iPhone using Tapatalk

all CFG's are default and when i click ok then it starts loading in once it reaches 100% it crashes

This is what the second error is (pic was taken 4 months ago)

latest crash P3d load test #426

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: 0x046b5590

Faulting process id: 0x6cc

Faulting application start time: 0x01d3200d241c0e7d

Faulting application path: C:\Prepar3D V3.4.22.19868\Prepar3D.exe

Faulting module path: unknown

Report Id: 2e47b103-c247-466a-8d2a-93c10a7ed50d

Faulting package full name:

Faulting package-relative application ID:

Disable all addons. Rename the dll.xml and exe.xml files. Shut down as many background programs. I notice from your screen cap that you might be running fraps.

Vic

This is from LM in 2015. Not sure if it will help but it is worth a shot. It may be caused by the controller you have plugged in. Try disconnecting your joystick and starting P3D. If it starts fine then shut it down and plug in your controller and try again.

Hello,

For this issue in particular there many different contributing factors (number of connected devices, types of devices connected, system performance, etc). We are aware of the many issues being reported in regards to the controls in general and plan to address them as soon as possible.

I will mark this issue as resolved for now since the proposed work-around seems to prevent the "Error Creating Child Window" message.

UPDATE:

I believe I have corrected this issue. The fix will be available in the next release.

Hi,

Looking at the stack trace this is an error in the .Net runtime and it is not telling you anything about what actually went wrong - it is basically just telling you that P3D can't display the error message window containing the actual problem. Seems a little bit like the spinning mouse cursor of death in FSX, where the sim would try to display an error message but can't.

Is your sim starting in windowed or fullscreen mode?

What I would do in this case:

Make sure that your .Net runtime and VC runtimes are intact and the exact versions that P3D requires.

PLEASE NOTE THAT YOU MUST HAVE MICROSOFT .NET FRAMEWORK 4.6.2 INSTALLED TO UPDATE TO HOTFIX 2

https://www.microsoft.com/de-de/download/details.aspx?id=53344

Visual C++ Redistributable Packages für Visual Studio 2013

https://www.microsoft.com/de-de/download/details.aspx?id=40784

And make sure that you don't have any localized versions of those (they would show up with a "clr" in their DLLs name).

I had the same error this weekend when I switched out hardware from my sim PC. It seemed to have somtehing to do with my external USB controllers too, because it just went away after all drivers had been updated.

Edit: I just noticed - I am not sure that P3D likes Win10 preview builds. It may be worth it to switch to a stable release version instead.

Hi,

 

Looking at the stack trace this is an error in the .Net runtime and it is not telling you anything about what actually went wrong - it is basically just telling you that P3D can't display the error message window containing the actual problem. Seems a little bit like the spinning mouse cursor of death in FSX, where the sim would try to display an error message but can't.

 

Is your sim starting in windowed or fullscreen mode?

 

What I would do in this case:

 

Make sure that your .Net runtime and VC runtimes are intact and the exact versions that P3D requires.

 

 

https://www.microsoft.com/de-de/download/details.aspx?id=53344

 

Visual C++ Redistributable Packages für Visual Studio 2013

https://www.microsoft.com/de-de/download/details.aspx?id=40784

 

And make sure that you don't have any localized versions of those (they would show up with a "clr" in their DLLs name).

 

I had the same error this weekend when I switched out hardware from my sim PC. It seemed to have somtehing to do with my external USB controllers too, because it just went away after all drivers had been updated.

 

Edit: I just noticed - I am not sure that P3D likes Win10 preview builds. It may be worth it to switch to a stable release version instead.

My sim starts in Full screen

According to other forum threads about this problem (CTD at 100%) it seems that it might be your controllers. Or rather the controller drivers. They recommend you unplug ALL your controllers. Then start P3D and if it runs then it's the controller drivers. When you plug them back in Win 10 should then go download (update) your controller drivers.

Chuck B

Napamule