On your version without any scripts, can you type this again and paste the results here?
//echo -a $os $version $md5($mircexe,2) $file($mircexe).sig $alias(0) $script(0) $dll(0) $com(0)
As far as finding out why it's crashing after awhile when connected to more than one network, that probably will be extremely difficult to track down if you aren't able to find any way to reproduce it on demand. Many users have it running 24/7 with multiple networks and don't crash, so it is probably something specific to your system (hardware, software that is running, drivers, etc) that is conflicting with mIRC. Options in that case would be updating all drivers and to try with all software closed besides mIRC and see if it crashes. Other software or utilities (or even viruses) can cause unrelated programs to crash through no fault of the program that's crashing. If it still crashes with nothing else running and all new drivers, then I'm not sure what to suggest from there.
You could also try one of the other recent versions and see if only 7.19 gives you the problem or if all 7.x versions do. If it's only 7.19, that helps narrow the problem down for Khaled.
It would also be good to try and determine what might be related. Are you doing anything in mIRC or just idling? If you join an empty channel on each network and don't join other channels, does it crash? If you connect to two different networks (not the ones you already tried), do you crash? There have been bugs in the past where a person could force your mIRC to crash and it's possible that an unknown bug has been found and someone's targeting you on one of the networks you were testing it on. By trying on different networks, you remove that as a possibility. Keep track of how long after connecting that you crash and see if it's the same amount of time each time or if it varies. If you have logging enabled with timestamps, it makes it easy to find out when you connected and when mIRC crashed. Beyond that, just try different things and see if you can find any other useful information that might make it easier to track down the problem. Unless you can find something that helps with that or if Khaled can reproduce it, finding the problem is just not going to be easy.
* For all testing, please do it without any scripts/DLLs/etc loaded.
