Yes I don’t know exactly what happened, but it’s very odd. Thanks.
BSOD points in 99% of the cases to a system issue and it must be a reason that windows found invalid system files on your disc. In special it is nothing related to MSFS.
It’s entirely possible that MSFS could have corrupted the files. However I’m guessing it was a freak bsod to do with windows update still doing clean up from the very fresh windows install (I’d literally just reinstalled save a few reboots to install drivers).
Your other reported CTD… ensure your windows is full updated, in special of a new installation of it. Also check the list of know conflicting applications or applications which running in parallel, if it is the case.
In special check sound-drivers or auto-installed sound tools like asus sonar, mixer, etc…
If you’d read my posts properly you would have known that I literally just reinstalled windows. The new install, as with the old install, is completely up to date and all relevant drivers installed. No other applications running besides Steam. Also note, It has CTD’d almost every time I’ve run it in the past week, which has been a lot in order to troubleshoot, this isn’t a couple of CTDs, this is it CTDing virtually every time it runs, and not always with the same module at fault in event viewer.
Thanks but I have followed all the guides three times over. All the testing I’ve done has been on a default sim install. I followed the guide to uninstall Realtek driver and use generic windows driver - it actually made msfs less stable.
PS: the software runs fine for some million people, so the solution is not to repeat in each of your post that the problem lies in MSFS. The game is not free of bugs, but also not the “bad boy for all issues caused from user systems”.
I never said it was, but it has A LOT of issues. Most of the steps mentioned in the troubleshooting guides should not be necessary for a stable properly functional program. There’s another thread posted in Jan with I think hundreds of people recently reporting constant CTDs making the game unplayable, which suggests something has been changed either server side or in WU7 that is causing it.
And dont forget , todo number one of searching possible reasons for CTD is : remove your mods and parallel running applications.
The very first thing I did was remove mods. I know what I’m doing, apart from experience in personal life I have also studied and worked as an IT professional and I have never had issues like this with any other software before. I can’t remember the last time I got a bsod. So I’m putting that one down to freak occurrence. But given how unstable MSFS is, and it was the only thing running, and it happened right when I closed msfs… it’s entirely possible it contributed to a corrupted a system file.
nope… MSFS does/can not corrupt system files 
we read that often, and then comes the worst asus tools on top, etc… 
The main point I want to mention was:
the game just works fine for a lot of users. I can not remember that I got a CTD… I had a freeze in december, may caused from weahter issue.
We have also topics about crash while closing the app… so far I remember it was windows virtual memory related, but its while ago. Important are for me to find solution if you report “crash allways after 10 minutes”. And all what we know here in forum about such “crashs after short time”, was system related. We here , in yellow category, can only discuss hints and you can tell what you tried from our hints / guesses … and with luck you find the root cause. In special exists hints / experiance related to ucrtbase.dll , nvwgf2umx_cfg.dll, etc. ( note that combination of error-number and dll is important ) and therefore the answers you get points to sound-drivers or other system issues.
1 Like
I don’t see how it can’t - If MSFS causes the system to hang or crash while a system file is being modified, that’s going to cause problems is it not? It happened when I clicked exit to desktop in MSFS - that’s some coincidence.
Yes both nvwgf2umx_cfg.dll and ucrtbase.dll have caused crashes, and with generic audio drivers I had crashes from audiodg.exe also, however mostly they are just FlightSimulator.exe. Have not seen a ucrtbase.dll one on new install yet.
One thing not mentioned is motherboard revisions and bios versions … early ones can be unstable hence why updates soon follow.
Bios, drivers, OS everything fully up to date, including peripherals drivers.
Fresh windows install.
No bloatware installed. GFE not installed.
Hardware and BIOS at factory settings except for XMP.
Fresh MSFS install.
Empty community folder and no 3rd party programs except Volanta. (I also tested before installing volanta - no different)
Realtek installed or uninstalled makes little difference, if anything less stable with generic driver.
Peripherals connected or disconnected- no difference.
Sim ran perfectly stable for hours on end with over 50 mods after SU7 + HF up to just a few days before WU7, or after WU7. Around that time.
There’s more but that should address the main concerns.
I will test without XMP as I have not tried yet but I can just about guarantee it will make no difference, nor should it.
Virtualisation is on by default for my MSI B550m board so check yours too… Off is definitely the better option for MSFS.
Will have a look at that cheers
1 Like
Just installed the latest Australia world update. Trying out the Brisbane landing challenge. 300 feet to go and CTD. Also, after the update was installed, the launcher just crashed. Anyone else?
Possibly a scenery mod in your community or official folder, as yet devs haven’t had time to test fully since the WU
old friend back
Faulting application name: FlightSimulator.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: nvwgf2umx_cfg.dll, version: 30.0.15.1165, time stamp: 0x61f3973c
Exception code: 0xc0000005
Fault offset: 0x00000000001b9769
Faulting process id: 0x2fd8
Faulting application start time: 0x01d81a7e153d6790
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_31a2adf8c49e7799\nvwgf2umx_cfg.dll
Report Id: 6bd43d68-a9cf-4aaf-a73f-33c710fb2e00
Faulting package full name: Microsoft.FlightSimulator_1.22.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App
the easiest test-case related to sound-issues you can do , is to disable windows audio services.
and you not again done manuall settings , e.g. as your former setting with custom GPU fan-curves with help of Afterburner ?
yes, but before was ok with that, couple a days set hags on, may be the cause, just flew without hags, around kfll-kmia all that place, then move my corsair to climb by keys west and landing on keyw, so it’s get some time, and no problems
btw, so long don’t look at af settings, who knows what settings, custom fan curve on or off… just check it, yes, manual settings for fans
hahaha keys west mean florida keys hehehe
Been there…done that…and now on X-Plane! Totally understand your frustration.
1 Like
Same problem for me. Ever since WU7 I’ve been ctding. Mine seems to happen when I click on a switch or button in the cockpit with my mouse. Did a full clean reinstall (took hours) and the first click on the battery button ctded me. I’m grounded right now! This sucks big time! Only occasionally ctd before.
4 Likes
there is no “but”… if you made your fans slower, it runs out of the specs which the manufactor configured that the GPU works stable. It is not recommended and we not need to think about a possible issue in-game
1 Like
I read all your posts, and I’m sorry for some, but in view of the number of forums and problems, FS2020 is simply not optimized!
All my other games (read dead redemption2, cyberpunk 2077, battlefront 2, star wars fallen orden… and again more !
), all without exception runs in 4k at home and 70fps. No crash, no desktop return, no desktop reset.
With FS, I have at least 3 CTDs during the day!!! always a buggy plane, the velocity for example absolutely refuses to work! and I’ve been building my PCs for 20 years now, I’ve just never seen that!..
this isnt what we discuss here… Nobody tell that the game is free of bugs/issues , just that a lot of people ( incl. me ) can play the game without a CTD. We here try to find solutions, workarounds, hints / … for users which run into issues so that they can futuremore play. If in discussion a in-game issue is determined the developer will fix it ( hopefull all users create ZenDesk tickets ).
Thinks like OC , manuall hardware settings which let run hardware out of specs, etc. is nothing related to MSFS and our hint for that is allways : revert OC and use manufactor settings. Or in case of pc-cooling issues, limit the fps ( which is good idea in each case ).
If you have an issue with a specific “buggy airplane” which cause CTD ( this is the topic here ) you can raise a new topic, also for third-party-mods exist a category.
1 Like
Asobo know the problem with velocity… since 3 months ! and already nothing for example…