Thats what Im working on now, is to isolate it. I am on windows XP Profession, and thos emessages are from my event viewer. Here is exactyl what i did to crash it (i haven't tryed it again yet tho, but i'll tell you if it happens again).
I had the clone up (socket clone using a dialog for output, that has been up easly 12 hours--no problems). I then worked ona swear kick for a user ont he forums with the hash tables. Made a dialog for that. (i only mention the hash table project because i know it can be memory intensive and have some effect on this event) As I said, the dialog was simple. It listed the words, and what action to take if each word is said. I made it so you could cancel and have no changes made (by saving the hash when the dialog is open, then if cancel is pressed--free the hash, and reload from hard-copy).
Welll, i must have reloaded the hash about maybe 4 times (checking if cancel work properly) that itself going from using memory to freeing to using to freeing may have contributed.
Anyways, I go back to the clone, and get ready to type a message in the text box, and boom. "Windows detected an error in mirc--would u like to send the error to microsoft..blah blah"
Again, im stil trying to replicate it as of now.
