March 8, 201214 yr HiWhen I choose "User-defined weather" inside FSX to get full cloud overcast, FSX crashes to desktop. I still get CTD when using PMDG and default FSX planes. I just uninstalled AS1012 which resulted in no CTD at all, that means AS2012 got a serious problem. I got suspicious because it happened twice using real world weather (online weather). 1st en-route from KSFO to KSEA and 2nd on the taxiway in KSEAThis is what Event Viewer shows:Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: API.DLL, version: 10.0.61472.0, time stamp: 0x475e180dException code: 0xc0000005Fault offset: 0x0003b9a3Faulting process id: 0x1638Faulting application start time: 0x01ccfd1da84ae8b8Faulting application path: C:\FSX\fsx.exeFaulting module path: C:\FSX\API.DLLReport Id: 37ca9a68-6911-11e1-bdc9-bcaec5c818d2Specs:Windows 7 64-bit SP1I5-2500K @ 4,6 GHz6GB RAM (3x2GB) 1866MHz DDR3Asus P8P67 Addons:AS2012 (Tested using pre-SP1 Beta build and using SP1 Beta) Ultimate Traffic 2PMDG 737NGX SP1cFSUIPC 4.80GEX 2.0 EuropeGEX North AmericaA couple of airport sceneries (default scenery at KSFO and KSEA)FPS Limiter 0.2Vista UIAutomationCore.dll (size: 149Kb)Any help is greatly appreciated :) Martin Stendersø SPECS: i5 2500K @ 4,7GHz 1GB GTX 560 TI (900MHz) (ASUS) 4 GB GT Dominator 1866 MHz DDR3 RAM (CORSAIR) P8P67 Motherboard (ASUS) Windows 7 SP1 64-Bit FSX SP2 Deluxe
March 8, 201214 yr API.dll is part of FSX - usually when you're getting crashes that reference sim or Windows OS component dlls like that it's a system problem - overheating CPU or GPU, unstable overclock, bad RAM, driver issues etc. This is a silly question, but do you have FSX SP1 and SP2 installed? Or have you done any kind of "repairs" on your install at all?
March 8, 201214 yr Author API.dll is part of FSX - usually when you're getting crashes that reference sim or Windows OS component dlls like that it's a system problem - overheating CPU or GPU, unstable overclock, bad RAM, driver issues etc. This is a silly question, but do you have FSX SP1 and SP2 installed? Or have you done any kind of "repairs" on your install at all?Thanks for your response :D I'm going to try some other RAM etc. The API.dll error might be related to overheated CPU, I'm going to work on that :)And yes both SP1 and SP2 installed ;) And no repairs since i reinstalled FSX and the rest of the addons a couple of weeks ago. Martin Stendersø SPECS: i5 2500K @ 4,7GHz 1GB GTX 560 TI (900MHz) (ASUS) 4 GB GT Dominator 1866 MHz DDR3 RAM (CORSAIR) P8P67 Motherboard (ASUS) Windows 7 SP1 64-Bit FSX SP2 Deluxe
March 8, 201214 yr Author I believe I've found a solution.Turning Vsync off in fsx.cfg results in a 100 % FPS increase (12-15 fps -> 30+ fps) = less CPU usage = no (hopefully) API.dll errors anymore! Finally ready for FS2CREW tonight :( Thanks for your help! :D Martin Stendersø SPECS: i5 2500K @ 4,7GHz 1GB GTX 560 TI (900MHz) (ASUS) 4 GB GT Dominator 1866 MHz DDR3 RAM (CORSAIR) P8P67 Motherboard (ASUS) Windows 7 SP1 64-Bit FSX SP2 Deluxe
March 8, 201214 yr Author Ah, yes the dreaded VSync....glad it is working now. Happy flying!Thanks! U too! :D Martin Stendersø SPECS: i5 2500K @ 4,7GHz 1GB GTX 560 TI (900MHz) (ASUS) 4 GB GT Dominator 1866 MHz DDR3 RAM (CORSAIR) P8P67 Motherboard (ASUS) Windows 7 SP1 64-Bit FSX SP2 Deluxe
Create an account or sign in to comment