After a lot of work checking into this...The problem is related to Shared Memory Errors. The problem was definately fixed in the public version of the jakarta connector, but not in the CF version. The CF version is based off of the version of the connector that has the bug. The primary reason some people see it and some don't, has to do with multiple sites and appliction pools. If you have a server running only one web site and only cf pages, than you will probably not see a problem. If you have multiple application pools, for instance running some ASP.net apps on the same server...then you will likely run into the problem of CF crashing. More so it seems to be more prone to crash when accessing applications in different application pools. Adobe is really the only person that can fix this because they have yet to make their connector code publicly available. The fix on the publicly available version was easy to incorporate and I don't understand why this is taking a while to fix.
It is easy to isolate this to a connector problem, becuase you can easily fix it by just recycling IIS. You will also find that CF is fully functioning if you enable the internal port and access CF without going through IIS when the problem occurs.
Reference Articles: