how to diagnose the root problem of a sql crash?

how will you go from a event viewer crash report like the below?
LVL 5
25112Asked:
Who is Participating?
 
Racim BOUDJAKDJIConnect With a Mentor Database Architect - Dba - Data ScientistCommented:
> Collect as much information as possible at the time of crash: isolate all events in the event viewer at the time of crash
> Read the SQL Server error logs at the time of crash
> Try to analyze the system dump if you had a blue screen

Hope this helps...
0
 
25112Author Commented:
error :
Faulting application name: sqlservr.exe, version: 2007.100.4064.0, time stamp: 0x4d6bf2d4

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x0000000492ab0052

Faulting process id: 0x10b4

Faulting application start time: 0x01cc84025f483ca2

Faulting application path: E:\Program Files\Microsoft SQL Server\MSSQL10.SIP002\MSSQL\Binn\sqlservr.exe

Faulting module path: unknown

Report Id: b951d0cf-f473-11e0-88bb-001517aeed8e

Open in new window

0
 
TempDBACommented:
Any more details?
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
AnujConnect With a Mentor SQL Server DBACommented:
check your windows error log and sql server error log you will get clues from there.
0
 
25112Author Commented:
this is the only error in the application part of the event viewer.. it is on a cluster.. so as soon as it crashed, it failed over and that is the next event in the viewer..

sql logs had nothing.. that is why it is puzzling..

the above error has not clues by itself, right?
0
 
TempDBAConnect With a Mentor Commented:
Do all the server has same version, patch, service pack of sql server and os?
When the server moved to secondary node in the cluster, does it failed back? And how long it was on the primary node from where it failed?
Did something happend or something new was running during the time when it failed?
Did you fail it back to its original node and was it able to rest there in peace?
0
 
25112Author Commented:
thanks for the clues.. we'll watch it more closely next time
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.