CTD on load

[caleb1 27]

MSFS 2020 is giving me a CTD during the loading bar after the press any key screen.

Watching task manager there is a quick spike of the GPU up to 100% right before it crashes.

Ive tried to reopen it many times and only about one out of 20 tries it made it to the flight configuration screen.

And even that one time it still CTD'd after hitting fly.

I have the latest version of windows and MSFS.

Does anyone else have this problem?

I read something saying that a potential fix could be to rollback to a previous version of windows...  Has anyone who has this problem tried this?

 

Thanks.

[caleb1 27]

On 10/10/2020 at 2:48 PM, Rob_Ainscough said:

Anything overclocked?  CPU/GPU?

Anything listed in the Event Viewer at the time of your CTD?

Rolling back to previous version of Windows shouldn't be needed.

Cheers, Rob.

Thanks for the reply.  No overclocks.

I just tried starting it again to look for the event viewer entry, I get this at time of crash.

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b
Faulting module name: d3d11.dll, version: 10.0.18362.387, time stamp: 0x7e72d1cb
Exception code: 0xc0000005
Fault offset: 0x0000000000170900
Faulting process id: 0x1d18
Faulting application start time: 0x01d6a0b7de4b0384
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: d4238d25-28f4-47db-9b4e-3f4f568aedc3
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Anyone have any ideas what this could mean?

Thanks.

Edited October 12, 2020 by caleb1

[wim123 761]

d3d11 fault points to driver issues,update drivers?

[caleb1 27]

38 minutes ago, wim123 said:

d3d11 fault points to driver issues,update drivers?

I did check and there is a new video card driver available.  I will update and report back.

I bet this will be the fix.

Edited October 12, 2020 by caleb1

[caleb1 27]

Just updated the video card drivers, that actually did not fix it....  Still have a similar error in event viewer. (still d3d11)

 

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b
Faulting module name: d3d11.dll, version: 10.0.18362.387, time stamp: 0x7e72d1cb
Exception code: 0xc0000005
Fault offset: 0x0000000000170900
Faulting process id: 0x320c
Faulting application start time: 0x01d6a0dcac7092e0
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: 94661190-5a11-4100-89a4-97211dbe2195
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Any ideas what else could be the issue.

I just noticed that the minimum specs is a GTX 770 or better, I have a GTX 745.  So I'm close but not quite there.  Do you think this might be the reason for the CTD?  I would think even if I do not meet the minimum requirements it should still at least open and run the UI... even if it couldn't render in flight.

[bean_sprout 1,201]

From what has been presented the issue seems to point to the video card.   Run dxdiag and see what comes up.

Is GTX 745 good for gaming?

This GeForce GTX 745 (OEM) graphics card is considered budget with poor modern game performance when playing anything more demanding than indie game requirements. Capable of running games with up to a DirectX 12 requirement.

 

Cheers

bs

Edited October 12, 2020 by bean_sprout

[wim123 761]

11 hours ago, caleb1 said:

Just updated the video card drivers, that actually did not fix it....  Still have a similar error in event viewer. (still d3d11)

 

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b
Faulting module name: d3d11.dll, version: 10.0.18362.387, time stamp: 0x7e72d1cb
Exception code: 0xc0000005
Fault offset: 0x0000000000170900
Faulting process id: 0x320c
Faulting application start time: 0x01d6a0dcac7092e0
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\SYSTEM32\d3d11.dll
Report Id: 94661190-5a11-4100-89a4-97211dbe2195
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

Any ideas what else could be the issue.

I just noticed that the minimum specs is a GTX 770 or better, I have a GTX 745.  So I'm close but not quite there.  Do you think this might be the reason for the CTD?  I would think even if I do not meet the minimum requirements it should still at least open and run the UI... even if it couldn't render in flight.

ahh, uh a 745 is not at all close to a 770.

upgrade your vidcard.

a 770 is about 3 times faster than a 745.

if you want to play this game properly, you need something way better than you have now.

Edited October 13, 2020 by wim123

[caleb1 27]

Thanks for the input everyone.

I am aware my video card isn't the greatest.  Wow you are right 745 seems close to 770 but 770 seems waay faster.  770 even seems faster than the 1050ti (I have considered upgrading to a 1050 ti in the past).  With the settings tuned properly my 745 does run P3D v4 with REX, A2A planes and orbx scenery at 25 to 40 fps so I'm content with it for now.

I'm not extremely exited or motivated to use MSFS enough though to justify getting a new vid card, it was more of just an experiment to see how it compared with P3D.  I got it though gamepass so no financial investment lost if I cant get it to work.

But I'll try anything I can to mess around with it.  I ran DXdaig just now and all the tabs say no problems found.

Am I supposed to be starting MSFS at the same time I run DXdaig or have it open during the crash?

 

Thanks.

[bean_sprout 1,201]

3 hours ago, caleb1 said:

Am I supposed to be starting MSFS at the same time I run DXdaig or have it open during the crash?

I would reboot and run dxdiag by itself.  If you can run P3D then the card is probably ok but not enough VRAM for FS2020 perhaps.

Regards

bs

[caleb1 27]

17 hours ago, bean_sprout said:

I would reboot and run dxdiag by itself.  If you can run P3D then the card is probably ok but not enough VRAM for FS2020 perhaps.

Regards

bs

Dxdiag still shows no problems detected when starting it after a reboot.

I think we've concluded my vcard is inadequate.

Thanks everyone for your help in troubleshooting this.