Sign in to follow this  
callum112233

Suddenly getting API.dll error

Recommended Posts

Hi.

 

So a few days ago. FSX was working fine. I came to start up FSX this afternoon and the program won't even get pat the loading splash screen.

 

The only two recent things I have installed are:

 

The PMDG 777 update

Earth Simulations Isle of Man photoscenery

 

Now, I uninstalled both of the above to see if they were causing the error but I am still having the same problems.

 

Here is a screenshot of the error report.

 

Untitled_zpsr3btlt50.jpg

 

 

I appreciate any help but I fear I may have to do a total clean install of fsx :(

 

Callum.

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

program won't even get pat the loading splash screen.

A few days ago I had the same sudden freeze but with boxed fsx and the event log looked different but here's the thread: http://www.avsim.com/topic/480887-new-geforce-gtx-970-driver-crashes-fsx/

 

I had updated the NVIDIA driver and rolling back to the last version cleared everything right up.  No clue if it's your issue... good luck.

Share this post


Link to post
Share on other sites

A few days ago I had the same sudden freeze but with boxed fsx and the event log looked different but here's the thread: http://www.avsim.com/topic/480887-new-geforce-gtx-970-driver-crashes-fsx/

 

I had updated the NVIDIA driver and rolling back to the last version cleared everything right up.  No clue if it's your issue... good luck.

 

Sadly not the case for me. I give up. I am gonna re-install the lot.

Share this post


Link to post
Share on other sites

Just wondering if you actually have 2 problems.  One being the API.Dll crash and the other not being able to

 

get past the SPLASH screen being caused by a corrupted Logbook.bin file.  Try going to My

 

Documents/Flight Simulator X folder and rename the Logbook.bin to something like Logbook_old.bin

 

and the restart FSX to see if it will work.  If the Logbook got corrupted, it can be fixed with a logbook

 

repair program.

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