Event 65, AppModel-Runtime

FWIW since we may all have something configuration specific and therefore slightly different going on based on the thread.

But I fixed this Event 65 issue on my configuration.  Hardware Lenovo P73 ThinkPad P73

I had to go to cntl-alt-delete screen, start up task manager and exit on each screen task bar lockup.  This would have the effect I think of resetting the graphics card (a blatant guess on my part).  It got me out but ewww... did this 3-4 times an hour ever since the scourge of Windows 10 2004  

So it turns out my Lenovo support guy (excellent guy) told me the Lenovo site that syncs up your drivers dutifully moved them forward for both onboard Intel and NVIDIA upgraded my machine properly at the time of the Windows 2004 deployment,  But after Windows 2004 produced a lot of issues, Lenovo investigated this one in particular and subsequently backed off their earlier "standard" configuration for Intel / NVIDIA driver versions.  

So switched to Hybrid mode from Discrete mode in BIOS.

• Downgraded  Intel UHD Graphics G30 to 26.20.100.7926 (made available in Feb 25 2020)
• Downgraded NVIDIA Quadro RTX 4000 to 26.21.14.4223 (made available in Jan 31 2020)
• Stayed on Windows 10 2004

Event 65 seems to have stopped.  While the specifics may not work for you, I suggest the "approach" may. 

• My HW (Lenovo) vendor seemed to know what was going on as HW vendors are basically just systems integrators at this point.
• They know they have Windows 10 2004 problems in several areas actually, not just graphics
• I get the sense that the automated update tools have a very hard time with downgrades for some very good reasons
• I think you have easier time describing / dealing with this issue eliminating more variables (aka the systems show up slightly different or widely different across hardware)  by possibly dealing with your HW vendor for support rather than NVIDIA may be the way to go.

Hope it works for you too!

Meanwhile, not looking forward to next Microsoft 10 release and playing driver roulette...

2004. I didn't even think to reinstall an older version since I figured the issue was typical Windows corruption; my last reinstall was three or so years ago. Then the issue occurred again, this time leading to a BSOD, and I saw multiple instances of Event 65 in Event Viewer. Entered that into Google and found this thread.

Thanks for the advice. I may reinstall 1909 yet if I can find the patience.

Hey MisterFlamp - speaking only for me, I did a clean reinstall of 2004.  I have a 1909 USB flash drive ready to go, so guess what my weekend project is, lol

Fortunately for me, I have multiple drives and a NAS where I can move the important stuff. It's still a pain in the ****, though.

Which Windows 10 release did you re-install?

If it was 2004, then that might explain still seeing the issue.

Suggest doing a clean install from a bootable Windows 10 1909 flash drive and delete the Windows partitions for the install drive.

Yes, it means re-installing apps and reconfigure. Total PITA if you only have one drive.

Want to add my voice to the list of those experiencing this issue. Did a full Windows reinstall hoping it would resolve the problem but it's still here. That was a fun waste of an afternoon.

It's absurd that each Windows update introduces yet another new issue. In practice I would opt out of these updates until they're more polished (presuming such a state is even achievable by MS), but I've been downloading them all hoping to see a fix to the problem the last one introduced.

Then there's radio silence in this thread -- not even a "we acknowledge the issue and are working on it" -- only useless directions like "ignore the errors." Hard to ignore your computer slowing to a crawl until you have no choice but to hard reset, BSOD, etc.

If I wasn't a gamer I would drop Windows so hard.

/rant

Will keep watch on this thread in hopes of an actual resolution.