Win 2003 enterprise crashing -

I'm experiencing random crashes of my windows 2k3 server. Its hapening about once a week at night but not on a perfect schedule. I got a memory dump and report posted below. The server is up to date and windows is patched but the crash keeps occuring.

Any help deciphering the dump file would be much appriciated.

Thanks in advance

Here are the server specs
Dell 1750
2g ecc ram
dual xeon processors
raid 5

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (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: 01190018, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000001, value 0 = read operation, 1 = write operation
Arg4: 7c82fecf, address which referenced memory

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


OVERLAPPED_MODULE: Address regions for 'b57xp32' and 'b57xp32.sys' overlap

WRITE_ADDRESS: 01190018

CURRENT_IRQL: 2

FAULTING_IP:
ntdll!RtlAllocateHeap+c82
7c82fecf 66894118 mov [ecx+0x18],ax

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from 7c82fecf to 80837ed5

STACK_TEXT:
b72f5d64 7c82fecf badb0d00 7c82ed54 00000000 nt!KiTrap0E+0x2a7
0104ef94 77e6bbe4 00080000 00140000 002005e4 ntdll!RtlAllocateHeap+0xc82
0104efe0 76cf2955 00000000 002005e4 0104f024 kernel32!LocalAlloc+0x58
0104eff0 76cf2ab7 002005e4 000a5888 0008d0d0 iphlpapi!GrabMemory+0x10
0104f024 76cf3052 00000000 76cf3d35 00000020 iphlpapi!GetAdapterOrderMap+0xcc
0104f278 76cf3241 00000000 00000000 76cf3d35 iphlpapi!GetAdapterList+0x46
0104f2b0 76cf3f70 0104f3c4 77e6b14b 76cf3d35 iphlpapi!GetAdapterInfo+0x29
0104f310 76cf3dcb 00000000 00000016 0104f360 iphlpapi!GetAdapterAddresses+0x17
0104f380 76cf3d9b 00000000 00000016 003467c8 iphlpapi!GetAdapterAddressesEx+0x26
0104f39c 76ed7072 00000000 00000016 00000000 iphlpapi!GetAdaptersAddresses+0x60
0104f3c8 76ed6e27 00000000 00000016 00000355 DNSAPI!IpHelp_GetAdaptersAddresses+0x5c
0104f454 766c3c3e 00000001 0104f8cc 0009eecc DNSAPI!NetInfo_Build+0x52
0104f47c 766c31db 0104f8cc 0104f8d0 766c17a2 dnsrslvr!GrabNetworkInfo+0xae
0104f488 766c17a2 0104f4ac 0104f8d4 0104fadc dnsrslvr!ResolverQuery+0xb
0104f8d0 77c70f3b 00000000 0009eecc 00000001 dnsrslvr!R_ResolverQuery+0xec
0104f8f8 77ce23f7 766c16be 0104fae0 00000005 RPCRT4!Invoke+0x30
0104fcf8 77ce26ed 00000000 00000000 000a2ecc RPCRT4!NdrStubCall2+0x299
0104fd14 77c709be 000a2ecc 0008b840 000a2ecc RPCRT4!NdrServerCall2+0x19
0104fd48 77c7093f 766c16b3 000a2ecc 0104fdec RPCRT4!DispatchToStubInCNoAvrf+0x38
0104fd9c 77c70865 00000007 00000000 766ca0a4 RPCRT4!RPC_INTERFACE:ispatchToStubWorker+0x117
0104fdc0 77c734b1 000a2ecc 00000000 766ca0a4 RPCRT4!RPC_INTERFACE:ispatchToStub+0xa3
0104fdfc 77c71bb3 000a2c60 0008b428 0009ee80 RPCRT4!LRPC_SCALL:ealWithRequestMessage+0x42c
0104fe20 77c75458 0008b460 0104fe38 000a2c60 RPCRT4!LRPC_ADDRESS:ealWithLRPCRequest+0x127
0104ff84 77c5778f 0104ffac 77c5f7dd 0008b428 RPCRT4!LRPC_ADDRESS::ReceiveLotsaCalls+0x430
0104ff8c 77c5f7dd 0008b428 00000000 00000000 RPCRT4!RecvLotsaCallsWrapper+0xd
0104ffac 77c5de88 00083ff8 0104ffec 77e66063 RPCRT4!BaseCachedThreadRoutine+0x9d
0104ffb8 77e66063 0008ac78 00000000 00000000 RPCRT4!ThreadStartRoutine+0x1b
0104ffec 00000000 77c5de6d 0008ac78 00000000 kernel32!BaseThreadStart+0x34


FOLLOWUP_IP:
nt!KiTrap0E+2a7
80837ed5 833d00ee8a8000 cmp dword ptr [nt!KiFreezeFlag (808aee00)],0x0

SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!KiTrap0E+2a7

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42435e60

STACK_COMMAND: kb

FAILURE_BUCKET_ID: 0xD1_W_nt!KiTrap0E+2a7

BUCKET_ID: 0xD1_W_nt!KiTrap0E+2a7

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

 

Cancel the help request.

I figured this one out on my own. Bad network drivers.

 

Thanks for the follow-up.