FS crashes to desktop WITH error message, after selecting the map

Today I had 4 crashes to desktop WITH error message, after selecting the map.

When starting a flight, I can select the map, but after a few minutes of flight, selecting the map causes FS to crash. Each time, I had flown between 10 and 25 minutes. In Japan.

Events viewer shows this:

Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f6cce4b
Faulting module name: RenoirCore.WindowsDesktop.dll, version: 0.0.0.0, time stamp: 0x5f6b4c44
Exception code: 0xc0000005
Fault offset: 0x0000000000051817
Faulting process id: 0x5d28
Faulting application start time: 0x01d698cb46827335
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe\RenoirCore.WindowsDesktop.dll
Report Id: 5202a9b2-83ba-4ec7-a30b-14813c79d5b2
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Known Issues

Thank you.
I never installed Windows 10 version 2004: too many bugs; wears down SSDs (apparently fixed now)…

Microsoft say “The sim may crash if the VFR Map is not opened right after starting the flight
Does it need to stay open?
For me, as long as I never open the VFR map, I have been fine. Opposite to what they say. It is when I select it that I get the crashes! I think I will turn it off in the Custom Toolbar, as I selected it by mistake…

I just had this crash also, although no crash report. Usually fly with the VFR map minimized, but had closed it completely. On opening it shortly after t/o the game froze and then CTD’d.

I am also experiencing crashes to the desktop when changing views, like the MAP or most often when changing from external to internal views. on version 1.8.3.0 the most common faulting module was “d3d11.dll” and I think that may have been due to the Zotac Firestorm software pushing my RTX2070 a bit too far on Auto settings. I uninstalled it and everything was OK for 8 days until 1.9.3.0 came out and since then the Faulting Module has been “RenoirCore.WindowsDesktop.dll”… See below

I don’t get an Error message on screen

Excerps from Event Viewer:

1.8.3.0
22/09/2020 14:05:12
Faulting module name: d3d11.dll, version: 10.0.19041.1, time stamp: 0x84d2d982
Faulting package full name: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe

21/09/2020 20:38:42
Faulting module name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x5f5b8327
Faulting package full name: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe

22/09/2020 14:11:04
Faulting module name: d3d11.dll, version: 10.0.19041.1, time stamp: 0x84d2d982
Faulting package full name: Microsoft.FlightSimulator_1.8.3.0_x64__8wekyb3d8bbwe

1.9.3.0
30/09/2020 16:51:54
Faulting module name: ucrtbase.dll, version: 10.0.19041.488, time stamp: 0x0d8057d8
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe

30/09/2020 19:17:05
Faulting module name: RenoirCore.WindowsDesktop.dll, version: 0.0.0.0, time stamp: 0x5f6b4c44
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe

03/10/2020 18:07:38
Faulting module name: RenoirCore.WindowsDesktop.dll, version: 0.0.0.0, time stamp: 0x5f6b4c44
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe

30/09/2020 15:22:35
Faulting module name: RenoirCore.WindowsDesktop.dll, version: 0.0.0.0, time stamp: 0x5f6b4c44
Faulting package full name: Microsoft.FlightSimulator_1.9.3.0_x64__8wekyb3d8bbwe

@ RevampedSine732

Just one thing I see.

Your screen resolution looks to me low so probably your HW is maybe old, correct? Look to your Exception Code, is very easy check this code on web and take some infos. Reasons:

  1. RAM errors.
  2. in cas of use HD -> BAD sectors, typical Access Violation.
  3. Corrupted registry.
  4. Malware infection.

This is badddddd… 5 times yesterday CTD while on AP from KSEA to KPDX, 5K Elevation in single turbo prop plane. It also occured while not on AP. The CTD occurs just after tapping the “V” key…for the map…but it doesnt ALWAYS Crash…Hopefully Zendesk read these posts?

al

No,

Zendesk reads report what you write on Zendesk :wink:

No:

  • the picture was only part of the screen: my monitor is native 1440p and set to 2560x1440:
  • Not on HDD, but on SSD: who puts game/flight sims on HDDs these days? C: is 512 Pro GB Samsung SSD, D: where FS is is 2 TB Pro Samsung
  • registry: no problem
  • no malware in last check.

SFC /scannow shows no problem either:
image

As I wrote in my first post above, the CTD occurred all after selecting the VFR map, and this only happens from version 1.9.3.0 . It’s obvious it comes from v 1.9.3.0 .

@ RevampedSine732

Shame that you didn’t post that infos soon,

many users maybe understood your situation better, also me :wink:

In times of internet and have data from System (crash dump, Crash vode, …) is maybe easy start solve, check all.

As soon as I updated to 1.9.3.0, the VFR map caused CTDs. And 4 yesterday.
It was just so obvious. In the version before, I never had any CTD when selecting the map.

Microsoft know there is a problem with the VFR map:
In


they say, at the end:
KNOWN ISSUES
  • Game may crash if the VFR Map is not opened right after starting the flight
    … several other problems

For me, it’s best I never open it! I disabled it in the top screen toolbar, which also disables the V key to display it.
So, MS/Asobo have got to fix this. No need to mess around with the PC and components.

Agree,

strange to me is their info as they stated about problem if VFR map isn’t opened right after starting flight :slight_smile: I don’t push this and sim working without problems hahahahahahahaha

How they can write this info??? This simply point to what I said hahahaha They have big chaos about state of this sim…

May or not?

Yes I agree.
I think what happens is that something gets corrupted with the map, at some point in flights.
Each time I opened it at the beginning of a flight, within a minute or 2 after starting the flight, I had no crash.
It’s only after 10 or 20 minutes later the map caused the CTD.
I guess some global variables in the code lose their data (problems with pointers?), then later when calling the map, the code fails because of missing data.
That is why they advise to open it at the start of a flight, and to keep it open (but they don’t explicitly say to keep it open!!!): if constantly open, data is not lost, and all keeps working OK.
At least, they problem is not with our systems!

Watch this video:

From 34:18 to 35:32, Jorg Neumann says they have gone too fast, had no time to check and introduced bugs…

Sry,

don’t have taste still :slight_smile: