P3D v4 w/ Hotfix Clicking on Primary Flight Display Causes CTD

[CXA001 5]

This has happened to me a couple of times now where if I am doing a 3+ hour flight and click on the primary flight display P3Dv4 will CTD.

I have had this issue with the 737NGX, 777 and B744 QOSII.

Event log is as follows:

Log Name:      Application
Source:        Application Error
Date:          15/07/2017 11:27:09 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:       
Description:
Faulting application name: Prepar3D.exe, version: 4.0.28.21686, time stamp: 0x594a7255
Faulting module name: api.dll, version: 4.0.28.21686, time stamp: 0x594a7300
Exception code: 0xc000041d
Fault offset: 0x0000000000025090
Faulting process id: 0x6f0
Faulting application start time: 0x01d2fdc6d1d2b804
Faulting application path: C:\Lockheed Martin Prepar3D v4\Prepar3D.exe
Faulting module path: C:\Lockheed Martin Prepar3D v4\api.dll
Report Id: a61bd216-69d6-11e7-b980-d4bed9fd63cc
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-07-16T03:27:09.000000000Z" />
    <EventRecordID>44895</EventRecordID>
    <Channel>Application</Channel>
    <Computer> </Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.0.28.21686</Data>
    <Data>594a7255</Data>
    <Data>api.dll</Data>
    <Data>4.0.28.21686</Data>
    <Data>594a7300</Data>
    <Data>c000041d</Data>
    <Data>0000000000025090</Data>
    <Data>6f0</Data>
    <Data>01d2fdc6d1d2b804</Data>
    <Data>C:\Lockheed Martin Prepar3D v4\Prepar3D.exe</Data>
    <Data>C:\Lockheed Martin Prepar3D v4\api.dll</Data>
    <Data>a61bd216-69d6-11e7-b980-d4bed9fd63cc</Data>
  </EventData>
</Event>

My P3D settings are not exaggerated (i.e. sliders to the max) and get very good performance with the sim, so I am confident it is not a performance issue.

Any ideas?