Event 65, AppModel-Runtime

Welp, guess what worked for me - formatting the drive and reinstalling 1909.  Thanks a lot, Microsoft.

This has happened to me too, many times after playing games.

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.

Hello.

I have been getting the same problems. I recently upgraded to an i9-10900k (stock settings), and a z490 master mobo. I did a fresh windows install on a new NVMe drive using a 2004 usb media (no choice, old system was 2004). I have a trusty asus rog strix 1080 ti oc (stock).

Ive gotten the nlvddkkm.sys error, and have any 3D game start crashing. (Eg RDR2 - err_gfx_state, overwatch - your rendering device has been lost, AC:Odyssey - Crash to Desktop (nvlddkmm.sys error), elite dangerous - hang, or any other 3D game.

Ive done sfc /scannow, and a dsim repair. No issues. Ive done clean nvidia driver installs of 451.67 /.48 and even the hotfix .81. All freeze / crash and rarely bsod when attempting to launch or run games.

Is reinstalling windows 1909 the only option?

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...