03-02-2008, 06:17 PM
Possibly some macro overwrites qm memory used for triggers. Review your recent macros. Macros running in qm process (ie not as separate process) can easily overwrite qm memory using Windows API functions, share, operator [] (strings, pointers). Or a dll/COM component used in macros can do it.