Jump to content
The simFlight Network Forums

Help with MSFS 2020 crash


james12
 Share

Recommended Posts

Hello Sir.  Can you please help me with MSFS 2020 crash problem ?  When using the MCDU in the default or fly by wire A320 the screen freezes for about 2 seconds and closes quickly. I have removed FSUICP to ensure its the cause of the problem.  Thanks much.

Link to comment
Share on other sites

13 hours ago, james12 said:

I have removed FSUICP to ensure its the cause of the problem. 

This does not ensure that FSUIPC is the cause of the problem. FSUIPC7 is a standalone executable - if it crashes, will not affect MSFS.
Did you check the windows event viewer to see if any crash or fault events were logged? If not, please check. Also, check your FSUIPC7.log file - you will most likely find that FUIPC7 exited normally as MSFS crashed - FSUIPC7 will always exit when MSFS crashes if it was auto-started by MSFS.

If you find an MSFS crash event in your windows event log, you should report the crash to Asobo and include the crash report.

Link to comment
Share on other sites

Hello Sir, this is going to painful for you as I'm not so good navigating windows.

Faulting application name: FSUIPC7.exe, version: 7.2.0.0, time stamp: 0x60be5226

Faulting module name: FSUIPC7.exe, version: 7.2.0.0, time stamp: 0x60be5226

Exception code: 0xc0000005

Fault offset: 0x0000000000019884

Faulting process id: 0x884

Faulting application start time: 0x01d76119e72ec154

Faulting application path: C:\FSUIPC7\FSUIPC7.exe

Faulting module path: C:\FSUIPC7\FSUIPC7.exe

Report Id: 8dec728b-568d-46ea-a0e6-51107026379f

Faulting package full name: 

Faulting package-relative application ID: 


 

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7

Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x60a521f7

Exception code: 0xc0000005

Fault offset: 0x00000000007bec13

Faulting process id: 0x179c

Faulting application start time: 0x01d76119b7e670be

Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe

Report Id: f027774c-2c7e-4f41-9b95-a1ddb1904462

Faulting package full name: Microsoft.FlightSimulator_1.16.2.0_x64__8wekyb3d8bbwe

Faulting package-relative application ID: App

 

Does this help?

Link to comment
Share on other sites

10 minutes ago, james12 said:

Does this help?

Yes, but your FSUIPC7.log file would also have been useful.

The events you posted show that it was MSFS that crashed. When this occurs, it generates a fault/exception in FSUIPC7, but FSUIPC7 should just close down nuormally as MSFS is no longer available. Your FSUIPC7.log file would confirm this.

So it looks like MSFS is crashing, nd FSUIPC7 is exiting gracefully as MSFS is no longer available. You should report the CTD to Asobo, including the information from the Event viewer.

 

Link to comment
Share on other sites

11 minutes ago, james12 said:

Could you be so kind to explain how to find FSUIPC7.log file?

The log file is in your FSUIPC7 installation folder. If you do not know where that is, you can use the File -> Open Installation Folder... menu option.
If you cannot see the log file, you have windows explorer set to hide known extensions. If this is the case, please see the Addendum in the Installing and Registering FSUIPC7.pdf.

 

 

Link to comment
Share on other sites

********* FSUIPC7, Version 7.1.0 (9th May 2021) by John Dowson *********
No registry entries found for MSFS - setting paths from APPDATA env variable
Checking for FS path in 'C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt'
FS path found = G:\FS2020\
WebSocket server found: G:\FSUIPC7ini\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "G:\FSUIPC7ini\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Sébastien Gomez"
User Addr="nopub.noreply@pm.me"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
      125 System time = 05/06/2021 12:43:17
      125 FLT path = "C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\"
      234 -------------------------------------------------------------------
      297 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      328 FS path = "G:\FS2020\"
      328 ---------------------- Joystick Device Scan -----------------------
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      375    GUIDs returned for product: VID_1234&PID_BEAD:
      375       GUID= {800CF910-793A-11EB-800C-444553540000}
      375       Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      375 Product= R-VPC Stick MT-50CM2
      375    Manufacturer= VIRPIL Controls/20210102
      375    Vendor=3344, Product=4130 (Version 0.1)
      375    GUIDs returned for product: VID_3344&PID_4130:
      375       GUID= {930E5E60-7902-11EB-8009-444553540000}
      375       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V16384,X16384,Y16384,Z16384
      375 Product= L-VPC Throttle MT-50CM3
      375    Manufacturer= VIRPIL Controls/20210102
      375    Vendor=3344, Product=8194 (Version 0.1)
      375    GUIDs returned for product: VID_3344&PID_8194:
      375       GUID= {E1695770-78F5-11EB-8007-444553540000}
      375       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      375 -------------------------------------------------------------------
      406    WARNING: Joystick ID 0 is duplicated in Registry
      406 Device acquired for use:
      406    Joystick ID = 2 (Registry okay)
      406    2=vJoy Device
      406    2.GUID={800CF910-793A-11EB-800C-444553540000}
      406 Device acquired for use:
      406    Joystick ID = 1 (Registry okay)
      406    1=RIGHT VPC Stick MT-50CM2
      406    1.GUID={930E5E60-7902-11EB-8009-444553540000}
      406 Device acquired for use:
      406    Joystick ID = 0 (Registry okay)
      406    0=LEFT VPC Throttle MT-50CM3
      406    0.GUID={E1697E80-78F5-11EB-8008-444553540000}
      406 -------------------------------------------------------------------
      438 LogOptions=00000000 00000001
     3281 Simulator detected
     8297   [INFO]: Connected to MSFS
     8375 SimConnect_Open succeeded
     8375 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
     8375 MSFS version = 11.0.282174.999
     8375 Initialising SimConnect data requests now
     8422 C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
     8422 SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
     8422 User Aircraft ID 1 supplied, now being used
     8516 Aircraft loaded: running normally now ...

 

is this right ? thanks again 

Link to comment
Share on other sites

10 hours ago, james12 said:

is this right ?

That is a log file from the 5th June. It is incomplete, so looks like FSUIPC7 did crash. However, you are also using an old and now unsupported version of FSUIPC7 - the current (and only supported version) is v7.2.0 - can you please update.

Once updated, if you experience your crash again, please show me the log file from the crash + any (and all) error from the Windows Event log + a description of what you were doing (i.e. what were you doing with the MCDU?). Thanks.

Link to comment
Share on other sites

FSUIPC7 v7.2.0 released on 8th June 2021 contains the following changes:
  - 'state' of AI traffic in trafic tables/offsets now populated correctly
  - removed logging of slope adjustments when no slope applied
  - Added new FSUIPC control: Trigger Auto-save. Used to manually trigger an 'auto-save'.
  - Added new facility to add lvars to offsets vi an LvarsToOffsets ini parameter section
  - WAPI/WASM updated to v0.5.1
  - AUTOPILOT VS SLOT INDEX simvar added to offset 0x02FC
  - Enabled write to offset 0x0818 AUTOPILOT ALTITUDE LOCK VAR:3. Write in feet, uses AP_ALT_VAR_SET_ENGLISH control
  - Updated to MSFS SDK 0.13.0 including adding additional events provided
  - Increased number of entries allowed under [AlsoManage] ini section from 32 to 64
  - Flagged LIGHT_POTENTIOMETER_SET as axis control
FSUIPC7 v7.1.0 released on 9th May 2021 contains the following changes:
  - Added simvars TURB ENG IGNITION SWITCH EX1:1/2/3/4 to offset area at 0x02C0/1/2/3.
  - Updated to recognise up to 128 buttons in Buttons Assignment panel
  - Added integration to the FSUIPC WASM module to provide lvar access as in FSUIPC5/6 (i.e. via macros and lua scripts)
  - additional lua functions added to read/write lvars as strings: readLvarSTR, writeLvarSTR
  - additional lua function added to activate hvars: activateHvar
  - WASM menu added to Add-ons menu when FSUIPC WASM detected
  - Read-only protection removed from offsets A000-A200 (so now available as free user offsets, as documented).
FSUIPC7 v7.0.9 released on 14th April 2021 contains the following changes:
  - rebuild against SDK 0.12.0.0 for MSFS 1.15.7.0
FSUIPC7 v7.0.8 released on 20th March 2021 contains the following changes:
  - fix for offset monitoring bug
  - fix to start axes scanning when FSUIPC7 started and MSFS already running + flight loaded
FSUIPC7 v7.0.7 released on 18th March 2021 contains the following changes:
  - update to starting/stopping [Auto] luas: now started when ready-to-fly
  - changes to default stall times
  - updates to killing luas to prevent problems when using the com library
  - correctuin to transponder offset 0x0354
  - correction to monitor functionality
FSUIPC7 v7.0.6 released on 10th March 2021 contains the following changes:
  - rebuilt against the latest MSFS SDK v0.11.0.0
  - changes to internal re-connection timers
  - Java SDK by Mouseviator updated to v1.1
FSUIPC7 v7.0.5 released on 17th February 2021 contains the following changes:
  - bug fixed that caused issues loading multiple *.evt files
  - New offsets added:
    0x0290 - AUTOPILOT ALTITUDE SLOT INDEX
    0x0294 - AUTOPILOT HEADING SLOT INDEX
    0x0298 - AUTOPILOT SPEED SLOT INDEX
    0x029D - APU SWITCH
  - increased allowable initial max stall time
  - built agaimst MSFS SDK 0.10.0.0
FSUIPC7 v7.0.4 released on 9th January 2021 contains the following changes:
  - fixed bug in key assignments to allow assignment to numpad keys with numlock off (PgDn, End, etc)
  - Correction to registry scanning that caused a crash when a non-existant device found
  - initial button delay now working, and improvements for a more accurate repeat rate (esp. with virtual buttons)
  - Further controls added from 0.9.0.0 SDK
  - lua event.cancel() function corrected to cancel all events on the argument function (previously only cancelled first found)
  - Further offsets added:
        0x0C10: GEAR CENTER STEER ANGLE
        0x0C46: AUTOBRAKES ACTIVE
        0c0C47 LIGHT BRAKE ON
  - added command-line option '-auto' that, when present, removes the 'Exit with FS' option and makes this mandatory
        (used when auto-starting FSUIPC7 from MSFS EXE.dll)
  - added new ini parameter AdjustNavForMagVar that adjusts the Nav1/2 in offsets 0x870 &7 0x0844 with magnetic variation
  - profile creation update to allow an empty axis profile to be created (i.e. when creating a new axis profile and not importing General axes)
 
FSUIPC7 v7.0.3 released on 24th December 2020 contains the following changes:
  - new *_EX1 controls added for throttle and prop pitch
  - console window position correction for -ve values
  - Autobrake offset added for A320Neo (0x0260)
  - reverted pushback direction select control (was reverted due to an SDK error that has now been corrected)
  - offset 0x0278 re-activated (Autocord Set)
  - Re-enabled offset 0x2F58 for write (Fuel Selected Transfer Mode)
  - Increased max parameter allowed for autobrake offset 0x2F80 to 6 (was 5)
  - arrow keys re-mapped for key input to allow assignment
  - added offsets for main control surface slopes (calibration) at offset 0x08A2
  - offsets for ALTITUDE and ATTITUDE FREEZE ON added at offsets 0x081C and 0x081D (although these are currently not populayed correctly for most, if not all, aircraft)
 
FSUIPC7 v7.0.2 released on 28th November 2020 contains the following changes:
  - Recompiled against MSFS SDK 0.8.0.0
  - Additional pause (sleep) control added
  - add-on controls now correctly annotated
  - allow DontLogThese ini parameter to be used in [Profile.xxx] sections (to be profile specific)
  - Allow MaxSteerSpeed to be set from user-defined offset. Also additional control added to set MaxSteerSpeed
  - List of axes controls updated
  - Alt key modifier re-activated, i.e. can now use as a modifier both when assigning keypresses and sending key presses to the sim
  - Added sim variable AUTOPILOT ALTITUDE LOCK VAR:3 at offset 0x0818
  - Correction to bug in loading macro files that only accessed L:vars (only 1st was recognised)
 
FSUIPC7 v7.0.1 released on 11th November 2020 contains the following changes:
  - Re-built against MSFS SDK 0.7.1.0
  - Fix for bug in Lua sound.play function
  - Improvemements to reconnection process when MSFS is restarted and FSUIPC7 left running
  - minor update to Delphi SDK

John Dowson
24th December 2020

 

Pretty sure this isn't what you looking for

Link to comment
Share on other sites

OK found it sorry again.... this is going to strange but.... while using the MCDU if I select a transition on the right side it closes immediately.

******** FSUIPC7, Version 7.1.0 (9th May 2021) by John Dowson *********
No registry entries found for MSFS - setting paths from APPDATA env variable
Checking for FS path in 'C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt'
FS path found = G:\FS2020\
WebSocket server found: G:\FSUIPC7ini\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Pro 64 Bit reported as Build 19042, Release ID: 2009 (OS 10.0)
Reading options from "G:\FSUIPC7ini\FSUIPC7.ini"
Checking the Registrations now ...
User Name="Sébastien Gomez"
User Addr="nopub.noreply@pm.me"
FSUIPC7 Key is provided
WIDEFS7 not user registered, or expired
      125 System time = 05/06/2021 12:43:17
      125 FLT path = "C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\"
      234 -------------------------------------------------------------------
      297 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      328 FS path = "G:\FS2020\"
      328 ---------------------- Joystick Device Scan -----------------------
      328 Product= vJoy - Virtual Joystick
      328    Manufacturer= Shaul Eizikovich
      328    Serial Number= 2.1.9
      328    Vendor=1234, Product=BEAD (Version 2.25)
      375    GUIDs returned for product: VID_1234&PID_BEAD:
      375       GUID= {800CF910-793A-11EB-800C-444553540000}
      375       Details: Btns=128, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      375 Product= R-VPC Stick MT-50CM2
      375    Manufacturer= VIRPIL Controls/20210102
      375    Vendor=3344, Product=4130 (Version 0.1)
      375    GUIDs returned for product: VID_3344&PID_4130:
      375       GUID= {930E5E60-7902-11EB-8009-444553540000}
      375       Details: Btns=31, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U16384,V16384,X16384,Y16384,Z16384
      375 Product= L-VPC Throttle MT-50CM3
      375    Manufacturer= VIRPIL Controls/20210102
      375    Vendor=3344, Product=8194 (Version 0.1)
      375    GUIDs returned for product: VID_3344&PID_8194:
      375       GUID= {E1695770-78F5-11EB-8007-444553540000}
      375       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X0,Y0,Z0
      375 -------------------------------------------------------------------
      406    WARNING: Joystick ID 0 is duplicated in Registry
      406 Device acquired for use:
      406    Joystick ID = 2 (Registry okay)
      406    2=vJoy Device
      406    2.GUID={800CF910-793A-11EB-800C-444553540000}
      406 Device acquired for use:
      406    Joystick ID = 1 (Registry okay)
      406    1=RIGHT VPC Stick MT-50CM2
      406    1.GUID={930E5E60-7902-11EB-8009-444553540000}
      406 Device acquired for use:
      406    Joystick ID = 0 (Registry okay)
      406    0=LEFT VPC Throttle MT-50CM3
      406    0.GUID={E1697E80-78F5-11EB-8008-444553540000}
      406 -------------------------------------------------------------------
      438 LogOptions=00000000 00000001
     3281 Simulator detected
     8297   [INFO]: Connected to MSFS
     8375 SimConnect_Open succeeded
     8375 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
     8375 MSFS version = 11.0.282174.999
     8375 Initialising SimConnect data requests now
     8422 C:\Users\Seb\AppData\Roaming\Microsoft Flight Simulator\MISSIONS\Custom\CustomFlight\CustomFlight.FLT
     8422 SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
     8422 User Aircraft ID 1 supplied, now being used
     8516 Aircraft loaded: running normally now ...

 

Link to comment
Share on other sites

9 minutes ago, james12 said:

Pretty sure this isn't what you looking for

No - thats the changes.txt file that I provide...

5 minutes ago, james12 said:

OK found it sorry again....

But this is exactly the same log that you previously posted. Did you not read my last comment? i.e. update to the latest (and only) supported version and try again, and show me the new log file if you get a CTD, together with all Windows Event error logs.

Link to comment
Share on other sites

Just now, james12 said:

I removed it and it works fine. we are going to have to agree to disagree.

Sorry, but disagree on what? I am still waiting to see your log file from v7.2.0 that you still have not provided. I cannot help you until you show me this file (from when you say FSUIPC7 crashed). Once I've seen that, we can go from there.
 

2 minutes ago, james12 said:

I will wait till you release an updated version and try again.

But any updated version will not necessarily fix your issue, as we do not know where it lies or what is the cause at the moment. It is strange that you ask for help but do not want to provide me with the information so that I can help you with your issue.

Link to comment
Share on other sites

One thing you can try to verify that it is FSUIPC7 crashing (or not, as the case may be) is the following:
   - start FSUIPC7 manually before you start MSFS
   - uncheck the option 'Exit with FS'
   - start MSFS. If you have MSFS set to auto-start FSUIPC7, this will generate an error which you can acknowledge and then ignore
   - Fly until you get your CTD
#When you do that, does MSFS CTD and FSUIPC7 keep running, or does FSUIPC7 exit/crash? If the latter, it is a problem in FSUIPC7 and you should show me your log file. If the former, FSUIPC7 is not crashing but exiting normally as MSFS has crashed, and this needs to be reported to Asobo.

  • Like 1
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.