Win2003 server reboot issue

Hi..

We are running a HP Proliant ML370 G3 server with Veritas Netbackup client32. It seems that the server reboots/crashes randomly with the following errorcode:
---------------------------------------------------------------------
Event Type: Error
Event Source: System Error
Event Category: (102)
Event ID: 1003
Date: 2004-11-24
Time: 15:59:19
User: N/A
Computer: LEO
Description:
Error code 0000000a, parameter1 00000016, parameter2 0000001b, parameter3 00000000, parameter4 804f3f7c.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 53 79 73 74 65 6d 20 45 System E
0008: 72 72 6f 72 20 20 45 72 rror Er
0010: 72 6f 72 20 63 6f 64 65 ror code
0018: 20 30 30 30 30 30 30 30 0000000
0020: 61 20 20 50 61 72 61 6d a Param
0028: 65 74 65 72 73 20 30 30 eters 00
0030: 30 30 30 30 31 36 2c 20 000016,
0038: 30 30 30 30 30 30 31 62 0000001b
0040: 2c 20 30 30 30 30 30 30 , 000000
0048: 30 30 2c 20 38 30 34 66 00, 804f
0050: 33 66 37 63 3f7c
--------------------------------------------------------

The Microsoft Online Crash Analysis claims it has to do with Veritas software but these crashes seems to occur even if the client is stopped so we think there might be another problem - maybe hardware. Any suggestions??

 

Welcome to the BBS bns.

I guess you visited the support page to look at software firmware updates?
http://h18004.www1.hp.com/support/files/server/us/locate/69_4307.html

Could be hardware, but maybe easier to try and rule out software/firmware issues first.

I guess it is set to automatically restart in system properties, startup and recovery? (sorry I'm not in front of my W2K3 at the mo.) Might be worth unchecking this box so you can read the stop message (BSOD) before it reboots, if you can afford the down time?

 

The server is updated with the newest patches, both firmware and drivers.
When the errors started the server just hang, unreachable, power off/on was the only solution. When using ASR an automatic reboot happened. After changing system board and Raid-controller (by HP) the server seemed to work, but started to misbehave after a week again. The difference now is that on this error I get this automatic analysis from Microsoft and I think I have to check it up before demanding a replacement of memeory and/or cpu.

According to HP there are some Pentium Xeon processors that have errors that will result in a system "hang/crash" but their latest firmware should include a workaround to this error.