Nine hour flight. About twenty minutes to go. CTD on view change. Running ChasePlane 0.4.180 Beta; PMDG T7. No issues throughout the flight changing views etc, until the CTD. I thought this was the FSX days... Details from the event viewer are below. Any thoughts on why would be great. Thnx.

My system:
Win 10 64 PRO
i7 5820K @ 4Mhz
32GB DDR4
GTX1070

Cheers

Faulting application name: Prepar3D.exe, version: 4.1.7.22841, time stamp: 0x59d67e95
Faulting module name: KERNELBASE.dll, version: 10.0.15063.726, time stamp: 0x1a9bbe0b
Exception code: 0xc000041d
Fault offset: 0x0000000000069d98
Faulting process id: 0x34cc
Faulting application start time: 0x01d3920060244576
Faulting application path: D:\P3DV4\Prepar3D.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 2c979e2a-873f-499f-8293-39493b6ad36f
Faulting package full name: 
Faulting package-relative application ID: 

Fault bucket 1831304271380590242, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 4.1.7.22841
P3: 59d67e95
P4: KERNELBASE.dll
P5: 10.0.15063.726
P6: 1a9bbe0b
P7: c000041d
P8: 0000000000069d98
P9: 
P10:

Same issue. This is the third occasion P3Dv4 has crashed in very similar circumstances. Approx 6.5 hrs flight time, on descent between FL200 - FL150. Three different locations 2 x FlyTampa (YSSY & OMDB) and ORBX (YMML).

I am using latest Chase Plane, ActiveSky (P3Dv4), MT6 and AivlaSoft EFB - each flight was PMDG QOTS II. Definitely not an OOM and FR around 35-40 when CTD occurred.

Thought I read somewhere that a recent (last month or so) system update my cause issues.

Bloody frustrating getting to the approach phase after almost 7 hours and losing it.

Any ideas appreciated.

cheers Steve

The AVSIM CTD Guide provides some suggestions, like below:

Kernelbase.dll – A system file so a problem with your computer system.  FSX or P3D just happened to be running when the event occurred.  Related to StackHash errors and NTDLL.dll errors.  No known fix but some have solved this problem by -

• Settings too high.  Rebuild FSX/P3D config.  (most likely cause)
• Updating or reinstalling their video card drivers. 
• Scanning your system for corrupt/missing files.
• Disable startup programs by typing msconfig in the Windows search box.  When open, look at the Startup tab and disable all startups (they are all not needed for operation of your computer).
• User Profile Corrupted – last resort, fix possible corrupted user profile.

I would rebuild the P3D.cfg and try the same flight with the default P3D settings.  High settings place a lot of stress on your system. If the crashes go away, then you will know this is or is not the fix.  Something just as simple as removing cloud reflections could fix this issue (for your computer system and no one else).