I am aware that this has been brought up before but I still haven't found a solution:

 

A few days ago I was repeatedly attempting a certain part of a flight (from a saved point) until I got a fatal error - I don't exactly remember if this was when it happened - but was not particularly worried as this has happened a few times before. However, when I went to start FSX the next day, I would get a little way into the starting blue box before a little window appeared saying a fatal error had occured and FSX would have to close. I tried the UIAutomationCore fix but this didn't work, nor did starting as administrator or launching in compatibility mode (I am running windows 7 professional 64 bit). I also tried deting the cfg file and the logbook? file.

 

I then copied into a folder on my desktop my world of ai planes (as they took so much hassle to put on) and a few other planes to put back on when everything worked and then unistalled service pack 2 and fsx, checking nothing was left behind. I then tried a reinstall and got a window about Microsoft Flight Simulator stopping working a little bit into startup. After trying service pack 1, this changed to the fatal error window. I have now tried a repair and a complete reinstall and am still getting the mfs has stopped working window on startup.

 

In case it helps, I saw in another post saying something about the event viewer and the faulting module path is C:\windows\system32\HID.DLL

 

If anyone can help I would be massively greatful, thanks.

Which directory did you install FSX in?

Originally in the programme files x86 then in a new folder i called fsx in the c drive root folder and then most recently back in the default programme files location

Hello

 

The best path choice was C:\fsx\

 

The HID.DLL User Library is part of the Windows operating system, it deals with Human Interface Devices; USB’s are part of that, and it is a known fact that some USB or Bluetooth devices can corrupt that file when connecting or installing their drivers.

 

Try to disconnect all USB’s (except Mouse and Keyboard) and see if FSX starts.

 

Also do a system file check.

Open a command prompt as administrator and execute: sfc /SCANNOW

 

Hope that helps

 

Cheers

That seems to have done the trick, thank you so much. I can't believe it was something as simple as a USB device!

This is an automatic message.

 

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
  
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  
• The images might not have been "illustrative" or "explanatory" in nature.
  
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
  

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.