Ok but what is 22h1
U can do this Clean Installation of Win11 with Rufus Software.
You know it took 5 tries before the sim would actually run this morning. 1st try chug chug gets to main menu and without touching a thing CTD. Refire chug chug get to main menu, choose the world menu CTD. repeat 2 more times 5th time I get to airport sitting on runway fps is showing 9 (chug chug chug), I launced by the end of the runway I managed 12, then 10 min into the flight it finally hit 20 I made my approach into erie and watched the fps go 20 15 10. But hey at least it ran I guess.
Then I ran xp12early access, it politely told me that beta 4 was avaliable and ask if I wanted it. Said yes waited 5 mins while it did it stuff. Games starts start my flight 45 fps on the runway with everything cranked to ultra. Notice the trees look a little better then last time flew the whole 15 min beta time with no problems at all.
Same here. Windows 11 Pro 22H2.
During my entire beta period I had no crashes. Last night on a LEBB flight during charging I had this CTD.
In summary: xp12a no chug chug, MSFS chuh chug a lot.
Noted!
Impossible to fly for more than a minute⌠Was already having issues with this throughout the whole Beta and still have them. Itâs a shame I cannot use MSFS2020. Hope the devs hotfix it soon. Cheers!
dont think that is has something to do with windows. Before SU10 there were no problems. Also Ive downloaded all windows updates and have the latest GPU driver.
Oh⌠I wasnât aware of it.
Thanks.
Do you have the same issue if you follow the OPâs steps to reproduce it?
yes
Provide extra information to complete the original description of the issue:
Are you using DX12?
no
Are you using DLSS?
no
If relevant, provide additional screenshots/video:
For me it feels so random that Hi actually think this problem is serverdriven somehowâŚ.
Makes no sense. Yesterday I crashed within 2 minutes while in menu. Today I took a 10 minute flight and it was smoother than ever. And now I let it be in the menu for some while to see what happens.
My graphics card and drivers are the same as yesterday and my FS installment alsoâŚâŚ
To me many problems with crashes seem to start by an update and further from an update it goes awayâŚ.
Received the message today, first time.
So we have to install win11? Just to get the sim to work
This is an error message introduced in one if the SU10 builds that made its way to the live version. This isnât related to Windows, so trying to rollback or reinstall Windows is a waste of time.
Nvidia and Microsoft are making you all think you donât have enough vram with this âbugâ just before the launch of the 4000 series so you all upgrade
I had some CTDs with a 3090 with 24 gb of VRAM⌠Nvidia and Microsoft can sit and waitâŚ
may be users did again a âtweakâ and new install of OS removed that tweak. Similar to the TDRLevel change, which some users did and now not getting the DLSS option till they removed the registry entry ( or set it to the value which is the default 3 ).
This topic becomes slowly similar to the âmemory could not readâ topic: some users get it and most users never get the message.
I donât think it has anything to do with it. In the whole beta process I didnât have a single ctd. In my case I have done absolutely nothing. Just update windows 11 and on the other hand get out of beta. This bug was already reported during the beta by many people and apparently it is present in the update 10 code. Which happens randomly regardless of whether you have windows 10, 11 and multiple hardware configurations.
Since I upgraded to SU10 I have been getting this error in the menu or while loading. This has nothing to do with windows updates or graphics settings. Iâve never encountered such an error before SU10. I also got a CTD 10 miles from the T/D on my 2 hour flight. Please fix it!