I'm not surprised that paren matching isn't working because after the stack your timers were probably disabled. Most of the time when you have a stack like that, the editor will behave kind of flaky because it might be in a weird state.
After looking at the code, seems like one would get that error if Core was trying to load a dll module and couldn't find it in the VSLICKBIN path. I'm not sure how exactly this would get messed up. I believe that you also have standalone SlickEdit, right? Have you ever done anything like using your SlickEdit config for your Core product? Have you ever fiddled with the VSLICKBIN environment variable? Do you have it set in Windows in your Environment Variable list?
I've attached a macro module that has a command which will spit out VSLICKBIN to a debug window. Save the attached module, open it in Core, load it, and then run the command davey from the SlickEdit command line. The value should be something like YOUR_ECLIPSE_DIR\plugins\com.slickedit.windows.libs_3.4.0\slickedit\win\. Let me know what you find.
After seeing what VSLICKBIN is, you can try using a brand new default config. Just copy your existing config directory somewhere and move it out of the way, and then start RDz back up. Core should create a brand new config...does the stack still occur?
Let me know what you find. Thanks.
- Ryan