Prolient DL380 rebooting every night

I've noticed for the last 4 nights around 3:00 a.m. my server is rebooting based on the system log:

Event Type: Error
Event Source: EventLog
Event Category: None
Event ID: 6008
Date: 11/5/2004
Time: 3:25:39 AM
User: N/A
Computer: SQL3
Description:
The previous system shutdown at 3:20:40 AM on 11/5/2004 was unexpected.
Data:
0000: d4 07 0b 00 05 00 05 00 .......
0008: 03 00 14 00 28 00 bb 00 ....(..
0010: d4 07 0b 00 05 00 05 00 .......
0018: 08 00 14 00 28 00 bb 00 ....(..

Insight Manager is setup to automatacally restart the server so I was unable to get the OSOD info.

I then retrieved the memory.dmp and used windbg to get more information. Here is the results:

3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

UNEXPECTED_KERNEL_MODE_TRAP (7f)
This means a trap occurred in kernel mode, and it's a trap of a kind
that the kernel isn't allowed to have/catch (bound trap) or that
is always instant death (double fault). The first number in the
bugcheck params is the number of the trap (8 = double fault, etc)
Consult an Intel x86 family manual to learn more about what these
traps are. Here is a *portion* of those codes:
If kv shows a taskGate
use .tss on the part before the colon, then kv.
Else if kv shows a trapframe
use .trap on that value
Else
.trap on the appropriate frame will show where the trap was taken
(on x86, this will be the ebp that goes with the procedure KiTrap)
Endif
kb will then show the corrected stack.
Arguments:
Arg1: 0000000a, EXCEPTION_INVALID_TSS
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


BUGCHECK_STR: 0x7f_a

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 80062bc0 to 8046a55e

STACK_TEXT:
8904edd4 80062bc0 0404eddc 80066fb8 0000017a nt!KiSystemFatalException+0xe
00000000 80465b8e 00000000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x68
8905b800 8905b800 00000000 00000000 0028624d nt!KiIdleLoop+0x16


FOLLOWUP_IP:
nt!KiSystemFatalException+e
8046a55e c3 ret

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiSystemFatalException+e

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 403d35e2

STACK_COMMAND: kb

BUCKET_ID: 0x7f_a_nt!KiSystemFatalException+e

Followup: MachineOwner
---------


The server is a dual proc with hyperthreading. From my research I cannot verify if its a hardware (CPU) or driver error.

Any additional information you can provide would be greatly appreciated!

Thanks

 

A couple of possibilities... Driver, or memory issue?

First I would check for updated drivers for your soundcard (or onboard sound) and graphics card. I also read that someone was having a similar problem till they updated their monitor driver. So if using a generic monitor driver, try selecting your monitor from the list, then go to windows update and see if it detects an updated monitor driver to install.

Secondly, it may be a memory problem?? If you have two sticks of memory, swap out one stick at a time and see if this stops the reboots.