OT: Proliant reboots during replication

Configuration: Proliant ML350 , Win2000 Server, SQL Server 2000
internal PCI ISDN adapter ASUS P-IN-100(W,D)
This server has number of merge replications (as publisher) and does
up to 15 replications every night. From time to time (once a week or
5-6 days, but always during replication) the machine reboots.
In Compaq Integrated Management Log Viewer we have ervery time :
-PCI Bus Error (Slot 0, Bus 0, Device 15, Function 0)
-ASR Detected by System ROM
-POST Error: A Critical Error occured prior to this power-up
and in System Log:
Event Type:Error
Event Source:cpqasm
Event Category:None
Event ID:4196
Date:25.3.2004
Time:23:05:20
User:N/A
Computer:xxxxxxxxx
Description:
The system encountered a Non-Maskable Interrupt (NMI) prior to this
boot. The NMI source was: PCI bus error, slot 0.
Computer Management reported that (Slot 0, Bus 0, Device 15, Function
0) is PCI Standard ISA Bridge.
During a day there is a lot of traffic using same ISDN adapter (lot of
FTP-s) without any problem. It seems that only replication is problem.
Although I know this is most probably ISDN Adapter/drivers problem
I'm trying in this group. Maybe somebody has some hint ?
Happy greetings,
Pagus
PS: Today we had same problem with same hardware configuration at
other location, this time Proliant + Win2003 SBS as publisher.
Same problem here... Proliant ML350 G3, reboots automatically at random times...
If we test our serial port (nothing connected) with the HP-tool CPQdiagnostics (SP27119.exe) the system crashes. When we connect a mouse to that particular serial port, we got a software-error of CPQdiagnostics.
All other hardwaretests look fine.
Here we attach some minidump-debuganalyses. Can you also test these things ? Maybe we have the same problem ?
Greetings
Dieter
Microsoft (R) Windows Debugger Version 6.2.0013.1
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Program Files\Debugging Tools for Windows\Mini040704-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_rtm.030324-2048
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Wed Apr 07 08:32:16 2004
System Uptime: 0 days 0:02:32.265
Loading Kernel Symbols
...................................... ...................................... .........
Loading unloaded module list
...
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 80527564, 8056c090, 0}
Probably caused by : ntkrnlmp.exe ( nt!KiDispatchException+19e )
Followup: MachineOwner
0: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 80527564, The address that the exception occurred at
Arg3: 8056c090, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - De instructie op 0x%08lx verwijst naar geheugen op 0x%08lx. De lees- of schrijfbewerking ("%s") op het geheugen is mislukt.
FAULTING_IP:
nt!KiDispatchException+19e
80527564 e92e65feff jmp nt!KiDispatchException+0x19e (8050da97)
TRAP_FRAME: 8056c090 -- (.trap ffffffff8056c090)
ESP EDITED! New esp=8056c3f0
ErrCode = 00000000
eax=8056c6cc ebx=8056c804 ecx=81987020 edx=00010000 esi=8056c7b0 edi=00000000
eip=80527564 esp=8056c104 ebp=8056c794 iopl=0 nv up ei ng nz na pe cy
cs=0000 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000283
nt!KiDispatchException+0x19e:
80527564 e92e65feff jmp nt!KiDispatchException+0x19e (8050da97)
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 804e087a to 80527564
STACK_TEXT:
8056c794 804e087a 8056c7b0 00000000 8056c804 nt!KiDispatchException+0x19e
8056c7fc 804e07fa 00000000 00000000 00000023 nt!CommonDispatchException+0x4a
8056c804 00000000 00000023 00000023 010cfee4 nt!KiExceptionExit+0x16a
FOLLOWUP_IP:
nt!KiDispatchException+19e
80527564 e92e65feff jmp nt!KiDispatchException+0x19e (8050da97)
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!KiDispatchException+19e
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3e8015c6
STACK_COMMAND: .trap ffffffff8056c090 ; kb
BUCKET_ID: 0x8E_nt!KiDispatchException+19e
Followup: MachineOwner
another one :
Loading Dump File [C:\Program Files\Debugging Tools for Windows\Mini040604-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows Server 2003 Kernel Version 3790 MP (4 procs) Free x86 compatible
Product: Server, suite: TerminalServer SingleUserTS
Built by: 3790.srv03_rtm.030324-2048
Kernel base = 0x804de000 PsLoadedModuleList = 0x8057b6a8
Debug session time: Tue Apr 06 09:33:17 2004
System Uptime: 0 days 0:07:34.015
Loading Kernel Symbols
...................................... ...................................... .......
Loading unloaded module list
...
Loading User Symbols
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {80000003, 804df1c0, f7752ba4, 0}
Probably caused by : ntkrnlmp.exe ( nt!RtlpBreakWithStatusInstruction+0 )
Followup: MachineOwner
1: kd> !analyze -v
************************************************** *****************************
* *
* Bugcheck Analysis *
* *
************************************************** *****************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
An exception code of 0x80000002 (STATUS_DATATYPE_MISALIGNMENT) indicates
that an unaligned data reference was encountered. The trap frame will
supply additional information.
Arguments:
Arg1: 80000003, The exception code that was not handled
Arg2: 804df1c0, The address that the exception occurred at
Arg3: f7752ba4, Trap Frame
Arg4: 00000000
Debugging Details:
EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Een of meer argumenten zijn ongeldig
FAULTING_IP:
nt!RtlpBreakWithStatusInstruction+0
804df1c0 cc int 3
TRAP_FRAME: f7752ba4 -- (.trap fffffffff7752ba4)
ErrCode = 00000000
eax=00000004 ebx=00000000 ecx=805429fd edx=00000000 esi=00000000 edi=80000003
eip=804df1c1 esp=f7752c18 ebp=f7752c60 iopl=0 nv up di pl zr na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000046
nt!RtlpBreakWithStatusInstruction+0x1:
804df1c1 c20400 ret 0x4
Resetting default scope
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x8E
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 80542289 to 804df1c1
STACK_TEXT:
f7752c14 80542289 00000004 80000003 00000000 nt!RtlpBreakWithStatusInstruction+0x1
f7752c60 805434e2 00000004 00000000 f77533c0 nt!KiBugCheckDebugBreak+0x19
f7752fc8 805435b9 0000008e 80000003 804df1c0 nt!KeBugCheck2+0x882
f7752fe8 80527624 0000008e 80000003 804df1c0 nt!KeBugCheckEx+0x19
f77533a4 804e087a f77533c0 00000000 f7753414 nt!KiDispatchException+0x2f5
f775340c 804e0fe1 00000000 00000000 00000000 nt!CommonDispatchException+0x4a
f775340c 804df1c1 00000000 00000000 00000000 nt!KiTrap03+0x9d
f7753484 80542289 00000004 80000003 00000000 nt!RtlpBreakWithStatusInstruction+0x1
f77534d0 805434e2 00000004 00000000 f7753c30 nt!KiBugCheckDebugBreak+0x19
f7753838 805435b9 0000008e 80000003 804df1c0 nt!KeBugCheck2+0x882
f7753858 80527624 0000008e 80000003 804df1c0 nt!KeBugCheckEx+0x19
f7753c14 804e087a f7753c30 00000000 f7753c84 nt!KiDispatchException+0x2f5
f7753c7c 804e0fe1 00000000 00000000 00000000 nt!CommonDispatchException+0x4a
f7753c7c 804df1c1 00000000 00000000 00000000 nt!KiTrap03+0x9d
f7753cf4 80542289 00000004 80000003 00000000 nt!RtlpBreakWithStatusInstruction+0x1
f7753d40 805434e2 00000004 00000000 f77544a0 nt!KiBugCheckDebugBreak+0x19
f77540a8 805435b9 0000008e 80000003 804df1c0 nt!KeBugCheck2+0x882
f77540c8 80527624 0000008e 80000003 804df1c0 nt!KeBugCheckEx+0x19
f7754484 804e087a f77544a0 00000000 f77544f4 nt!KiDispatchException+0x2f5
f77544ec 804e0fe1 00000000 00000000 00000000 nt!CommonDispatchException+0x4a
f77544ec 804df1c1 00000000 00000000 00000000 nt!KiTrap03+0x9d
f7754564 80542289 00000004 80000003 00000000 nt!RtlpBreakWithStatusInstruction+0x1
f77545b0 805434e2 00000004 00000000 f7754d10 nt!KiBugCheckDebugBreak+0x19
f7754918 805435b9 0000008e 80000003 804df1c0 nt!KeBugCheck2+0x882
f7754938 80527624 0000008e 80000003 804df1c0 nt!KeBugCheckEx+0x19
f7754cf4 804e087a f7754d10 00000000 f7754d64 nt!KiDispatchException+0x2f5
f7754d5c 804e0fe1 00000000 00000000 00000020 nt!CommonDispatchException+0x4a
f7754d5c 804df1c1 00000000 00000000 00000020 nt!KiTrap03+0x9d
f7754dd4 80542289 00000004 00000000 00000000 nt!RtlpBreakWithStatusInstruction+0x1
f7754e20 805434e2 00000004 a2000000 84010400 nt!KiBugCheckDebugBreak+0x19
f7755188 805435b9 0000009c 00000000 f77551d0 nt!KeBugCheck2+0x882
f77551a8 8074cfab 0000009c 00000000 f77551d0 nt!KeBugCheckEx+0x19
f77552d4 8074584f f774fef0 00000000 00000000 hal!HalpMcaExceptionHandler+0xc9
FOLLOWUP_IP:
nt!RtlpBreakWithStatusInstruction+0
804df1c0 cc int 3
FOLLOWUP_NAME: MachineOwner
SYMBOL_NAME: nt!RtlpBreakWithStatusInstruction+0
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 3e8015c6
STACK_COMMAND: .trap fffffffff7752ba4 ; kb
BUCKET_ID: 0x8E_nt!RtlpBreakWithStatusInstruction+0
Followup: MachineOwner