OK nik, pleased to help, but when you have time, go back to event viewer and work down the list of red crosses dated when you last had a ctd in SH3, and look to see what the message says in the description box - dont bother with going to the Microsoft link.
The fact that you have got errors in the application log suggests it is third -party ( i.e. SH3) rather then a system problem - unless you also have red crosses in the System event log as well......
If the errant module can be identified, then maybe folks here can apply their wisdom and experience into finding a solution. That is where the description box info comes in.
When I had this problem in the past, it came down to old savs and old profile which I had tried to continue from before modifying the game with GWX. Natch, one doesn't want to lose all that renown. As I recall, I had to bite the bullet and start absolutely from scratch...
There also may be work-arounds. I had a situation where I got a CTD because I was in shallow water and one of the boats hunting me had blown its back-end off with its own depth-charge. Each time I tried to approach it to have a nosey, I got a CTD... that was easy enough to solve, but maybe your situation is of that sort - the boys will know, don't lose heart, just give as much detail as you can so they can get an idea of what is causing the problem.
