Event 65, AppModel-Runtime

HI MisterFlamp - FWIW, I'm not convinced that it's the NV drivers either.  I'll have to do a re-install of Windows to go back to 1909 :(  But, so be it.

Hello,

Honestly, going back to 1909 may be the quickest way to tell if Windows is the root cause. Unfortunately, that is the most painful way to tell. My system is set up to be fairly easy when installing from scratch, i.e., clean install of Windows. I have separate drives to re-install huge downloads, e.g., games. Yeah, I re-partition and wipe the Windows drive... I have learned the hard way about MS testing of Windows prior to releases.

Seeing that this issue (AppModel runtime spewage along with spiking the GPU workloads ending up with a forced reboot) correlates to Windows 10 for the most part AFAIK.

The frustrating aspects of this issue is that MS is virtually silent and it has persisted for at least one month.

I am not convinced that NVIDIA GPU drivers is the root cause.

Hi MisterFlamp:  It's interesting, so lemme describe what's happening here.  I have a pair of 2080S cards, although it does not seem to matter whether SLI is on or off.  I'm consistently getting nvlddmkm crashes in any 3D-accelerated applications - I first noticed the issue in an old DX9 game too - L4D2, but it's happening across everything these days.  DX9, DX10, DX11, Vulkan, DX12 - doesn't make a difference.  What's interesting is that CUDA/OpenCL work seems completely unaffected - I can fire up Folding at Home, do OptiX renders in Blender, etc., all just fine - no crashes, no issues, which suggests to me that something somewhere in the Windows display render pipeline is barfing.

I can also reliably trigger driver crashes in any desktop application, like Google Maps in a web browser, that seems to make use of hardware acceleration. 

For what it's worth, I'm running W10 2004, and HAGS is off.   Here's what I got in Event Viewer when I just now tried to fire up 3DMark and Left4Dead2:

Display driver nvlddmkm stopped responding and has successfully recovered.

• System

  - Provider

   [ Name]  Display

  - EventID 4101

   [ Qualifiers]  0

   Version 0

   Level 3

   Task 0

   Opcode 0

   Keywords 0x80000000000000

  - TimeCreated

   [ SystemTime]  2020-07-26T19:18:42.2231795Z

   EventRecordID 8758

   Correlation

  - Execution

   [ ProcessID]  0

   [ ThreadID]  0

   Channel System

   Computer JUPITER

   Security

• EventData

   nvlddmkm

Fault bucket , type 0

Event Name: LiveKernelEvent

Response: Not available

Cab Id: 0

Problem signature:

P1: 141

P2: ffffe4011df8c010

P3: fffff80385d4b668

P4: 0

P5: 4440

P6: 10_0_19041

P7: 0_0

P8: 256_1

P9:

P10:

Attached files:

\?\C:\WINDOWS\LiveKernelReports\WATCHDOG\WATCHDOG-20200726-1518.dmp

\?\C:\WINDOWS\TEMP\WER-54511203-0.sysdata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD528.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD548.tmp.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD55D.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERD59C.tmp.txt

These files may be available here:

\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Kernel_141_6c95b261963cdaac3eab12f5a47386598a23c79_00000000_cab_3e555e85-401c-4657-8528-41264fe4427e

Analysis symbol:

Rechecking for solution: 0

Report Id: 3e555e85-401c-4657-8528-41264fe4427e

Report Status: 2049

Hashed bucket:

Cab Guid: 0

I don't think this have to do with NVidia drivers.  my setup is 

Asus tuf x570 mobo

ryzen 3600

corsair 2x8 gb ram 

Radeon rx590 gpu.

I have never use an nvidia gpu so I shouldn't have any driver from them specially now that I did a new windows custom install deleting everything on my nvme. What I notice is that my mobo have the raid setup with enable nvme but I only have one nvme so I didn't see any point on having raid on. I get memory bsod errors so I change it to htci and now I get this 65 error like veryone else. pc just shuts down restart without any bsod.

Hello MisterFlamp,

As additional information I have my laptop connected to a monitor via HDMI cable. My monitor model is Samsung SyncMaster T22B350. I think the problem is also lies here.

Thank for your help Nvidia!.

Regards a good luck!