Jump to content
The simFlight Network Forums

FSUIPC4.dll caused FSX crashes to desktop (CTD) and restarts after loaded a flight


Recommended Posts

After I loaded a flight in FSX for about 5 to 10 seconds, it crashes and restarts. I tried to find a solution to this error in some forums including here and heard something called the Windows Event Viewer, and I found the problem which caused FSX to crash and restart is from FSUIPC4.dll.

Here is the faulting module:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: FSUIPC4.dll, version: 4.9.7.6, time stamp: 0x6001e32f
Exception code: 0xc00000fd
Fault offset: 0x000ded47
Faulting process id: 0x421c
Faulting application start time: 0x01d7860ce8558de7
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
Report Id: e4e67aea-8d3b-4d50-b22e-8e6daf716b64
Faulting package full name: 
Faulting package-relative application ID: 

And here's the log file that I attached here in case you need them.

FSUIPC4.log

Link to comment
Share on other sites

3 hours ago, Steven Nguyen said:

Faulting module name: FSUIPC4.dll, version: 4.9.7.6, time stamp: 0x6001e32f
Exception code: 0xc00000fd

Best I can make out is that exception FD is to do with a hardware driver.

The log you appended actually shows a good session with FSUIPC closing normally after 365 seconds (6 minutes):

   365797 === Closing session: waiting for DLLStop to be called ...
   388578 === DLLStop called ...
   388578 === Closing external processes we started ...
   389578 === About to kill any Lua plug-ins still running ...
   389719 === Closing global Lua thread
   390719 === About to kill my timers ...
   390922 === Restoring window procs ...
   390922 === Unloading libraries ...
   390922 === stopping other threads ...
   390922 === ... Memory checking ...
   390922 === ... Button scanning ...
   391031 === ... Axis scanning ...
   391125 === Releasing joystick devices ...
   391125 === Freeing macro memory
   391125 === Removing any offset overrides
   391125 === Clearing any displays left
   391125 === NOTE: not calling SimConnect_Close ...
   391125 === AI slots deleted!
   391125 === Freeing button memory ...
   391125 === Closing my Windows ...
   391141 === Freeing FS libraries ...
   392141 === Closing devices ...
   392141 === Closing the Log ... Bye Bye! ...
   392141 System time = 31/07/2021 20:18:01
   392141 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Minimum available memory recorded was 32768Mb
G3D fix: Passes 8266, Null pointers 0, Bad pointers 0, Separate instances 0
Maximum AI traffic for session was 0 aircraft
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

The meaning of error FD isn't clear, but if it is at all related to FSUIPC then it seems likely to be down to a driver for one of the devices you have connected.

You don't appear to be using FSUIPC for any joystick devices. Are you using any Lua plug-ins? Maybe you should show us your FSUIPC4.INI file which contains your settings.

Also, look further in the Windows Event Viewer to see if there's a preceding FSX crash.

If FSX is immediately restarting (which it shouldn't!) then a new log would be created when FSUIPC is loaded, so you reall need the Prev log, which is also saved.

You don't really supply enough information for me to help you further at present.

Pete

 

Link to comment
Share on other sites

On 7/31/2021 at 11:40 PM, Pete Dowson said:

Best I can make out is that exception FD is to do with a hardware driver.

The log you appended actually shows a good session with FSUIPC closing normally after 365 seconds (6 minutes):

   365797 === Closing session: waiting for DLLStop to be called ...
   388578 === DLLStop called ...
   388578 === Closing external processes we started ...
   389578 === About to kill any Lua plug-ins still running ...
   389719 === Closing global Lua thread
   390719 === About to kill my timers ...
   390922 === Restoring window procs ...
   390922 === Unloading libraries ...
   390922 === stopping other threads ...
   390922 === ... Memory checking ...
   390922 === ... Button scanning ...
   391031 === ... Axis scanning ...
   391125 === Releasing joystick devices ...
   391125 === Freeing macro memory
   391125 === Removing any offset overrides
   391125 === Clearing any displays left
   391125 === NOTE: not calling SimConnect_Close ...
   391125 === AI slots deleted!
   391125 === Freeing button memory ...
   391125 === Closing my Windows ...
   391141 === Freeing FS libraries ...
   392141 === Closing devices ...
   392141 === Closing the Log ... Bye Bye! ...
   392141 System time = 31/07/2021 20:18:01
   392141 *** FSUIPC log file being closed
Minimum frame rate was 32768.0 fps, Maximum was 0.0 fps
Minimum available memory recorded was 32768Mb
G3D fix: Passes 8266, Null pointers 0, Bad pointers 0, Separate instances 0
Maximum AI traffic for session was 0 aircraft
Memory managed: 4 Allocs, 4 Freed
********* FSUIPC Log file closed ***********

The meaning of error FD isn't clear, but if it is at all related to FSUIPC then it seems likely to be down to a driver for one of the devices you have connected.

You don't appear to be using FSUIPC for any joystick devices. Are you using any Lua plug-ins? Maybe you should show us your FSUIPC4.INI file which contains your settings.

Also, look further in the Windows Event Viewer to see if there's a preceding FSX crash.

If FSX is immediately restarting (which it shouldn't!) then a new log would be created when FSUIPC is loaded, so you reall need the Prev log, which is also saved.

You don't really supply enough information for me to help you further at present.

Pete

 

Ok, thanks for nothing. But I tried a solution which was to restart the computer and FSUIPC is okay now for me.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 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.