# Prepare P3D 3.4 CTD ,prevent long flight & Kill sim passion

## Recommended Posts

Hello Flights simmers

I have a big problem that kill the want to use the sim & the black beast of every one which is sim crash

I was stable at flight level 370 in 01H30 flight and approaching to top of descent when suddenly the screen became black and a small window message telling me "Display driver stopped responding and has recovered", few seconds after P3D not respond and crash . this happened to me several time at different phase of flights and not in all flights ;it's random , your help will be very much appreciated to rescue my flight sim life .

Using appcrash view i get the following results :

Prepar3D.exe    Stopped working    09/01/2018 23:24:51    All Users    0xc0000005    0x002206c0    g2d.dll    3.4.9.18400    C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe    41.342    C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_a18a94db1b5a475db875a3258913e84d447ea618_670bd722\Report.wer

Version=1
EventType=APPCRASH
EventTime=131600102913210275
ReportType=2
Consent=1
ReportIdentifier=e823833e-f58b-11e7-96a4-bc5ff4f7752c
IntegratorReportIdentifier=e823833d-f58b-11e7-96a4-bc5ff4f7752c
WOW64=1
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=g2d.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=3.4.9.18400
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=57d9b22e
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=002206c0
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1036
UI[2]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe
UI[3]=A fatal error occurred.
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
LoadedModule[179]=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Aerosoft\Flight Recorder\AS-FlightRecorder.dll
Sec[0].Key=LCID
Sec[0].Value=1036
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Lockheed Martin® Prepar3D®
AppPath=C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe

Present Addons on the flight :

PMDG737-EZDOC Camera-ORBX - FSWX -LInda- FSUIPC-go flight module

PC :

Nvidia Geforce GTX 770

RAM : 16 go

CPU : AMD A10 7850K Radeon R7,12 Compute core 4C+8G 3.70 GHZ

For any more details ,please don't hesitate

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

G2D possible fixes –

• Rebuild the sim’s config, as appropriate (moving or renaming the config and then restarting the application).
• Uninstall/reinstall video card drivers or go back to previous version.  Make sure drivers are not ‘beta’.
• 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.

I personally think you have a high setting in your P3D.cfg and/or display drivers (which should not be touched).  Renaming the P3D.cfg to P3D.cfg.off and restarting the sim and flying the flight should fix the problem.  You should not try to adjust any of the settings (other than the monitor resolution).  You are investigating to see if it is the P3D.cfg that is causing the G2D error.

Best regards,

Jim

##### Share on other sites

Hi Jim

I will apply your suggestions and return back to you , it will take a lot of time as i can't know where and when the problem come back ,as i reported above itnot happen in all flights .

I will test and report

Thanks again

##### Share on other sites

I did not see where you stated it did not occur on every flight.  Just some.  I have read it again and still cannot see where you stated that.

In any case, you have a 32 bit application and only 4GB's of Virtual Address Space (VAS).  If you have high settings in your P3D.cfg, any flight you have may not always be successful.  It depends on the weather, the aircraft, the scenery, the time of the day, and autogen and AI settings.  This is because, when P3DV3 runs out of VAS or low on VAS, the sim will crash.  Most of the time it will say you have run out of memory (VAS) but any error msg could pop up.

With P3DV3 and earlier, you cannot have high settings at all or risk running out of VAS.  So, my suggestion to rename your P3D.cfg remains valid and is the best possible solution for your scenario.  You have a powerful system and that's the problem too in that you think you can have high settings because you think your system can handle the high settings.  With P3Dv3 and earlier, you cannot mess with your settings or be very careful as to how high you raise your settings.  It is the main reason why many have moved to P3DV4 as you have unlimited VAS and you can raise your settings as high as you want (but will still suffer performance problems with low FPS).

Best regards,

Jim

##### Share on other sites

Quote

this happened to me several time at different phase of flights and not in all flights ;it's random

Unquote

Thank you Jim for all the cited clarification

Best regards

## 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!

$23,205.00 of$36,000.00 goal reached.