FS-SE Crash to Desktop

[Skyseek 18]

Intermittently, I am getting a Crash to Desktop while flying!

I looked at the application log in the Windows 10 event viewer and it had this error message:

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: g2d.dll, version: 10.0.62615.0, time stamp: 0x559f9ab4
Exception code: 0xc0000005
Fault offset: 0x00029d3c
Faulting process id: 0x1b9c
Faulting application start time: 0x01d29b3c300bf58f
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\g2d.dll
Report Id: f698c6eb-9fa2-4abf-bc43-11a79e343446
Faulting package full name:
Faulting package-relative application ID:

  Any Ideas?

 

Thanks!

[charliearon 3,022]

I think Jim has mentioned before that on page 32 are a bunch of things to try for correcting this CTD.

 

 

[Skyseek 18]

Thanks, I will check it out!

Quote

 

 

[Skyseek 18]

Thanks for the help.

I installed the latest Nvidia drivers and it seemed to fix that problem. Although I have another Crash to Desktop error.  I did some googling and nothing seemed to work.

I did a scan and it is located in this folder.... C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a

Faulting application name: fsx.exe, version: 10.0.62615.0, time stamp: 0x559f9a9a
Faulting module name: MSVCR80.dll, version: 8.0.50727.9268, time stamp: 0x573d297f
Exception code: 0xc000000d
Fault offset: 0x00008aa0
Faulting process id: 0x1854
Faulting application start time: 0x01d2a04324a9c16a
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe
Faulting module path: C:\WINDOWS\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.9268_none_d08e1538442a243e\MSVCR80.dll
Report Id: 8fd6e620-10a3-4a23-9f45-12347e24318e
Faulting package full name:
Faulting package-relative application ID:

[Jim Young 2,356]

That's Microsoft Visual C++2008 error which means there might be a problem with one of your addons developed using Microsoft Visual 2008.  See page 33 of the AVSIM CTD Guide for repair tools and further information.

Best regards,

Jim

[Skyseek 18]

Thanks again Jim!  You're awesome!