Hello all

 

I've recently been suffering CTD's from API.DLL i beleive, its when i minimise FSX, it just has a fatal error, this is the log'

 

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: API.DLL, version: 10.0.61472.0, time stamp: 0x475e180d

Exception code: 0xc0000005

Fault offset: 0x000493d3

Faulting process id: 0xbcc

Faulting application start time: 0x01cd6fba4bc062c6

Faulting application path: B:\FSX\fsx.exe

Faulting module path: B:\FSX\API.DLL

Report Id: 6421f5a1-dbc4-11e1-af95-1c6f65d944c7

 

any ideas?

 

Cheers

Did you install SP1 and SP2 to FSX? Make sure these SP's are installed OR you can install Acceleration and that has both updates in that package. Some previous API.dll crashes were stopped by uninstalling MyTraffic2010. It's possible a recent addon was not installed correctly. A new aircraft, new scenery, a new utility?

 

Best regards,

Jim

Both the fsx.exe and api.dll build numbers are 61472, which is FSX/SP2.

 

firehawk: nice to see someone from Woodbridge. I spent most of my life in Dale City (Glendale) before moving out here. Went to WSHS, though...

I wasn't sure whether 61472 was SP1 or SP2. FSX/Acceleration is 61637. So you have SP2 installed. Do you have MyTraffic2010 installed? There is no 'magic bullet' to fix this problem. My suggestion is to run a Google search for 'API.DLL, version: 10.0.61472.0'. There are hundreds fellow flight simmers who have experienced this problem and a Google search will give you results from all over the flight sim community.

 

I live over in the Lake Ridge community in the middle of the county just off the Prince William parkway. Glendale is close as I'm not far from Minneville Road.

 

Best regards,

Jim

Here are the build numbers back to FS98:

 

FS 6.1 - 418

FS 6.5 (CFS1) - 5020

FS 7.0 - 4781

FS 7.5 (CFS2) - 20219

FS 8.0 - 10919

CFS3 - 30203

FS 9.0 - 30612

FS 9.1 - 40901

FSX - 60905

FSX/SP1 - 61242

FSX/SP2 - 61472

FSX/XPACK - 61637

ESP 1.0 - 195

Flight Beta - 62808

Flight Beta Update - 40009

Flight 1.0.0 - 30016

Flight 1.0.1 - 30023

Flight 1.0.1 (Update) - 30029

Flight 1.1.0 - 30041

 

I have no add-ons installed. My intuitive reaction is that an add-on is doing something, or causing FSX to do something, that it wasn't intended to do. Same with the UIAutomationCore issue; I've never seen that problem, but I also have no add-ons installed. I'll have a look at some crash reports and see if I can't get to the bottom of the problem.

 

Lake Ridge, cool. It sounds like you're somewhat close to WSHS, sort of near where the old Woodbridge Airport used to be.

 

Have a great day!

Lake Ridge, cool. It sounds like you're somewhat close to WSHS, sort of near where the old Woodbridge Airport used to be.

 

Thanks for the build numbers. Never seen a list that thorough. The Exception Code 005 indicates you had a Memory_Access_Violation. Could be from having sliders set too high or your system memory not configured properly or your virtual memory (page file) setting is not set to System Managed Size. That setting seems to work best for FSX in Vista and Windows 7 OS's and has fixed issues for many here. Is the API.dll always being shown as the faulting module? Perhaps it was being called when there's a memory issue and could not perform its task for FSX. Many people have been very successful fixing issues with FSX by deleting or renaming the fsx.cfg and letting the config rebuild when fsx is started again (mainly because it brings all the sliders back to the default).

 

Woodbridge Senior High is located across from Potomac Mills. I'm about 6 miles from that location. My son went to Potomac HS near Dumfries back in the 80's so don't know much more about WSHS. This area will be one of the largest, weathiest, and most populated area in the United States soon as our government expands....

 

Best regards,

Jim

Correct, x'C0000005' indicates an access violation. This is not usually an indication of a problem with running out of physical/virutal memory for a given process. Rather, this is usually an indication of a program trying to access invalid memory, something we refer to as de-referencing a null pointer. Sometimes, a function will assume that a pointer passed to it is "good" and, if the pointer passed is "bad", then the function will cause the program to crash. For example:

 

int main(int argc, char** argv)

{

char* name = NULL;

if( argc > 1 )

{

name = argv[1];

}

 

int length = strlen(name);

printf("name = %s, length = %d characters\r\n", name, length);

return 0;

}

 

If you compile, then run the code above like this:

 

C:\Temp>foo.exe me

name = me, length = 2 characters

 

you'll see the indicated output. However, if you run it like this, (i.e. with no argument):

 

C:\Temp>foo.exe

 

then you'll get a crash:

 

Unhandled exception at 0x00ca1140 in foo.exe: 0xC0000005: Access violation reading location 0x00000000.

 

There are a couple of problems with api.dll, all of which involve opening and reading files. I didn't look too closely at these today; I should have time tomorrow.

 

With respect to the uiautomatiocore problem, the problem is starting in the xuipc.dll module, which is ends up calling functions in the uiautomationcore module, which ends up de-ref'ing a null pointer. I suspect that this is coming from some add-on because i cannot reproduce the error using an installation of fsx that has no add-ons included.