Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Not sure if this is where I should be posting this, but here goes... had a CTD tonight with FSUIPC4.dll being reported as the culprit. Here's what I've got:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: FSUIPC4.dll, version: 4.9.3.9, time stamp: 0x54d9e947
Exception code: 0xc0000005
Fault offset: 0x0004c87b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
 
Any suggestions? I'm not very savvy with this sort of thing so it might as well be in Klingon. Any help would be greatly appreciated.
Posted

 

Not sure if this is where I should be posting this, but here goes... had a CTD tonight with FSUIPC4.dll being reported as the culprit. Here's what I've got:

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: FSUIPC4.dll, version: 4.9.3.9, time stamp: 0x54d9e947
Exception code: 0xc0000005
Fault offset: 0x0004c87b
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
 
Any suggestions? I'm not very savvy with this sort of thing so it might as well be in Klingon. Any help would be greatly appreciated.

 

 

Is a log produced?  I'd need to see that too, please.

 

And please try again with the very latest test version, Install FSUIPC4939b_TEST so that any crash data you get will match my current code.

 

Pete

 

 

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.