Jump to content
The simFlight Network Forums

MSFS 2020 FSUIPC 7 CTD


Georgios Giannoukos
 Share

Recommended Posts

Hello, since i installed the final release of FSUIPC 7, I get CTD one after the other.

Here is the event viewer. Please Advise and support 

Thank you,

Georgios

Log Name:      Application
Source:        Application Error
Date:          02/09/2021 10:48:25
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-EOVLSGP
Description:
Faulting application name: FSUIPC7.exe, version: 7.2.0.7, time stamp: 0x6123de89
Faulting module name: FSUIPC7.exe, version: 7.2.0.7, time stamp: 0x6123de89
Exception code: 0xc0000005
Fault offset: 0x00000000000198a4
Faulting process id: 0x274c
Faulting application start time: 0x01d79fcd9dbb2ef7
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report Id: 9eaf7fae-ec19-4980-9a8e-5f5266cc431c
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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-02T07:48:25.7558667Z" />
    <EventRecordID>36527</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-EOVLSGP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.7</Data>
    <Data>6123de89</Data>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.7</Data>
    <Data>6123de89</Data>
    <Data>c0000005</Data>
    <Data>00000000000198a4</Data>
    <Data>274c</Data>
    <Data>01d79fcd9dbb2ef7</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>9eaf7fae-ec19-4980-9a8e-5f5266cc431c</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

2,

Log Name:      Application
Source:        Application Error
Date:          02/09/2021 10:33:05
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-EOVLSGP
Description:
Faulting application name: FSUIPC7.exe, version: 7.2.0.7, time stamp: 0x6123de89
Faulting module name: FSUIPC7.exe, version: 7.2.0.7, time stamp: 0x6123de89
Exception code: 0xc0000005
Fault offset: 0x00000000000198a4
Faulting process id: 0x12e8
Faulting application start time: 0x01d79fcaa51dd123
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report Id: 2aa99e0c-5165-43af-bd30-968ea6053152
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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-02T07:33:05.3795437Z" />
    <EventRecordID>36521</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-EOVLSGP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.7</Data>
    <Data>6123de89</Data>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.7</Data>
    <Data>6123de89</Data>
    <Data>c0000005</Data>
    <Data>00000000000198a4</Data>
    <Data>12e8</Data>
    <Data>01d79fcaa51dd123</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>2aa99e0c-5165-43af-bd30-968ea6053152</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

 

3,

Log Name:      Application
Source:        Application Error
Date:          02/09/2021 10:32:57
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-EOVLSGP
Description:
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001a12757
Faulting process id: 0x1e68
Faulting application start time: 0x01d79fca61d0a1c2
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: c1d4cc44-4e83-41be-aff4-1fd4518b4b46
Faulting package full name: Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-02T07:32:57.3215261Z" />
    <EventRecordID>36518</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-EOVLSGP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>0.0.0.0</Data>
    <Data>00000000</Data>
    <Data>c0000005</Data>
    <Data>0000000001a12757</Data>
    <Data>1e68</Data>
    <Data>01d79fca61d0a1c2</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data>
    <Data>c1d4cc44-4e83-41be-aff4-1fd4518b4b46</Data>
    <Data>Microsoft.FlightSimulator_1.18.15.0_x64__8wekyb3d8bbwe</Data>
    <Data>App</Data>
  </EventData>
</Event>

Link to comment
Share on other sites

First, please download and update to v7.2.8. Then replace the FSUIPC7.exe with the attached one and try again: FSUIPC7.exe

If you still get a CTD, please show me  your FSUIPC7.log and FSUIPC7.ini files, as well as the Event viewer info, thanks.

The Event viewer info you posted shows that it was MSFS that actually crashed first, causing an issue in FSUIPC7 afterwards. If you check your FSUIPC7.log file, you will most probably find that it exited automatically due to MSFS crashing.

Link to comment
Share on other sites

FSUIPC7.log

FSUIPC7.ini

Log Name:      Application
Source:        Application Error
Date:          02/09/2021 14:24:16
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      DESKTOP-EOVLSGP
Description:
Faulting application name: FSUIPC7.exe, version: 7.2.0.9, time stamp: 0x612fb88d
Faulting module name: FSUIPC7.exe, version: 7.2.0.9, time stamp: 0x612fb88d
Exception code: 0xc0000005
Fault offset: 0x00000000000198a4
Faulting process id: 0x944
Faulting application start time: 0x01d79feb36129e8f
Faulting application path: C:\FSUIPC7\FSUIPC7.exe
Faulting module path: C:\FSUIPC7\FSUIPC7.exe
Report Id: a7d44e85-5e4b-4f8b-8f95-a57f706b19fc
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>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2021-09-02T11:24:16.7255729Z" />
    <EventRecordID>36586</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-EOVLSGP</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.9</Data>
    <Data>612fb88d</Data>
    <Data>FSUIPC7.exe</Data>
    <Data>7.2.0.9</Data>
    <Data>612fb88d</Data>
    <Data>c0000005</Data>
    <Data>00000000000198a4</Data>
    <Data>944</Data>
    <Data>01d79feb36129e8f</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>C:\FSUIPC7\FSUIPC7.exe</Data>
    <Data>a7d44e85-5e4b-4f8b-8f95-a57f706b19fc</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Link to comment
Share on other sites

2 hours ago, Georgios Giannoukos said:

v7.2.8 was updated also replaced the .exe file as you advised but still CTD. Please accept the files you requested and please advise

Your FSUIPC7.log file shows that it was MSFS that crashed, and FSUIPC7 exited normally:
 

Quote

   ...
   793094 MSFS no longer running - exiting
   ...

FSUIPC7 will exit when MSFS CTDs. If you check your Event viewer logs, I'm sure you will see and MSFS crash report entry before that of FSUIPC7. As O said, when MSFS CTDs, this creates an exception in FSUIPC7 as the SimConnect handle is no longer valid. This will generate fault reports in FSUIPC, but they are handled gracefully. However, when FSUIPC7 is auto-started by MSFS, it must close when MSFS is no longer available, otherwise the MSFS process will not exit cleanly.

So, your problem is with MSFS - you need to check the Asobo forums on CTD issues and raise a new report if necessary.

If you want to verify this, start FSUIPC7 manually BEFORE you start MSFS, and uncheck the option Exit with FS. You will get an error when MSFS tries to start FSUIPC7, but this can be ignored. When you do this, you will see that if/when MSFS CTDs, FSUIPC7 keeps running. So the promlem is with MSFS/Asobo, not FSUIPC.

John

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.