ProLiant Servers - Netservers
1751967 Members
4608 Online
108783 Solutions
New Discussion юеВ

Re: Proliant DL580 spontaneous reboot problem

 
Jon S. Thompson
New Member

Proliant DL580 spontaneous reboot problem

We have a ProLiant DL580 running MS Windows 2000 Advanced Server SP4 with clustering services that 4 times over the last 3 weeks has rebooted itself in the middle of the day. The Event logs are not reporting any associated errors at all, however, Insight Manager has recorded Blue Screen Trap BugCheck Stop errors for each occurrence.
1.) Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x4D4F433A, 0x00000002, 0x00000000, 0xBFD5A953))
2.) Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x0000001F, 0x00000002, 0x00000000, 0xBF709CE4))
3.) Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x000000A0, 0x00000002, 0x00000000, 0xF62309B0))
4.) Blue Screen Trap (BugCheck, STOP: 0x000000D1 (0x3D3D3D3D, 0x00000002, 0x00000000, 0xF6230AB1))

We can find no other errors or failures. I have attached a text file with the essential O.S. and hardware configuration for this server.

Thanks in advance for any direction you may provide...
2 REPLIES 2
sandeep_raman
Honored Contributor

Re: Proliant DL580 spontaneous reboot problem

Hello Jon,

Before suspecting a hardware fault,if its ok to try patching the server.

1.System ROM
http://h18023.www1.hp.com/support/files/server/us/download/20505.html

2.PSP
http://h18023.www1.hp.com/support/files/server/us/download/24183.html

3.All MS patches(Windows update i suppose)

Whats the array controller model and its firmware rev?
Any external storage box connected?

SRH
Terrence Healy
New Member

Re: Proliant DL580 spontaneous reboot problem

I had a the same problem. I was running a DL360 G3 with a Quad Controller Card.
I had configured my Broadcom Nic to do Protocol Tagging or Similiar IP"s in different Vlans. THe Machine would spontaneously reboot with that error. I fixed it by Disabling the on board nics and used an Intel 1000. I went to HP with the problem and they tried several things and could not fix it, this has been working ever since.