[Uncle_Meat]

Does it mention exactly what has caused it to crash? Go to Control Panel/Administration Tools/Event Viewer/System(probably, try the others if not) see if there is a mention of the faulting .dll or whatever in there.

There's a great method of debugging specific app crashes using an application called Windbg, but I'll save that for another time as I'm strapped for time at the mo.

I imagine it'll be summat network-related anyway, given the obvious symptoms. Maybe try resetting Winsock/Winsock LSPs. To do this, go to command prompt and issue the comment "netsh winsock reset" without the quotes, obviously.