Crashing all of FSX...not just the planes within

[GunnyG]

What is the typical problem I should consider when I'm seeing these sorts of messages pop up?

https://scontent-sea1-1.xx.fbcdn.net/hphotos-xpf1/t31.0-8/s2048x2048/12473754_10206797183262761_8156158696093529310_o.j pg

[rvn817j]

Since installing Windows 10 (on to my original Win7 operating system) I have been having all kinds of issues and, as a result, I've been doing lots of research and changes. My system is running an OC'd Phenom II 980BE and an HD7950. When you first switch to Windows 10 it is best to go through all your drivers (disk controller, graphics, network controller, etc.) and ensure you have up to date Windows 10 compatible drivers installed. (It is best to look at Windows Device Manager for "!"'s and sometimes you have to go back to your motherboard mfg. site to get these drivers.)

Next (and this has been the subject of many board posts) I would look at memory usage. There may be other programs "hogging" your memory. A couple years ago we used to talk about a "clean boot" and fortunately we have gotten away from that, but memory is still an issue. I check memory usage by loading FSX, stay on the opening screen, and then load "Task Manager". Task Manager will show all the other programs using memory while FSX is using memory. I have found that one of the first programs that needs to go while running FSX is your antivirus program. Usually you can disable that program for some period of time.

There are many ways to shut down programs and I use AVG Tuneup which allows you to disable programs easily. (AVG Tuneup can be bought on sale (I use Newegg) relatively inexpensively.)

Finally, if all the preceding is insufficient to get you a smooth running FSX, you need to get rid of the FSX detail and "eye candy" by slider action in the customization area. Hopefully, others will chime in here with other solutions because I'm still looking for the "holy grail".

[ncooper]

If you go to the Windows event viewer, you will be able to see why
FSX stopped working.
Without that knowledge, correcting the error will be next to impossible,
or perhaps a lucky guess.

[rvn817j]

If you go to the Windows event viewer, you will be able to see why
FSX stopped working.
Without that knowledge, correcting the error will be next to impossible,
or perhaps a lucky guess.

ncooper - Below is my Windows event log. Can you tell me what it means (I'm getting tired of guessing)? TIA.

Log Name: Application
Source: Application Error
Date: 1/18/2016 7:31:14 AM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xedc5fcd0
Faulting process id: 0x2190
Faulting application start time: 0x01d151f290cd9a61
Faulting application path: G:\MS FSX\fsx.exe
Faulting module path: unknown
Report Id: b289e210-947d-4690-aa48-ad5ec01bdecc
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-01-18T13:31:14.000000000Z" />
<EventRecordID>13982</EventRecordID>
<Channel>Application</Channel>
<Computer>980BlackEdition</Computer>
<Security />
</System>
<EventData>
<Data>fsx.exe</Data>
<Data>10.0.61637.0</Data>
<Data>46fadb14</Data>
<Data>unknown</Data>
<Data>0.0.0.0</Data>
<Data>00000000</Data>
<Data>c0000005</Data>
<Data>edc5fcd0</Data>
<Data>2190</Data>
<Data>01d151f290cd9a61</Data>
<Data>G:\MS FSX\fsx.exe</Data>
<Data>unknown</Data>
<Data>b289e210-947d-4690-aa48-ad5ec01bdecc</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[Bradburger]

I'm running FSX SE, and since the Windows 10 upgrade to the newer build, I all of a sudden started getting a lot of crashes, and sometimes fatal errors, a lot more than before.

(it was getting to the point where it was not worth trying to run the sim!)

Most of them were to do with the Visual C++ 2005 libraries (specifically MSVCR80.dll), although I would also get crashes caused by the FSX.exe, the terrain.dll, and sometimes the display.dll amongst others.

After some frustrating times trying to work out why these crashes had started happening so often, I decided to remove the various Visual C++ 2005 libraries, and it seems the culprit on my system was the 'vcredist_x86' update dated 8/27/2007, with file version 6.0.3790.0 (product version 6.00.3790.0).

After uninstalling this, the stability of FSX SE has improved, and I 've had no more of the continuous crashes.

It might or not be what's causing the crashes that are the subject of this thread, but I guess it's worth an investigation!

Cheers

Paul

[RodgerC130]

I didn't see this thread prior to posting about my problems with Windows 10, but I am having the same problem plus, none of my aircraft will accelerate to take off speed. Just incredibly slow. Don't know what to do.