Thanks!
Unfortunately, the crash indicates something has corrupted the memory heap, so the dump only gives us a symptom and not the cause.
This could be a bug in Opus itself. We fixed one which was similar recently, so if you're not using the latest beta version (11.5.6), grabbing that may help.
It's also possible the bug is in a shell extension or similar 3rd party DLL which gets loaded into the Opus process. If that is the case, tracking it down can be quite difficult, and may amount to using ShellExView to disable shell extensions until the problem goes away.
If you can work out ways to reliably trigger the problem, or things that seem connected to it (e.g. viewing video files, particular folders, or particular columns in the file display) that can speed up diagnosing which component is causing it or, if it's in Opus itself, where the bug is in the code.