Windows Lock screen causing WPF Render Thread Exception (UCEERR_RENDERTHREADFAILURE)

I get the render thread exception after MS Windows has been on a lock screen for an indeterminate amount of time. The stack trace will go back pointing to any window type in my application.

Each WPF window in my application has it's own thread/dispatcher.

Over the years I've scoured the web looking for an answer to no avail.

I haven't seen an update from Microsoft since 2013 about this failure: (https://blogs.msdn.microsoft.com/dsui_team/2013/11/18/wpf-render-thread-failures/). None of their recommendation makes any difference. That seems to be the last time Microsoft addressed it.

All the latest drivers have been loaded. The machines are not running out of memory. And it doesn't seem to happen unless the person locks there computer for at least 10 minutes.

It now happens for several clients after they come back from the Windows 10 lock screen. Is the Windows lock screen somehow locking some COM interfaces that WPF apps need?

It's always on the SyncFlush call where it seems to die.

Anybody have any new ideas on how to diagnose/fix this problem.

I would even take recover from this problem. Because once the render thread is in this state there doesn't seem to be a way to recover from it.

This is the bottom of the exception stack: UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406)

System.Runtime.InteropServices.COMException (0x88980406): UCEERR_RENDERTHREADFAILURE (Exception from HRESULT: 0x88980406) at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()