If you can pause VMMap (Ctrl+Space, or Options > Trace Snapshot Interval > Paused) and get it to save the trace/dump to a file just after the memory starts climbing, that would probably contain all the information we need.
That said, I've been looking into this today and found that VMMap currently locks up for me when I try to save a trace. I'm not sure what the issue is, but found another person with the same problem on Windows 10, so it may be a problem caused by OS changes. Looks like you're on Windows 7, so hopefully it won't affect you.
If we can't rely on VMMap then I'm not sure there is a good alternative. I've been looking today and there are other tools but none that are suited to you running them to capture information to send to us.
If VMMap is a no-go, let's try another tactic. First, it would be good to find out if your Opus configuration is a factor. If it is, we can look at what's causing it, and if it's not then we can focus on third party components as the problem is most likely in them.
With Opus not running at all, please run this from the Win+R (Start > Run) dialog:
"C:\Program Files\GPSoftware\Directory Opus\dopusrt.exe" /cmd Prefs BACKUPRESTORE
Hopefully that will open the Backup & Restore wizard, and no other Opus windows will open, nor will the memory issue start happening. This will depend a bit on your Opus Startup preferences, however.
If you are able to use the Backup & Restore wizard to make a complete backup of your configuration, please save it to a safe place, then uninstall Opus (this will wipe the config), reboot, and then reinstall Opus and see if the problem still happens.
If you aren't able to use the wizard, you can do a manual config backup, but there are also some other things we can try first. If that's the case, please don't do anything yet, but reply to this thread and let us know what happens, and in particular if any other windows open when you run the command above; I can then advise on how to prevent them opening, which may let you use the wizard.