I saw in another crash like thie the solution was:

Please import the following Registry key, where "image.exe" is replaced with the name of the faulting application. >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\"image.exe"]"MaxLoaderThreads"=dword:00000001

What does this do, the application that was scanned while crashing is a multi threaded application.

I’ve seen this on a couple Server 2019 new installations.  Uninstalling, removing all traces (program files, programdata, etc.) then reinstalling seemed to do the trick.  Still scary, though, especially for a server.

This is on a corporate, controlled, locked down machine, there is going to be no uninstall or removal of Webroot. Crash also happens if you temporarily “shut down protection” in Webroot protection. Any other ideas? Can this at least be logged as a bug in Webroot so maybe it can get fixed in an update? I have a crash dump I can provide to help. Also running under Windows 10 x64, version 20H2 19042.685

If you have time to work with support on this issue, they’ll send you some tools to help gather logs.  Because mine were servers, I didn’t have time to help them troubleshoot - I just needed a quick fix.

I have time to work with them, this is even a development machine, but I am not an authorized Webroot contact on the corporate account, so I cannot follow that route. Hopefully they will see this and reach out to me. 

BenKBC136’s answer worked for me, thanks for sharing.. vidmate app save insta