Aharon 465 Posted January 14, 2017 Share Posted January 14, 2017 Shalom and greetings all my pals, I have no problem using FSX Deluxe with SP1 and SP2 in my new powerful laptop with Windows 10 Professional using Vatsim online via VPilot Client version 2.0.8 having flown about 30 flights with much success until today. During my flight from FSX default LOWS to FSX default EKCH, my final runway approach to runway 30 always resulted into crash about 1 or 2 nautical mile from the runway. I tried second attempt which also met with same crash problem. So for third attempt, I picked runway 22L and landed without any incident. Meaning that I had come to conclusion that there must be something defective with runway 30?? Has anybody experienced this problem with that particular defective runway 30 and is there any solution for that? Here is the crash message as seen below: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: sim1.dll, version: 10.0.61472.0, time stamp: 0x475e180d Exception code: 0xc0000005 Fault offset: 0x0006df64 Faulting process id: 0x1a24 Faulting application start time: 0x01d26ea262c3bd38 Faulting application path: D:\Microsoft Flight Simulator X\fsx.exe Faulting module path: D:\Microsoft Flight Simulator X\sim1.dll Report Id: 2a1b70f5-da97-11e6-967e-d8cb8af5a92e Faulting package full name: Faulting package-relative application ID: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61472.0 P3: 475e17d3 P4: sim1.dll P5: 10.0.61472.0 P6: 475e180d P7: c0000005 P8: 0006df64 P9: P10: Attached files: C:\Users\Aharon\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Aharon\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Aharon\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Aharon\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Aharon\AppData\Roaming\Microsoft\FSX\dll.xml C:\Users\Aharon\AppData\Local\Temp\WER1528.tmp.WERInternalMetadata.xml These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_982e167ad08b29da63ecb9d992c493b5912ffe62_00000000_2cb72c3b Analysis symbol: Rechecking for solution: 0 Report Id: 9cde4e8f-da95-11e6-967e-d8cb8af5a92e Report Status: 97 Hashed bucket: Thanks, Aharon Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted January 15, 2017 Aerosoft Share Posted January 15, 2017 I have never seen scenery actually crash the sim. Link to comment Share on other sites More sharing options...
Deputy Sheriffs Tom A320 4915 Posted January 15, 2017 Deputy Sheriffs Share Posted January 15, 2017 Lots of posts you will find via Google about "sim1.dll" point to either a faulty FSX installation, most likely corrupted texture files, e.g. http://www.avsim.com/topic/469335-sim1dll-crash/ But there are tons of more posts regarding an FSX "sim1.dll" crash... Link to comment Share on other sites More sharing options...
Aharon 465 Posted January 15, 2017 Author Share Posted January 15, 2017 6 hours ago, Mathijs Kok said: I have never seen scenery actually crash the sim. It happened once to me years ago in another pc. I bought new Blueprint Simulations KIAD Dulles scenery and whenever I approached to get ready to land on KIAD runways, FSX always crashed just 10 feet above any of runways of KIAD. They told me to turn off crash detection in FSX and everything went smoothly. Unfortunately, in my new laptop's FSX, the crash detection is already turned off therefore ruling it out as strange cause why runway 30 of EKCH always causes crashes while other runways of EKCH give me no no no problem for landings. Strange!! Quote TomA320: Lots of posts you will find via Google about "sim1.dll" point to either a faulty FSX installation, most likely corrupted texture files, e.g. Tom, you are right that sim1.dll's main cause for crash is from bad or wrong or corrupted textures of livery but the livery being used in the flight to EKCH was used in other few flights without problems. Only EKCH runway 30 "dislikes" the particular livery while other runways of EKCH result into perfect landings. Strange. Oh well chalk it up as one time bizarre glitch and I will be avoiding EKCH runway 30 while praying that EKCH controllers do not ask me to go to runway 30 LOL Regards, Aharon Link to comment Share on other sites More sharing options...
scotth6 145 Posted January 15, 2017 Share Posted January 15, 2017 Hi Aharon, I also looked up sim1.dll crashes before after reading your post, and there seem to be a number of possible causes. Some were pointing to aircraft textures, and some were even pointing to Nvidia Inspector drivers. It is a strange one. Link to comment Share on other sites More sharing options...
Aerosoft Aerosoft Team [Inactive Account] 51558 Posted January 16, 2017 Aerosoft Share Posted January 16, 2017 19 hours ago, Aharon said: It happened once to me years ago in another pc. I bought new Blueprint Simulations KIAD Dulles scenery and whenever I approached to get ready to land on KIAD runways, FSX always crashed just 10 feet above any of runways of KIAD. They told me to turn off crash detection in FSX and everything went smoothly. Ahhh right, corrupted crash boxes can cause the sim to CTD. Link to comment Share on other sites More sharing options...
Aharon 465 Posted January 16, 2017 Author Share Posted January 16, 2017 It might be true that any freeware or payware add on scenery can cause this but there is no add on scenery in this area and I did mention I was using FSX default airport sceneries. Also, the cause of the error message sim1.dll is derived from bad or corruptive or wrong livery texture. Although I am unable to pinpoint the cause, I experienced unusual new problem in next flight. Whenever I started pushback from any airport, the FSX crashed with same error message precisely 15 seconds after pushback meaning I was unable to start a flight and was unable to use FSX!!! So I got fed up and decided to delete log.bin, all temporary files in appdata's FSX section, wxstation bin files, and FSX.cfg file so that FSX could rebuild its files by itself. Then the next flight worked like charm flyig from ENGM to ENDU. And hopefully will remain problem-free for further flights just like my first 35 flights in FSX in my new powerful laptop were smooth and problem-free. The only drawback for this repair that was successful due to deletion of files was that FSX's settings went back to default as if it was new and starting first flight. Took me some time to modify settings to my desired levels. I wish I knew the pinpoint of the cause of the crash but hey FSX went back to normal anyway (I hope so considering the fact I bought blazing fast powerful hot rod laptop 2 months ago or so)! Regards, Aharon Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.