SQL Server Crashes with a stack dump

One of my SQL Servers(2008R2 SP1) crashed this morning with error:

SQL Server is terminating because of fatal exception c0000005. This error may be caused by an unhandled Win32 or C++ exception, or by an access violation encountered during exception handling. Check the SQL error log for any related stack dumps or messages. This exception forces SQL Server to shutdown. To recover from this error, restart the server (unless SQLAgent is configured to auto restart).

I also found a stack dump in the error log.

I have restarted the service since then and it is working fine now, DBCC comes clean, so does hardware diagnostic. Has anybody seen this before? I have found numorous links on the net like this one http://bit.ly/LaWD0L but I just want to see if you guys have experienced this before and what the best thing to do to avoid chance of it happening again?

P.S. I am planning to open a ticket with MS to see what they have to say(in case I hit a bug or windows update cause the problem etc..).

Edit:

I just found out security update was applied two hours before the crash, not sure it was the culprit.

UPDATE:

Worked with MS support engineers and just wanted to update the question here with their findings in case somebody else find it useful. They find out from the stack dump that the crash has something to do with the database access engine(we use Microsoft 64-bit ACE provider to upload data from Excel to SQL Server) and I was told to apply patches KB2460011 and KB2516475 and seems like the issue if fixed(we were not able to replicate the issue after applying the hotfixes; it crashed twice before that).