Initially this event happened on Jan 20th after my PC updated to Win10 build 1709. I am not certain this is the root cause but the proximity of the update to appearance of the problem is suspicious...

On starting P3D with the Majestic Q400 in a saved state partway through a flight P3D loaded, the Q400 was screwed up, with control inputs unresponsive, indicators flashing and was generally unuseable. (I have had this occur following a win10 update before and reinstalling the Q400 fixed the problem...not so this time however!)

I exited P3D and attempted to load a new flight but every attempt subsequently has resulted in P3D 4.1 CTD a few seconds after clicking 'load scenario'.

This occurs regardless of whether the a/c selected is an add-on or default a/c, with scenery in default state or not, with no external apps running.

I have attempt the following:
1. cleared shaders
2. used the 'delete generated files' shortcut in the P3D root folder
3. moved the 'Prepar3D v4 Add-ons' folder to the desktop
4. deactivated all scenery in scenery library
All actions result in the same CTD, no change
My PC says it has all windows updates updated properly
I have uninstalled and reinstalled the P3D 4.1 client, again no change.

Any other ideas please people?
Thanks Kevin

 

PS after reboot P3D loaded up the default flight scenario.  After closing P3D I am back to CTD every time again in the same way....

Hi Kevin,

You should post the event from your Event Viewer or download AppCrashView and post the results here.  See the AVSIM CTD Guide (see link in my signature) for details.  The Event Viewer and/or AppCrashView will show the faulting module and, although the module may or may not be the cause of your crash(es), it provides a clue.  In the Event Viewer, look in Custom Views>Administrative Events.  This will show you every issue with your computer as well as every crash or freeze.  Look for one with P3D in it.

Whenever you shutdown P3D, getting a CTD is common depending on the software installed on your system.  I have gotten them occasionally and now have enabled 'prompt on exit'.  That should stop those CTD's.  It is a known problem where an add-on application does not completely shutdown.

Best regards,

Jim

Event Viewer..

Prepar3D.exe
4.1.7.22841
59d67e95
ntdll.dll
10.0.16299.192
6dead514
c0000374
00000000000f87cb
810
01d398e6a4d4cece
C:\Prepar3D v4\Prepar3D.exe
C:\WINDOWS\SYSTEM32\ntdll.dll
92207576-6004-4e19-8aa4-ce9433d3c9b9

 

AppcrashView

Version=1
EventType=APPCRASH
EventTime=131616930988833546
ReportType=2
Consent=1
UploadTime=131616931003363745
ReportStatus=268435456
ReportIdentifier=9bd523fb-1546-4ad1-b614-f884b9cbd284
IntegratorReportIdentifier=92207576-6004-4e19-8aa4-ce9433d3c9b9
Wow64Host=34404
NsAppName=Prepar3D.exe
AppSessionGuid=00000810-0001-000a-cece-d4a4e698d301
TargetAppId=W:0000f0e3cd7a622a9f58f96eda9e904fcd8500000904!0000fe4ba4844cdbd482c25c2fa58f1644d0a18615dd!Prepar3D.exe
TargetAppVer=2017//10//05:18:48:53!2d051c!Prepar3D.exe
BootId=4294967295
TargetAsId=1173
UserImpactVector=271593744
Response.BucketId=6d03e8c8cbf6db097513d3141d6adf5b
Response.BucketTable=4
Response.LegacyBucketId=1518789582700339035
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Prepar3D.exe
Sig[1].Name=Application Version
Sig[1].Value=4.1.7.22841
Sig[2].Name=Application Timestamp
Sig[2].Value=59d67e95
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_6c62
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.16299.192
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=6dead514
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=PCH_0C_FROM_ntdll+0x00000000000A09C4

 

Interestingly enough, the default F22 scenario CTD's but if I load another addon a/c then P3D does load the scenario?

You are getting a StackHash and NTDLL which indicates too high settings.  If you have MyTrafficX installed, you need to disable the mytrafficmil.bgl (known fix).  Also, I see you have your system overclocked to 4.8GHz.  I would save those settings in the ASUS BIOS (think under tools) and then load the optimized defaults.  These are all known fixes for this error.  See my pinned topic in this forum.