Jump to content
Sign in to follow this  
ideoplastic

CTD caused by Simconnect

Recommended Posts

Recently did clean installation of Win7 64 on 2 PCs - One with FSX only and the other with ASN, widefs, etc.

 

I have had 4 CTDs mainly while on approach or close to landing. The error message is always the same.

 

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: SimConnect.dll, version: 10.0.61637.0, time stamp: 0x46fad5b6
Exception code: 0xc0000005
Fault offset: 0x000049d0
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13

 

Both PCs have the Acceleration simconnect version 10.0.61259.0 and after searching windows this is the only version I have found.

 

Totally stumped why this is happening. Any suggestions or feedback much appreciated.

 

Thanks

Share this post


Link to post
Share on other sites

One with FSX only and the other with ASN, widefs, etc.

Doesn't ASN have their own simconnect.msi for networked computers? See page 79 of the ASN Users Guide.

 

Best regards,


Jim Young | AVSIM Online! - Simming's Premier Resource!

Member, AVSIM Board of Directors - Serving AVSIM since 2001

Submit News to AVSIM
Important other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS)

I7 8086K  5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10 

 

Share this post


Link to post
Share on other sites

Thank you JIm, once again you are a lifesaver!

 

It was all my fault after all, when I set-up ASN for networking I made the terrible mistake of running the simmconect.msi from the acceleration SDK in the FSX PC, when it is only meant to be run on a client. After repairing Accelleration and reinstalling FSUIPC all seems to be good so far. It pays to pay close attention to the instruccions, sometimes I try to do things in a hurry which can lead to these problems.

 

All the best

Share this post


Link to post
Share on other sites

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
Sign in to follow this  

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...