Server Reboots itself with Bugchck

  • Thread starter Thread starter BJ
  • Start date Start date
B

BJ

I've got a server that has begun to reboot itself. It's
very random and has started to occur more and more. The
memory dump points to the ethernet card. We've replaced
twice and updated drivers no luck. Below is a copy of
the last memory dump. Any suggestions would be helpful.

Probably caused by : el90Xbc5.SYS ( el90Xbc5+2da0 )
DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pagable (or completely
invalid) address at an
interrupt request level (IRQL) that is too high. This is
usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: 00000019, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write
operation
Arg4: f770ada0, address which referenced memory

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

WRITE_ADDRESS: 00000019

CURRENT_IRQL: 2

FAULTING_IP:
el90Xbc5+2da0
f770ada0 895018 mov [eax+0x18],edx

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

TRAP_FRAME: 804712c0 -- (.trap ffffffff804712c0)
ErrCode = 00000002
eax=00000001 ebx=00000000 ecx=83f7a274 edx=83f73f48
esi=83f7a008 edi=83f72200
eip=f770ada0 esp=80471334 ebp=80471344 iopl=0 nv
up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030
gs=0000 efl=00010286
el90Xbc5+2da0:
f770ada0 895018 mov [eax+0x18],edx
ds:0023:00000019=????????
Resetting default context

LAST_CONTROL_TRANSFER: from f770a95c to f770ada0

STACK_TEXT:
WARNING: Stack unwind information not available.
Following frames may be wrong.
80471344 f770a95c 83f7a008 83f7a280 804022a0
el90Xbc5+0x2da0
0000000e 00000000 00000000 00000000 00000000
el90Xbc5+0x295c

FOLLOWUP_IP:
el90Xbc5+2da0
f770ada0 895018 mov [eax+0x18],edx

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: el90Xbc5+2da0

MODULE_NAME: el90Xbc5

IMAGE_NAME: el90Xbc5.SYS

DEBUG_FLR_IMAGE_TIMESTAMP: 3d59dc28

STACK_COMMAND: .trap ffffffff804712c0 ; kb

BUCKET_ID: 0xD1_W_el90Xbc5+2da0

Followup: MachineOwner
---------
 
I've had problems with 3Com controllers plenty. If the NIC is sharing an
IRQ with another device then disable that other device and let the
server run a while to see if that's it. Also, my 3Com NIC was sharing
with my video so I ditched it altogether and just installed an Intel
card and that solved my problem.

Best of Luck...
 
Back
Top