Make sure the issuer of the certificate is not a rogue CA intended to try to exploit a vulnerability in your MS code that checks to see if the certificate is still valid or if it has been revoked/compromised.
You can usually do this by saving the certificate and looking at the details. Unplugging the network card to keep it from talking to the remote CA for Certificate Revocation List Retrieval might also help in this process. Pull the cable from the wall, open the message and see if it still does it.
Beyond that I would recommend getting a good insightful program that will let you pick the crashing process apart. Sysinternals has some nice utilities which collectively are capable of giving you enough insight to see what is going on. Saving the dump file is also helpful. You should be able to figure out exactly what the error was by looking through the dump file.
TCPDUMP,PROCESS EXPLORER, FILEMON are the essential tools.
Post more info after you know more.