Error with P3D

[Bradallen43]

I'm probably going back to FSX because it seems that prepar3-D is more problematic than FSX. Just really frustrated by that program because every time I start it up, it seems something else is messed up. So ticked off right now.
Need a few days away from all of this.

 

[jeff3163]

Yes, a few days back in FSX should set you straight.   

Once you get P3D dialed in, you will never want to go back to FSX again.  So go back and look around.  Say goodbye to old friends and pack up your favorite stuff. (fsx native, of course.  No FS9!)   You've got time to get some coffee, read the paper, and check your email while it's loading.  When you change scenery locations, you can mow the lawn while you wait for that to reload.  P3D doesn't offer that kind of task management!  I still have both installed, but when I fly . . . it's in P3D.   

(maybe we can help you "dial in" P3D? )

[NeptuneP2V7]

YEP YEP .. As, Robert, JEFF,.... for me also, is very awesome ..P3d

all ORBX FTX, and some good planes...... and no more ...

FSX/DX10 for expérimantal trying .......

Patrick

[Bradallen43]

Okay, great. Please help me get this CTD problem sorted out if you can. Lockheed support is non-existent.

I'm getting CTD's now in P3D 2.2 Pro version. I can fly for only a few minutes then a crash to desktop occurs with the following event information shown.

Please let me know what I need to do to remedy this. I have nVidia driver 337.88 installed in my EVGA Titan X GPU and have not installed the latest problematic driver according to what I see on my system.

My Event view log.

Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53468776
Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521ea8e7
Exception code: 0xc0000374
Fault offset: 0x000ce753
Faulting process id: 0x101c
Faulting application start time: 0x01cfb00608dbe0d8
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: b86d1fb3-1bfa-11e4-a451-54271e918e12

Brad

[jeff3163]

Hello Brad,
     For some people, putting the UIAutomationCore.dll file from Vista into the root P3D folder fixes this error.  For others, it didn't.    I have it in both of my sims' root directories, and I don't get this crash.  It's worth a try.   

 
  https://www.dropbox.com/s/3jezw6imy2ntknk/UIAutomationCore.zip
UIAutomationCore.dll 
                 Size:  159,008
     Packed Size:  79,407
          Modified:  2014-08-04  20:01

Quote from N4gix on AvSim forum at:
( http://forum.avsim.net/topic/427572-the-menu-crashes-are-borderline-rediculous/page-2 )

The Vista version is 6.0.5840.16386

Also, can you specify what EXACTLY you and the sim are doing when it CTD? 
(Pause and then resume flight, or using the menu alot, or right-click menu, etc.) 

[Bradallen43]

Jeff, I'll give that a whirl. Thanks. The CTD is happening about a minute after I take off. During flight. Different locations too. Default flight at start up in the F-22 and a new flight in the Carenado C185 Tundra at CYYD.
Brad

[ualani]

If I recall, the UIAutomationCore.dll file was an answer to crashes caused by multiple clicks on the menu bar in the FSX window. This started happening with FSX SP2, and this fixed it for me. I seriously doubt that it will cure ntdll crashes.

[Dieter]

I'm sure that this problem is not related to the P3Dv2 itself.

Does this happen with every aircraft?

Are you using latest version of FSUIPC?
Did you try to deactivate FSUIPC?  Same problem then?

Latest NVIDIA driver?
Latest Sound drivers?

Interesting read:
http://en.wikipedia.org/wiki/Microsoft_Windows_library_files#Ntdll.dll

http://pcsupport.about.com/od/fixtheproblem/a/ntdlldll.htm

Dieter

[dexthom]

Yesterday I removed FSX from my system and I won't look back.  There are bugs in P3Dv2.2 but they will be fixed and the bugs that show up in 2.3 will be fixed.  As far as the LM forum is concerned, it's mostly "are we there yet" but there are a few knowledgeable folks on there who do offer help.  Take Jeff's advice and hang in for awhile.  think of it like you are a beta tester and continue on.  There are a bunch of folks that are still stuck on FS9 and new scenery is released every day.  This too will pass...

[ualani]

After reading the Wikipedia article, which is as clear as mud, it appears that ntdll is a library written around and for 32 bit architecture.  As long as P3D and FSX remain as 32 bit applications, this stuff is going to creep in for some people. Were you getting ntdll crashes in FSX too? I used to get them in FSX/DX9, (as well as D3Ddll crashes) on 4 different machines running both Xp and 7, but no more in DX10.  The only extremely rare crashes I get anymore are FSUIPC and Instant Scenery module related for some reason.

[Bradallen43]

Here's the popup error in P3D that I just got this morning less than a minute after taking off. Followed by a CTD.

[ualani]

What does your Windows Event Log say about this?

[Dieter]

Yes, content of Windows Event Log is important.

Additionally,
- do you have microsoft.net framework package installed and uptodate?
- Install/update latest Microsoft Visuals, only 32-bit version is necessary as P3D is a 32 bit application

Dieter

[Doug]

Brad...empty out the shaders folder. That is the cause that error.

[Bradallen43]

Event View shows this:

Faulting application name: Prepar3D.exe, version: 2.2.10438.0, time stamp: 0x53468776
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
Exception code: 0x40000015
Fault offset: 0x0008d6fd
Faulting process id: 0x6e4
Faulting application start time: 0x01cfb0ad8233017b
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: C:\Windows\system32\MSVCR100.dll
Report Id: 07135450-1ca3-11e4-9fcb-54271e918e12