Search the Community

Still testing my fresh install of MSFS with everything still at default, I flew a Land's End to John O'Groats flight (using the nearest runways to those locations) whilst visiting the UK's highest peaks en route. Anyhoo... After 4 hours 40 min, I'd had a single micro-pause early in the flight and nothing else amiss when suddenly the PC shut down. I immediately reached for the top of the case to see if there was an excess of heat but it was significantly below the sort of temperature I'd expect to cause a problem. I restarted and looked at the Event Viewer: The only thing of note I could see was "The GameInput Service service terminated unexpectedly. It has done this 5 time(s). The following corrective action will be taken in 1000 milliseconds: Restart the service." This was one of the 5 entries for this error recorded at the restart, so I assume this occurred at the shutdown. A quick search showed this has been reported (whether accurately or not) as the cause of shutdowns for other Windows users. Any thoughts? I ran SFC which said "Windows Resource Protection found corrupt files and successfully repaired them." The resultant CBS log file is massive but at the end it said "2023-12-09 19:19:29, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\bthmodem.sys 2023-12-09 19:19:29, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\bthmodem.sys" (I can share the log but it has 28903 lines!) According to I'm none the wiser. I do however use a Bluetooth mouse and keyboard but I'm not sure if BthModem either affects their use or would cause a crash.

One weird error i have came across a few days ago. I took a break from P3Dv3.4 for 1 month it was working perfectly, expect i could not start in the UK. I come back after a month and then i cant start at Elgin AFB the default airport even with the default aircraft, it crashes when it reaches 100% on "Loading Air Traffic Control" i've done nothing to the simulator at all this just happened it self. I've tried other airports that don't seem to contain much scenery, still i get the same error. So far i haven't found a solution to it. Not only that but i can't even change aircraft (PMDG aircraft 777 and 747), i press select then the screen goes black then i comes up with a error message. I have tried uninstalling p3dv3 and trying again but still no hope, there are no errors on my P3DV4. But i prefer V3 as i have many addons rather then V4. Here is my error report. Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc000041d Fault offset: 0x2290eef0 Faulting process ID: 0x1b64 Faulting application start time: 0x01d33ed688c71208 Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: unknown Report ID: 891dd634-7b00-41f9-818b-965bdc6749d6 Faulting package full name: Faulting package-relative application ID: i have had this error message alot. People have said its the Windows kb4038788 update but i dont have that installed. I have also found people getting the g2d.dll but i don't Any help will be appreciated.

Hi For the last few months I haven't been able to complete any flight using the PMDG 737NGX or the 747V2 in Prepar3D. It always ends with this: I have tried several GeForce driver versions. Now using the latest version, 382.05. P3D runs smooth, not using too heavy settings Any help would be highly appreciated. System information: Prepar3D v3.4.22 Window 10 Home 64 bit v1703 Nvidia GeForce GTX 670 Intel i5-4670 @ 3,4 GHz 8 GB RAM Kjell A.

Hello there internet! Some help please? :)System spec belowSo this evening I wanted to fly the a321 wich I haven't done for ages. (I have played without any problems for the last months). And I looked for the aircraft but I musthave deleted it sometime... So i googled and I read that I should use the repair tool from disk one.I started it and it finsihed... When I looked into my simobjects/airplanes folder I saw the a321 now! Started the game and then for the first time EVER, Microsoft flight simulator har crashed (fatal error). I was like cause it worked just 15 minutes ago and all I did was using the repair tool from the cd to get my a321 back wich it did.Now I've no clue what to do! The game wont even start so i can click the menus such as free flight, missions you know the deal. It only shows the fsx startup thing and then I get the Fatal error message from windows .What I've done is installed the microsoft XP UIAutomationCore.dll after I've read that this is a common error. Didnt help a bit!I've deleted the logbook file after I read that this helped for another user with the same problem.The same user later fixed his problem by changing the FSX.CFG file with an added .BAK to the end so FSX could recreate that file. I can't find it and I dunno how to search for hidden files. <-- Delete could work?I've also read here on avsim that g3d.dll? might be the problem but I've no clue what that is...Unfortunatly I gotta go to bed now, school tomorrow but I'll be checking with you tomorrow to see if there has been any good comments that can help me ;)Mayby restore the FSX folder to an older date? Dunno how to... heheAnyway, I will be very happy if someone bothers helping me so I can play this awesome game again and I'll be happy to reply to your comments and questions!btw im not very good at computer language ;)If you have any similar threads (wich I cant find obviously) then please link them and ill delete this post ASAP if it helps me! ;) CheersWindows 7 64bitFlight simulator Deluxe edition with a couple of freeware addonsAllaround a ok computer wich I know can handle fsx!!! Worked yesterday and before that...David (sorry for misspelling)

Hello friends, I have a particular problem with the PMDG 737. When I have already had a flight time of 2-4 hours or even less, the FSX freezes and shuts down completely. Or also when I want to go to the main menu of the game, the screen goes black and the simulator closes. This is particularly the case for the 737 Since with PMDG 777 or 747, this does not happen Can you help me with a possible solution?

I've been enjoying the NGX for several years now but there is an annoying event that occurs at what so far seems to be random times. I've searched the forum repeatedly for this problem but I see no mention of it yet. I'm using FSX-SE on Win 10. Here the problem, occasionally, when I select a saved NGX flight with a fully setup FMC flight (while starting the sim fresh or after just completing another flight), right at the beginning of the 18 second countdown the plane will begin to flip about wildly on the tarmac, usually about the pitch axis, and of course a crash is detected and the flight starts over. On the second go it usually stays put but the entire panel state is lost and all work that went into it is gone. If I close and restart the sim the same wild flip crash will again happen for that saved flight. These crashing saved flights only occur once and a while (maybe 25% of the time) and many times I can save a flight and open it later with no problem. I haven't been able to determine what might be wrong but I suspect it is something that I can adjust if I just knew where to start. I have Saitek Pedals and Yolk but the problem occurs whether they are connected or not. I'm really at a loss and I was hoping to get some insight from the knowledgeable users here. One thing I haven't done is uninstall and re-install the NGX. Thanks for you help, Eric Anderson

Hi, It started today afer an PMDG center update. When I select the vehicle, any B737NGX, after all systems initiate the plane sinks to the ground and P3D V4 resets to default flight. I tried other vehicles in the P3D V4 selection and this does not happen. I suspect the altimeter because I get a message that says my altimeter is set incorrectly, but my attempts to reset the altimeter failed. Thanks for any help Carlos Alvarez

I can't seem to start at northern airports in the UK in P3Dv3.4. The first time this happened to me was when i was planning to do Leeds Bradford to London Heathrow in the Aerosoft airbus A319 it crashed when it was loading the scenario, also i was doing San Francisco to Heathrow in the PMDG 747 (in the sim rate) it crashed when i entered Scotland (not when i was on sim rate) again the reasons were the same when ever i would try to start at a airport in the northern parts. This error seems to happen from Leeds Bradford and airports further up such as Manchester, Newcastle, Edinburgh and Aberdeen. However i get multiple crash reasons such as util.dll, ntdll.dll and MSVCR120.dll. Some errors even dont have a reason. It loads till it gets up to around 42% and some times 17% both on 'Loading terrain data' then it says 'Prepar3d.exe has stopped working'. I got to my Event viewer and what errors they are and see what i can do, I've tried my best to fix it, but i can't. Incase addons are key i have as follows, ORBX FTX Global, Openlc Europe, Vector and TreesHD, Ultimate Terrain, UK2000 scenery free Leeds, Manchester (Full version), Newcastle, Edinburgh, Aberdeen, Birmingham and Glasgow. I have tons of more addons then listed, but i believe it is not causing it to crash. Here are my 3 crash reports i got from Event viewer This one is util.dll: Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: util.dll, version: 3.4.22.19868, time stamp: 0x588f7d46 Exception code: 0xc0000005 Fault offset: 0x00021a8e Faulting process ID: 0x28a4 Faulting application start time: 0x01d3145b8d744fe9 Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: D:\Lockheed Martin\Prepar3D v3\util.dll Report ID: b9a49f15-f225-4d43-a1a3-4763746f3c27 Faulting package full name: Faulting package-relative application ID: This one is ntdll.dll: Faulting application name: dxdiag.exe, version: 10.0.15063.0, time stamp: 0x2ed44323 Faulting module name: ntdll.dll, version: 10.0.15063.447, time stamp: 0xd51d5c5e Exception code: 0xc0000005 Fault offset: 0x00058899 Faulting process ID: 0x1230 Faulting application start time: 0x01d3145b87b1873c Faulting application path: C:\WINDOWS\SysWOW64\dxdiag.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report ID: dc38f95f-1102-41aa-ad0e-1639087d0315 Faulting package full name: Faulting package-relative application ID: This one is MSVCR120.dll: Faulting application name: Prepar3D.exe, version: 3.4.22.19868, time stamp: 0x588f7cbf Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f7ce6 Exception code: 0xc0000005 Fault offset: 0x000345ac Faulting process ID: 0xa4c Faulting application start time: 0x01d31458d7afe0fb Faulting application path: D:\Lockheed Martin\Prepar3D v3\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\MSVCR120.dll Report ID: 1af6e92d-0e89-4e04-a4ff-040d5b03ffe1 Faulting package full name: Faulting package-relative application ID: Any help will be appreciated

Hi Nico Terribly sorry to be bothering you again but today I launched PSX at UK2000 Luton together with Aivlasoft EFB but after a few second EFB crashed leaving no trace in the Windows error log but here is the PSX log file: Wed Jan 24 21:02:53 2018 (utc) version 9.17 PSXseeconTraffic (64 bit) for any user aircraft in Prepar3D v4 21:02:53 Start reading and processing parameters from PSXseeconTraffic.cfg ********* Parameters ********** ALWAYS_ON_TOP=0 HELICOPTERS=0 LIGHT_AIRCRAFT=0 LIMITED_VERTICAL_RANGE=0 AUTO_MODE=1 COLLISION_DET_AIR=0 COLLISION_DET_GND=1 LOG_MATCHING=0 LOG_PARKING=0 LOG_TAKEOFF=0 LOG_LANDING=0 VERSION_CHECKED_AT=Fri Jan 19 VMRGENERATOR= FLIGHTPLANSFOLDER=flightplans LATERAL_RANGE=40 AUTO_GND=15 AUTO_BELOW_ALT_IN_RANGE=20 AUTO_BELOW_ALT_OUT_OF_RANGE=30 AUTO_ALT=10000 AUTO_RANGE=15 AUTO_ABOVE_ALT=40 AUTO_VERTICAL_RANGE_GND=5000 AUTO_VERTICAL_BELOW_ALT_IN_RANGE=7500 AUTO_VERTICAL_BELOW_ALT_OUT_OF_RANGE=10000 AUTO_VERTICAL_ABOVE_ALT=15000 LIMIT_VERTICAL_RANGE=10000 FLOOR_ALTITUDE=0 ONLY_INJECT_WHEN_USER_AIRBORNE=0 FLOOR_ALTITUDE_ACTIVE=0 PARK_STATIC=1 VERSION_CHECK=1 ********************************* Version check ... Looks like an updated verson is available. VERSION_CHECKED_AT=Wed Jan 24 There are 4211 airports in the internal database 21:02:55 Start reading and processing AI_liveries.txt ... ********* AI_liveries.txt summary ********* 731 liveries read from file AI_liveries.txt 57 Registration codes for a livery no generic Boeing liveries no generic Airbus liveries no generic Embraer liveries no generic Bombardier liveries no generic ATR liveries no generic Private liveries 203 unique airlines 41 unique aircraft types Default livery set for aircraft category Heavy, type A306, num liveries: 5 Default livery set for aircraft category Middle, type A318, num liveries: 5 Default livery set for aircraft category Light, type DHC6, num liveries: 8 No default livery found for aircraft category Helicopter **************************************** 21:02:55 Initializing PSX server at port 10747 21:02:55 Waiting for FlightSimulator to connect ... 21:02:55 Waiting for RealTraffic to connect ... 21:02:56 RealTraffic connected 21:02:58 Waiting for FlightSimulator to connect ... 21:03:02 Waiting for FlightSimulator to connect ... 21:03:05 Waiting for FlightSimulator to connect ... 21:03:08 Waiting for FlightSimulator to connect ... 21:03:12 Waiting for FlightSimulator to connect ... 21:03:15 Waiting for FlightSimulator to connect ... 21:03:19 Waiting for FlightSimulator to connect ... 21:03:22 Waiting for FlightSimulator to connect ... 21:03:26 Waiting for FlightSimulator to connect ... 21:03:29 Waiting for FlightSimulator to connect ... 21:03:32 Waiting for FlightSimulator to connect ... 21:03:36 Waiting for FlightSimulator to connect ... 21:03:39 Waiting for FlightSimulator to connect ... 21:03:43 Waiting for FlightSimulator to connect ... 21:03:46 Waiting for FlightSimulator to connect ... 21:03:50 Waiting for FlightSimulator to connect ... 21:03:53 Waiting for FlightSimulator to connect ... 21:03:56 Waiting for FlightSimulator to connect ... 21:04:00 Waiting for FlightSimulator to connect ... 21:04:03 Waiting for FlightSimulator to connect ... 21:04:07 Waiting for FlightSimulator to connect ... 21:04:10 Waiting for FlightSimulator to connect ... 21:04:13 Waiting for FlightSimulator to connect ... 21:04:17 Waiting for FlightSimulator to connect ... 21:04:20 Waiting for FlightSimulator to connect ... 21:04:24 Waiting for FlightSimulator to connect ... 21:04:27 Waiting for FlightSimulator to connect ... 21:04:31 Waiting for FlightSimulator to connect ... 21:04:34 Waiting for FlightSimulator to connect ... 21:04:37 Waiting for FlightSimulator to connect ... 21:04:41 Waiting for FlightSimulator to connect ... 21:04:44 Waiting for FlightSimulator to connect ... 21:04:48 Waiting for FlightSimulator to connect ... 21:04:51 Waiting for FlightSimulator to connect ... 21:04:55 Waiting for FlightSimulator to connect ... 21:04:58 Waiting for FlightSimulator to connect ... 21:05:01 Waiting for FlightSimulator to connect ... 21:05:05 Waiting for FlightSimulator to connect ... 21:05:08 Waiting for FlightSimulator to connect ... 21:05:12 Waiting for FlightSimulator to connect ... 21:05:15 Waiting for FlightSimulator to connect ... 21:05:19 Waiting for FlightSimulator to connect ... 21:05:22 Waiting for FlightSimulator to connect ... 21:05:25 Waiting for FlightSimulator to connect ... 21:05:29 Waiting for FlightSimulator to connect ... 21:05:32 Waiting for FlightSimulator to connect ... 21:05:36 Waiting for FlightSimulator to connect ... 21:05:39 Waiting for FlightSimulator to connect ... 21:05:43 Waiting for FlightSimulator to connect ... 21:05:46 Waiting for FlightSimulator to connect ... 21:05:49 Waiting for FlightSimulator to connect ... 21:05:53 Waiting for FlightSimulator to connect ... 21:05:58 Lockheed Martin® Prepar3D® v4 connected 21:10:35 User aircraft title: PMDG 777-300ER Brussels Airlines 21:10:35 User aircraft model: B77W, category: H 21:10:36 User aircraft position: latitude, longitude 51.871995,-0.383255 21:10:36 User aircraft at 51.871995,-0.383255, close to or at airport EGGW, dist 0.5 Nm PERCENTAGE_PARKED=35 NUM_PARK_POSITIONS=30 21:10:36 35 % parked set for EGGW 21:10:36 EGGW has 29 parking positions 21:10:36 10 aircraft to be parked AIRPORT_ALTITUDE_FEET=526 21:10:36 Connecting QNH Reader to UDP port 49004 ... 21:10:36 QNH Reader connected 21:10:37 Connecting Traffic Reader to UDP port 49003 ... 21:10:37 Traffic Reader connected third party aircraft detected with callsign OO-YAF 21:10:38 Parked at r73: no parked aircraft found 21:10:38 QNH: 1005 {"ICAO": "EGGW","QNH": 1005, "METAR": "EGGW 242050Z AUTO 21012KT 9999 FEW010 06/05 Q1005", "NAME": "London Luton Airport", "IATA": "LTN","DISTNM": 0.6} Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4661104, liv: Wizzair 'New Livery' Airbus A321-200 'Sharklets' Warning: Simconnect call to create AI ac in sim failed (?) rtid: 4223687, liv: FAIB Airbus A321-200S CFM FFT Frontier Airlines NC "Max the Lynx" N706FR 21:12:40 User closed PSXseeconTraffic, wait till all processes have stopped ... ******************** live traffic livery matching summary ***************************************** 5 liveries needed, 80% were completely matched, of which 0% were matched upon registration code =X= 1 random livery for similar type *************************************************************************************************** 21:12:40 QNH Reader has stopped 21:12:40 Traffic Reader has stopped 21:12:42 Flight Simulator disconnected Wed Jan 24 21:12:42 2018 Now I fully understand the EFB crash might have nothing to do with this but since it is a program that shows position of all injected ai traffic on the airport chart there is the possibility of a connection. I'd be grateful if you could look further into this. Bardia

Hi guys, I've just installed now the latest version of LINDA alongside profiles for PMDG 737, 777 and 747. I'm encountering this strange problem where P3D crashes to desktop without any errors ONLY when loading the PMDG 747. When loading other aicraft and even other PMDG addons, everything loads up fine. Howerver, P3D will NOT crash if I load up the PMDG 747 from another aircraft (i.e.: Moving from a 777 to a 747 inside the sim itself) I tried deleting LINDA, whereas afterwards the PMDG 747 loads up fine upon initial load. Anyone knows what may seem to be the problem?

Hi, I've picked up P3D and the PMDG 777-300ER and 200LR Base Pack a couple days ago and WHENEVER I do a flight from KLAX to YSSY or vice versa, the sim ALWAYS stops working no matter what! The aircraft I used for this flight was the 300ER FYI "P3D has stopped working" When I was looking through the event viewer log section, this VCRUNTIME140.dll pops up every time I've attached crash reports found in the Event Viewer, associated with their dates (3/4/18 is latest crash I had when I attempted to fly from YSSY to KLAX) Addons I have: 1) Chaseplane 2) PMDG 737/747/777-200LR/F and 300ER 3) FS DreamTeam KLAX Scenery Things I've tried to do: 1) Reinstall EVERYTHING (doesn't work) 2) Fully Update and Reinstall the latest NVIDIA drivers (doesn't work P3D is running as administrator as usual 3/1/18 Problem signature Problem Event Name: CLR20r3 Problem Signature 01: Prepar3D.exe Problem Signature 02: 4.2.21.24048 Problem Signature 03: 5a7c832c Problem Signature 04: PresentationFramework Problem Signature 05: 4.7.2633.0 Problem Signature 06: 5a4edeff Problem Signature 07: d97 Problem Signature 08: 17 Problem Signature 09: System.InvalidOperationException OS Version: 10.0.16299.2.0.0.768.101 Locale ID: 1033 Additional Information 1: ff95 Additional Information 2: ff95e8bdc950896e5979542771c5a6c3 Additional Information 3: 10ee Additional Information 4: 10ee927f0bef1a1ab444a49a0c7aa6b9 Extra information about the problem Bucket ID: 3f28bfd1e215c48dd1f9d95a85896663 (1295305350656386659) 3/4/18 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FF849C2CAA7 Faulting application name: Prepar3D.exe, version: 4.2.21.24048, time stamp: 0x5a7c832c Faulting module name: VCRUNTIME140.dll, version: 14.12.25810.0, time stamp: 0x59dd7da2 Exception code: 0xc0000005 Fault offset: 0x000000000000caa7 Faulting process id: 0x248c Faulting application start time: 0x01d3b36cbc0044cd Faulting application path: C:\Users\17ris\Desktop\P3D Location\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll Report Id: fc5cc3ec-d856-4c0d-b127-f9e686ebfe7a Faulting package full name: Faulting package-relative application ID: Fault bucket 2030224097460462690, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: Prepar3D.exe P2: 4.2.21.24048 P3: 5a7c832c P4: VCRUNTIME140.dll P5: 14.12.25810.0 P6: 59dd7da2 P7: c0000005 P8: 000000000000caa7 P9: P10:

I spent the entire afternoon yesterday prepping for a flight down to Sydney only ti wake up in the morning to find that "P3D has stopped WORKING" thus I pulled this from my event viewer. Have I've been the only one who's been receiving this issue lately its happened like 3 times! The only addons I have are: FS DreamTeam KLAX PMDG 737 NGX 600/700/900/900 PMDG 747 PMDG 777-200LR/F and 300ER Chaseplane ONE of the crashes were related to .NET Runtime Prepar3D.exe 4.2.21.24048 5a7c832c VCRUNTIME140.dll 14.12.25810.0 59dd7da2 c0000005 000000000000caa7 3db0 01d3b2569ab0fc23 C:\Users\17ris\Desktop\P3D\Prepar3D.exe C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll 3a704d6e-b87a-4be1-a792-c05125f5b6d9 Application: Prepar3D.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 00007FFD1236CAA7

Hi,I recently started up FSX and I had continuous fatal errors, so I checked the event logger and found this:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: visualfx.dll, version: 10.0.61637.0, time stamp: 0x46fadb59Exception code: 0xc0000005Fault offset: 0x00020cbbFaulting process id: 0x19e4Faulting application start time: 0x01cc74cb6926dae7Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dllReport Id: da6f65e3-e0be-11e0-a95a-0026b90ac075I don't know how to fix it and would like some help please!Thanks

For some reason, I suddenly started having CTDs (Crash to Desktop) during assorted FSX flight sessions. I thought I had discovered a cause - having Flight Sim Commander running weather as well as REX 2.0 OD doing real-time weather at the same time. However today, I had FSCommander off and it crashed.As a registered FSUIPC user, I naturally downloaded the latest DLL library and copied it to the FSUIPC folder. Unfortunately, that did not completely eliminate my CTD issue.Got a CTD this morning while I had FSX simulation speed running at 8x on PMDG 737ngx flight from Groton CT to JFK New York. I don't always use the speed-up function in FSX, but I was going to be unable to finish the flight if I ran it at "normal" speed. Bingo- I get the crash when I switched back down from 8x to normal sim rate.I am aware of the UIAutomationCore.DLL fix and had performed that long ago when I first installed FSX, so I knew the problem most-likely lay elsewhere, and having already updated FSUIPC - I had no clue what else to try, so I dug into the crash log to try to discover what modules were involved. Of course FSX itself was running, so it was listed int the crash log report - then another DLL was mentioned.I used the System Event Log to troubleshoot and locate the file that was involved in the crash, and the offender was shown (after googling it) to be a part of Microsoft's C++ runtime library files. So I then went to programs & features to look at the C++ runtimes that were installed, and discovered to my dismay that there several different 'versions' of C++ runtimes, and there were several different iterations (file dates) within those.Simply put, I believed there were WAY TOO MANY C++ runtime files - AFAIK you should only need 1 of each year for 2005/2008/2010. In theory, the 2010 version should be backward compatible with 2005 and 2008, possibly the system would operate with ONLY the 2010 runtime but I didn't take the chance.What I had prior to cleaning out the excess versions:C++ 2005 Runtimesx86 version << didn't think that belonged on a 64-bit version of Win 7 (removed)x64 versions (3 or 4 listed - picked the highest version number and removed all the older ones)x older version number (deleted) y older different version number (deleted)z newest version number (KEPT) x64C++ 2008 Runtimesx64 versions (3 or 4 listed - picked the highest version number and removed all the older ones) w older version (deleted) x older version (deleted) y older version (deleted)z newest version number (KEPT) x64C++ 2010 Runtimes (added by me) x64w current version (KEPT)Since I run Windows 7 --64 bit -- The proper C++ runtime libraries for me needed to be x64 NOT x86 (x86 is 32-bit) If you run 32-bit Windows or Vista, you would keep x86 versions NOT x64.So I found 1 instance of 32-bit C++ 2005 and removed it completely.I removed all but the latest (highest file number sequence) of Versions 2005 and 2008, and then I searched Microsoft and downloaded the 2010 version (x64) as well.So now I have only ONE version EACH of C++ 2005 / C++ 2008 and C++2010 on my system [All are x64]. (Looking at Programs and Features within Control Panel in Win7)I repeated the flight, and cautiously optimistic that the crash problem -- may -- possibly be gone. (It didn't crash again on the same flight plan running 8x sim speed)Elected to share this discovery with others here on Avsim.WARNING: If you're 'new' to PC's you may not have implemented a strong backup schema using a product like Acronis System Image or Windows 7 Built-in Backup. It's always wise to have a full system image (backup) of your machine BEFORE you make any changes (such as I am speaking of here).Of course once you do backups, you also need to know how to RESTORE your machine via those backups. Given the fact that hard disk drives are not bulletproof, you will greatly benefit from instituting a regular scheme designed to re-image your system to an external hard drive (e.g. USB External, eSata External or even in the cloud.Windows System Restore is not the same as restoring from backup - I'm sure there are tutorials on YouTube to cover this topic. Just want to caution everyone to backup their entire system prior to making changes. Worst case scenario: You make changes that later prove to either "not work as expected" or somehow cause problems ranging from low-grade to severe. That's when you pull your Rescue Boot CD out and plug in the external backup drive and "put everything back as it was".For those who already know this topic, I apologize. For those who didn't know about it - in the strongest possible terms it is suggested you undertake the backup advice....Hoping this works I will report back after further testing.Backup!

Hello, i tested the new Ovation to get more familiar with it and what can i say!? I do not like it yet. I started at EDHL with Flaps in Takeoff-Position, clear Weather and 5kt Head-Wind. With increasing speed it became increasingly difficult to hold the Aircraft in Lane. Then the Aircraft swung extremely to the right and chrashed into the grass of the edge strip. Because I could not believe it i tried it a second time with the same conditions and again - crash. I tried it without Flaps and i could start like usual. I love to fly the Turbine Duke and the Saratoga and so my first amateur-impressions are: Pos: I like the cockpit instruments and arrangements (my reason to buy it!) Neg: Start-Crash with Takeoff-Flaps Moving Propeller is not visible from inside the cockpit Bad brakes Abbreviations on the Annunciator Panel are blurred and hardly legible Some Click-Sounds are missing when i operate the Switch with an assigned Key on my Joystick The AP reacts very sluggishly The Switch-Illumination on the AP is far too garish The Speed-Break-Knob is allmost unreachable Outside-View is to close to the Airplane and distorted Thats what i noticed so far - so it is not love at first sight... Regards Raller

Hi fellow members, I'm having some trouble since recent update (0.1.672) Alpha exp 1.5. Since this update my chaseplane keeps crashing unexpectedly within 2 to 3 mins of P3D loading flight. Doesnt matter whether i proceed to do preflight checks or just have the aircraft sitting there without doing anything. I've tried changing all different settings within chaseplane & also restarting it as the un-experimental mode, however it just seems chaseplane seems to jeep crashing. I've also tried finding the error log file on my system numerous times and can't find it. Any help would be much appreciated or to hear from others with similar issues. Many thanks, Simon :)

After a recent windows update, Chaseplane no longer opens, I have fired up the sim and all my usual add-ons and it seems like only chaseplane was affected by my recent windows update. The log indicates Could not load file or assembly 'SlimDX.dll' or one of its dependencies. The specified module could not be found Troubleshooting I have done so far: I have uninstalled and re-installed chaseplane, nothing I have uninstalled both chaseplane and vfx-central and then re-installed both, still nothing. I have attempted to manually install the slimdx runtime by downloading the standalone installer (from https://slimdx.org/) and halfway through the installation it throws an error "an account already exists" And oh, A little more detail, The initial crash prompt says the usual "it looks like something unexpected occured.........A log file.......Please send it to *****@******.com......." after that a second prompt says "To prevent you from being stuck in an infinite loop of death, we reverted Chaseplane back to the stable channel, To enable Alpha 1.5 again, toggle Experimental Versions in preferences." the failsafe precaution is appreciated but it doesn't work and is pointless because I can't toggle experimental versions because chaseplane would not even generate its window and open at all, I am stuck inside this infinite loop of death that it tries to prevent. I have already forwarded the log and sent an email to the support channel but I'm hoping to get faster answers here.

hello all, during all my longhaul flights that ive done so far, my P3D started to lag after flying for about 5 or 6hrs. It doesnt crash (at least not immediately), but it starts to load for about 10 to 15 seconds (during this time the flight is stopped or paused), then it works again for maybe 5 seconds. Then it loads again for 15 seconds and stops, then works again and so on and so on. it certainly is not possible to continiue a flight when having such sort of lags or stutters. I have checked my event manager after experiencing this problem but I didnt found anything there. I have also done quite long flights with the pmdg 737 (with turnarounds) and have never experienced such a problem. I would be very glad if someone could help me because i really like the pmdg 777 and would love to succesfully complete one long haul flight with it. bye

Whenever I press the 'Liver downloader' on the operation centre I get this error : https://gyazo.com/17065e2767c2f1438dbb19960a710576 <- paste that into google and it will show the error.

So I've looked in this and other forums, including the CTD forum and have not seen a solution. I have a fresh install of Windows 10 Pro X64 ver 1703, build 15063.332. Running on a couple of raided 250gb samsung EVO 850 ssd's. Having to use a Marvell SATA expansion card because the Gigabyte 990FXA-UD3 mainboard won't support the VNAND technology the 850 evo's use. I have a GTX470 card 1 GB and 16 GB DDR3 system memory. I was pretty careful to follow the PMDG install instructions and it flies fine. Autoland works, it activated without any issues. It's just that when I hit "end flight" in the menu, it crashes every time. The readout from my event viewer is here, if anyone cares to take a look: fsx.exe 10.0.61637.0 46fadb14 PMDG_737NGX.DLL 1.0.0.0 55119308 c000041d 000ec433 1e74 01d2dceaf6b80da4 C:\FSX\fsx.exe C:\FSX\GAUGES\PMDG_737NGX.DLL 70eacba6-1e8a-4d8a-9dfc-6910e1b74f6f I have already once uninstalled EVERYTHING FSX, PMDG, using IO Uninstaller and cleaned up EVERYTHING that was left over. As I said, I had no issues flying, and after Ryan helped me with the crashing ops center issue, i was able to download, install and fly with my southwest liveries. I've been running windows7 for the last couple of years specifically becasue FSX and a lot of my other programs wouldn't run on it, and now that a lot of that has been weeded out, i'm frustrated that i can't get PMDG to run right now. Haven't tried any other add-ons yet, I'm hoping the reason i'm not finding the solution to this issue anywhere in the forums is because it is something simple and stupid- and everybody already knows about it- except me and a few others.. Any help with this would be appreciated. Thanks Joe Connolly KSTL

Hi, I got problem with P3dV4. Whenever I start it up it will enter to default flight which is F22 Raptor parking on the sea on the west of Africa. I try to set another flight with my 747-400 and save as default flight. Before saving the flight, I check on Green "Default" check box. The airplane change to 747-400 but it stays on the same place, on the sea, then the plane crash into the water. I don't know how to fix it and google about it. I found no answer about that. Would you please help me? It is annoying. Moreover, I cannot save any of my flight at all. It will be the same, start on the water near Africa.

Hi thanks for your work really help full It's not really a big problem but I found strange this behave, ChasePlane always crash after closing P3D latest version 3.4.22.1968. On the overall is working fine.

Anyone know what happened? It's obvious he hit something, but it's hard to tell where.Never mind. Found a good description.

Under certain circumstances, the use of CereProc voices has been causing the Speech Synthesizer engine to crash, bringing Pilot2ATC down with it, or causing Pilot2ATC to freeze. I have alerted CereProc to this issue and will work with them to try and find a resolution. In the meantime, I recommend you do not use CereProc voices. Microsoft and Ivona voices are not causing any issues. Regards, Dave

After the 1.10.11.0 update my game doesn't start anymore. I have a blackscreen with a loading symbol at the bottom right corner for a few seconds after I launch the game. At his poin the game just closes. Does anyone have similar problems? Image: https://imgur.com/a/cIqcK33 PC: Intel Xeon X5670 rx 570 4gb 12gb ddr3 What I tried: - AMD driver update - Removed content from the community folder - Disabled OC - Disabled startup programs - Disabled Antivirus - Re-installed Miscrosoft Visual Studio I can't and also don't want to re install the game. I don't want to install over 150gb and discover that the problem isn't gone or that the next update would have fixed the problem. Is waiting all I can do?