Event 65, AppModel-Runtime

Hi Brian - I can actually help with that.  Rufus will create a bootable USB drive with the Windows installer loaded up and ready to go.  Download Rufus here:

https://rufus.ie/

You can just download the portable version of Rufus - no point in installing it on a Windows install you're about to delete :)

Once you download it, start it up.  You'll see a dropdown for "device" - use that to select the USB flash drive you want to use.  Below that you'll see another dropdown that says "select" - pull that down and select "download" instead. 

Once you've selected "download", click on that same box where it says "download" - that will let you select Windows 10 or 8.1.  Select "Windows 10" and then you'll see a dropdown to select which version of Win 10 you want to install, everything from 2004 all the way back to 1507, and everything in between. 

Tell it which edition you want (Home/Pro or Education), the language and architecture, which should usually be x64.  Click on "download", and then settle in for a bit while it downloads the .iso and builds the bootable drive.  Once that's done, you can set your compuuter to boot from the USB and reinstall Windows.

PLEASE be sure to back up any important files before you do this - anything on your disk will likely be lost during a clean install of 1909 or whatever.

The only option that worked for me is to clean install 1909 until Microsoft wakes up and fixes whatever horrible bug exists in 2004. I am amazed that Microsoft is COMPLETELY and annoyingly silent on this issue and has not delivered a hotfix.

It is easy to reproduce this crippling bug.

My system is very stable and games like Doom 2016 run w/ all options essentially maxed out on my GTX 1080 with the latest NVIDIA drivers.

Microsoft?? Are you listening?

2004 is a disaster as far as I am concerned.

The AppModel runtime errors are gone for me after a clean install of Windows 10. I also installed the latest patches prior to testing.

I tried the stock NVIDIA drivers, 432.00 with no hitches (due to the bug that is) and no crashes to reboot.

I tested F.E.A.R. and Doom 2016. Alt-tabbed to the desktop and back to the full screen games.

No AppModel runtime errors for these.

I updated to the latest NVIDIA drivers 451.67 for my GTX 1080.

No frame skipping and crashes again...

Checked Event Viewer - no AppModel runtime errors due to this issue.

Conclusion: Stick w/ Windows 10 1909 and do not upgrade to 2004. However, this may not fit others' issues. Certainly does not seem at all related to NVIDIA's drivers.

Hey MS the problem still being there, everytime that I going to fullscreen.

Same problem

- Intermittent lock ups

• Same error as everyone else
• NVIDIA RTX 4000 similar to others
• Very occasionally on startup prior to 2004 version
• Tried versions like everyone else
• Happens a great deal after 2004 (1-4 times an hour)

However, my workaround seems to function quite reliably (90%)

• First notice of Windows task bar not responsive, not able to switch windows, etc
• When encountering the problem, cntl-alt-del and pulll up task manager.  Exit task manager
• Things go back to normal for me, at least for a while.  Pain in the **** workaround but, better than previous reboot

1. Does this work for others?
2. Any guesses why the problem resets from this?  Looking for some kind of causal issue here related to what's going on when we cntl-alt-delete / go to task manager.