Fault offset & Faulting process id within SQL

Is it possible to track down on the faulting info provided by the logs regarding a sql server instance crash?
-----------------------
Faulting application name: sqlservr.exe, version: 2007.100.5500.0, time stamp: 0x4e7ba697
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000487530052
Faulting process id: 0x2068
Faulting application start time: 0x01cdf1d58f6e13be
Faulting application path: E:\Program Files\Microsoft SQL Server\MSSQL10.SIP002\MSSQL\Binn\sqlservr.exe
Faulting module path: unknown
LVL 5
25112Asked:
Who is Participating?
 
Ryan McCauleyData and Analytics ManagerCommented:
Is this something that's repeating, or was a one-time thing? If it's repeating, is the behavior predictable (do you know what you can do to force its occurance)?

I did some quick searching and found this MSKB, though not sure it applies because it's for 2008 R2 and you appear (from your path and version numbers) to be using 2008 SP3:

http://support.microsoft.com/kb/2515489

I also found a case of something getting something similiar with 2008 SP3 (your same build) in late 2011 (http://social.msdn.microsoft.com/Forums/da-DK/sqldatabaseengine/thread/cc53260b-b77c-4c8e-a749-5b6723ffeb1d), which they claim Microsoft said would be patched in a later CU (which I'd assume is long since out by now), but they didn't give any more detail. I don't see a connect item that looks like it's related, but I'd recommend testing the latest CU (especially if you can reproduce this in a second location that's not production, and you're free to patch it at will).
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.