Server keeps on rebooting occasionally

[Noor Hishamuddin Hashim]

Hi,

I have one server that keeps on rebooting occasionally, and generate dump as below everytime.Any idea what cause this issue?

Server model: ProLiant DL380 G4
Windows 2003

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 7F, {8, f7767fe0, 0, 0}

*** ERROR: Symbol file could not be found. Defaulted to export symbols for nsifiltr.sys -
*** ERROR: Module load completed but symbols could not be loaded for SYMEVENT.SYS
*** ERROR: Module load completed but symbols could not be loaded for dblhook.sys
*** ERROR: Module load completed but symbols could not be loaded for savrt.sys
Probably caused by : sis.sys ( sis!SipCommonRead+23d )

Followup: MachineOwner

[Igor Karasik]

Hi,
Did you see this article ?
http://support.microsoft.com/kb/842465

[Jeremy Thomas]

Hmm... SIS.SYS is related to Single Instance Storage Filter

1. Check ALL the firmware is up to date
2. Update all the drivers
3. You got SP2 on there?
4. Run Memtest86 from www.memtest.org

http://support.microsoft.com/kb/817771
Suggests possible hotfix

http://msdn2.microsoft.com/en-us/library/ms795478.aspx
Indicates:
Cause

Bug check 0x7F typically occurs after you install a faulty or mismatched hardware (especially memory) or if installed hardware fails.

A double fault can occur when the kernel stack overflows. This overflow occurs if multiple drivers are attached to the same stack. For example, if two file system filter drivers are attached to the same stack and then the file system recurses back in, the stack overflows.

Also suggests that the most likely cause is dodgy memory.

[Noor Hishamuddin Hashim]

Recently updated the system ROM and server has been very stable.

[Ivan Bohannon]

Dblhook.sys and NsiFiltr.sys are drivers that I maintain. If you have a crash dump available, I can take a look. Quite often these are caused by running out of stack space, which occurs if you have lots of filter drivers installed. Do a "fltmc" at the command line to see how many filter drivers you have running, perhaps you can remove some.

Ivan Bohannon

[Noor Hishamuddin Hashim]

when i run fltmc I can see only 7 filter?
nsifiltr and dblhook not listed.