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.

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)

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!

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