PSX closing itself

[jobepilot 7]

Hi Nico

I still have this issue.  Any ideas ?  Psx closes itself for no reason.

Windows report

<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="2019-08-30T15:25:47.918037400Z" />

  <EventRecordID>4818</EventRecordID>

  <Channel>Application</Channel>

  <Computer>DESKTOP-79RE3FQ</Computer>

  <Security />

  </System>

- <EventData>

  <Data>PSXseeconTraffic64.exe</Data>

  <Data>16.0.0.0</Data>

  <Data>5d5ef79b</Data>

  <Data>PSXseeconTraffic64.exe</Data>

  <Data>16.0.0.0</Data>

  <Data>5d5ef79b</Data>

  <Data>c0000005</Data>

  <Data>00000000000724ca</Data>

  <Data>99c</Data>

  <Data>01d55efaa00382e1</Data>

  <Data>C:\PSXseeconTraffic\PSXseeconTraffic64.exe</Data>

  <Data>C:\PSXseeconTraffic\PSXseeconTraffic64.exe</Data>

  <Data>eae597dc-2c86-4956-a4ff-778f48014942</Data>

  <Data />

  <Data />

  </EventData>

  </Event>

 

 

Log Name:      Application
Source:        Application Error
Date:          30/08/2019 00:18:23
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-79RE3FQ
Description:
Faulting application name: PSXseeconTraffic64.exe, version: 16.0.0.0, time stamp: 0x5d5ef79b
Faulting module name: PSXseeconTraffic64.exe, version: 16.0.0.0, time stamp: 0x5d5ef79b
Exception code: 0xc0000005
Fault offset: 0x00000000000724ca
Faulting process ID: 0x3568
Faulting application start time: 0x01d55e8661ccfbce
Faulting application path: C:\PSXseeconTraffic\PSXseeconTraffic64.exe
Faulting module path: C:\PSXseeconTraffic\PSXseeconTraffic64.exe
Report ID: 91c93ed9-d888-4fcc-87d7-b623f580f5bf
Faulting package full name: 
Faulting package-relative application ID: 
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="2019-08-29T23:18:23.991994600Z" />
    <EventRecordID>4439</EventRecordID>
    <Channel>Application</Channel>
    <Computer>DESKTOP-79RE3FQ</Computer>
    <Security />
  </System>
  <EventData>
    <Data>PSXseeconTraffic64.exe</Data>
    <Data>16.0.0.0</Data>
    <Data>5d5ef79b</Data>
    <Data>PSXseeconTraffic64.exe</Data>
    <Data>16.0.0.0</Data>
    <Data>5d5ef79b</Data>
    <Data>c0000005</Data>
    <Data>00000000000724ca</Data>
    <Data>3568</Data>
    <Data>01d55e8661ccfbce</Data>
    <Data>C:\PSXseeconTraffic\PSXseeconTraffic64.exe</Data>
    <Data>C:\PSXseeconTraffic\PSXseeconTraffic64.exe</Data>
    <Data>91c93ed9-d888-4fcc-87d7-b623f580f5bf</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[kiek 1,204]

The exception code means "access violation" . That could be caused by  a null pointer in PSXT but then I'd expect more posts about this problem...

Another possible cause is bad memory. Could you check your RAM?

Edited August 30, 2019 by kiek

[jobepilot 7]

Interesting.  Will look into it.  It's been running for 30 hours no problem.  

 

Will report back. 

[riivrtwo 3]

Hi,

I've been having PSXT also close itself for at least 3 or 4 point releases. Very hard to track down, cleaned out all possible liveries errors but still closing at random intervals, sometimes OK for a day, sometimes multiple times in one day.

Has happened on two separate machines, which lowers the probability of bad ram.

 

Faulting application name: PSXseeconTraffic64.exe, version: 16.0.0.0, time stamp: 0x5d5ef79b
Faulting module name: PSXseeconTraffic64.exe, version: 16.0.0.0, time stamp: 0x5d5ef79b
Exception code: 0xc0000005
Fault offset: 0x00000000000724ca
Faulting process id: 0x10fc
Faulting application start time: 0x01d5621456d63371
Faulting application path: C:\Lockheed Martin\PSXseeconTraffic\PSXseeconTraffic64.exe
Faulting module path: C:\Lockheed Martin\PSXseeconTraffic\PSXseeconTraffic64.exe
Report Id: 5379bb27-2b16-4bbb-addb-57a0d5747efb
Faulting package full name: 
Faulting package-relative application ID: 

 

Hope this helps.

Edited September 5, 2019 by riivrtwo
.

[riivrtwo 3]

Just compared event logs from two machines. PSXT will sometimes close within a minute of each other on two different computers.

Is it possible malformed data in the RealTraffic stream is causing a problem in PSXT?

[jobepilot 7]

Mine ran for 35 hours non stop then closed itself.  Since then it has closed itself frequently.  

[kiek 1,204]

Are you guys running with third party AI? (Traffic slider in P3D/FSX not 0).

Edited September 8, 2019 by kiek

[jobepilot 7]

My AI is numerous.  FAIB, Ultimate traffic, Aim AIG, traffic global, and many more.

 

P3DV4 set to zero.  The AI in injected through your app.  

[GSalden 4,651]

On 9/5/2019 at 12:55 PM, riivrtwo said:

Just compared event logs from two machines. PSXT will sometimes close within a minute of each other on two different computers.

Is it possible malformed data in the RealTraffic stream is causing a problem in PSXT?

Probably a certain AI model is causing this.

Perhaps a FS9 aircraft that has been ported over to P3Dv4...

Start with only 1 AI Traffic package and test what happens. If everything is ok add a second one and so on.

 

[jobepilot 7]

Thanks.  Strange that it was running for 30 plus hours without an issue.  

 

When I get time I will look into it some more.

[kiek 1,204]

1 hour ago, GSalden said:

Probably a certain AI model is causing this.

Perhaps a FS9 aircraft that has been ported over to P3Dv4...

Start with only 1 AI Traffic package and test what happens. If everything is ok add a second one and so on.

 

A faulty livery may crash P3D but not PSXT. I don't think that is the cause.

PSXT crashes if it divides by 0 or has a dangling pointer or cannot access a memory location. These errors are very hard to find. Ofcourse I have taken all kinds of measures that this does not happen, for instance by using data structures and operations on data structures from a library (STL).

The strange thing is that so far only two users report these CTD's. This might indicate that local issues are involved.

[jobepilot 7]

It seems you are correct Nico.  It is model related.  I removed some AI, and no crash.  I will keep testing it.  

[kiek 1,204]

17 minutes ago, jobepilot said:

It seems you are correct Nico.  It is model related.  I removed some AI, and no crash.  I will keep testing it.  

Well  i doubt that would be the cause. It could be coincidental. 

The day before yesterday  I had PSXT closing itself too... I found a spot and corrected it in 16.2  but I will  continue to search my code for dangling pointers...

Edited September 16, 2019 by kiek

[jobepilot 7]

Ok thanks for the information.  Will monitor it