I already had that turned off under Power Settings, but I was still getting a phantom USB disconnect that was crashing FS. Since I had already disconnected every USB device that I considered unnecessary and still found all those devices still listed in device manager, I decided to turn their power management off locally too.
I was definitely hearing the USB disconnect chime just before my system crashed, but the event viewer showed a loss of drive 8. I have 7 SSDs (3 PCIE NVME and 4 SATA) installed in the system, so I don’t know what #8 would be. I sent the event viewer files to ZenDesk. One of the recommendations they sent me (but they were all pretty generic like turning off XMP or CPU overclocking, which have nothing to do with USB disconnect) was to delete the rolling cache. I wondered if this could have been “drive 8” but still don’t know why I would have heard the USB disconnect chime. However, I’ve flown 3 flights now in excess of 4 hours each with no rolling cache (before the new patch), and I haven’t had a USB disconnect. So, whether that was the power settings in device manager–which admittedly should have been overridden by the Power Settings in Control Panel Advanced Settings–or if it was the rolling cache, *******wait a minute…I just heard the USB disconnect as I was typing this!!! Wow, what timing. The new patch is installed, and I’m in the middle of a flight, and the system did not crash or even pause. So, that’s good news, but the USB disconnect is still a mystery but at least it isn’t crashing FS anymore!
I went into event viewer, and I got the following Administrative Event that caused the same chime as a USB disconnect: “Event ID:65 - Failed with 0x57 retrieving AppModel Runtime status for package Windows.” It looks like I’m getting this same event very often according to the viewer. A half-dozen times an hour at least. I have no idea what that is, and it doesn’t cause the USB disconnect chime that often, so I’ll have to do some digging to try to find out what could be causing that “AppModel-Runtime” error.
Also, MSFS2020 gave us some information about the upcoming patch. Unlucky, CTD´s are not the main focus of this patch, but maybe some bug fixes will help avoing them! The developers want to focus on the ingame experience on that one.
Also, I want to say Thank you, to our Community Managers / Moderators for supporting this topic, implementing it in the guide section and all the work, they are doing for us!
it’s xvdd msft < virtual cd, what install microsoft, must be using for emulate msfs dvd via digital owner, my guess all msfs versions steam, store and dvd are exactly same, so why you see “give me a disk 1” when your inet unstable, and digital owner messing with system with on/off virtual cd, what can be one of ctd’s cause ---- in my case it’s disk 5, and i see in the event log, many yellow triangles with this error> disk5 was removed
p.s. i think you can hear ding not before crash, but after, then virtual disk with virtual dvd1 removed
Since the last patch, I have not CTD because of this error, but I still get them from time to time. I have turned off rolling cache completely, so I do not know if that is why the frequency of my getting that error has gone way down, but at least my system no longer crashes to desktop when I do get that error.
I am gonna to talk to you guys later, about the issues with different windows versions. We are already aware of this issue and I also reported that to Zendesk. Atm I am not at my computer, so I am gonna answer later!
After doing all the actions in this topic my fps is dropping from 41 to 17 fps.
Yes, it results in No CTD’s, but the graphic speed is so low that the sim is not playable anymore.
I reversed it all back, but only set the virtual mem page manual and put VSync on with 30fps max.
Now i had no CTD’s yet and the fps are almost stable at 30 fps.
@PliantWings5288, as written in the guide, task/settings with this icon " " can affect the performance on your computer. I think you downclocked your GPU too hard, this will result in a hard performance decrease. The strange thing is, that turning on VSYNC results in the hardest performance decrease for most people. However, every computer got his own behavior, regarding the installed hardware/software, etc. . So, I am just happy you found a capable solution for your CTD´s!
As you already noticed, the “Event ID:65 - Failed with 0x57 retrieving AppModel Runtime status for package Windows” error is a common one for Windows 2004 users.
The problem can occur many times, check this Event Viewer Log:
Windows 2019 users don´t get this error. After some research in the WWW, I found different people complaining about it, cause it crashes also games like Warzone, etc. . Unlucky there´s no solution for this so far! I found two answers under a Microsoft Support topic, that recommend doing a clean GPU driver reinstall and reinstalling Visual Studio. This will not help at all. The good thing is, this error crashs your Simulator very rarely! If it happens more frequent to you, unlucky there is no other solution then waiting, until Microsoft fixed that.
Yes, I saw the thread on the Microsoft forum where folks said that their only solution thus far was to roll back their OS to the 1909 edition and the faults went away. Now that the last update of FS solved most of my CTDs, I’m willing to wait before resorting to something that drastic. However, since FS is also a MS product, I sent Zendesk copies of my Event Viewer log files showing the fault in the hopes that they can get someone from the Windows OS team to fix the “Event ID: 65 - Failed with 0x57 retrieving Appmodel Runtime status for package Windows” error in an upcoming OS update sooner rather than later. It’s very annoying.
it’s not so much you can’t defrag ssds, it’s just pointless as access is instant on ssds where as there’s seek time on an HDD to move their reading head. It also degrades the life of the ssd as they have a maximum write cycle
My issue on CTD was from a years ago old school tweak for 16GB ram. I found my Virtual Memory was Custom Sized at 200/200MB to “force RAM into the faster sticks”. I changed this to a total of 16384/16384 MB. 4096 MB on C: and 12288 MB on F:, both are Samsung SSD drives. No more CTD and still upping the MSFS settings gradually to find the sweet spot.
" can affect the performance on your computer. I think you downclocked your GPU too hard, this will result in a hard performance decrease. The strange thing is, that turning on VSYNC results in the hardest performance decrease for most people. However, every computer got his own behavior, regarding the installed hardware/software, etc. . So, I am just happy you found a capable solution for your CTD´s! 
for