asked on

how to diagnose the root problem of a sql crash?

how will you go from a event viewer crash report like the below?

ASKER

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

TempDBA

Any more details?

ASKER CERTIFIED SOLUTION

Racim BOUDJAKDJI

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Anuj

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

25112

ASKER

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?

SOLUTION

TempDBA

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

25112

ASKER

thanks for the clues.. we'll watch it more closely next time