Sure, its theoretically possible that a specific condition caused by live weather could crash the simulator. But that could be identified by correlating the crashes on the time dimension. If a lot of people crashed at the same time. From what I’ve profiled from MSFS it doesn’t have itself a crash dump upload functionality to Microsoft, which I find very strange. But Watson captures the crash reports on C:\ProgramData\Microsoft\Windows\WER\ReportArchive, so it could be sent to Asobo although only with user’s consent.
Otherwise, if you have constant crashes and suspect its live weather, disable it and use presets for a month. The problem is that the absence of crashes doesn’t mean that you found the cause, but it adds a data point into the investigation.
I’ll tell you this: I had my first CTD this week. I upgraded to the latest NVidia driver (511.65) out of curiosity, as I had an old driver (460.79), to see if I would gain FPS. But I upgraded without rebooting. After that MSFS started crashing on load, and always at the exact point in the loading screen. But not only MSFS, other games too. I then rolled back to my old driver, and it still CTD! Until I restarted the machine… Then both drivers work, and now I am running with the latest one.
By the way @Stardrifter2232 can you check your C:\ProgramData\Microsoft\Windows\WER\ReportArchive folder to see if you have reports of MSFS crashes? If you have, please post the file, its a .wer extension but its a text file, you can rename it to .pln to attach it here. Here is the one I had this week as an example:
Report - Copy.pln (29.3 KB)
You can see on line 31 that the actual source of the crash was d3d11.dll. Unfortunately there is not much more information beyond that.