Jump to content
The simFlight Network Forums

Recommended Posts

Posted

MSFS crashes after loading. I see the FSUICP splash screen about halfway through loading wait. 

I'll paste a copy of the Application Log from Event Viewer and FSUICP7.log

Log Name:      Application
Source:        Application Error
Date:          1/1/2023 12:57:00 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Pixel-Crusher
Description:
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x637cad1c
Exception code: 0x80000003
Fault offset: 0x0000000001fd0282
Faulting process id: 0x5c2c
Faulting application start time: 0x01d91da454518b77
Faulting application path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: 57ca6248-2143-427a-b28a-d5f2b3b98551
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="2023-01-01T05:57:00.1445035Z" />
    <EventRecordID>20804</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Pixel-Crusher</Computer>
    <Security />
  </System>
  <EventData>
    <Data>FlightSimulator.exe</Data>
    <Data>1.29.30.0</Data>
    <Data>637cad1c</Data>
    <Data>FlightSimulator.exe</Data>
    <Data>1.29.30.0</Data>
    <Data>637cad1c</Data>
    <Data>80000003</Data>
    <Data>0000000001fd0282</Data>
    <Data>5c2c</Data>
    <Data>01d91da454518b77</Data>
    <Data>F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data>
    <Data>F:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe</Data>
    <Data>57ca6248-2143-427a-b28a-d5f2b3b98551</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>

 

********* FSUIPC7, Version 7.3.15 (15th November 2022) by John Dowson *********
Steam installation detected: Checking for FS path in 'C:\Users\Brian\AppData\Roaming\Microsoft Flight Simulator\UserCfg.opt'
FS path found = F:\Program Files (F)\
WebSocket server found: C:\FSUIPC7\\Utils\FSUIPCWebSocketServer.exe
Windows 10 Home 64 Bit reported as Build 19044, Release ID: 2009 (OS 10.0)
Reading options from "C:\FSUIPC7\FSUIPC7.ini"
Checking the Registrations now ...
User Name=""
User Addr=""
FSUIPC7 not user registered
WIDEFS7 not user registered, or expired
      110 System time = 01/01/2023 00:56:22
      110 FLT path = "C:\Users\Brian\AppData\Roaming\Microsoft Flight Simulator\"
      110 Allowing calibration when not assigned with 'Send direct to FSUIPC Calibration'
      110 -------------------------------------------------------------------
      125 Preset file 'C:\FSUIPC7\myevents.txt' not found [info only]
      125 8374 Calculator Code presets have been loaded and are available for use
      204 Registered HotKey 'InvokeFSUIPCOptionsKey' (key=0x46, modifier=0x1)
      235 FS path = "F:\Program Files (F)\"
      235 ### Note: AI Traffic related facilities and data are inhibited!
      250 LogOptions=00000000 00000001
     3204 Simulator detected
    25954 SimConnect_Open succeeded
    25954 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
    25954 MSFS version = 11.0.282174.999
    25954 Initialising SimConnect data requests now
    25954 Offset file 'C:\FSUIPC7\myOffsets.txt' not found (info only)
    26157 Maximum number of custom events available is 1024 (defined by ini parameter MaxNumberOfCustomEvents)
    34094 F:\Program Files (F)\Community\flybywire-aircraft-a320-neo\SimObjects\Airplanes\FlyByWire_A320_NEO\aircraft.CFG
    35110 Aircraft loaded: running normally now ...
    35157 User Aircraft ID not supplied -- trying default
    36532 System time = 01/01/2023 00:56:58, Simulator time = 04:56:56 (05:56Z)
    40219 Failed on SimConnect_CallDispatch for Message, return = 0xC000014B
    43204 MSFS no longer running - exiting
    43219 === Hot key unregistered
    43219 === Stop called ...
    43219 === Closing external processes we started ...
    43719 === About to kill any Lua plug-ins still running ...
    44641 === About to kill my timers ...
    44641 === Restoring window procs ...
    44641 === Unloading libraries ...
    44641 === stopping other threads ...
    44641 === ... Button scanning ...
    44750 === ... Axis scanning ...
    44860 === Releasing joystick devices ...
    44860 === Freeing macro memory
    44860 === Removing any offset overrides
    44860 === Clearing any displays left
    44860 === Calling SimConnect_Close ...
    44969 === SimConnect_Close done!
    44969 === AI slots deleted!
    44969 === Freeing button memory ...
    44969 === Closing my Windows ...
    44969 === Freeing FS libraries ...
    45985 === Closing devices ...
    45985 === Closing the Log ... Bye Bye! ...
    45985 System time = 01/01/2023 00:57:07
    45985 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Average frame rate for running time of 5 secs = 39.5 fps
Memory managed: 2 Allocs, 1 Freed
********* FSUIPC Log file closed ***********

</Event>

If I missed anything pls let me know. 

 

Thank you, and Happy New Year!

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.