Crash BXVBDX.SYS with W2K3 SP2

Hello !
(sorry for my english... I'm french )
I have an error when I started my server Dell PowerEdge 2950 with network card Broadcom .

Can you help me to fix it ? Thanks for your help...

The result of debugging is :
-----------------------------------
[FONT= "Courier New"]Loading Dump File [C:\WINDOWS\Minidump\Mini040708-65.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: C:\WINDOWS\Symbols
Executable search path is:
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (4 procs) Free x86 compatible
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8
Debug session time: Mon Apr 7 12:11:24.437 2008 (GMT+2)
System Uptime: 0 days 0:00:29.453
Unable to load image \WINDOWS\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
Loading Kernel Symbols
..............................................................................................................
Loading User Symbols
Loading unloaded module list
.....
Unable to load image bxvbdx.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for bxvbdx.sys
*** ERROR: Module load completed but symbols could not be loaded for bxvbdx.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck D1, {0, d0000002, 0, f783d472}

*** WARNING: Unable to verify timestamp for bxnd52x.sys
*** ERROR: Module load completed but symbols could not be loaded for bxnd52x.sys
*** WARNING: Unable to verify timestamp for NDIS.sys
Unable to load image \SystemRoot\system32\DRIVERS\baspxp32.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for baspxp32.sys
*** ERROR: Module load completed but symbols could not be loaded for baspxp32.sys
*** WARNING: Unable to verify timestamp for tcpip.sys
Unable to load image \SystemRoot\system32\DRIVERS\netbt.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for netbt.sys
*** WARNING: Unable to verify timestamp for ati2mtag.sys


Probably caused by : bxvbdx.sys ( bxvbdx+e472 )

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

2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f783d472, address which referenced memory

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




READ_ADDRESS: 00000000

CURRENT_IRQL: 2

FAULTING_IP:
bxvbdx+e472
f783d472 ?? ???

CUSTOMER_CRASH_COUNT: 65

DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP

BUGCHECK_STR: 0xD1

PROCESS_NAME: svchost.exe

LAST_CONTROL_TRANSFER: from f783d472 to 8088c963

STACK_TEXT:
f78ba5b4 f783d472 badb0d00 00000000 80a5a44b nt!ExFreePoolWithTag+0x62d
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ba62c f783a4e4 89a2b914 888c0da8 888c0db4 bxvbdx+0xe472
f78ba650 f75ee099 89184000 888c0d90 888c0da8 bxvbdx+0xb4e4
f78ba680 f75ee14e 89775148 f78ba698 891fb030 bxnd52x+0x7099
f78ba69c f7a1ac8a 89187338 02775148 00000000 bxnd52x+0x714e
f78ba6b0 ba4562dd 89826f10 89775148 888be288 NDIS!NdisInitiateOffload+0x24
f78ba6f0 f7a1ac8a 891fb030 89775148 88a07648 baspxp32+0x62dd
f78ba704 b8fe2429 8971c008 89775148 888be240 NDIS!NdisInitiateOffload+0x24
f78ba74c b8fe5c38 00000000 00000000 87be4e4c tcpip!ArpInitiateOffload+0x55d
f78ba788 b8fed6cc 00000000 89c9c7e8 87bfcd20 tcpip!IpInitiateOffload+0x3cb
f78ba7a8 b8feadc6 888be2cc 00000002 00000000 tcpip!TcpInitiateOffload+0x20e
f78ba7cc b8fd67d8 87bfcd20 00000002 87be6cd0 tcpip!DoStateBasedProcessing+0x88
f78ba7e0 b8fbd5fb 87be6cd0 00000048 00000002 tcpip!OlmNotifyRequest+0x32
f78ba814 b8fbbedd 00000001 00000000 00000048 tcpip!TdiSend+0x1e2
f78ba850 b8fb6d13 87be9d3c 029f224c 888aa7a8 tcpip!TCPSendData+0xbf
f78ba86c 8081df65 88b73288 889f21b8 00000048 tcpip!TCPDispatchInternalDeviceControl+0x19a
f78ba880 b8f4fbae 888e45c0 888aa7a8 00000000 nt!IoCsqInitialize+0x31
f78ba89c b8f5044f 889f21b8 00000000 00000048 netbt!TdiSend+0x102
f78ba8ec b8f51397 888aa788 00000000 00000000 netbt!SessionStartupContinue+0x2f1
f78ba908 8081e103 88c0c360 888eb770 89b70730 netbt!TcpConnectComplete+0x43
f78ba938 b8fb6b41 87c1beb8 87be6cd0 00000002 nt!IoCsqRemoveIrp+0x3f
f78ba950 b8fba358 888eb770 00000000 00000000 tcpip!TCPDataRequestComplete+0xa6
f78ba964 b8fbc98a 888eb770 00000000 00000000 tcpip!TCPRequestComplete+0x12
f78ba984 b8fbc862 87be6cd0 f78baae8 00000000 tcpip!CompleteConnReq+0x87
f78baa50 b8fb8236 88b6fda0 487c3e0a 347c3e0a tcpip!TCPRcv+0xa09
f78baab0 b8fb645e 00000020 88b6fda0 b8fbb9d2 tcpip!DeliverToUser+0x189
f78bab40 b8fb6684 88b6fda0 890cccac 0000001a tcpip!IPRcvPacket+0x686
f78bab80 b8fb6517 00000000 891f9eb0 890ccc8a tcpip!ARPRcvIndicationNew+0x167
f78babd8 f7a3f208 88a07648 891f9eb0 f78bac50 tcpip!ARPRcvPacket+0x2f9
f78bac2c ba456c83 8978b858 f78bac4c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x385
f78bad50 ba456e55 00000001 891fb16c 00000000 baspxp32+0x6c83
f78bad78 f7a3f405 8922bed0 f78baeec 89187338 baspxp32+0x6e55
f78badc8 f75ef214 89882ab0 f78bade0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x6a0
f78baeb8 f75ef27d 89187570 00000000 89a2b010 bxnd52x+0x8214
f78baed0 f7833537 89187338 f78baeec 00000000 bxnd52x+0x827d
f78baef8 f783374b 89a2b010 00000000 f78baf50 bxvbdx+0x4537
f78baf24 f7837ca3 89a2b010 89184000 f78baf44 bxvbdx+0x474b
f78baf60 f7837eba 00000000 118e30b2 89a2b010 bxvbdx+0x8ca3
f78baf80 f7837fdf f772fa40 89a2d540 f7837f4a bxvbdx+0x8eba
f78baf9c 808320f0 89a2d540 89a2b010 00000000 bxvbdx+0x8fdf
f78baff4 8088db27 b8cffb20 00000000 00000000 nt!MiUnmapViewOfSection+0x24
f78bb004 00000000 00000000 00000000 00000000 nt!ExAllocatePoolWithTag+0xff9


STACK_COMMAND: kb

FOLLOWUP_IP:
bxvbdx+e472
f783d472 ?? ???

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: bxvbdx+e472

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: bxvbdx

IMAGE_NAME: bxvbdx.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 46bcfed1

FAILURE_BUCKET_ID: 0xD1_bxvbdx+e472

BUCKET_ID: 0xD1_bxvbdx+e472

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

2: kd> lmvm bxvbdx
start end module name
f782f000 f7897000 bxvbdx T (no symbols)
Loaded symbol image file: bxvbdx.sys
Image path: bxvbdx.sys
Image name: bxvbdx.sys
Timestamp: Sat Aug 11 02:12:01 2007 (46BCFED1)
CheckSum: 0006E389
ImageSize: 00068000
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0[/FONT]

 

One mimidump is insufficient to confirm the root cause. If you have 3 to 5 minidumps and all of them are crashed at the same module. The failing module is the culprit. If the minidumps are crashed with different bugcheck code, attach the debug report here. In the meantime bxvbdx.sys maybe the culprit but it is not confirmed.

 

You can found here another minidump, but for me, it's the same... just with another process_name.

I've found a new release of driver NetXtreme II on the Broadcom Site. Do you think it's a possible solution ?

Patrice

[FONT= "Courier New"]*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
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: 00000000, memory referenced
Arg2: d0000002, IRQL
Arg3: 00000000, value 0 = read operation, 1 = write operation
Arg4: f783d472, address which referenced memory
Debugging Details:
------------------
READ_ADDRESS: 00000000
CURRENT_IRQL: 2
FAULTING_IP:
bxvbdx+e472
f783d472 ?? ???
CUSTOMER_CRASH_COUNT: 64
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0xD1
PROCESS_NAME: dsm_om_shrsvc32
LAST_CONTROL_TRANSFER: from f783d472 to 8088c963
STACK_TEXT:
f78ba5b4 f783d472 badb0d00 00000000 80a5a44b nt!ExFreePoolWithTag+0x62d
WARNING: Stack unwind information not available. Following frames may be wrong.
f78ba62c f783a4e4 89a2b914 87c22d98 87c22da4 bxvbdx+0xe472
f78ba650 f75be099 89183000 87c22d80 87c22d98 bxvbdx+0xb4e4
f78ba680 f75be14e 88900c50 f78ba698 891fd030 bxnd52x+0x7099
f78ba69c f7a1ac8a 89186658 02900c50 00000000 bxnd52x+0x714e
f78ba6b0 ba4562dd 89721bf8 88900c50 888fadb8 NDIS!NdisInitiateOffload+0x24
f78ba6f0 f7a1ac8a 891fd030 88900c50 88bb03a8 baspxp32+0x62dd
f78ba704 b8fe2429 88c13830 88900c50 888fad70 NDIS!NdisInitiateOffload+0x24
f78ba74c b8fe5c38 00000000 00000000 888fb29c tcpip!ArpInitiateOffload+0x55d
f78ba788 b8fed6cc 00000000 89b72720 87c1bd18 tcpip!IpInitiateOffload+0x3cb
f78ba7a8 b8feadc6 888fadfc 00000002 00000000 tcpip!TcpInitiateOffload+0x20e
f78ba7cc b8fd67d8 87c1bd18 00000002 87bf9e40 tcpip!DoStateBasedProcessing+0x88
f78ba7e0 b8fbd5fb 87bf9e40 00000048 00000002 tcpip!OlmNotifyRequest+0x32
f78ba814 b8fbbedd 00000001 00000000 00000048 tcpip!TdiSend+0x1e2
f78ba850 b8fb6d13 87c01eb4 0276624c 89776240 tcpip!TCPSendData+0xbf
f78ba86c 8081df65 88b766a0 897661b8 00000048 tcpip!TCPDispatchInternalDeviceControl+0x19a
f78ba880 b8f4fbae 8888c4f0 89776240 00000000 nt!IoCsqInitialize+0x31
f78ba89c b8f5044f 897661b8 00000000 00000048 netbt!TdiSend+0x102
f78ba8ec b8f51397 89776220 00000000 00000000 netbt!SessionStartupContinue+0x2f1
f78ba908 8081e103 88a0f2d0 89b67798 898e5cd0 netbt!TcpConnectComplete+0x43
f78ba938 b8fb6b41 89187108 87bf9e40 00000002 nt!IoCsqRemoveIrp+0x3f
f78ba950 b8fba358 89b67798 00000000 00000000 tcpip!TCPDataRequestComplete+0xa6
f78ba964 b8fbc98a 89b67798 00000000 00000000 tcpip!TCPRequestComplete+0x12
f78ba984 b8fbc862 87bf9e40 f78baae8 00000000 tcpip!CompleteConnReq+0x87
f78baa50 b8fb8236 88a192a0 487c3e0a 347c3e0a tcpip!TCPRcv+0xa09
f78baab0 b8fb645e 00000020 88a192a0 b8fbb9d2 tcpip!DeliverToUser+0x189
f78bab40 b8fb6684 88a192a0 890cbd6c 0000001a tcpip!IPRcvPacket+0x686
f78bab80 b8fb6517 00000000 891fbdd8 890cbd4a tcpip!ARPRcvIndicationNew+0x167
f78babd8 f7a3f208 88bb03a8 891fbdd8 f78bac50 tcpip!ARPRcvPacket+0x2f9
f78bac2c ba456c83 8973f130 f78bac4c 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x385
f78bad50 ba456e55 00000001 891fd16c 00000000 baspxp32+0x6c83
f78bad78 f7a3f405 8922ded0 f78baeec 89186658 baspxp32+0x6e55
f78badc8 f75bf214 898aa130 f78bade0 00000001 NDIS!ethFilterDprIndicateReceivePacket+0x6a0
f78baeb8 f75bf27d 89186890 00000000 89a2b010 bxnd52x+0x8214
f78baed0 f7833537 89186658 f78baeec 00000000 bxnd52x+0x827d
f78baef8 f783374b 89a2b010 00000000 f78baf50 bxvbdx+0x4537
f78baf24 f7837ca3 89a2b010 89183000 f78baf44 bxvbdx+0x474b
f78baf60 f7837eba 00000000 11490c80 89a2b010 bxvbdx+0x8ca3
f78baf80 f7837fdf f772fa40 89a2d540 f7837f4a bxvbdx+0x8eba
f78baf9c 808320f0 89a2d540 89a2b010 00000000 bxvbdx+0x8fdf
f78baff4 8088db27 b8b7bd10 00000000 00000000 nt!MiUnmapViewOfSection+0x24
f78bb004 00000000 00000000 00000000 00000000 nt!ExAllocatePoolWithTag+0xff9
STACK_COMMAND: kb
FOLLOWUP_IP:
bxvbdx+e472
f783d472 ?? ???
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: bxvbdx+e472
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: bxvbdx
IMAGE_NAME: bxvbdx.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 46bcfed1
FAILURE_BUCKET_ID: 0xD1_bxvbdx+e472
BUCKET_ID: 0xD1_bxvbdx+e472
Followup: MachineOwner[/FONT]

 

The 2nd dump is exactly same as the 1st dump. Most likely the culprit is bxvbdx.sys (Broadcom NetXtreme driver). Upgrade or fallback the device driver Broadcom may resolve the blue screen problem.

 

Ok I try to upgrade the package Broadcom (I saw a new release in her site).

Thanks for your information

Patrice

sorry for the red text