From the crash dumps, I see you're using EMET in some way, and WinDbg is coming up with this:
Probably caused by : mscorwks.dll ( mscorwks!DontCallDirectlyForceStackOverflow+10 )
Searching on that finds some discussion talking about how some EMET settings may trigger it. Nothing definite, and it could be a symptom rather than a cause, but it is worth trying with EMET disabled to see if it makes a difference.
mscorwks.dll is part of the .Net framework, so this also indicates that a shell extension may have loaded .Net into the Opus process, which often indicates a shell extension has been loaded which is breaking various rules (not using .Net is traditionally one of the rules for shell extrensions, although newer versions of .Net are less problematic than before when loaded into file managers and other processes where lots of 3rd party components have to coexist).
So it's worth a try using ShellExView to disable most shell extensions (you can usually leave the ones which are part of Windows itself, although the File History extension in Windows 10 is worth disabling as it has some serious bugs at the moment). After disabling them, reboot and see if the problem is still there. If it is, re-enable everything again as we then know they aren't involved. But if the problem is gone, only re-enable a few at a time and see when it comes back.