# P3D V3.4

## Recommended Posts

I'm facing crashes very often now, don't know what is causing it.

On App Crash View I see Couatl and P3D together sometimes.

Here is the Crash report for P3D:

Version=1
EventType=APPCRASH
EventTime=131264955774398235
ReportType=2
Consent=1
ReportIdentifier=62069971-c4bb-11e6-a244-08606eece9c7
IntegratorReportIdentifier=19078238-8629-4e63-a9c1-61acb0de3bc6
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=000019e4-0002-009d-714c-9521c758d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=5128539397502dc0d5f5379a6e79f5e8
Response.BucketTable=1
Response.LegacyBucketId=108633161545
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400
Sig[2].Name=Application Timestamp
Sig[2].Value=57d9b14e
Sig[3].Name=Fault Module Name
Sig[3].Value=util.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.4.9.18400
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=57d9b21a
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0001e86a
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1046
DynamicSig[22].Value=a6a1
DynamicSig[23].Value=a6a168da3d7661da609288f65e50f73c
DynamicSig[24].Value=79db
DynamicSig[25].Value=79db91a6b3a34cb93c38e75b76221f4e
UI[2]=E:\Simulator\Lockheed Martin\Prepar3D v3\Prepar3D.exe
UI[3]=Prepar3D exe has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Prepar3D exe
AppPath=E:\Simulator\Lockheed Martin\Prepar3D v3\Prepar3D.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=CF1BD4FB76FA39D9D3E874A8D6DB162A
MetadataHash=1287130517

This is the Coualt Crash Report:

﻿Version=1
EventType=APPCRASH
EventTime=131264955887318248
ReportType=2
Consent=1
ReportIdentifier=68bf09db-c4bb-11e6-a244-08606eece9c7
IntegratorReportIdentifier=0000b9ba-b772-4271-a664-3f12a1ff9ba9
WOW64=1
NsAppName=couatl.exe
AppSessionGuid=00003aa0-0002-009d-ed1d-694bc758d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!couatl.exe
TargetAppVer=2016//08//25:14:37:22!7f95fb!couatl.exe
BootId=4294967295
Response.BucketId=d2b2b8d11cf9f12988a1e2e10f2d5733
Response.BucketTable=1
Response.LegacyBucketId=108615020106
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=couatl.exe
Sig[1].Name=Application Version
Sig[1].Value=3.1.0.3536
Sig[2].Name=Application Timestamp
Sig[2].Value=57bf02a2
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_fbb0
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.14393.479
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=58256ca0
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_BF_FROM_ntdll+0x0006EB8C
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.14393.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1046
DynamicSig[22].Value=fbb0
DynamicSig[23].Value=fbb0523fdd6eea22a957853e315ac7d9
DynamicSig[24].Value=f316
DynamicSig[25].Value=f3168a455eaf02ea5796f2e5bf166fe4
UI[2]=E:\Simulator\Lockheed Martin\Prepar3D v3\fsdreamteam\couatl\couatl.exe
UI[3]=Couatl™ Scripting Engine for FSX//ESP has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Couatl™ Scripting Engine for FSX//ESP
AppPath=E:\Simulator\Lockheed Martin\Prepar3D v3\fsdreamteam\couatl\couatl.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=A305B6655E0EA404D9F8130B7E945C66
MetadataHash=239469192

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

Any incompatibilities will cause a Stackhash (see AVSIM CTD Guide regarding Stackhashes).    The fix above should fix all of your crashes but if you continue to get the util.dll error (which is extremely rare), you will have to go to Lockheed Martin and see if they have a fix for this crash there.

Best regards,

Jim

##### Share on other sites

Thanks Jim for the help.

I'm running P3D v3.4.9 not the latest 3.4.14

I already ran the Addon Manager stand alone installer to update my FSDT content.

AS16 I'm running the latest too the 6118 (not the Beta because I'm with 3.4.9 not the 3.4.14).

I have already the latest nvidia driver (I have a GTX 1080), already tried a clean install, it's not a problem, spent yesterday playing Battlefield 1 for a long period and no crash or any problem happened.

##### Share on other sites

New problem

﻿Version=1
EventType=APPCRASH
EventTime=131265449271665757
ReportType=2
Consent=1
ReportIdentifier=48c053cf-c52e-11e6-a245-08606eece9c7
IntegratorReportIdentifier=4646a0ca-5a95-48a6-bbf1-fbae5e93dcd3
WOW64=1
NsAppName=Prepar3D.exe
AppSessionGuid=000012bc-0001-009e-1c1f-73a63459d201
TargetAppId=W:0000da39a3ee5e6b4b0d3255bfef95601890afd80709!0000da39a3ee5e6b4b0d3255bfef95601890afd80709!Prepar3D.exe
TargetAppVer=2016//09//14:20:21:34!75f13!Prepar3D.exe
BootId=4294967295
Response.BucketId=e42b2a89cce99c65d5181f9110127933
Response.BucketTable=1
Response.LegacyBucketId=108634094951
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=3.4.9.18400
Sig[2].Name=Application Timestamp
Sig[2].Value=57d9b14e
Sig[3].Name=Fault Module Name
Sig[3].Value=nvwgf2um.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=21.21.13.7633
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=584d974c
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0084d8a1


##### Share on other sites

The latest crash is one of the Nvidia modules for version 376.33 (the latest driver).  I would go into C:\Intel\Display Drivers\and right click the setup for driver 376.33 and select Run as Administrator.  See if that works.

Suggest you go to your P3D.exe, right click it and then select Properties.  Open up the 'Compatibility' tab and look all the way down and click on Change settings for all users.  Look down in the next page and make sure it is marked to Run as an administrator there too.

Couatl errors occur occasionally when things get out of whack with your installation of P3D.  I would go on the FSDT website and download the latest Standalone Addon Manager and install it to get Couatl resyced.

If you continue to receive Stackhash and/or ntdll.dll errors and you know you have the proper versions of the Standalone, FSUIPC, ASN installed, then the next probability is your BIOS.  If you are overclocked to say, 4.4GHz, lower it to 4.2GHz, save and try again.  If it continues, reset your BIOS to the Optimal Defaults.

There is no known ONE solution for a Stackhash.  A stackhash is nothing as it is not a module or a file on your computer.  Something is probably stuck in memory.  I usually fix my stackhashes (you'll get them all of the time) by resetting my overclock but once I resolved it by reformatting my HDD and reinstalling Windows 7 and then all of FSX and all of my addons, one by one (ugh!).  I now do not think I needed to do that and resetting the BIOS usually fixes it.

Best regards,

Jim

##### Share on other sites

Hi Jim,

I have tried to do a driver clean install as Admin and running P3D 3.4.18 (updated) as Admin too, didn't use AS16 yet, now the problem maybe got worse because I had couple BSODs

My last guess is that Plane Chase is causing it, all add-ons are updated even the GSX newest release, FSUIPC 4959.

##### Share on other sites

My last guess is that Plane Chase is causing it, all add-ons are updated even the GSX newest release, FSUIPC 4959.

The only way you will know for sure is to disable it somehow or uninstall it and see if the problem reoccurs.  Does ChasePlane have a module loading in the dll.xml?  You can disable it there as per the instructions in the AVSIM CTD Guide.

If it is causing the crashes, you can check their support forums here at AVSIM for a solution.

Best regards,

Jim

##### Share on other sites

Happy 2017!

So, long time trying tons of tests and none of them worked.

My last resource, uninstall P3D and do a fresh install of the Sim and the Add-ons.

##### Share on other sites

Checking my minidump files I found some errors on Windows 10 Kernel and not my Nvidia Driver, and looking the date of the 1607 Windows 10 update it may be related, so before doing a clean install of P3D v3.4 I will reinstall the latest Windows 10 update and see what happens.

##### Share on other sites

Didn't work, I'm uninstalling everything, deleting all files inside %AppData% Local and Roaming, %ProgramData% and all registries related to P3Dv3 and Add-Ons inside Regedit.

Hope it solve my problems, because the only thing having problem is P3D v3, I have XP 10 and now XP 11 (my secondary Flight Sim) and I also play some new title games and never had a crash or BSOD with them.

Not to lie, XP11 I had some crash but they were add-on related because, after Flight Factor update I didn't have them again.

##### Share on other sites

The AVSIM CTD Guide, page 10, provides information on how to fix most crashes/freezes.  Reinstalling P3D and all of your addons is a last resort.  In the AVSIM CTD Guide, I tell you to move, rename or delete the p3d.cfg and let it rebuild.  If this does not fix the problem, you should then rename the scenery.cfg to scenery.old and restart P3D and let the config rebuild.  See if this fixes the problem.  If not, rename the dll.xml (there is one in the directory where the p3d.cfg is located and one (the new default) in the folder where the scenery.cfg is located.  Restart P3D.  The dll.xml will be rebuilt with the default.  You are now at the default configuration of P3D, exactly the same as if you uninstalled/reinstalled P3D.  If this does not fix the problem, then it is a computer system problem (most likely in the BIOS).

Best regards,

Jim

##### Share on other sites

So, I did clean install of P3D v3 and the g2d.dll crash still happening.

I already used the http://www.wagnardsoft.com/ tool to remove any other video driver remaining in my system and one registry from my GTX Titan X Maxwell, I upgraded to GTX 1080 it cleaned and I performed a clean install of nvidia driver 376.33.

I'm running out of options here, nothing else in my system was changed, CPU, Motherboard, BIOS they're very solid and don't have updates since 2014.

What else should I try?

##### Share on other sites

Now my P3D only have installed ORBX, REX+Soft Clouds (1024 textures) products and FSUIPC, nothing else.

My ORBX list

FTX Global

openLC Europe

openLC North America

Trees HD

Vector

ESSA

EU Airport Pack

NA Airport Pack

ORBX Libraries

EU England

EU Germany North

EU Ireland

EU Norway

EU Scotland

EU Wales

EGFF

NA Central Rockies

NA Northern California

NA Northern Rockies

NA Pacific Fjords

NA Pacific Northwest

NA Southern California

AU Australia

NZ North Island

NZ South Island

NZQN

My last 2 crashes were G2D.dll and I'm sure it's not Driver problem, just did the clean install

##### Share on other sites

I'm afraid that I have the same problem as this guy:

http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=122236&start=15

The AVSIM CTD Guide provides probable causes and possible fixes for the G2D.dll error (as collection from FS websites around the Internet).

Best regards,

Jim

##### Share on other sites

The AVSIM CTD Guide provides probable causes and possible fixes for the G2D.dll error (as collection from FS websites around the Internet).

Best regards,

Jim

I know, I read it and my causes are not them:

G2D.dll - This module handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running any simulator and the plain text words in the respective Menu, like the words Options, View, etc. There may be something corrupted in your dll.xml which loads menu items. Possible fixes –
 Rebuild the sim’s config, as appropriate (moving or renaming the config and then restarting the application).
I have a fresh install of P3D v3.4 hotfix 2
 Uninstall/reinstall video card drivers or go back to previous version. Make sure drivers are not ‘beta’.
Done and didn't work, used DDU tool (Display Driver Uninstaller)
 Do not disable ORBX/FTX, GEX, and/or UTX entries via the scenery.cfg. Use the appropriate interface utility to enable/disable features in these programs.
Already tried before installing ORBX sceneries.
 Move the dll.xml to a temporary folder and see if this fixes the problem. If so, there is a module in the dll.xml that is causing the problem.
already tried before the P3D v3.4 fresh install, didn't work and now I have fresh install of P3D v3.4

Everything related to CTD Guide I already did it and I still have the same issue.

##### Share on other sites

I have seen this error a lot since P3D.  It happened occasionally with FSX.  I was thinking it might be the updates/fixes to P3D but only a few are getting the error.  So it has to be the individual installation of P3D.  Sorry I could not find a fix.  I'm in the process of building a new system and will have to install Windows 10 as the i7 7700K requires it so I might be running into these problems soon myself.

Best regards,

Jim

##### Share on other sites

Not a problem Jim, thank you for your support so far!

I just installed a Hotfix driver from NVIDIA, the 376.60 and will test soon!

And we're in the same boat, I'm about to change my system to Kaby Lake.

##### Share on other sites

I have seen this error a lot since P3D.  It happened occasionally with FSX.  I was thinking it might be the updates/fixes to P3D but only a few are getting the error.  So it has to be the individual installation of P3D.  Sorry I could not find a fix.  I'm in the process of building a new system and will have to install Windows 10 as the i7 7700K requires it so I might be running into these problems soon myself.

Best regards,

Jim

Great news!

I'm not having crashes anymore, at least so far I did 3 flights around 1h30 each.

My i7 7700k arrived and I already overclocked it to 5ghz with 1.28V, looks like a great chip!

For the test I didn't format the OS, just replaced the drivers, to make sure the rig was almost the same apart from CPU, Mobo and memory.

Then I installed my i7 3770k back and the crash happened and started to dig more about it and found my chip with one core loading in P3D the voltage was going up to 1.4V, the core clocked down and the crash happened.

My mobo was set to 1.25V for 4.6Ghz overclock on 3770k chip, but somehow P3D load made the voltage increase and I found one setting that allowed the voltage to go up to 1.42, I set to be manual e offset only up to 1.25, went back to P3D and the crash was gone.

Moving back to my new rig, at least I found the cause of my crash

And about performance, I moved from 25 - 35 fps to 40-45

##### Share on other sites

My i7 7700k arrived and I already overclocked it to 5ghz with 1.28V, looks like a great chip!

It is a great chip!  I think you made a brilliant move upgrading from the 3770K to the 7700K.  I just went from 4770K to 7700K but I see improvements already and I still have not completed insalling everything. To hit an overclock at 4.5GHz by just telling the BIOS to give you the optimized default settings is awesome.  I installed ASUS Suite III and it automatically overclocked me to 5.0GHz and it thinks I can do more (see my specs in my signature).  My overclock is at 19% above the default. To think back in 2010 I could overclock my system to 5.0GHz automatically would have been mind-boogling!

But the computer experts say there are no major gains from the i7 6800K except for the fact the i7 7700K is sitting at 4.2GHz when you first turn it on and then 4.5GHz when you use the optimized defaults and most can only get a measly 4.8GHz overclock.  :smile:

In regards to FPS, I was way over 50 fps until I installed the PMDG 777/737 and I was starting to see the 40's in the FPS counter.  I just install MyTrafficProfessional and I'm now in the 20's some of the time but mostly over 30.  There is no fix for that.  An optimized or professionally developed program for modern systems is the only solution.  I am only using 30% AI and it is disappointing.  The Germans can do better!!  But I still like the program...

Best regards,

Jim

##### Share on other sites

It is a great chip!  I think you made a brilliant move upgrading from the 3770K to the 7700K.  I just went from 4770K to 7700K but I see improvements already and I still have not completed insalling everything. To hit an overclock at 4.5GHz by just telling the BIOS to give you the optimized default settings is awesome.  I installed ASUS Suite III and it automatically overclocked me to 5.0GHz and it thinks I can do more (see my specs in my signature).  My overclock is at 19% above the default. To think back in 2010 I could overclock my system to 5.0GHz automatically would have been mind-boogling!

But the computer experts say there are no major gains from the i7 6800K except for the fact the i7 7700K is sitting at 4.2GHz when you first turn it on and then 4.5GHz when you use the optimized defaults and most can only get a measly 4.8GHz overclock.  :smile:

In regards to FPS, I was way over 50 fps until I installed the PMDG 777/737 and I was starting to see the 40's in the FPS counter.  I just install MyTrafficProfessional and I'm now in the 20's some of the time but mostly over 30.  There is no fix for that.  An optimized or professionally developed program for modern systems is the only solution.  I am only using 30% AI and it is disappointing.  The Germans can do better!!  But I still like the program...

Best regards,

Jim

So, Jim, you're saying that in terms of P3D (FPS, stutters, etc) the move from the 4770K to the 7700K didn't improve things substantially, is that right?!

##### Share on other sites

That's incorrect.

##### Share on other sites

That's incorrect.

So I misunderstood when you said "there's no fix for that". Good to know anyway. I do have a 4770K aircooled running at 4.5 and wonder what the improvement would be with a 7700K.

##### Share on other sites

So I misunderstood when you said "there's no fix for that". Good to know anyway. I do have a 4770K aircooled running at 4.5 and wonder what the improvement would be with a 7700K.

The biggest difference is stability.  Having tried to overclock my 'old' air-cooled 4770K to 4.5GHz several times and thinking I was successful, I in fact was not successful because, 30, 60, or 90 days later I would get a StackHash or an ntdll.dll error and lowering the clock to 4.2GHz or returning to the optimized default (3.8GHz) always fixed this issue.  With the water-cooled i7 7770K cpu, it is sitting at 4.2GHz right out of the box.  Optimized default is 4.5GHz and, with ASUS Suite III, it was able to overclock to 5.0GHz automatically.  I didn't have to touch nothing.  So far very stable but time will only tell.  So, if you are an overclocker, and would like to be overclocked at 4.5GHz with optimized default settings, then the CPU is for you.  If you want to play with periodic stability issues with overclocking the 4770K, then you would want to stay with your current system.

As far as FPS/VAS usage, I have not seen that much difference and doubt I will ever see any improvements. As I stated above, AI is the difference, at least for me in regards to FPS.  VAS usage, negative impact or I haven't seen it yet.  P3D manages VAS well if properly configured.

Best regards,

Jim

##### Share on other sites

Thanks Jim for such a complete information. I'm running at the current clock for quite a few months already and I consider it stable, provided the room temperature doesn't get past 27 degrees Celsius (as per a thermometer installed nearby my rig), otherwise I may get a BSoD or have to turn aircond on. As a matter of fact I deeply suspect the temperature issue is related to the North Bridge stuff (which I have overclocked as well), as the fans never get too rapid. Anyway I plan to keep things like this and don't plan to change hardware anytime soon.

BTW: AI Traffic kills my frame rate as well, that's why I keep it at 1% (just aircraft) and also limit the absolute number down to 20. It's good enough not to give the impression of solitude. :-)

## Create an account

Register a new account

• Tom Allensworth,
Founder of AVSIM Online

• ### Hot Spots

• Flight Simulation's Premier Resource!

AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

• ### Donation Goals

AVSIM's 2018 Fundraising Goal

Donate to our annual general fund. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.

$19,365.00 of$36,000.00 goal reached.
Donate Now