Author Topic: KMEM CTD  (Read 5709 times)

mbell

  • Newbie
  • *
  • Posts: 24
KMEM CTD
« on: July 19, 2016, 07:24:39 am »
Sorry for a repeat post. I have read the other posts and updated Fuisip and ASN. After KMEM loads I get the load symbol (spinning circle) and it crashes. The SODE test shows active. All of your other airports work fine. Please help.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51367
    • VIRTUALI Sagl
Re: KMEM CTD
« Reply #1 on: July 19, 2016, 01:48:11 pm »
Sorry for a repeat post. I have read the other posts and updated Fuisip and ASN.

So you would probably have seen that, all crashes were caused by something else. Do you have Ezdok camera too ? If yes, you must update to the very latest version, because they confirmed crashes with earlier versions.

Latest reports from an affected user, said it was caused by FSUIPC, but it's not possible for us to understand why ( I have FSUIPC installed and it works fine at KMEM ) and Pete Dowson is currently on vacation.

mbell

  • Newbie
  • *
  • Posts: 24
Re: KMEM CTD
« Reply #2 on: July 19, 2016, 06:35:06 pm »
I don't have EZDOC. Updated FUISIP and ASN

Hnla

  • Hero Member
  • *****
  • Posts: 697
Re: KMEM CTD
« Reply #3 on: July 19, 2016, 07:49:46 pm »
I don't have EZDOC. Updated FUISIP and ASN

Post your crash report from windows event viewer in this thread:

http://www.fsdreamteam.com/forum/index.php/topic,13623.0.html

mbell

  • Newbie
  • *
  • Posts: 24
Re: KMEM CTD
« Reply #4 on: July 19, 2016, 07:53:13 pm »
Where do I go to get this? I have Windows 7

Hnla

  • Hero Member
  • *****
  • Posts: 697
Re: KMEM CTD
« Reply #5 on: July 19, 2016, 07:56:46 pm »
Where do I go to get this? I have Windows 7

Go to start->Right Click on Computer->Manage->Event Viewer->Application->Select the FSX Error.

Post contents here.

mbell

  • Newbie
  • *
  • Posts: 24
Re: KMEM CTD
« Reply #6 on: July 19, 2016, 08:10:59 pm »
Here you go
Log Name:      Application
Source:        Windows Error Reporting
Date:          7/18/2016 11:19:27 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-PC
Description:
Fault bucket 678795150, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: fsx.exe
P2: 10.0.61637.0
P3: 46fadb14
P4: g2d.dll
P5: 10.0.61637.0
P6: 46fadb58
P7: c0000005
P8: 00085da0
P9:
P10:

Attached files:
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\dxdiag.txt
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\scenery.cfg
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\fdr.dat
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\dll.xml
C:\Users\Michael\AppData\Local\Temp\WER5773.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Michael\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_88c03cf1253a2f692965b166e7c23a9b4136b_1d2b707e

Analysis symbol:
Rechecking for solution: 0
Report Id: f698ab86-4d67-11e6-aaa2-180373e3c2e3
Report Status: 0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-07-19T04:19:27.000000000Z" />
    <EventRecordID>147792</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Michael-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>678795150</Data>
    <Data>1</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>fsx.exe</Data>
    <Data>10.0.61637.0</Data>
    <Data>46fadb14</Data>
    <Data>g2d.dll</Data>
    <Data>10.0.61637.0</Data>
    <Data>46fadb58</Data>
    <Data>c0000005</Data>
    <Data>00085da0</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\dxdiag.txt
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\scenery.cfg
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\fdr.dat
C:\Users\Michael\AppData\Roaming\Microsoft\FSX\dll.xml
C:\Users\Michael\AppData\Local\Temp\WER5773.tmp.WERInternalMetadata.xml</Data>
    <Data>C:\Users\Michael\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_88c03cf1253a2f692965b166e7c23a9b4136b_1d2b707e</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>f698ab86-4d67-11e6-aaa2-180373e3c2e3</Data>
    <Data>0</Data>
  </EventData>
</Event>

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51367
    • VIRTUALI Sagl
Re: KMEM CTD
« Reply #7 on: July 20, 2016, 02:45:38 pm »
Try to turn off AI traffic entirely, and see if the crash happens again.