Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

BUCKET_ID: WRONG_SYMBOLS - bxnd52x.sys


  • Please log in to reply

#1
Mohan Doss

Mohan Doss

    New Member

  • Member
  • Pip
  • 2 posts
Hi,

My Server Windows 2003 Enterprices SP2 is keep rebooting unexpectdely with
BugCheck 100000D1, {0, d0000002, 0, b9fada6c}

I have updated Firmware and System BIOS upto date even server rebooting once ina week there is no system error message. I have find below information from mini dump but could not find the fix.
NIC Driver Version: 5.2.17.0

Please help me to resolve the problem.

1: kd> !analyze -v
*************************************************************************
* Bugcheck alysis *
* ***************************************************************************

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: b9fada6c, address which referenced memory

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

***** Kernel symbols are WRONG. Please fix symbols to do analysis.

*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*************************************************************************
*** Your debugger is not using the correct symbols ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***
*************************************************************************
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_KPRCB ***

*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************
* Symbols can not be loaded because symbol path is not initialized. *

* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
*********************************************************************

MODULE_NAME: bxnd52x

FAULTING_MODULE: 80800000 nt

DEBUG_FLR_IMAGE_TIMESTAMP: 48a27c40

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPoolCodeStart
unable to get nt!MmPoolCodeEnd
00000000

CURRENT_IRQL: d0000002

FAULTING_IP:
tcpip+19a6c
b9fada6c 8b36 mov esi,dword ptr [esi]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WRONG_SYMBOLS

BUGCHECK_STR: 0xD1

LAST_CONTROL_TRANSFER: from b9faa632 to b9fada6c

STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
f78aaba0 b9faa632 891504a8 89150440 00000000 tcpip+0x19a6c
f78aabd8 b9fa94e6 89b7e168 00254248 00000000 tcpip+0x16632
f78aabfc f71501f9 891a9380 88254248 00000000 tcpip+0x154e6
f78aac20 ba660124 8a7959d8 88254248 00000000 NDIS+0x201f9
f78aac4c f7209921 00000000 f78aac5c 00000000 bxnd52x+0x9124
f78aac70 f7209956 89f26010 89f28320 89a3c000 bxvbdx+0x5921
f78aac90 f720eadc 89f26010 89f28320 f78aaca8 bxvbdx+0x5956
f78aacb8 f720eb9d 6cc8d610 89f26010 00000205 bxvbdx+0xaadc
f78aacdc f720ef3d f7727a40 89f27a4c f720ee98 bxvbdx+0xab9d
f78aacf8 8083d99a 89f27a4c 89f26010 00000001 bxvbdx+0xaf3d
f78aad50 80839b3f 00000000 0000000e 00000000 nt+0x3d99a
f78aad54 00000000 0000000e 00000000 00000000 nt+0x39b3f


STACK_COMMAND: kb

FOLLOWUP_IP:
bxnd52x+9124
ba660124 ?? ???

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: bxnd52x+9124

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: bxnd52x.sys

BUCKET_ID: WRONG_SYMBOLS

Followup: MachineOwner
---------
  • 0

Advertisements


#2
happyrock

happyrock

    Tech Moderator

  • Retired Staff
  • 9,285 posts
try reinstalling the Broadcom NetXtreme II GigE driver...
  • 0

#3
Mohan Doss

Mohan Doss

    New Member

  • Topic Starter
  • Member
  • Pip
  • 2 posts
I have updated the NIC driver, Let me try to reinstall !!!

Thanks
mohan
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP