Yes, there's a problem of compatibility between sysreset and mIRC >= 6.10. If you want to help to the resolution of the problem, please try to contribute to the other threads (as ParaBrat said, try the search function with "sysreset" or "fserve crash" with AND option). Especially give details about your configuration (OS level, other packages installed like .NET, ...) and in what mode you use sysreset (firewalled conf maybe?).
There's also a rather long thread in the sysreset msg board you may want to read to know the extent of the problem...
As a matter of fact, NO

, it's NOT proven that sysreset is the only culprit here. Other fserve scripts are experiencing the same problem at the same moment. These scripts use some mIRC commands intensively, especially chat windows management. It can trigger very weird things either in mIRC or even in Windows (mIRC uses not less than 13 system DLL directlty and up to 20 as a whole

).