Archived

This topic is now archived and is closed to further replies.

Alvega

API.dll crash

Recommended Posts

Hi,I cant seem to get any luck here with this sim. On my vista system using sp2 I get the common msvcr80.dll crash that microsft has conveniently blamed on nvidias drivers, and nvidia has conveniently blamed on microsoft. Ok, fine Ill use my xp setup, but on my xp setup I get api.dll crashes and d3d9 crashes. I have seen hardly any posts on the forum about them, google doesnt help either. Does anyone know what to do about them, especially the api crashes? Installing dx doesnt help. Is this a known issue? Does the march upgrade fix anything? Maybe Mr. Taylor would like to comment?

Share this post


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

The nV issue is usually related to using a menu in fullscreen.If that isnt involved in the repro steps, this could be something else.For instance, Nils pointed you to the VC redists, since an add-on that doesnt include the right one of those will cause crashes.So yes how it happens is crucial to diagnosis.

Share this post


Link to post
Share on other sites

Thanks, it happens with the lds 767, maddog 2006, and the ariane 737, (the onyl heavies I have installed right now), it is a random crash, not a menu crash, it happens in windowed mode and fullscreen mode and is completley random, it never happens in the same place or time twice. Are those link for the api crash or msvcr80? Right now my main issue is the api.dll, since msvcr80 crashes in visat only so far and I want to get my xp setup working.

Share this post


Link to post
Share on other sites

Did you install the runtime provided by Phil's link?If the CTDs still occur, deactivate your add-ons, which are using their own DLLs (dll.xml, modules folder).Also install the latest updates and SPs for your add-ons (e.g. latest Leveld SP2a) and if you are using FSinn/FScopilot make sure to use the latest versions.

Share this post


Link to post
Share on other sites

Thanks for the response, I already had the redist installed, but I reinstalled it anyway, I installed the march update for dx also. I get the crash randomly, its pretty much impossible to replicate it at the same data time and circumstance. Its not a menu crash, it just happens during the course of a normal flight, not because I clicked something, or anything else significant. I also have the latest sp for level d, but its not leveld, it happens with all of my addons. It is a larger problem.

Share this post


Link to post
Share on other sites

Hi Mike,I've had the same FSX SP2 crashes. Only way I could eliminate them was to uninstall SP2.Richard

Share this post


Link to post
Share on other sites

Hi Richard,Yeah I was afraid of that, the problem is I cant use my cheyenne with sp1 only and its nice to have the added performance fixes of sp2. So Phil, is this a known issue? Have you heard of this before? Any planned fixes? It seems like there are many users with problems using sp2. I guess im lucky I dont have the menu crash too.I would also like to hear if any ati users are having trouble with sp2 or not, is it only the nvidia users? It does seem like a tough thing to pin on nvidia (although I can see the menu crash being a driver issue), it doesnt seem like a graphics problem to me, its completly random and has no odd side effects or tells that other graphics problems have, but I could certainly be wrong.

Share this post


Link to post
Share on other sites

My situation is this:I never had a single BSOD and rarely a CTD before I installed Acceleration. During the time I had Acceleration installed, I had numerous BSODs and CTDs. I did not have the menu CTD that has been reported. The crashes were random. I got fed up and uninstalled Acceleration. Everything seemed back to normal until I had a BSOD shortly after landing at an airfield in Brazil in the Cessna(default). I had hoped it was a fluke but just the other day I had another BSOD. this time I was in the Baron. I had lowered my traffic settings. the time of day was different. the weather was differnt. The only constant was that the crash occurred shortly after landing.I've checked the dates on the dx files and some of them are the newer files. System restore wont 'roll back' the dx version on my system.I'm updating one driver after each BSOD in an attempt to track it down.they're pretty rare but they used not to happen at all and I dont run my computer that often. The last crash referenced a stop error that related to the CD Rom?? I dont think thats right.I'm hoping its my sound card. that would make more sense. (its an Audigy 2 value using the drivers that came with it)I'm sure it has something to do with the latest Dx versions requests/requirements and my hardware/drivers not being able to comply. its my best guess with my limited knowledge on the subject.EDIT: BTW - If anyone who has knowledge of how flight sim 'does its thing' under the hood, I would like to know what all happens shortly after you touch down at an airport. The scenario is consistent for me -- I land, I brake and slow down, I retract flaps, I start to head for parking and then BSOD! So I'd love to know what kinds of things happen after you land. I thought it might be AI and so I lowered my settings. I seem to recall SP2 having a panel update or something for AI and I also seem to recall that uninstalling didnt revert back all of those files. I'l have to check on that again.

Share this post


Link to post
Share on other sites

Hmm, A bsod is usually soemthing different, that is usually related to your hadware configuration, caused by overheating or a part that is failing. Ive never gotten a bsod with my current machine, ever, only those pesky "microsft flight simulator has encountered an error and need to close..." you know the rest.

Share this post


Link to post
Share on other sites

I guess it could be unrelated but I never had a BSOD until I installed Acceleration one Saturday afternoon. By the end of the day I had had two BSODs and at least one CTD. I was angry. I gave up and tried again the next day.Thats how it went for the next week until I just had enough and uninstalled Acceleration.I've flown a lot since then and only had the two BSODs. I want them to go away completely but I need to know whats causing them to do that.

Share this post


Link to post
Share on other sites

I feel your pain, I wish fsx could be less tempermental so we could have our minds on flying and not on software problems. One thing you can always do to test your hardware is download occt, or orthos, they will stress your cpu and ram to their limits and let you know if anything is wrong. A somewhat stable pc should run for at least 11 hours, and a 100% stable system should run for 24. If I were you i would give that a try, if it fails download memtest86+ and if that detects errors it is your ram. If not it could be your gpu, cpu, or motherboard, it could alos be your psu, if you psu is on the way out it can cause these kinds of issues. If you want to test your psu you need to get a multimeter, if you want to know how to do it shoot me a pm.

Share this post


Link to post
Share on other sites

Mike, do you get those errors with the default airplanes and are they happening in every location of the world or do you mainly fly the same route?I don't think it's a SP2 problem, because i have the LevelD too and i'm using FSX+XPack and i don't get errors like that.Would be helpful if you would post your dll.xml and exe.xml here.Nobody knows what you are exactly doing, all your add-ons, all your drivers etc.. so, 'i get CTD XYZ, please tell me the reason' will not work...

Share this post


Link to post
Share on other sites

Without knowing the error code and involved driver, it's nearly impossible to help you. I'm only pretty sure that Acceleration doesn't cause your problems.You could monitor your temperatures and check the Windows eventlog for critical errors.http://www.cpuid.com/hwmonitor.php

Share this post


Link to post
Share on other sites

Its not a hardware issue with temps or anything like that, I am an experienced system builder and overclocker so my temps and hardware are always in check. There was no driver in the crash dialog, and even viewer doesnt havea record of the crash for some reason. Its just a random api.dll APPCRASH. What causes an api.dll crash usually?

Share this post


Link to post
Share on other sites

My post #15 is referring to Dave (post #12).I wrote something for you in my post #14.If you are an 'experienced system builder' you should know that it isn't as easy as your question insinuates and that it is necessary to develop a schema to isolate the possible source of error. API=application programming interface.. i'm pretty sure that there is more than only one possible reason for a CTD...

Share this post


Link to post
Share on other sites

"If you are an 'experienced system builder' you should know that it isn't as easy as your question insinuates and that it is necessary to develop a schema to isolate the possible source of error. API=application programming interface.. i'm pretty sure that there is more than only one possible reason for a CTD..."Yeah well Im giving you all that I can provide, If I had any more information you can bet I would give it to you, btw I dont know if it makes any difference but I was running active sky, trackir, and fsinn. If I had any more information about how to replicate the crash in fsx dont you think i would have posted it? Here is my dll.xml <?xml version="1.0" encoding="Windows-1252" ?> - Launchdll.xmlFalseFalse - Level-D SimulationsFalseFalseModulesLVLD.dll- Object Placement ToolTrueFalse..Microsoft Flight Simulator X SDKSDKMission Creation Kitobject_placement.dll- Traffic ToolboxTrueFalse..Microsoft Flight Simulator X SDKSDKEnvironment KitTraffic Toolbox SDKtraffictoolbox.dll- Visual Effects ToolTrueFalse..Microsoft Flight Simulator X SDKSDKEnvironment KitSpecial Effects SDKvisualfxtool.dll- Maddog 2006FalseFalseC:Program FilesMicrosoft GamesMicrosoft Flight Simulator XModulesLeonardoSH.dll- FSUIPC 4FalseModulesFSUIPC4.dll- FSCopilotFalseModulesFSCopilot.dllWhere do I find exe.xml?Thanks for all of the help.

Share this post


Link to post
Share on other sites

Given one of the scenarios is a mismatched msvc80.dll used by an add-on, you need to remove all add-ons and see if that helps.it is the 1st step in an isolate-diagnose-repeat process.

Share this post


Link to post
Share on other sites

Thank you fro the reply Phil, but I am running a dual boot with vista 64 and xp 32. On this setup we are talking about (XP) I dont get an msvcr80.dll crash, that is only on my vista 64 +sp2 system (on which I have removed sp2 and i have yet to get an msvcr80.dll crash), this last crash was on my xp +sp2 system and I have not gotten the msvcr80.dll crash on that yet, only api.dll.

Share this post


Link to post
Share on other sites

Hi, If you scroll up a couple posts you can see that I posted my dll.xml file, and I asked where do i find the exe.xml file? I cant tell you if it happens with default aircraft because I never fly them, but it doesnt happen with only the lds 767, it happens with all of my addons. There are tonns of posts about sp2 causing problems on this forum, I dont think this is because of my addons. Im using the latest nvidia drivers (169.20?).

Share this post


Link to post
Share on other sites

Mike,that was my post i wrote yesterday to you, before you posted your dll.xml...Thanks for posting your ddl.xml! The exe.xml doesn't exist by default, it is used, if an add-on loads an exe file with FSX.I'm not sure if FScopilot (1.7) is already fully FSX SP2 and Vista (64) compatible and the last time i read the LevelD forum, there were a lot of problems because of FScopilot. So, the chances are good to find the source by disabling FSCopilot. To do so, please make a back up of your dll.xml and copy it to your desktop. Remove the FScopilot entry from your original dll.xml or set disable to true:FSCopilotFalseModulesFSCopilot.dlland then run a test flight.FSX or SP2 it-self will never cause CTDs, it's always an add-on, which is not fully FSX or SP2 ready, or somebody has ruined his FSX installation, or nVidia is involved.Regarding your Vista installation.. it's a little bit confusing. If you only uninstalled SP2, i would recommend you to make a clean installation of FSX with both SPs and then to install your add-ons, one by one. Again, FSCopilot is critical and what version of active sky do you use? Make sure to use the latest service packs/updates for AS and make sure that your add-ons are supporting Vista.Unfortunately not every add-on is fully Vista and especially Vista64 compatible...

Share this post


Link to post
Share on other sites

Hi,Thanks for the continuous replies, I appreciate the help. I know this can get pretty confusing, but the api.dll crash is happening only with my xp fsx sp2 setep, my vista setup was crashing with the msvcr80.dll, but I have removed fsx sp2 and I dont have that problem anymore, afaik the vista setup is working fine with fsx and sp1 only. The problem lies in my xp fsx sp2 setup, I have only gotten api.dll crashes, I am using the latest sp's for the 767 (2a), the latest service pack for asx also. The addons I run are asx, fsinn 1.3 for fsx, the lds 767, utx, gex. and fex, I also have the maddog 2006, da piper cheyenne, and ariane 737 installed, I have had the api.dll crash with all of those addons except for the cheyenne and Im sure that is because I have yet to take a flight more than a half hour with it. Btw the lds 767 does have an issue with fscopilot, but that is easilly fixed by moving the level d entry above the fscopilot entry in the dll.xml.

Share this post


Link to post
Share on other sites

In my opinion you have no hope of diagnosing this on either system with either SP1 or SP2 unless you start with a clean FSX with no add-ons.Unless you do that, you are unable to authoritatively isolate the problem.

Share this post


Link to post
Share on other sites